[06:57] <MTecknology> wow.. it's unreal how busy the kernel ML is
[07:22] <amitk> MTecknology: lkml?
[07:33] <MTecknology> amitk: on lists.ubuntu.com
[07:33] <MTecknology> amitk: and the bugs running through ~ubuntu-kernel-team
[07:35] <amitk> yeah, it has certainly grown over time
[07:37] <MTecknology> I decided to hop out of ~ubuntu-kernel-team and hop into teams that are more specific to my interest - probably not a big deal considering the lack of involvement I've had.
[07:38] <MTecknology> I aimed too high - tried to do too much stuff - and now I have simple projects that are over a year old and still unreleased :(
[07:40] <MTecknology> ok.. nappy time
[08:24] <apw> drew212, yes if your touchpad is missing a bug is needed
[08:28] <ikepanhc> apw: about bug 634702
[08:28] <ubot2> Launchpad bug 634702 in linux (Ubuntu) "Kernel 2.6.35-19 fails to boot Lenovo S10-3 (affects: 1) (heat: 8)" [Critical,In progress] https://launchpad.net/bugs/634702
[08:29] <ikepanhc> I believe the new module intel_idle is the root cause
[08:29] <apw> ikepanhc, interesting
[08:29] <ikepanhc> but dont know much about the module, any idea who we shall ask?
[08:30] <smb> I guess it would be something to bring up on the acpi mailing list
[08:30] <ikepanhc> The S10-3 use N450 as CPU
[08:30] <smb> Maybe cc Len Brown
[08:30] <apw> well if we have proven its the cause, like via black-listing, then acpi list sounds good, and the authors of course
[08:30] <smb> good morning btw... :)
[08:31] <apw> moin
[08:31] <ikepanhc> good morning .eu :)
[08:31] <ikepanhc> will write to Len Brown
[08:31] <ikepanhc> you guys have any N450 machine?
[08:31] <smb> ikepanhc, But don't forget linux-acpi, I want to watch the thread. ::)
[08:31] <apw> ikepanhc, i would email the authors of the commit which adds it
[08:32] <apw> cc: acpi and len, its the authors who are most likely to have a clue
[08:32] <ikepanhc> I wonder it happens on all N450 machine or only S10-3
[08:32] <smb> Hm, No I only have old 270s
[08:32] <apw> ikepanhc, i would not be supprised if it is all, perhaps a search for those symptoms may help
[09:16] <kengyu> ikepanhc, iirc, samos is N450?
[09:47] <jmg> hi all
[09:47] <jmg> i need to do an instruction trace on the kernel
[09:48] <jmg> what debugger should i use?
[09:48] <jmg> kdb and kgdb dont seem to be in the repos
[10:02] <jmg> hmm
[10:02] <jmg> hi balbir
[10:20] <balbir> jmg: hi
[10:21] <jk-> jmg: what are you looking to do?
[10:21] <jk-> (ie, what would you like to trace? or do you want to step through a particular function?)
[10:21] <jmg> get an instruction trace for usb-storage operations
[10:22] <jmg> so i can figure out what instructions to use in a tool im writing
[10:23] <jmg> the instruction trace for overwriting a file would get me a long way
[10:23] <apw> sounds like you want a usb trace more than an instruction trace
[10:24] <jmg> i cant read usb
[10:24] <jmg> if i could, that would help
[10:29] <apw> there is some way to trace usb traffic
[10:29] <jmg> yeah i saw it
[10:29] <jmg> debugfs
[10:29] <smb> https://wiki.ubuntu.com/Kernel/Debugging/USB
[10:30] <TeTeT> are there any known USB problems in the Lucid kernel, especially on T61/x61? A customer reports problems on 3G (USB), printers (USB) and wonders if there's a known issue
[10:31] <smb> TeTeT, Vaguely known at most. I think I remember some reports but not really details
[10:31] <smb> And it depends an "problems"
[10:31] <smb> problem not being detected at all or traffic problems
[10:32] <TeTeT> smb: problem as in arbitrarily happening losses of devices, e.g. 3g no longer working, printing not possible
[10:33] <TeTeT> smb: I try to get more details from the customer, but they have themselves problems collecting detailed information from the field
[10:35] <smb> TeTeT, Those rather not known and may be device specific or not. Can you make sure problems are reported for each device (if it is not something like all usb traffic is broken after some time)
[10:35] <TeTeT> smb: yes, will file bug reports as soon as I get enough details
[10:37] <jmg> ok the usb trace
[10:37] <RAOF> Hm.  How can I work out what's the most recent commit in the drm-intel kernel PPA build?
[10:39] <RAOF> Or, more specifically, how can I tell whether the commits that should fix bug #600453 have landed in there.
[10:39] <ubot2> Launchpad bug 600453 in linux (Ubuntu) "[arrandale] [i915] DELL E6510: blank screen on boot (Intel GPU) (affects: 16) (heat: 143)" [High,Confirmed] https://launchpad.net/bugs/600453
[10:42] <jmg> i cant read it :(
[10:44] <apw> RAOF, there is a COMMIT file in the newer result directories which have the commit id which was built
[10:45] <apw> RAOF, the latest build is in 'current' always
[10:45] <cking> apw, where is the list of current kernel team bugs for maverick?
[10:47] <smb> cking, https://wiki.ubuntu.com/Kernel/Tagging
[10:49] <jmg> f***ing usb, how does it work?
[10:56] <apw> jmg, heh now that is is a big question
[10:56] <smb> jmg, Have you looked at the link I posted?
[10:56] <apw> not sure what you think you'll find from an instruction level trace thats going to be easier to understand
[10:56] <smb> (assuming you have problems getting the trace)
[10:56] <apw> i thought there was a library for interacting with usb devices
[10:57] <apw> libusb i think is the one, perhaps that would have documentation too
[11:03] <jmg> smb: yes
[11:05] <jmg> libusb is what i will use to write my tool
[11:05] <jmg> one i know what to send
[11:06] <jmg> once*
[11:08] <jmg> maybe i should just read the usbms spec heh
[11:21] <apw> cking, bouncy?
[11:50] <apw> mjg59`, just saw your backlight writeup, has the kernel side stuff hit mainline>
[11:50] <apw> (it sounds like a very sane approach to the moras)
[12:16]  * apw lunches
[12:33] <mjg59`> apw: Not yet
[12:51]  * smb is back
[12:54] <apw> mjg59`, ta for the info, very interesting none the less
[12:59] <DrKenobi> Hi! I'm looking the log of the meeting about bug triage of last Saturday. Where can I find it?
[13:03] <smb> http://irclogs.ubuntu.com/2010/09/11/%23ubuntu-classroom.html
[13:03] <smb> DrKenobi, ^
[13:06] <DrKenobi> smb, thanks! great! I think it would be great to have this link at https://wiki.ubuntu.com/Kernel/BugTriage/Summit/Maverick It would be helpfull
[13:07] <smb> DrKenobi, I guess you will have the power to do that. ;-)
[13:08] <DrKenobi> I can? OK, I'll try. Just a basic question: this is automatically generated, or someone has to copy/paste?
[13:09] <smb> These are automatically generated daily by channel (I guess limited to ubuntu channels)
[13:10] <smb> This channel is there as well
[13:11] <DrKenobi> Great. I knew the chat the channels history (log?) was stored, but I never found it. Thanks.
[13:30] <mjg59`> apw: Needs to go through Richard Purdie's tree, and I think he's stuck in Portland at the moment
[13:49] <n1ght0wl> hey guys.
[13:50] <n1ght0wl> i saw strange kernel oopses with maverick kernel tag 2.6.35-20.29 from ubuntu-maverick repository built on ubuntu-lucid on x86_64.
[13:50] <n1ght0wl> kernel oops can be achived by running lshw command which in most cases hangs and cannot be killed using kill -9.
[13:53] <apw> n1ght0wl, yes that one we know about, the fix should be in the -21.30 kernel when it hits the archive
[13:54] <n1ght0wl> apw: thanks.
[13:54] <n1ght0wl> apw: is there any url related to this problem?
[13:56] <n1ght0wl> is this it?
[13:56] <n1ght0wl> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/636679
[13:56] <ubot2> Launchpad bug 636679 in linux (Ubuntu) "[119903.693261] BUG: unable to handle kernel NULL pointer dereference at 00000008 (affects: 1) (heat: 6)" [Undecided,New]
[13:59] <n1ght0wl> thanks alot guys!
[14:16] <apw> tgardner, ok talked to cjwatson and it seems that now that linux-libc-dev is bumped to -803 we cannot upload anything (for armel) which is lower than that, full stop
[14:16] <apw> tgardner, the recommendation is therefore to bump the abi component for linux-libc-dev above that for the maverick master
[14:17] <apw> tgardner, he has given me some techniques to use for that, so am going to try them out
[14:17] <apw> what a mess
[14:21] <tgardner> apw, I think we need a bodge in the rules that checks for master which is the only branch that should build linux-libc-dev
[14:22] <apw> tgardner, yeah i am also liking that idea ... explode on build
[14:22] <apw> i'll do that as well
[14:31] <apw> ogasawara, fyi armel maverick is failing, know what it is and am working on it
[14:49] <cnd> pgraner, what's the status on the firmware updates?
[15:58] <pgraner> cnd, no status yet, keep with what we have for now
[15:59] <cnd> pgraner, you're killing me :)
[17:32] <tgardner> apw, I have 2.6.36-rc4 amd64 natty kernels on tangerine.buildd:~rtg/natty/kern if you'd like to experiment with your i915 issues
[17:50] <apw> tgardner, sounds interesting
[18:28] <sconklin> apw, ogasawara: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/629711
[18:28] <ubot2> Launchpad bug 629711 in linux (Ubuntu Maverick) (and 2 other projects) "[Maverick] Removing external display on Vostro 3500 corrupts the screen (affects: 1) (heat: 8)" [High,Triaged]
[18:33] <ogasawara> sconklin: thanks, looks like that patch just landed in 2.6.36-rc4 and Cc'd stable
[18:33] <sconklin> ogasawara: cool. That was in the queue for the bugchat we didn't have today, so I wanted you to know
[18:33] <ogasawara> sconklin: I'm going to wait a few days and hope the 2.6.35.5 stable lands so we can rebase Maverick before freeze
[18:33] <ogasawara> sconklin: so we might get it for free, regardless I'll build them a test kernel with the patch
[18:34] <apw> ogasawara, just waiting on the last test build before i ship you the ti-omap-disaster patches
[18:35] <ogasawara> apw: cool, I was going to apply you patch and re-upload to get armel building again as well as having the kernel rebuilt against the latest gcc
[18:37] <Sarvatt> apw: regarding the mainstream kernels, comedi should be fixed now  - http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=10022a0675a8f8722068d956a798f1fddb02e71c
[18:37] <apw> Sarvatt, in theory the patches should self-stop applying
[18:38] <Sarvatt> oh, nice!
[18:38] <Sarvatt> not sure if it was even still being applied, i just noticed it upstream
[18:39] <apw> if you look at that one, its gone ... all by itself ... http://kernel.ubuntu.com/~kernel-ppa/mainline/v2.6.36-rc4-maverick/
[18:39] <Sarvatt> awesome :)
[18:39]  * apw pats self on the back, the first time its worked :)
[18:53] <kees> smb: when do you want to do the next kernel security update?
[18:54] <smb> kees, want? (must be a trick question) We likely want the current lucid proposed in updates
[18:54] <kees> smb: heh. I guess I mean "when would it be best?" :P
[18:56] <smb> kees, I guess so. :) I will have a look at the sru status tomorrow and then its probably worth starting to pass some processing on to bjf and sconklin this time.
[18:56] <kees> okay, cool
[19:01]  * apw wanders off to gte some food in
[19:03]  * tgardner lunches
[19:03]  * smb wander towards eod
[19:06] <bjf> ogasawara: am doing some patchwork cleanup
[19:06] <bjf> ogasawara: i'm looking at "musb: move usb_add_hcd to the core init code from gadget code (v2)" by Bryan Wu which you have under review
[19:07] <bjf> ogasawara: was it really a pull request or just a discussion?
[19:09] <ogasawara> bjf: I think it was just a discussion and last I remember bryan was still waiting for feedback
[19:09] <bjf> ogasawara: can I also mark the "xsave" patches as rejected?
[19:09] <ogasawara> bjf: not till kernel freeze
[19:10] <ogasawara> bjf: as it was dependent on them getting us test cases by kernel freeze if I'd consider applying to maverick or not
[19:10] <ogasawara> bjf: for lucid SRU they're a nack
[19:10] <ogasawara> s/lucid/maverick
[19:11] <bjf> ogasawara: ah, your waiting for the winged pigs to appear
[19:11] <ogasawara> bjf: exactly :)
[19:11] <ogasawara> bjf: so I'll mark them as rejected on thurs
[19:11]  * cking calls it a wrap
[19:11] <bjf> np
[19:50] <smoser> apw, jjohansen says there is some kernel/upstart bug that is related to bug 606373
[19:50] <ubot2> Launchpad bug 606373 in linux-ec2 (Ubuntu Maverick) (and 3 other projects) "cloud-init output does not get to console when booted with pv-grub and ramdisk (affects: 1) (heat: 73)" [Undecided,New] https://launchpad.net/bugs/606373
[19:50] <smoser> do you happen to know that bug number ?
[19:51] <apw> bug #554172
[19:51] <ubot2> Launchpad bug 554172 in upstart (Ubuntu Maverick) (and 5 other projects) "system services using "console output" not starting at boot (affects: 208) (dups: 16) (heat: 924)" [Medium,Fix released] https://launchpad.net/bugs/554172
[19:51] <apw> smoser, ^^
[19:52] <smoser> danke
[19:53] <jjohansen> yeah
[20:15]  * ogasawara lunch
[20:41] <jjohansen> -> Lunch
[21:54]  * jjohansen -> running errand back in a bit
[22:08] <bjf> ogasawara: i'm confused by lbm version numbers I'm seeing
[22:08] <ogasawara> bjf: for which release?
[22:08] <bjf> ogasawara: lucid
[22:09] <bjf> ogasawara: if I bring up the "Synaptic Package Manager" and type in "linux-backports-modules-alsa" in the "Quick search" box ..
[22:09] <bjf> ogasawara: I see modules with the description of "Backported drivers for alsa-driver snapshot"
[22:10] <bjf> ogasawara: as well as "Ubuntu supplied Linux modules for version 2.6.32 ALSA snapshots."
[22:10] <bjf> ogasawara: 2.6.32-25.22 is what I just recently uploaded and was built, I don't know what these "2.6.32.25.27" versioned packages are
[22:11] <ogasawara> bjf: that looks like the meta package version
[22:11] <bjf> ogasawara: there is a lbm meta package?
[22:12] <ogasawara> bjf: the linux-meta package generate lbm meta packages
[22:12] <bjf> huh
[22:23] <bhuey> got an nvidia module crash
[22:23] <bhuey> softirq hang
[22:26] <bhuey> trying to file a bug report is a pain
[22:26] <bhuey> anybody ?