**** BEGIN LOGGING AT Fri Aug 06 02:59:58 2010
**** ENDING LOGGING AT Fri Aug 06 05:44:27 2010

**** BEGIN LOGGING AT Fri Aug 06 08:30:14 2010
**** ENDING LOGGING AT Fri Aug 06 08:30:21 2010

**** BEGIN LOGGING AT Fri Aug 06 08:32:14 2010
Aug 06 09:24:27 <lag> ogra: ping
Aug 06 09:33:27 <ogra> lag, i havent seen bug 605488 recently, but iirc it never showed up immediately
Aug 06 09:33:34 <ubot2> Launchpad bug 605488 in linux-ti-omap4 (Ubuntu Maverick) (and 1 other project) "BUG: scheduling while atomic: mmcqd/46/0x00000002 (affects: 1) (heat: 177)" [High,In progress] https://launchpad.net/bugs/605488
Aug 06 09:34:43 <cooloney> ogra, lag, me either
Aug 06 09:34:43 <lag> ogra: You ever seen this? http://paste.ubuntu.com/473947/
Aug 06 09:35:28 <lag> --^ On XM
Aug 06 09:35:30 <ogra> lag, yeah, could be
Aug 06 09:35:32 <cooloney> lag: i never saw that. could you try the latest upload.
Aug 06 09:35:40 <cooloney> oh, XM
Aug 06 09:35:48 <ogra> lag, that might be the memory bug in the XM
Aug 06 09:36:08 <ogra> lag, iirc rcn-ee has workaround patches for u-boot and the kernel somewhere
Aug 06 09:36:23 <ogra> until the final HW comes out
Aug 06 09:37:11 <ogra> i planned to pull the u-boot side of them into the next upload
Aug 06 09:38:00 <ogra> i dont exactly know how the memory bug manifests so i'm only guessing
Aug 06 09:39:12 <lag> cooloney: Do you have XM?
Aug 06 09:39:27 <lag> ogra: Do you know when the new HW comes out?
Aug 06 09:39:42 <ogra> lag, once all bugs are fixed :) no idea
Aug 06 09:40:00 <ogra> lag, #beagle might be of help
Aug 06 09:46:01 <cooloney> lag: no
Aug 06 09:46:22 <cooloney> lag: i just have beagle C3 and panda
Aug 06 11:42:41 <rcn-ee> hey lag, yeap those are on my list. ;)
Aug 06 11:42:57 <dcordes_> hi
Aug 06 11:54:46 <lag> rcn-ee: List?
Aug 06 11:57:49 <rcn-ee> basicly every error on xm's boot.. say does your XM have Micron 512?
Aug 06 11:59:00 <rcn-ee> Numonyx is the other possibility (working)..
Aug 06 12:05:20 <rcn-ee> lag, if your's is a 512 model, make sure your x-load has this patch http://cgit.openembedded.org/cgit.cgi/openembedded/commit/?id=b4c5ef7e0e06890b1369bfbd5c767820024adb21  (r15 from rcn-ee.net)
Aug 06 12:10:31 <lag> rcn-ee: What's the easiest way to find out?
Aug 06 12:11:34 <rcn-ee> there really isn't a good way.. no 'version' bumps, only way I know is the "rX" value angstrom auto addes to the file name..
Aug 06 12:12:20 <lag> And what's the easiest way to find out if I have a Micron or Numonyx?
Aug 06 12:12:48 <rcn-ee> considering Koen did the tweak 9 days ago... it might have been too quick specially with alpha 3..
Aug 06 12:13:19 <ogra_cmpc> right, our x-loader doesnt have it yet
Aug 06 12:13:33 <rcn-ee> I'm hoping Numonyx sticks their logo on the memory module.. Micron should have a weird "M", i know Elpida sticks their name on it..
Aug 06 12:14:07 <lag> Yeah, I have an M with a circle round it
Aug 06 12:14:15 <rcn-ee> is it 512?
Aug 06 12:14:30 <rcn-ee> looks back at pastbin..
Aug 06 12:14:38 <ogra_cmpc> are there non-512 ones ?
Aug 06 12:14:47 <lag> Hang on
Aug 06 12:14:50 <ogra_cmpc> it is
Aug 06 12:14:57 <ogra_cmpc> all the ones we have are 512
Aug 06 12:15:02 <ogra_cmpc> no need to check
Aug 06 12:15:19 <ogra_cmpc> though i'm surprised there are others
Aug 06 12:15:51 <rcn-ee> yeap yours is like mine...  the Micron memory has been dropped till Micron figures why they dont' work properly, some boards work fine, some fail weirdly..
Aug 06 12:16:27 <lag> So will that patch help me?
Aug 06 12:16:50 <ogra_cmpc> nope
Aug 06 12:17:11 <rcn-ee> it'll only help the production Numonyx ones coming out in a week or two..
Aug 06 12:17:36 <ogra_cmpc> i might have one (not near it atm)
Aug 06 12:17:58 <ogra_cmpc> lag, you still got the same board you always had ?
Aug 06 12:18:06 <ogra_cmpc> or was yours replaced too ?
Aug 06 12:18:27 <lag> Not yet
Aug 06 12:18:31 <rcn-ee> they were weird, according to gerald, some of the micron ones were fine (passed testing) but others had to be de-soldered and replaced, half yields..
Aug 06 12:18:55 <lag> I think I'm just going to have to leave it until I get new HW
Aug 06 12:19:26 <ogra_cmpc> well, the mmc error isnt memory induced, is it ?
Aug 06 12:20:00 <rcn-ee> myself, i'm just taking care of bugs i can.. cause as soon as i do an "aptitude update" or "update-initframs" my memory corrupts and takes the board down..
Aug 06 12:21:03 <rcn-ee> nope it isn't.. it seems config related, my 2.6.35+lots of patches custom config doesn't do it.. but my 2.6.35+xm does hit the error.. so more config testing this morning..
Aug 06 12:21:28 <ogra_cmpc> yeah, i saw the lots of bugmail :)
Aug 06 12:21:59 <rcn-ee> i'm kinda supprised about the Bx/Cx hitting it too now.. that one should be solid..
Aug 06 12:22:16 <ogra_cmpc> probably its two different bugs
Aug 06 12:22:23 * cwillu_at_work perks up
Aug 06 12:23:08 <ogra_cmpc> i at least have seen two issues i think, one is the -110 error, with the other one the card is found but readonly
Aug 06 12:23:14 <rcn-ee> specially from atleast cwillu_at_work ;).. he's tested every card known to man..
Aug 06 12:23:30 <cwillu_at_work> well, I've tested c3 and c4 :p
Aug 06 12:23:41 <cwillu_at_work> a dozen or so
Aug 06 12:23:52 <ogra_cmpc> using mainline kernels ?
Aug 06 12:23:58 <cwillu_at_work> no, rcn
Aug 06 12:24:03 <ogra_cmpc> right
Aug 06 12:24:06 <cwillu_at_work> close enough :p
Aug 06 12:25:10 <rcn-ee> yeah the 'ro' is to parts, the xm the wp bit.. the bx/cx is a weird regression over possibly a broken implementation.. http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ed8303fc111e58530e22bd29b0d7e08dced75999 (bisected..)
Aug 06 12:26:19 <rcn-ee> if you revert that commit.. the 'ro' issue doesn't happen with bx/cx... But if you play with the wp slot on any SD card it's not even detected, which leads to the gpio mux on the wp line doesn't work..
Aug 06 12:30:17 <rcn-ee> ogra_cmpc, here's my 'ro' bx testing 2.6.34/2.6.35 SD card wp handle testing: http://pastebin.com/Hx08KR5G
Aug 06 13:15:01 <lag> ogra: What's meant to be in boot.scr in the new daily image?
Aug 06 13:30:25 <ogra_cmpc> lag, the file is in cleartext stored in /boot/boot.script
Aug 06 13:30:30 <ogra_cmpc> in the rootfs
Aug 06 13:32:58 <lag> What's the one in boot all about?
Aug 06 13:33:30 <lag> I mean before first boot
Aug 06 13:54:20 <ogra> the one in /boot is the one the user uses to make changes
Aug 06 13:54:38 <ogra> like /boot/grub/menu.lst
Aug 06 14:00:48 <hrw> user usually tweak /etc/default/grub
Aug 06 14:00:57 <hrw> lcuk: hi here
Aug 06 14:01:02 <lcuk> heya :)
Aug 06 14:03:06 <lag> ogra: The one in boot is full of 0x150 zeros!
Aug 06 14:04:28 <ogra> lag, i'll take a look after the call
Aug 06 14:04:50 <lag> ogra: Can't you multitask ;)
Aug 06 14:05:06 <ogra> no, i'm no girl :P
Aug 06 14:05:35 <lag> Really? My mistake
Aug 06 14:05:41 <lag> Must be the hair :)
Aug 06 14:06:04 <ogra> i might slowly grow big enough to wear a bra though ... working from home changes you ;)
Aug 06 14:06:16 <lag> :)
Aug 06 14:10:24 <ogra> fun :)
Aug 06 14:10:26 <ogra> https://lists.ubuntu.com/archives/ubuntu-devel/2010-August/031073.html
Aug 06 14:10:29 <hrw> ogra: buy nice one ;d
Aug 06 14:10:56 <ogra> hrw, i'D never buy ugly underwear :)
Aug 06 14:29:47 <ogra> lag, my boot.scr looks proper (if i ignore the uboot header)
Aug 06 14:30:01 <lag> Okay
Aug 06 14:30:04 <lag> I'll re-dd
Aug 06 14:30:09 <lag> Probably a dd error
Aug 06 14:30:15 <ogra> http://paste.ubuntu.com/474071/
Aug 06 14:30:36 <lag> np
Aug 06 14:30:43 <ogra> (thats omap3)
Aug 06 14:30:50 <ogra> panda looks a bit different
Aug 06 14:32:11 <lag> cat your boot.scr from the new Panda image
Aug 06 14:32:25 <ogra> i need to dd that first
Aug 06 14:40:11 <ogra> lag, http://paste.ubuntu.com/474075/
Aug 06 14:40:39 <ogra> ndec, http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/alpha-3/
Aug 06 14:42:22 <ogra> asac, !
Aug 06 14:42:37 <asac> ogra: !
Aug 06 14:42:41 <asac> what can i do?
Aug 06 14:43:09 <ogra> see #arm
Aug 06 18:39:35 <rcn-ee_lpt> mpoirier, ping.. ;)
Aug 06 18:42:44 <mpoirier> rcn-ee_lpt: hello !
Aug 06 18:43:08 <rcn-ee_lpt> how's it going mpoirier any news in the deep depths of CONFIG_SOUND.. ;)
Aug 06 18:43:42 <mpoirier> I also get the same result: CONFIG_SND_OMAP_SOC seems to be the culprit !
Aug 06 18:44:00 <mpoirier> how it related to sdhc card is a mystery.
Aug 06 18:44:24 <mpoirier> I am currently rebuilding, just to make sure all the hours spend looking at config files havent' damaged my brain.
Aug 06 18:44:38 <zumbi> hrw|gone: do you mind to point me to your source packages?
Aug 06 18:44:44 <rcn-ee_lpt> no idea either, other then the possible SPI based sound card? or maybe we are getting hte same clocks?
Aug 06 18:45:31 <mpoirier> remember that CONFIG_CPU_IDLE|FREQ are also curing the issue/
Aug 06 18:45:44 <mpoirier> clock is definitively an option.
Aug 06 18:45:58 <mpoirier> sound is going to sleep, the clock is killed...
Aug 06 18:46:05 <mpoirier> and the sdhc card dies.
Aug 06 18:46:34 <rcn-ee_lpt> which if it just happens to be the same 'clock' on the xm.. (we get more clock sources with the dm37xx, some are still not being taken care off..)
Aug 06 18:46:39 <lool> zumbi: It's probably late for hrw
Aug 06 18:47:03 <mpoirier> do you know for sure that sdhc and sound are on the same clock ?
Aug 06 18:47:36 <zumbi> lool: where are their sources? :)
Aug 06 18:47:43 <zumbi> s,their,his
Aug 06 18:48:03 <rcn-ee_lpt> no, i'm actually assuming... based on what seems like a direct link..
Aug 06 18:48:29 <mpoirier> indeed - I was looking for a quick break.
Aug 06 18:49:13 <rcn-ee_lpt> do you guys have better contacts at ti? maybe the dm37xx clock tree would give some hints.. (i'm thinking they inserted a new clock between to existing ones?)
Aug 06 18:49:13 <mpoirier> now that the problem seem to have been cornered, looking at code is the next step
Aug 06 18:49:35 <mpoirier> yes, we have an open door to TI.
Aug 06 18:50:01 <mpoirier> in a couple of sentence, what is hte dm37xx you're referring to ?
Aug 06 18:50:23 <rcn-ee_lpt> oh, that's what the xm's chip will be called...
Aug 06 18:50:49 <rcn-ee_lpt> dm replaces omap... (for this model)
Aug 06 18:51:55 <mpoirier> you mean the XM has a dm rather than omap ?
Aug 06 18:52:21 <rcn-ee_lpt> blaim it on marketing... the omap is now 'dm'....
Aug 06 18:52:43 <mpoirier> ok, but on your XM, do you have an omap3530 ?
Aug 06 18:53:31 <rcn-ee_lpt> the omap3530 is only on the Bx/Cx.. the xm gets the improved omap3630 which then got tweaked/tuned and renamed into dm37xx
Aug 06 18:53:57 <mpoirier> ha. I get it thanks for the clarification.
Aug 06 18:54:18 <mpoirier> seems like the clocks are the same though since the problem occur on both.
Aug 06 18:54:27 <rcn-ee_lpt> no problem.. it's a crazy nightmare... ;)
Aug 06 18:54:45 <mpoirier> ok, next I'll poke my TI contact and put them on the case.
Aug 06 18:55:22 <rcn-ee_lpt> cool, we had another user ask today, and they keep pointing to use the am3715 doc's.. so hopefully you guys have more push. ;)
Aug 06 18:55:23 <mpoirier> I also have access to the original people who wrote the driver.
Aug 06 18:55:27 <mpoirier> they are in india.
Aug 06 18:55:40 <mpoirier> I'll send them an email with our little findings.
Aug 06 18:58:13 <rcn-ee_lpt> it'll be interesting... do you think there's much point to retrying on 2.6.34 to see if maybe we can maybe bisect? i wouldn't go lower then that for the xm..
Aug 06 18:59:11 <mpoirier> as far as I can tell, the problem started with 2.6.34, nope, no point going lower
Aug 06 18:59:25 <mpoirier> bisect is also something to consider.
Aug 06 18:59:49 <mpoirier> but we still don't know that to look for.
Aug 06 18:59:59 <mpoirier> we have a better idea but...
Aug 06 19:00:26 <mpoirier> there would be a lot of bisects.
Aug 06 19:01:50 <rcn-ee_lpt> 4 minutes per build, 30 seconds to copy, 30 to boot..  i've done worse bisecting on a beagle (6hrs between..)
Aug 06 19:01:52 <rcn-ee_lpt> ;)
Aug 06 19:03:49 <lag_> rcn-ee: mpoirier: Good work! Keep it up
Aug 06 19:03:53 <lag_> ;
Aug 06 19:03:56 <lag_> ;)
Aug 06 19:04:16 <mpoirier> lag: you're supposed to be in a bar by this time
Aug 06 19:04:26 <lag_> mpoirier: Meh!
Aug 06 19:04:44 <lool> zumbi: I don't know
Aug 06 19:04:49 <lag_> I'm working on something for myself (Bluetooth)
Aug 06 19:05:00 <rcn-ee_lpt> what, you guys don't drink and code?
Aug 06 19:05:23 <mpoirier> lag: do you at least have a beer next to you ?
Aug 06 19:05:51 <lag_> I'm 3/4 bottle of wine down ;)
Aug 06 19:05:59 <mpoirier> fabulous !
Aug 06 19:06:54 <mpoirier> rcn-ee_lpt: i'll checkout 2.6.34-rc1 to rc7 and try to isolate where the problem was introduced.
Aug 06 19:07:01 <mpoirier> from there I'
Aug 06 19:07:13 <mpoirier> I'll start a bisect.
Aug 06 19:07:48 <rcn-ee_lpt> i got my machine going too.. just gota tweak the one patch for 2.6.34..
Aug 06 19:10:47 <rsavoye> rcn-ee: hey, did you see that error log I pasted last night ?
Aug 06 19:11:25 <rcn-ee_lpt> yeah rsavoye although it was on my other machine..
Aug 06 19:11:37 <rsavoye> ok. hope it was useful
Aug 06 19:14:25 <rcn-ee> yeah... http://paste.ubuntu.com/473807/  i've been fighting that one too on my normal beagles..  plenty of ram, and swap.. but it starts oom'ing..
Aug 06 19:14:55 <rsavoye> I tried using -O0 tp reduce stress, but no such luck
Aug 06 19:15:17 <rsavoye> after a few dozen of those stack dumps, my XM often hangs completely
Aug 06 19:16:31 <rcn-ee_lpt> yeap after the first one it's just a matter of time...  i'm kinda hoping either the ramz or ram-defrag stuff takes care of it in 2.6.35.. i know cwillu_at_work was fighting it too..
Aug 06 19:26:02 <rsalveti> rcn-ee_lpt: have you ever tested ramz on beagle? don't know how stable or unstable it is
Aug 06 19:26:26 <rsalveti> I heard from ogra that was quite unstable, with bugs
Aug 06 19:26:30 <rsalveti> but no more than that
Aug 06 19:27:28 <rcn-ee_lpt> sorry, been to busy with the xm, so other then enabling it, haven't really tested it..
Aug 06 19:27:56 <rcn-ee_lpt> it's based of the compcache ubuntu's been shipping for awhile right?
Aug 06 19:29:55 <rcn-ee_lpt> nope.. pre 2.6.34: [    4.296813] mmc0: error -110 whilst initialising SD card
Aug 06 19:32:21 <rsalveti> yep, but it's disabled for omap, I believe
Aug 06 19:34:33 <prpplague> someone refresh my memory, where is the location in ubuntu (x86 desktop) to tweak the removable media settings?
Aug 06 19:35:29 <XorA> prpplague: I think they ate it
Aug 06 19:35:49 <XorA> prpplague: I dont have the gnome removable media tool in my menus by default
Aug 06 19:35:55 <prpplague> XorA: seems like there is a command line you cna issue
Aug 06 19:36:20 <rcn-ee_lpt> yeah it's gone..  right a script for and pray the device id never changes. ;)
Aug 06 19:36:38 <XorA> or run KDE :_)
Aug 06 19:37:13 <XorA> not that I would wish that hell on anyone
Aug 06 19:37:31 <prpplague> rcn-ee_lpt: i just don't want it to pop up a window every time it mounts
Aug 06 19:38:49 <rcn-ee_lpt> yeah, it's annoying.. not sure how to take care of that, i know my 'setup_sd.sh' flashes the pop up 4-5 times..
Aug 06 19:43:18 * prpplague has done it before
Aug 06 19:47:36 <prpplague> ahh found it
Aug 06 19:47:41 <rcn-ee_lpt> prpplague, give https://answers.launchpad.net/ubuntu/+question/30501 a try.. gconf-editor has a media_automount_open..
Aug 06 19:48:51 <prpplague> rcn-ee_lpt: if you open a window browsing the contents, you can go edit preferences and there are some options there
Aug 06 19:50:07 <rcn-ee_lpt> cool. i see it too.. disabled..
Aug 06 20:43:23 <GrueMaster> NCommander: Should we enable netboot images for omap4?
Aug 06 20:54:12 <mpoirier> rcn-ee_lpt: did you try 2.6.35-rc1 to rc5 ?
Aug 06 20:54:38 <mpoirier> rcn-ee_lpt: meant 2.6.34-rc1 to rc5
Aug 06 20:56:15 <GrueMaster> mpoirier: Not sure how difficult it would be, but have you taken the omap kernel config and tried it on the Working Lucid kernel?
Aug 06 20:56:42 <GrueMaster> Or is there no significant changes in the config?
Aug 06 20:57:08 <NCommander> GrueMaster: that can be done with a little fiddling to DI, assign me a bug
Aug 06 20:57:53 <GrueMaster> NCommander: Not sure if it is already part of the preinstalled image blueprint.  Need to check there first.
Aug 06 20:58:12 <rcn-ee_lpt> mpoirier, i went as low as 2.6.34-rc7 anything else won't post on the Xm..
Aug 06 20:58:46 <mpoirier> 2.6.34-rc1 to rc5 don't output anything on the console
Aug 06 20:59:08 <mpoirier> here's the kicker: 2.6.33.rc8 works fine.
Aug 06 20:59:15 <rcn-ee_lpt> that's funny...
Aug 06 20:59:27 <mpoirier> and the next booting tag, 2.6.34-rc6 is broken.
Aug 06 20:59:39 <rcn-ee_lpt> so it's somewhere between 2.6.33-rc8 - 2.6.34-rc7
Aug 06 21:00:11 <rcn-ee_lpt> this is on the Bx right?
Aug 06 21:00:18 <mpoirier> 2.6.33-rc8 and 2.6.34-rc6
Aug 06 21:00:27 <mpoirier> Cx
Aug 06 21:00:30 <rcn-ee_lpt> c4.. i mean.. i'm the only one with old stuff
Aug 06 21:00:46 <mpoirier> somewhere in there...
Aug 06 21:01:11 <mpoirier> but it is impossible to find since the kernel won't boot.
Aug 06 21:01:18 <mpoirier> hence you can't bisect that.
Aug 06 21:02:19 <mpoirier> I just asked about the r1 to rc5 in #beagle but nobody replied.
Aug 06 21:04:43 <rcn-ee_lpt> mpoirier, yeah #beagle doesn't really care unless it's angstrom's kernel.. ;) ..
Aug 06 21:04:51 <rcn-ee_lpt> one small problem... http://pastebin.com/APevgWD6
Aug 06 21:04:57 <rcn-ee_lpt> i need to dig thru my sdhc cards...
Aug 06 21:06:49 <hrw|gone> zumbi: https://edge.launchpad.net/~hrw/+archive/arm-cross-compiler/
Aug 06 21:07:38 <mpoirier> rcn-ee_lpt: what is this link you just sent ?
Aug 06 21:08:28 <rcn-ee_lpt> that is the same micro sd card.. that fails on my Xm... but not on my Bx... (Bx needs a Micro to BIG convertor)
Aug 06 21:14:10 <rcn-ee_lpt> yeah, i was asleep during 2.6.34 develment, i can't find any notes about the console in my old trees..
Aug 06 21:23:35 <rcn-ee_lpt> guys kridner just posted the xm schematics: http://beagleboard.org/hardware/design
Aug 06 21:25:01 <rsalveti> nice
Aug 06 21:36:01 <rcn-ee_lpt> okay back in businness, found a pny sdhc card that fails on my bx "mmc0: error -110"
Aug 06 21:38:22 <GrueMaster> Who do I ping with spelling errors in the XM manual? (And if they used OpenOffice it would have already found these.)
Aug 06 21:38:38 <GrueMaster> :P
Aug 06 21:38:41 <rcn-ee_lpt> gerald on beagleboard.org..
Aug 06 21:39:37 <GrueMaster> Grumble.  4 years of college and all I really know is how to proofread.
Aug 06 21:41:46 <lool> Oh there's an A2 now
Aug 06 21:43:51 <hrw|gone> lool: xm a2?
Aug 06 21:45:04 <rcn-ee_lpt> mpoirier, 2.6.34-rc5 is bad.. this patch will take care of most of 2.6.34-rc's.. http://rcn-ee.homeip.net:81/testing/patch-2.6.34-rc.diff
Aug 06 21:45:24 <rcn-ee_lpt> yeap the xm A2 is the first production one..
Aug 06 21:45:57 <mpoirier> are you tacking our little mmc problem or the console not coming out ?
Aug 06 21:46:18 <rcn-ee_lpt> the patch is a console patch... earlyprintk (serial boot) was converted in that rc cycle..
Aug 06 21:46:33 <rcn-ee_lpt> omap specific to generic conversion...
Aug 06 21:47:23 <mpoirier> fantastic - I was actually bisecting between 2.6.33-rc8 and 2.6.34-rc1 to find what broke the console output.
Aug 06 21:55:28 <lool> hrw|gone: Yeah
Aug 06 21:57:11 <rcn-ee_lpt> crap, for 2.6.34-rc2, remove the omap_vram/dss2 stuff.. it breaks..
Aug 06 22:03:06 <rcn-ee_lpt> mpoirier, for 2.6.34-rc2 you'll need: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=5c1f96f4
Aug 06 22:03:28 <mpoirier> console again ?
Aug 06 22:03:56 <rcn-ee_lpt> vram.c failes to compile.. so 2.6.34-rc2 won't build..  (2.6.34-rc3 fails mmc -110)
Aug 06 22:07:37 <rcn-ee_lpt> 2.6.34-rc2 fails.. i really hope it isn't the rc1 merge...
Aug 06 22:11:01 <rcn-ee_lpt> for 2.6.34-rc1 we need: (for serial) http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=21b9034
Aug 06 22:17:27 <rcn-ee_lpt> crap 2.6.34-rc1 fails...  so that leaves 2.6.33-rc8 -> 2.6.34-rc1...
Aug 06 22:28:20 <rcn-ee_lpt> mpoirier, are you guys sure 2.6.33 failed?  there was a large omap conversion from 2.6.33->34-rc1
Aug 06 22:28:51 <mpoirier> 2.6.33-rc8 works.
Aug 06 22:29:08 <mpoirier> rc2 fails,
Aug 06 22:29:21 <mpoirier> therefore it is between 2.6.33-rc8 and 34-rc1
Aug 06 22:32:43 <rcn-ee_lpt> yay.. ;) crabs another beer... there's lots of config changes..
Aug 06 22:34:55 <mpoirier> you're always one step ahead of me.
Aug 06 22:35:24 <mpoirier> i'm currently compiling 34-rc1 after cherry-picking 21b9034
Aug 06 22:35:58 <rcn-ee_lpt> ;) it's just easier when you have all the patches from the last time i had to build it for real..
Aug 06 22:36:13 <mpoirier> and a lot of experience doing it.
Aug 06 22:36:51 <mpoirier> do you know how many patches between 33-rc8 and 34-rc1 ?
Aug 06 22:37:52 <rcn-ee_lpt> well, i'm just trying to get 2.6.33 built right now.. (and praying to rule out rc1) but alot of the config names changed...
Aug 06 22:43:08 <mpoirier> rcn-ee_lpt: still no console output on 34-rc1, even after cherry picking 21b9034.
Aug 06 22:43:15 <mpoirier> did i miss something ?
Aug 06 22:44:27 <rcn-ee_lpt> for rc1 you need 21b9034 (merge rc2) and then the previous one too...
Aug 06 22:45:41 <rcn-ee_lpt> this is the 'pervious' one mimized as much as possible http://rcn-ee.homeip.net:81/testing/patch-2.6.34-rc-take2.diff
Aug 06 22:46:31 <mpoirier> ok, let me try
Aug 06 22:47:23 <rcn-ee_lpt> sure.. well 2.6.33 works...  i'll post my config in second just incase i ended up remving too much..  but itlooks like 2.6.33 -> 2.6.34-rc..
Aug 06 22:48:06 <mpoirier> you mean 33-rc8 -> 34-rc1 ?
Aug 06 22:48:07 <rcn-ee_lpt> http://rcn-ee.homeip.net:81/testing/2.6.33-config
Aug 06 22:48:50 <rcn-ee_lpt> well i got 2.6.33 to boot (no problems with mmc card...) but i'm going to double check the config.. incase oldconfig removed too much
Aug 06 22:49:25 <mpoirier> you can go all the way to 33-rc8 if you want.
Aug 06 22:51:07 <mpoirier> ok, got console output on 34-rc1.
Aug 06 22:51:20 <rcn-ee_lpt> cool
Aug 06 23:06:02 <mpoirier> rcn-ee_lpt: I started a bisect between 33-rc8 and 34-rc1.
Aug 06 23:06:15 <mpoirier> apparently, i have only 12 steps to go
Aug 06 23:06:21 <mpoirier> does that sound right to you ?
Aug 06 23:06:33 <rcn-ee_lpt> yeah, i'm doing about the same.. i got 2.6.33 to work, other than that.. ;)
Aug 06 23:07:18 <rcn-ee_lpt> hopefully we come with the same..
Aug 06 23:07:53 <mpoirier> why did you choose to start from 2.6.33 rather than 2.6.33-rc8 ?
Aug 06 23:07:56 <rcn-ee_lpt> btw disable the touchbook, it gets in away alot..
Aug 06 23:09:05 <rcn-ee_lpt> a hunch as i got 2.6.33 to work.... so far the first bisect points to 2.6.34-rc1 vs 2.6.33, as long as one fails i'm good
Aug 06 23:09:46 <mpoirier> but we know 2.6.33-rc8 works... won't that reduce the number of iteration ?
Aug 06 23:10:14 <mpoirier> I'm not questionning your work - just want to learn.
Aug 06 23:10:56 <rcn-ee_lpt> do you mean maybe 2.6.33-git8? cause 2.6.33-rc8 < 2.6.33 < 2.6.34-rc1..
Aug 06 23:11:20 <mpoirier> oh !
Aug 06 23:11:49 <mpoirier> i thought 2.6.33 < 2.6.33-rc1 < 2.6.33-rc2...
Aug 06 23:11:50 <rcn-ee_lpt> (it twists my mind out too.. ;) )
Aug 06 23:13:04 <rcn-ee_lpt> i'm so glad it isn't that one.. .as it has the mach -> plat conversion..
Aug 06 23:16:09 <rcn-ee_lpt> yes it broke.. qgit shows a omap hsmmc merge.. ;)
Aug 06 23:18:14 <mpoirier> congrats - do you have a sha1 ?
Aug 06 23:18:57 <rcn-ee_lpt> still going between them... currently bisect good 47871999 bisect bad 1154fab73
Aug 06 23:19:09 <rcn-ee_lpt> you need the vram patch
Aug 06 23:19:23 <rcn-ee_lpt> console works fine asiss
Aug 06 23:20:54 <mpoirier> I'm behind - I had to restart my bisect...
Aug 06 23:20:55 <rcn-ee_lpt> keep checking your config in there, the omap34xx config names change..
Aug 06 23:21:09 <mpoirier> ok.
Aug 06 23:23:26 <rcn-ee_lpt> when the config changes, you lose all the omap modules too (snd/mmc/etc..) so it'll take a little extra time between builds..
Aug 06 23:55:04 <rcn-ee_lpt> geting down there, 15ish revisions to go, kinda wish i had 8-16G of a ramdrive.. ;)
Aug 07 00:01:53 <mpoirier> rcn-ee_lpt: got to log out now - i'll catch up with you on Monday.
Aug 07 00:01:59 <mpoirier> Thanks for your time and help
Aug 07 00:02:50 <rcn-ee_lpt> sure no problem, have a good weekend
Aug 07 00:39:00 <rcn-ee_lpt> sweet, got it...  2.6.35 + revert(6da20c89) fixes the mmc -110 error on bx/cx and xm... ;)
Aug 07 02:56:19 <GrueMaster> rcn-ee: Excellent job, thanks.
**** ENDING LOGGING AT Sat Aug 07 02:59:57 2010