[00:07] <jaminc> I'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?
[00:07] <ubot2> Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/538097
[00:07] <ubot2> Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592239
[00:40] <Sarvatt> any reason the i386 kernels are using CONFIG_M586=y in maverick that went to i686 by default?
[02:42] <ScottL> does anyone know why the -preempt kernel keeps building uninstallable binaries?
[02:43] <ScottL> i think this is keeping the ISo testing from building a proper ubuntu studio ISO
[02:54] <jaminc> I'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?
[02:54] <ubot2> Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/538097
[02:54] <ubot2> Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592239
[07:38]  * abogani2 waves
[07:52] <abogani2> apw, ogasawara: Are you around?
[08:00] <MTecknology> abogani2: hi
[08:18] <abogani2> MTecknology: hi :-)
[08:36]  * apw yawns
[08:37] <ikepanhc> good morning .eu
[08:37] <apw> morning
[08:37] <smb> Morning .*
[08:38] <cking> morning .* too
[08:39] <ikepanhc> There is CONFIG_PREVENT_FIRMWARE_BUILD in driver/Kconfig, but seems no code use it, anyone knows how it works?
[08:40] <ikepanhc> s/driver/drivers
[08:40] <ikepanhc> eh drivers/base/Kconfig
[08:40] <apw> ikepanhc, isn't that an intermederary configuration option, one that gets selected
[08:41] <smb> cooloney, Heya Brian. Is Eric around today?
[08:41] <ikepanhc> oh, I see them
[08:42] <cooloney> apw: smb cking morning guys
[08:42] <abogani2> apw: There is a bug into maverick-meta package: -preempt is still there. Could you remove it, please?
[08:42]  * apw waves generally
[08:42] <smb> cooloney, moin
[08:43] <cooloney> smb: he seems to be dropped.
[08:43] <cooloney> smb anything urgent?
[08:43] <cooloney> i can call him
[08:43] <smb> cooloney, Meh, semi-urgent. Not worth a coll I think. I write him an email
[08:44] <abogani2> smb: I suppose than you can remove the linux-rt signed directory in your home at Zinc. Thanks for all!
[08:44] <apw> abogani2, hrm, i'll get leann to drop it from the next upload, wonder how that got missed
[08:44] <abogani2> apw: Thanks!
[08:44] <smb> abogani2, I am lazy. So it gets removed the next time I add something new. :) You're welcome
[08:45] <abogani2> smb: :)
[08:45] <abogani2> apw: Only for keep you updated: the last lowlatency test build is done at https://launchpad.net/~abogani/+archive/broken/+packages
[08:51] <ikepanhc> apw: about the lucid ABI number, is it good to use a greater number such as 1000+ for oem kernel branch?
[08:51] <ikepanhc> sorry forget to trace this issue after last time I asked you
[08:53] <ikepanhc> oh, and I asked for several oem guys, seems no oem project using karmic netbook branch
[09:00] <apw> ikepanhc, ABI number> it depends if they are going to be new branches or merge into the existing ones
[09:00] <apw> ikepanhc, karmic netbook> seems this branch is dead then, will talk to smb about its fate
[09:02] <apw> ikepanhc, so you do not have any use for the branch any more ?
[09:02] <smb> apw, ikepanhc If noboday is using that, then I'd vote for removal
[09:02]  * apw concurs with smb, one less branch to fix :)
[09:03] <ikepanhc> apw: yeah, that's the problem, if using a greater ABI number on a branch, it will let the branch can not be merged - build server will reject uploading a smaller ABI number
[09:03] <smb> Not that I never did much with that
[09:06]  * ikepanhc ponders for removal
[09:13] <ericm|ubuntu> smb, the merge looks good, I'm doing a building and will have a smoke test on dove hw, get back to you soon
[09:14] <smb> ericm|ubuntu, Ok, great. I hold back and upload as soon as you give your ok
[09:16]  * ericm|ubuntu feels sick about the error message: ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be preloaded: ignored.
[09:17] <ericm|ubuntu> anyone knows why 'fakeroot echo $LD_PRELOAD' doesn't show any clue?
[09:17] <maxb> Because your shell expanded $LD_PRELOAD before fakeroot was invoked
[09:18] <smb> If you were on i386 it might be a 32/64bit issue...
[09:18] <ericm|ubuntu> maxb, ah right
[09:18] <ericm|ubuntu> smb, I'm on amd64, ia32lib installed though
[09:18] <ericm|ubuntu> maxb, let me try encapsulate that into a shell script then
[09:19] <ericm|ubuntu> now it shows: LD_PRELOAD=libfakeroot-sysv.so
[09:21] <jk-> ericm|ubuntu: do you have libfakeroot for 32-bit?
[09:22] <ericm|ubuntu> jk, nope
[09:22] <jk-> and are you trying to run a 32-bit binary ?
[09:22] <ericm|ubuntu> jk-, that could possibly be the cause
[09:22] <ericm|ubuntu> it's a codesourcery toolchain and it should be 32-bit binary
[09:23] <apw> ikepanhc, smb, karmic netbook> i propose we tag the tip of the branch netbook-mothball and remove the branch ... then we can get it back if we need to
[09:23] <ericm|ubuntu> jk-, you are right: file ~/bin/arm-2010q1/bin/arm-none-linux-gnueabi-gcc
[09:23] <ericm|ubuntu> /home/ycmiao/bin/arm-2010q1/bin/arm-none-linux-gnueabi-gcc: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.2.5, stripped
[09:23] <apw> ericm|ubuntu, i run those in a 32bit chroot
[09:23] <ikepanhc> apw: that's a good idea
[09:23] <ikepanhc> apw: +1 from me
[09:23] <apw> smb, ?
[09:23] <smb> apw, ikepanhc Sonds like a good middle way between complete removal and carrying it around
[09:23] <smb> apw, +1
[09:23]  * apw takes the action ...
[09:24] <ericm|ubuntu> apw, you are right
[09:24]  * ericm|ubuntu sees apw happily removing a branch
[09:37]  * smb finds a Lucid ABI 23 in the meta repo done by apw... I guess not uploaded, yet?
[09:40] <apw> smb, right, its an UNRELEASED one right?
[09:40] <apw> thats there to trigger pre-proposed to pick up the abi change
[09:40] <smb> Yep it is.
[09:40] <smb> I am just finalizing it
[09:41] <smb> Just a bit confused why the -22 is marked proposed too
[09:41] <apw> did i do -22 ?  i don't recall touching that
[09:42] <smb> Hm, looking at the archive, it looks ok though
[09:42] <smb> Maybe the day0 update
[09:43] <apw> yeah i wondered about that, though i thought that was not a bumper
[09:43] <smb> I just got confused because I did not do an ABI bump since release. But maybe we did and its just half erased from memory. :-P
[09:43] <smb> We should be in sync now
[09:43] <apw> ok cool
[09:44] <ericm|ubuntu> smb, it works all right
[09:44] <smb> ericm|ubuntu, Ok, thanks for the verification, I will upload in a few minutes
[09:44] <ericm|ubuntu> smb, thanks for the work - really appreciated
[09:45] <smb> ericm|ubuntu, It was partially the confusion about the whitespace. But I am glad it is good now
[09:46] <ericm|ubuntu> smb, yeah - their patches s*ck but I was not doing good to educate
[13:31] <jaminc> I'm experiencing a seeming random kernel crash and system reboot.  I have a crash dump, the system detects the previous crash and offers to report it, however every attempt to report it seems to fail with an HTTP 500 Error (bug #538097) additionally, apport-retrace fails with an index out of range (bug #592239)... so, what are my options for either reporting this crash or getting some meaningful information out of it?
[13:31] <ubot2> Launchpad bug 538097 in apport (Ubuntu) (and 1 other project) "+storeblob fails with "500 Internal server error" on production (works on edge) (affects: 104) (dups: 6) (heat: 533)" [High,Invalid] https://launchpad.net/bugs/538097
[13:31] <ubot2> Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592239
[13:34] <pgraner> jaminc: you can use https://bugs.launchpad.net/ubuntu/+source/linux/+filebug to file the bug and then use apport-collect <bug number> to attach all the needed debug info
[13:36] <jaminc> isn't that likely to suffer from the same issue with the automated upload?
[13:37] <pgraner> jaminc: don't know, but its worth a try, if it fails then you can upload everything manually via the web interface
[13:39]  * apw lunches
[13:49] <TeTeT> smb: I escalated the x201 WWAN module problem, maybe it will end in your lap
[13:49] <jaminc> pgraner, can't seem to attach a file to bug report after filing it... keep getting "Cannot upload empty file." even after selecting the file and seeing it listed in the selection box
[13:52] <smb> TeTeT, Thanks for the heads up. I will see... :)
[13:55] <tgardner> smb, Is Lucid -meta stuck in the queue?
[14:02] <pgraner> jaminc: whats the bug number?
[14:02] <jaminc> 593650, uploading the file now, forgot that the crash dumps are only accessible by root
[14:03] <jaminc> any tags that are needed since the crash dump is being uploaded manually?
[14:03] <pgraner> jaminc: yea one sec
[14:04] <pgraner> jaminc: https://wiki.ubuntu.com/Kernel/Tagging look at the last table and pick the appropriate ones
[14:04] <pgraner> jaminc: I'll get out triager to get it into the right state when he comes online
[14:05] <jaminc> thought there were tags to indicate a need for a retrace and such?
[14:14] <jaminc> pgraner, upload got to 100%, page started to reload and then gave me: "Sorry, there was a problem connecting to the Launchpad server."
[14:17] <pgraner> jaminc: what was the name of that file? Several are on the report now
[14:18] <jaminc> those are the ones from apport-bug, the manual upload was the kernel crash dump: linux-image-2.6.32-22-generic.0.crash 
[14:20] <apw> uploading crash dumps to launchpad ... just how big is that thing?
[14:20] <MTecknology> apw: that's a really early lunch... I wasn't even to work yet
[14:21] <apw> MTecknology, depends on where the sun is in the sky in my part of the world :)
[14:21] <jaminc> this one is smallish 309M, others are quite large... have had one up to 2.5G
[14:21] <apw> jaminc, i suspect that the upload is timing out
[14:21] <pgraner> jaminc: use apport-collect 593650 <full path to the crash file>         and see if that will get it to go
[14:22] <MTecknology> apw: I live in the US - therefor you all abide by my time.
[14:22] <pgraner> apw: launchpad is having issues today, I'm getting timeouts just refreshing pages
[14:22] <jpds> jaminc: I think bug #592239 is a dup of bug #585269.
[14:22] <apw> MTecknology, luckily we have learned how to ignore .us
[14:22] <ubot2> Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/592239
[14:22] <ubot2> Launchpad bug 585269 in apport "apport-retrace shouldn't expect a Package field for kernel crashes (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/585269
[14:22] <MTecknology> apw: :P
[14:22] <pgraner> jpds: we don't care about dupes, we need a new report on all kernel bugs
[14:23] <jaminc> pgraner, no, he's talking about why I can't locally retrace it... different item
[14:24] <pgraner> jaminc: yea I saw that after the bug desc popped up
[14:24] <jaminc> pgraner, apport-collect 593650 /var/crash/linux-image-2.6.32-22-generic.0.crash 
[14:24] <jaminc> Usage: apport-collect <report number>
[14:25] <pgraner> jaminc: then it I don't know
[14:35] <apw> jaminc, i would try attaching it using the attach file option, i suspect it will puke again at which point i suspect your only choiuce is to make it available somewhere else
[14:36] <jaminc> apw, already tried using the attach file option that's what resulted in the "Sorry, there was a problem connecting to the Launchpad server."
[14:36] <apw> jaminc, i suspect they never ever considered files that big being attached and its timing out in the middle
[14:37] <jaminc> the problem is that the crash needs a retrace, I'd happily do the retrace myself (have built and installed the debug version of the kernel), just not sure how to do it since apport-retrace bombs
[14:38] <ogra> hmm, did we get a new defconfig for omap with the last upload ? i suddenly get weird error messages with the latest omap3 binary
[14:39] <ogra> i cant relly see any valid stuff in the uploaded changelogs 
[14:40] <jaminc> would the kernel crash dump contain potentially sensitive information?
[14:43] <amitk> yes
[14:43] <amitk> it dumps your entire physical memory
[14:43] <amitk> so potentially decrypted keys
[14:45] <jaminc> then hosting it publicly isn't much of an option.  any other way I can get a useful trace from it?
[14:47] <amitk> jaminc: do the analysis yourself?
[14:48] <jaminc> I'm offering to... however all the tools referred to by the documents I've found fail... so I'm asking for guidance...
[14:49] <jaminc> https://wiki.ubuntu.com/KernelTeam/CrashdumpRecipe refers to using apport-retrace, however as bugs #592239 and #585269 illustrate, that's not possible currently even with self built debug kernels installed
[14:49] <ubot2> Launchpad bug 592239 in apport (Ubuntu) "apport-retrace - IndexError: list index out of range (dup-of: 585269)" [Undecided,New] https://launchpad.net/bugs/592239
[14:49] <ubot2> Launchpad bug 585269 in apport "apport-retrace shouldn't expect a Package field for kernel crashes (affects: 2) (dups: 1) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/585269
[14:50] <cwillu_at_work> jaminc, should be easy to hack up apport-retrace to not try to include it, it's just a python script
[14:56] <jaminc> seems the upload issue is a very old bug #95822
[14:56] <ubot2> Launchpad bug 95822 in apport (Ubuntu) (and 1 other project) "Malone connection generates an "Internal Server Error" on large file attachments (affects: 6) (dups: 6) (heat: 84)" [Medium,Confirmed] https://launchpad.net/bugs/95822
[15:10] <jaminc> cwillu_at_work, by george you were right... a single line change to the python script and a small change to how apport-retrace was called and I appear to have a viable trace
[15:18] <ogra> hmm, the omap3 error seems to come from a patch that enables IO-CHAIN wakeups 
[15:18] <ogra> "Wake up daisy chain activation failed."
[15:19] <ogra> i dont see changes related to that in the changelog ... do we not include everything in the debian/changelog file ?
[15:22] <ogra> (i mean upstream commits)
[15:31] <ogra> amitk, ^^^ any idea ? 
[15:31]  * ogra suspects http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18213.html entered mainline recently or something like that
[15:31] <ogra> in any case it makes the beagle kernel unbootable atm
[15:32] <amitk> ogra: which omap error?
[15:32] <ogra> "Wake up daisy chain activation failed."
[15:33] <ogra> over and over
[15:33] <amitk> lucid or maverick?
[15:33] <ogra> maverick indeed :)
[15:34] <amitk> ogra: this is with new kernel?
[15:34] <ogra> i used 2.6.34 for testing until today 
[15:34] <ogra> this error shows up with 2.6.25-2.2
[15:34] <ogra> err
[15:34] <ogra> -2.3
[15:35] <ogra> so something changed between .34 and .35
[15:35] <amitk> _lots_ of omap changes went in then
[15:35] <ogra> where are the changelogs for that in our package ? 
[15:36] <ogra> we should somehow generate an upstream changelog that goes into the package docs 
[15:39] <manjo> JFo, you feeling better ? are we doing the bug meeting today?
[15:40] <JFo> manjo, not much. I think something I ate in SC didn't agree with me. We will be having the bug chat
[15:40] <tgardner> ogra, we do not generate a changelog of that size since it would have tens of thousands of changes, not a manageable amount IMHO.
[15:40] <ogra> hmm, i thought we used to have such a feature once
[15:40] <manjo> JFo, sorry to hear that... will talk to you at the meeting 
[15:40] <JFo> k :)
[15:40] <ogra> in the package changelog actually
[15:41] <amitk> ogra: the entire upstream changelog isn't in debian/changelog, only a pointer to what tag we rebased to. 
[15:41] <ogra> it would help a lot during development 
[15:41] <tgardner> ogra, we do for minor updates, but going from 2.6.34 to 2.6.35 is a big jump
[15:41] <amitk> ogra: you wouldn't know where to even look if the entire 2.6.34..35 changelog was put into debian/changelog
[15:41] <ogra> yeah, i understand ...
[15:42] <ogra> well, i could gep for buzzwords
[15:42] <ogra> i.e. in the above case i would expect something like IO-CHAIN to show up in a changelog entry
[15:42] <amitk> ogra: git log | grep buzzword :-p
[15:42] <ogra> amitk, then i need to pull the git tree 
[15:43] <ogra> having a changelog file would be a lot more convenient for a non kernel developer 
[15:43] <ogra> but if its to big then its indeed no option
[15:44] <tgardner> ogra, 9479 commits from 2.6.34 to 2.6.35-rc3
[15:45] <ogra> yeah, thats surely a lot
[15:47] <amitk> ogra: I just checked, even debian doesn't do something like that. Just a one-liner saying "update from tag1 to tag2"
[15:48] <ogra> amitk, yeah, seems i took wrong that changes sometimes show up and sometimes they dont 
[15:51] <ogra> http://www.gossamer-threads.com/lists/linux/kernel/1228828 aha
[15:51] <ogra> Mike Chan (2): 
[15:51] <ogra> OMAP3: PM: Enable IO / IO-CHAIN wakeups for PER 
[15:54] <amitk> mpoirier_: are you looking at bug 566645?
[15:54] <ubot2> Launchpad bug 566645 in linux-ti-omap (Ubuntu Maverick) (and 2 other projects) "OTG configuration is broken on omap kernel (affects: 2) (heat: 70)" [High,Confirmed] https://launchpad.net/bugs/566645
[15:54] <mpoirier_> yes and no.
[15:54] <mpoirier_> discovered a problem with SD card.
[15:55] <mpoirier_> very tedious.
[15:55] <mpoirier_> took me a week to find it.
[15:56] <mpoirier_> I'll jump on 566645 as soon as this one is fixed.
[15:57] <mpoirier_> I have the answer on SD card.  Just need to go through the patch set to see which one broke the SD card.
[15:57] <amitk> mpoirier_: ok, it would be nice if you, lag and Bryan divided up the bugs at https://bugs.edge.launchpad.net/ubuntu/+source/linux-ti-omap/ amongst yourselves, depending on what HW each of you have.
[15:58] <mpoirier_> to the best of  me knowledge Bryan doesn't have HW.
[15:58] <amitk> they are important enough bugs for our maverick work too, so if the fix isn't yet in 2.6.35-rc3, then we need to apply it as a sauce in maverick
[15:59] <mpoirier_> here's a question:
[15:59] <amitk> mpoirier_: I'll see if I can make arrangements for some more HW
[15:59] <mpoirier_> What has precedence: maverick on panda or bug fixes ?
[16:00] <mpoirier_> I'm working on SD card for now while no kernel from TI for panda.
[16:00] <mpoirier_> but when kernel is given to us, I don't know what comes first.
[16:00] <mpoirier_> and where to fit OTG ?
[16:00] <mpoirier_> I just need priorities.
[16:01] <amitk> mpoirier_: that (priority) is a question for tgardner, but I believe we need to fix the confirmed bugs in lucid and make sure they don't recur on marverick
[16:01] <mpoirier_> Therefore, SD card and OTG would come first.
[16:01] <tgardner> mpoirier: for now I think amitk's suggestion is best.
[16:02] <mpoirier_> I should check in SD card today or tomorrow. tgardner, we need to talk about the problem and the fix.
[16:03] <tgardner> mpoirier: ack
[16:03] <mpoirier_> I'll jump on OTG after.  I think upstream got it working.
[16:03] <amitk> mpoirier_: with panda, we have a totally new kernel (separate branch, new HW generation, etc.). There will be new bugs. But atleast the OMAP3 stuff should work well on lucid and maverick.
[16:03] <amitk> it gives our community something to hack on widely available boards
[16:04] <mpoirier_> Ok, if priorities are to fix bugs on OMAP3, that's what I'll do.
[16:04] <mpoirier_> there aren't that many.
[16:04] <mpoirier_> Who will take care of OMAP4 then ?
[16:05] <mpoirier_> people will start asking me questions ?
[16:05] <tgardner> mpoirier: we can worry about that when we actually have HW
[16:06] <mpoirier_> I have a panda board right next to me.
[16:06] <tgardner> ogasawara, are you planning an -rc3 based upload today? I suspect it'll fix some of the process hang problems I've had with the LTS backport.
[16:07] <tgardner> mpoirier: indeed, I thought it was still under development.
[16:07] <tgardner> but, as amitk suggested, lets make Lucid work well first
[16:07] <tgardner> Lucid/maverick
[16:07] <amitk> lucid/maverick on OMAP3
[16:08] <tgardner> amitk, OMAP4 is maverick only, right?
[16:09] <amitk> tgardner: right
[16:09] <mpoirier_> Who will be working with TI on panda OMAP4 while I fix OMAP4
[16:09] <mpoirier_> fix OMAP3 that is.
[16:09] <ogasawara> tgardner: yep, planning to rebase this morning
[16:10] <tgardner> ogasawara, I did a test rebase, it was completely painless
[16:10] <ogasawara> tgardner: sweet, should be quick then
[16:11] <tgardner> ogasawara, I did bump the ABI before building though, just as a matter of course
[16:11] <ogra> mpoirier, lag and you have the omap4 HW 
[16:12] <ogra> mpoirier_, so he should be able to take over 
[16:12] <lag> ogra: I have Panda
[16:12] <ogra> right
[16:12] <ogra> thats what i was saying :)
[16:13] <amitk> ogra: do you have more beagles in your team lying unused?
[16:13] <ogra> (or at least meaning if it came across differently :) )
[16:13] <tgardner> mpoirier: between you and lag there'll be plenty to do. the pit of bugs is bottomless.
[16:13] <lag> I was agreeing with you
[16:13] <ogra> amitk, not to my knowledge, lets ask davidm
[16:13]  * lag gets a warm fuzzy feeling
[16:14] <mpoirier_> all good with me.
[16:14] <mpoirier_> We all need to agree on who does what so that we don't drop the ball.
[16:14] <tgardner> mpoirier_, thats what jfo does for you
[16:15] <mpoirier_> Just to be clear, I'll keep fixing OMAP3 while OMAP4 support is assured by lag.
[16:15] <mpoirier_> And therefore won't look at OMAP4 at this point.
[16:17] <lag> I'm happy to look at either 
[16:17]  * JFo looks at *
[16:17] <JFo> :)
[16:18] <mpoirier_> same here - no preference.
[16:19] <lag> Or both
[16:20] <lag> My intention was to just select bugs and work on them
[16:20] <lag> I should have my OMAP3 board sometime tomorrow all being well
[16:21] <amitk> ohh good, then just split up the bugs amongst yourselves
[16:21] <mpoirier_> lag: beableboard ?
[16:22] <lag> Yep
[16:22] <amitk> mpoirier_: beagleboard, with a 'g' :)
[16:23] <mpoirier_> yes, sloppy fingers this morning.
[16:23] <amitk> mpoirier_: not a coffee drinker? ;)
[16:23] <mpoirier_> have been going without a drop for 4 years now.
[16:24] <amitk> hehe, good call
[16:24] <tgardner> mpoirier_, that way lies madness
[16:24] <mpoirier_> fantastic !
[16:29] <ogra> mpoirier_, did yuo test the latest archive kernel already ? 
[16:29] <ogra> since i cant get it to boot at all here+
[16:30]  * ogra wonders if it boots for anyone else
[16:30] <mpoirier_> ogra: hold on.
[16:30] <mpoirier_> ogra: you mean 35-rc3 ?
[16:30] <ogra> 2.6.35-2.3
[16:31] <ogra> latest uploaded archive kernel
[16:31] <mpoirier_> haven't no. I'll try and get back to  you.
[16:32] <ogra> i seem to have issues with this patch http://www.mail-archive.com/linux-omap@vger.kernel.org/msg18213.html
[16:32] <ogra> ending up with endless "Wake up daisy chain activation failed." messages and unresponsive board
[16:33] <mpoirier_> gruemaster was seeing something like that when I was chasing the SD card problem.
[16:33] <mpoirier_> he was trying my kernels.
[16:33] <ogra> hmm
[16:33] <mpoirier_> but he had some weird user space.
[16:34] <ogra> yeah, and he also had mmc timeout errors
[16:34] <mpoirier_> yep - you seem to have a blessed SD card.
[16:36]  * ogra learned to use sandisk for actual work ... i have about ten other brands to test though and didnt see issues 
[16:36] <ogra> but i used 2.6.34 until this morning since i needed a reliable kernel for the image building stuff
[16:36] <ogra> now i built the first image with .35 which got me the new issues (no mmc timeouts though)
[16:37] <mpoirier_> fabulous !
[16:38] <mpoirier_> I should have a fix soon.
[16:38] <ogra> great
[16:40] <mpoirier_> fix for SD card that is - no nothing about daisy chain.
[16:40] <mpoirier_> I'll try to reproduce
[16:54] <manjo> lag, you can also cat /etc/issues 
[16:54] <lag> cat: /etc/issues: No such file or directory
[16:54] <manjo> cat /etc/issue
[16:54] <lag> Ubuntu 10.04 LTS \n \l 
[16:55] <manjo> sconklin, you are cutting off 
[16:55] <manjo> sconklin, stop your upload 
[16:57] <manjo> sconklin, you not audiable 
[16:57] <sconklin> let me try restarting mumble
[16:59] <manjo> sucks
[16:59] <manjo> sconklin, sucks
[16:59] <sconklin> I give up
[16:59] <manjo> sconklin, you need a better ISP
[16:59] <sconklin> JFo: please catch me on IRC after the meeting
[16:59] <JFo> will do sconklin 
[17:01] <manjo> apw, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.searchtext=&orderby=-importance&field.status:list=NEW&field.status:list=INCOMPLETE_WITH_RESPONSE&field.status:list=INCOMPLETE_WITHOUT_RESPONSE&field.status:list=CONFIRMED&field.status:list=TRIAGED&field.status:list=INPROGRESS&field.status:list=FIXCOMMITTED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.
[17:01] <manjo> tag=kernel-candidate&field.tags_combinator=ALL&field.status_upstream-empty-marker=1&field.has_cve.used=&field.omit_dupes.used=&field.omit_dupes=on&field.affects_me.used=&field.has_patch.used=&field.has_branches.used=&field.has_no_branches.used=&search=Search
[17:02] <manjo> http://qa.ubuntu.com/reports/jfo/kernel-Top50.html
[17:02] <manjo> http://goo.gl/jwSj
[17:09] <sconklin> I can hear.
[17:10] <JFo> heh
[17:10] <sconklin> Just that this might be a situation where we would consider attempting to write a fix
[17:11] <sconklin> Several of the ones I put on the list would require significant dedication of engineer resources
[17:12] <sconklin> might just be a backport
[17:13] <sconklin> I think this can be backported but isn't in stable yet
[17:15] <sconklin> I can look at that
[17:16] <sconklin> ok, I'll see if it applies and builds and send a review request?
[17:16] <sconklin> stefan, OK?
[17:16] <sconklin> :)
[17:17] <sconklin> all good on the previous one
[17:17] <JFo> cool
[17:17] <sconklin> move on
[17:17] <sconklin> X61 clone mode
[17:18] <sconklin> Yeah, that's what we have to talk about mostly
[17:18] <sconklin> This is apparently a big deal, and ~something~ should be done, but I think it falls on the HWE people
[17:19] <sconklin> It was explained in private email that we have to fix it even in a private custom build
[17:19] <sconklin> presales, willing to take a custom ppa build
[17:21] <sconklin> I don't think we have the hardware to reproduce it
[17:22] <sconklin> I think it was all ripped out
[17:37] <sconklin> next two and the last one on the list may all be the same bug. There is a brand-new upstream patch that I'm going to put in a PPA for testing.  There are still more bugs which may be the same one. I'm working on this whether it's on the list or not, so it doesn't matter if it's in the top 50
[17:38] <sconklin> that sounds good
[17:38] <sconklin> NO
[17:38] <sconklin> See whether the patch fixes all of them
[17:38] <sconklin> good!
[17:48] <manjo> http://qa.ubuntu.com/reports/jfo/kernel-buglist.html
[18:05] <falktx_> hi guys
[18:06] <falktx_> is this the right place for kernel specific issues?
[18:07] <abogani2> falktx_: yes
[18:09] <falktx_> my friend is having issues with a new kernel
[18:09] <falktx_> the mininote 
[18:09] <falktx_> it worked on 2.6.32-21
[18:09] <falktx_> but not with 2.6.32-22
[18:09] <_guitarman_> yes this is me...
[18:09] <falktx_> _guitarman_: please explain
[18:10] <_guitarman_> my hp mininote 110 seemed to work ok when upgraded from karmic to lucid, but then i wiped it and did a clean install of lucid and now although i have 2.6.32-22 kernel, only the 2.6.32-21 kernel will boot
[18:11] <_guitarman_> the other kernel just sits there nothing displays - just a flashing cursor at the top left
[18:11] <_guitarman_> i am not sure if this is updates to the system that bust it, or if it is hard disk geometry or grub or what.
[18:11] <_guitarman_> any thoughts
[18:11]  * _guitarman_ is also googling
[18:14] <abogani2> _guitarman_: Could you try to remove the kernel command line options "quiet" and "splash"?
[18:14] <tgardner> smb, bjf: ^^ possible Lucid regression
[18:14] <bjf> tgardner, ack
[18:14] <_guitarman_> abogani2: i will try this now and let you know
[18:15] <abogani2> _guitarman_: I hope that you are using an other computer for IRC... ;-)
[18:16] <_guitarman_> heheh yup
[18:17] <abogani2> _guitarman_: In meanwhile could you give me some details about your installation? Did you have install closed video drivers for example?
[18:18] <_guitarman_> ok so... i installed the ubuntu fwcutter driver for the broadcomm wireless whereas before i think i used STA
[18:18] <_guitarman_> that may be an issue
[18:18] <_guitarman_> abogani2: i booted and it hangs while running /scripts/local-top ... final item is ata4: DUMMY usb 1-5: new high speed usb device using ehci_hcd and address 3
[18:19] <abogani2> _guitarman_: The ALT+SysReq keystroke works?
[18:19] <_guitarman_> no
[18:19] <_guitarman_> its hard locked
[18:20] <abogani2> _guitarman_: Sorry I meant the ALT+SysReq+S keystroke works?
[18:21] <_guitarman_> abogani2: you mean RSEIUB? nope nothing works in here... and if you mean alt-sysrequest,S <-- letter S? that doesn't do anything either
[18:21] <_guitarman_> abogani2: pressing that now while it is sitting here doesn't help
[18:22] <smb> tgardner, That would be the day0 update
[18:22] <smb> tgardner, Maybe he wants to try the -23 kernel
[18:22] <_guitarman_> abogani2: do you think if i boot into .21, change wireless driver to sta, reboot and try 22 - would that help identify if thats the conflicting driver that is stopping boot?
[18:22] <tgardner> smb, um, I can't remember what was in the day 0 update.
[18:23] <ogasawara> apw, abogani2: I'm dropping preempt from linux-meta.  Was an oversight on my part when we dropped it in the linux package.
[18:24] <apw> ogasawara, cool thanks
[18:24] <abogani2> _guitarman_: Yes!
[18:24] <abogani2> ogasawara: Thanks!
[18:24] <_guitarman_> abogani2: ok, i'll do that now
[18:30]  * smb reboots to nohpet to try to fix his strange disconnects
[18:35] <falktx_> i noticed a new kernel update in proposed
[18:35] <falktx_> _guitarman_: u should try it
[18:36] <_guitarman_> falktx_: sorry - i will try tihs first then look at the kernel update at least it will help isolate the issue. for some reason the hardware drivers applet is misbehaving in kubuntu
[18:37] <_guitarman_> says sorry-jockey - systemerror:installarchives()failed
[18:38] <falktx_> _guitarman_: did u try other kernel versions?
[18:38] <_guitarman_> is there a way i can do this from cmd line abogani2 falktx_ ? choose the restricted driver
[18:38] <falktx_> 2.6.33/34?
[18:38] <_guitarman_> falktx_: .33 is a fail
[18:38] <_guitarman_> falktx_: i haven't tried .34
[18:39] <falktx_> i have to go
[18:39] <falktx_> _guitarman_: i hope it works
[18:39] <_guitarman_> ok take care falktx_ talk to ytou later
[18:39] <_guitarman_> falktx_: thx
[18:42] <abogani2> _guitarman_: :-?
[18:44] <_guitarman_> abogani2: restricted driver install isn't working in kubuntu proper for me
[18:44] <abogani2> _guitarman_: Which driver you are trying to remove?
[18:45] <_guitarman_> it says that error: sorry-jockey - SystemnError:InstallArchves()failed
[18:45] <_guitarman_> abogani2: happens when i make any change in restricted hardware. active, deactiveate etc.
[18:45] <methril_work> some kernel release manager here*
[18:46] <methril_work> ?
[18:46] <_guitarman_> i tried to deactivate the b43 and activate the sta wireless driver but it said that error
[18:46] <_guitarman_> abogani2: then when i log out and log back in, i only had sta listed as a choice and i still couldn't activate it
[18:47] <_guitarman_> abogani2: yipes, now my .21 won't boot
[18:47]  * _guitarman_ is screwed
[18:49] <_guitarman_> abogani2: booted into recovery .21 kernel in single user, then telinit 4 , startx and i am in again.  going to see what restricted drivers looks like now
[18:49] <abogani2> _guitarman_: sudo apt-get remove --purge b43-fwcutter
[18:50] <_guitarman_> abogani2: will do that now
[18:50]  * abogani2 goes off for 10 minutes
[18:50] <_guitarman_> abogani2: ok, i've done that
[18:51] <_guitarman_> ugh.
[18:52] <methril_work> what is the process to ask for a update of the luci kernel?
[18:52] <_guitarman_> abogani2: it removed it, tried to load again, and didn't have source for this kernel anymore then tryied it for my rtkernel .33 and that bailed.. now i have bcmwl-kernel-source as a error in dpkg
[18:52] <methril_work> i`ve to fill a bug asking for a release update?
[18:53] <_guitarman_> abogani2: how can i install and activate the broadcom sta wireless driver now - through the hardware drivers applet which doesn't seem tob e working or is there a way to do that in apt
[18:55] <eagles0513875> hey guys i have a question for yall
[18:55] <eagles0513875> what would cause a kernel panic relating to the VFS
[18:55] <_guitarman_> abogani2: will installing broadcom-sta-common and -source get it going?
[18:56] <eagles0513875> _guitarman_: what card
[18:56] <_guitarman_> eagles0513875: BCM4312
[18:56] <_guitarman_> 80211b/g rev01
[18:56] <eagles0513875> _guitarman_: give me a sec
[18:58] <_guitarman_> eagles0513875: the whole problem i am having is kernels 2.6.32-22 and 23-realtime don't boot on my hpmininote... i was trying to see if it was that i was using the b43-fwcutter driver being an issue. but the hardware drivers applet wasn't working proper
[18:58] <_guitarman_> eagles0513875: my 2.6.32-21 kernel boots but even it is sometimes failing and i can then get in via recovery option for the -21 kernel.
[18:59] <_guitarman_> eagles0513875: so i was trying to install and activate it via apt to then reboot and see if that driver ws the cause of hanging boot on 22 and 23
[19:00] <eagles0513875> guitarman i have always used the b43-fwcutter no  problem
[19:00] <_guitarman_> i am trying it out this way to see if that is the issue of the booting no working
[19:01] <eagles0513875> O_o
[19:01] <eagles0513875> booting not working???
[19:01] <_guitarman_> i've just tried to apt-get install the broadcom-sta-common and -source to see if the reboot into kernel -22 and -23 works with it
[19:01] <_guitarman_> eagles0513875: nope - hpmininote won't boot into the -22 and 23 kernels but will boot sometimes into -21
[19:01] <eagles0513875> strange im having other nightmares with lucid on my desktop 
[19:01] <_guitarman_> eagles0513875: i wondered if it was the driver so i tried removing it and rebooting. 
[19:01] <eagles0513875> not wifi related though :( 
[19:02] <_guitarman_> eagles0513875: heheh yeah. good times
[19:02] <eagles0513875> _guitarman_: did you upgrade from karmic to lucid
[19:02] <_guitarman_> eagles0513875: that install worke dfine
[19:02] <_guitarman_> eagles0513875: i did a clean install and had probs!
[19:02] <_guitarman_> funny eh
[19:02] <eagles0513875> what kinda problems outa curiosity
[19:02] <_guitarman_> eagles0513875: the clean install?
[19:03] <eagles0513875> ya
[19:03] <_guitarman_> eagles0513875: oddly my microphone didn't work when it did before (onboard mic)
[19:03] <eagles0513875> using a live usb for me i ended up with a kernel panic something about a VFS not being able to mount
[19:03] <eagles0513875> that was on reboot 
[19:03] <eagles0513875> trying with a cd now to install 
[19:03] <_guitarman_> eagles0513875: oh thats an odd one
[19:04] <eagles0513875> ya
[19:04] <eagles0513875> and i also get file mismatches as well when copying .so files some times which sometimes with constant hitting of retry get copied other times they dont :( 
[19:04] <eagles0513875> knock on wood that hasnt happened yet 
[19:05] <eagles0513875> ive isolated part of my issue to a faulty sata cable
[19:05] <eagles0513875> cant dual boot cuz my cd drive cant read my win 7 dvd
[19:05] <_guitarman_> oh sounds like a bit of a picle
[19:05] <_guitarman_> pickle
[19:05] <eagles0513875> ya
[19:06] <eagles0513875> thought it was the surge protector which didnt protect me 
[19:06] <eagles0513875> which was the case 
[19:06] <eagles0513875> the problem was worse then it is now atm 
[19:07] <eagles0513875> _guitarman_: join me in hi_jack_this
[19:07] <eagles0513875> its just a channel full of tech nuts hehe
[19:07] <eagles0513875> we provide support to each other etc
[19:07] <_guitarman_> heheh interesting
[19:22] <abogani2> _guitarman_: Could you boot your mininote on 2.6.32-22-generic without b43-fwcutter and without STA?
[19:23] <eagles0513875> btw _guitarman_ do you have both of them installed cuz i tried the sta and i had issues with it and it ended up not working so i uninstalled sta and went with the fwcutter
[19:27] <_guitarman_> abogani2: i tried it and it doesn't work
[19:27] <_guitarman_> abogani2: i wonder if there is a loose cable or something ... i'm at a loss.
[19:27] <_guitarman_> abogani2: windows 7 is still on here and it works fine
[19:27] <_guitarman_> :(
[19:27] <eagles0513875> _guitarman_: do you have the same issue with karmic
[19:28] <eagles0513875> here goes nothing on my reboot
[19:28] <_guitarman_> eagles0513875: well this is the odd thing... karmic upgrade to lucid was fine... fresh lucid install was not fine
[19:28] <eagles0513875> O_o
[19:28] <abogani2> _guitarman_: So b43-fwcutter and STA are unrelated.
[19:28] <_guitarman_> good luck on your reboot eagles0513875 
[19:28] <eagles0513875> thanks _guitarman_ :) and so far it is looking good :) 
[19:28] <eagles0513875> yay
[19:28] <_guitarman_> abogani2: i guess thats what this would indicate
[19:29] <abogani2> _guitarman_: Are your sure that STA driver is removed?
[19:39] <_guitarman_> abogani2: well, neither driver shows as active in the hardware drivers app.  i did purge on both but got some errors
[19:40] <abogani2> _guitarman_: c&p on paste.ubuntu.com
[19:41] <_guitarman_> abogani2: ok 1 moment. booting back in
[19:45] <jjohansen> -> Lunch
[19:46]  * smb is out
[19:47]  * JFo wanders off to get headache medicine
[19:47] <_guitarman_> abogani2: http://paste.ubuntu.com/449790
[19:50] <abogani2> _guitarman_: Please remove 33-realtime.
[19:57] <_guitarman_> abogani2: did sudo apt-get remove --purge kxstudio-kernel-realtime-33 ... done
[19:58] <_guitarman_> it still trying to build initial module for 2.6.33-1-realtime
[19:58] <_guitarman_> the bcmwl-kernel-source
[20:00] <abogani2> _guitarman_: reboot and remove b43-fwcutter and bcmwl-kernel source too
[20:01] <_guitarman_> abogani2: ok, will do
[20:02] <abogani2> _guitarman_: I'm wondering where is kxstudio-kernel-realtime-33 package come from?
[20:02] <_guitarman_> isn't it in your repo?
[20:02] <_guitarman_> abogani2: 
[20:02] <_guitarman_> abogani2:  or did falktx put it in his as well
[20:02]  * _guitarman_ wonders
[20:03] <abogani2> I don't have idea what kxstudio stand for...
[20:04] <_guitarman_> k must be for kde
[20:05] <_guitarman_> abogani2: apparently thats done
[20:05] <_guitarman_> abogani2: removed
[20:06] <abogani2> _guitarman_: b43* and bcmwl* too?
[20:06] <_guitarman_> yes
[20:07] <abogani2> _guitarman_: uname -a?
[20:07] <_guitarman_> right now i am in 2.6.32-12
[20:08] <abogani2> _guitarman_: So now we have booting system at least. :-)
[20:09] <_guitarman_> i'm not sure why the realtime still shows in grub
[20:09] <_guitarman_> i removed the package
[20:10] <abogani2> ls -l /boot
[20:10] <_guitarman_> ah .. i searched realtime and see stuff there
[20:10] <_guitarman_> removing
[20:10] <abogani2> _guitarman_: Good.
[20:10] <abogani2> _guitarman_: Try sudo update-grub to be sure.
[20:11] <_guitarman_> thats better
[20:11] <_guitarman_> now only have the -22-lowlatency and -22-tgeneric and -21-generic
[20:12] <_guitarman_> shall i try and reboot now that we have wifi cleared out and realtime kernel removed?
[20:12] <abogani2> _guitarman_: Yes.
[20:12] <abogani2> _guitarman_: 32-22-generic
[20:14] <_guitarman_> rebooting now
[20:15] <_guitarman_> abogani2: stuck again. :(
[20:15] <_guitarman_> i guess its not that
[20:16] <_guitarman_> i wonder what the difference is between the 2 kernels
[20:16] <_guitarman_> abogani2: shall i remove 22 and reinstall it?
[20:17] <abogani2> _guitarman_: No but you can try to update initrd image: sudo update-initramfs -u -k all 
[20:18] <abogani2> _guitarman_: At the end reboot removing quiet and splash options.
[20:18] <methril_work> how you mark a bug as superseed
[20:18] <methril_work> ?
[20:19] <JFo> methril_work, what do you mean superseeded?
[20:19] <methril_work> bug #588832 superseeds #575853
[20:19] <ubot2> Launchpad bug 588832 in linux (Ubuntu Lucid) (and 1 other project) "[Lucid] Update to 2.6.32.14/15 Stable Kernel (affects: 2) (heat: 16)" [Undecided,Fix committed] https://launchpad.net/bugs/588832
[20:20] <JFo> bugs don't really supersede each other
[20:20] <JFo> if one is invalid
[20:20] <JFo> then that should be the status it is changed to 
[20:20] <JFo> with a pointer to the bug that made it invalid
[20:20] <methril_work> if you apply 2.6.32.15. you could close the 2.6.32.12 one
[20:20] <methril_work> ok
[20:22] <methril_work> only release team members are allowed to do that?
[20:22] <_guitarman_> abogani2: thx did that and rebooting and will clear out those options and see what happenes inb the -22 kernel.
[20:22] <JFo> methril_work, I think bugsquad or bugcontrol can
[20:22] <JFo> not sure who else
[20:23] <JFo> I know I can, but not sure which team I get it from
[20:23] <methril_work> also i see the same situation with #583414
[20:23] <_guitarman_> abogani2: its being a real pest... hangs at the same place - ata4:dummy
[20:24] <methril_work> i`m trying to learn the ubuntu-way of bug fixing ;)
[20:24] <JFo> methril_work, are you meaning that they are duplicates in some way?
[20:26] <abogani2> _guitarman_: Could you capture the sreen?
[20:26] <abogani2> *screen
[20:26] <methril_work> JFo: The #575853 refers to update to 2.6.32.12. the #583414 refers to update the 2.6.32.13 and the #588832 refers to update to 2.6.32.14/15
[20:27] <methril_work> JFo: i don`t think are duplicates
[20:27] <methril_work> JFo: but in some way they are
[20:28] <methril_work> the usuall way is to mark them as duplicates?
[20:28] <_guitarman_> abogani2: i don't have a camera
[20:29] <_guitarman_> i can type it if you like into paste.ubuntu.come
[20:29] <_guitarman_> com
[20:30] <_guitarman_> abogani2: working on it now.
[20:31] <abogani2> _guitarman_: The ALT+SysRQ+H don't print anything on the screen?
[20:32] <_guitarman_> abogani2: that does nothing
[20:32] <_guitarman_> its full on locked
[20:33] <JFo> methril_work, no, that is the way things used to work. we are on a no duplication of bugs policy now
[20:34] <JFo> the effort is designed to have all reporters file new bugs per issues
[20:34] <JFo> issue*
[20:35] <_guitarman_> abogani2: almost done typing
[20:35] <_guitarman_> lol
[20:37] <_guitarman_> abogani2: http://paste.ubuntu.com/449810/
[20:38] <_guitarman_> done pheuf.  thats booting the -22 kernel... the 21 boots fine ... i going to lunch now with co-worker
[20:38] <shadeslayer> um ... just to promote my bug : bug 593041
[20:38] <_guitarman_> thx for all your sleuthwork so far abogani2 :)
[20:38] <ubot2> Launchpad bug 593041 in linux (Ubuntu) "New 2.6.35 kernel keeps toggling bluetooth radio (affects: 1) (heat: 6)" [Undecided,Incomplete] https://launchpad.net/bugs/593041
[20:38] <shadeslayer> ive tried the mainline kernel as well... 
[20:39] <abogani2> _guitarman_: :-)
[20:40] <methril_work> JFo, could i promote the bug as fixed or works for me? I would like to help reducing the SRUs
[20:41] <abogani2> _guitarman_: I suspect than the culprit is the line 12
[20:42]  * _guitarman_ hasn't left yet... still chewing on sandwich
[20:42] <_guitarman_> abogani2: b43 ... bug in -22 ?
[20:42] <abogani2> _guitarman_: IMO You shouldn't have that line (aka b43*).
[20:43] <_guitarman_> because we removed it right
[20:43] <abogani2> Exactly.
[20:43] <_guitarman_> i dont understand what went wrong
[20:43] <_guitarman_> what exact command should i run
[20:44] <_guitarman_> i ran the one you suggested
[20:44] <abogani2> _guitarman_: Try to add these lines on /etc/modprobe.d/blacklist.conf:
[20:45] <abogani2> blacklist b43
[20:45] <abogani2> blacklist b43legacy
[20:45] <_guitarman_> ok doing now
[20:45] <abogani2> _guitarman_: blacklist ssb
[20:46] <abogani2> _guitarman_: sudo update-initramfs -u -k all
[20:46] <abogani2> the reboot
[20:46] <abogani2> *then
[20:47] <JFo> methril_work, I usually ping the original reporter asking if it is still an issue in the latest release version
[20:47] <JFo> if so, a test of the latest mainline is in order
[20:47] <JFo> based on the answer, I determine if it can be closed
[20:48] <_guitarman_> ack now no kernels boot - this is before i had a chance to do as suggested.
[20:48] <_guitarman_> abogani2: i am going to hit lunch now since this is going to require a livecd and chroot
[20:48] <_guitarman_> i will let you know if that works after i get back
[20:50] <abogani2> _guitarman_: Ok. 
[21:04] <tgardner> ogasawara, is the one apw was referring to? http://lkml.org/lkml/2010/6/13/155
[21:05] <tgardner> is this*
[21:05] <ogasawara> tgardner: yep, it's already in Dave's net-2.6
[21:05] <tgardner> ogasawara, cool. thanks
[21:05] <ogasawara> tgardner: so I just pulled it from there
[21:05] <tgardner> wfm
[21:51] <manjo> sconklin, you are broken
[22:04] <dgtombs> anyone here willing to help me with ACPI backlight stuff? i want to make a DebuggingBacklight page on the wiki since there seems to be no solid information on how to debug this