[01:48] <brucezhang> hi all, i have a camera supporting the Mjpeg and H264 format. Now i can play the mjpeg format streaming, but i have no idea to play the h264 format. the linux do not support the h264 format.
[01:49] <brucezhang> Could you give me some advices?
[01:56] <RAOF> I think that it's highly unlikely this is a kernel problem; looking further up the stack is probably what you need to do.
[02:10] <brucezhang> Hi RAOF , thanks for your reply. I want to add MPEG format  to the V4L2 Driver. Do you have any ideas? 
[02:21] <RAOF> brucezhang: Is the V4L2 layer currently incapable of forwarding mpeg streams on?  It's not a problem further up?
[02:30] <brucezhang> In linux driver layer, V4l2 does not support the H264 format.
[02:32] <RAOF> It surely can't be too hard to add that :)
[02:33] <RAOF> You're basically just passing on data from the card, right?  All that's needed is an extension of the content negotiation, and possibly some metadata?
[02:34] <brucezhang> i get data from usb dev.
[02:35] <brucezhang> by the command usb-devices, the MJPEG interface can mount the dirver, but the MPEG interface can not mount the driver.
[09:42] <akgraner> apw - guess what is happening again - but now it's not all the time - and I am trying to narrow down what triggers the temp increase reliably 
[09:43] <apw> akgraner, bah i hate that machine
[09:43] <akgraner> me too
[09:43] <akgraner> just want to give you a heads up
[09:44] <akgraner> as soon as I figure the trigger part - I'll file a bug :-)
[15:07] <mpoirier> sconklin: https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/654590
[15:07] <ubot2> Launchpad bug 654590 in linux-linaro (Ubuntu Maverick) (and 1 other project) "WLAN-BT GPIOs need proper initialization (affects: 1) (heat: 12)" [Undecided,Fix released]
[15:17] <tseliot> apw: did you port this patch of yours to 2.6.37? http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=985f7e2eabee43c30fd3f4d44c8c291c143615f3
[15:20] <apw>  tseliot i believe this is patch is currently missing as it failed to apply
[15:20] <apw> its on my list to fix
[15:20] <apw> tseliot, seeing issues ?
[15:21] <tseliot> apw: ok, I was asking as, after porting some new radeon code to Maverick's kernel, the kernel works well but the ddx driver can't open the drm device
[15:22] <apw> could easily be the issue, i have a crap load of patches on the floor at the moment
[15:23] <tseliot> apw: I'll work on it as otherwise I really wouldn't know what could be causing the issue
[15:23] <apw> want me to have a peek ? 
[15:24] <apw> tseliot, ^^
[15:24] <tseliot> apw: yes, please, help would be welcome :)
[15:33] <tseliot> apw: BTW here's what I get in the X log (i.e. it fails to open /dev/dri/card0): http://pastebin.ubuntu.com/530053/
[17:10] <smoser> jj-afk, smb if you're both about (i realize jj-afk is afk) then we can chat a bit whenever
[17:10] <jj-afk> smoser: i'm here
[17:10] <smoser> smb, ?
[17:10] <smb> Got here
[17:11] <smb> Is it 6pm utc ?
[17:11] <smoser> cool
[17:11] <smoser> no. not for another 50 minutes, but if we're here and available we can get it out of the way
[17:11] <smb> sounds good
[17:11] <smb> just got another cup of tea
[17:12] <smoser> ok. you want to just do it here ?
[17:12] <smoser> i see no reason not to, unless others are annoyed by it
[17:12] <smb> Nah, they are mostly on holiday anyway. :)
[17:12] <smoser> ok
[17:12] <smoser> walking through http://paste.ubuntu.com/530110/
[17:13] <smoser> bug 614853
[17:13] <ubot2> Launchpad bug 614853 in linux-ec2 (Ubuntu) (and 1 other project) "kernel panic divide error: 0000 [#1] SMP (affects: 2) (heat: 22)" [Undecided,New] https://launchpad.net/bugs/614853
[17:13] <smoser> jj-afk, it looks like we've got a functional patch there ?
[17:13] <jj-afk> right I think we have this one
[17:13] <smoser> ok. so you are who supplied the kernel, that wasn't apparent to me
[17:14] <jj-afk> but the question is whether the patch is SRUable
[17:14] <smoser> really ?
[17:14] <jj-afk> yeah sorry, I built that at UDS
[17:14] <smoser> http://launchpadlibrarian.net/58956370/lp614853.patch ?
[17:14] <smoser> kind of looks SRUable to me :)
[17:14] <jj-afk> hehe
[17:14] <jj-afk> we can try
[17:14] <smb> Main question about sru ability is whether upstream takes it
[17:14] <jj-afk> upstream will not take it
[17:15] <smb> have you asked?
[17:15] <smoser> well, this is quite common, so we need to get a fix in for it.
[17:15] <smoser> who do we/I have to beg ?
[17:15] <jj-afk> smb: no but there hasn't been any desire to pickup the 2.6.35 fix that its backported from
[17:15] <smb> I think what jj-afk means is that it only covers things, but does not fix the main issue
[17:16] <jj-afk> smoser: we can send it to gregkh for the stable tree
[17:16] <jj-afk> but with it not going into newer kernels I doubt he will take it
[17:16] <smb> jj-afk, Though he usually wil reject it when there is no upstream
[17:16] <jj-afk> right
[17:16] <smb> yeah
[17:16] <smoser> i've not seen this on maverick (ie, newer kernels)
[17:16] <jj-afk> we can try to push it as an UBUNTU: SAUCE:
[17:16] <smoser> possibly still there, but we dont see it. only on linux-ec2.
[17:17] <smb> We will probably need to see who is upstream for that bit and see whether it is acceptable as temp solution
[17:17] <smb> until they find the real fix
[17:17] <jj-afk> smoser: the schedule is significantly different on newer but it still exists
[17:17] <smoser> well, ok. so will one of you push on that (and put these comments in the bug) ?
[17:17] <smoser> push on that == SRU 
[17:18] <jj-afk> smoser: speaking of which can you bundle and upload the test kernel for me, I haven't been able to get my credentials to work
[17:18] <jj-afk> smoser: yes
[17:19] <smoser> jj-afk, where is that kernel ?
[17:19] <jj-afk> smb, and /me will coordinate
[17:20] <smoser> ok. jj-afk get me a link to your kernel builds for that and i'll get them uploaded
[17:20] <smoser> next bug
[17:20] <smoser> bug 651370
[17:20] <ubot2> Launchpad bug 651370 in linux (Ubuntu Maverick) (and 1 other project) "ec2 kernel crash invalid opcode 0000 [#1] (affects: 7) (dups: 1) (heat: 54)" [Medium,In progress] https://launchpad.net/bugs/651370
[17:20] <smb> I think were only waiting for it to be applied to maverick
[17:20] <smoser> i think we have that ready to go.
[17:20] <smb> (disabling intel_idle for virtual)
[17:20] <smoser> so its in kernel teams tree ?
[17:21] <jj-afk> yes
[17:21] <smb> not yet I believe
[17:21] <smb> mostly due to uds and plumbers
[17:21] <jj-afk> hrmm, I got a merged mail
[17:21] <jj-afk> maybe it was only natty
[17:21] <smoser> and when would the next sru kernel come ?
[17:21] <smb> I think it was for natty
[17:21] <smb> yeah
[17:21] <smoser> ie, when can we have this in ?
[17:21] <jj-afk> but sent for both natty and maverick
[17:21] <smoser> for maverick, when can we have it in.
[17:22] <smb> I ll chat with ogasawara  about it
[17:22] <smoser> ok. thanks.
[17:22] <smoser> next bug
[17:22] <smb> basically I could as well as the acks are there but I don't wan to mess
[17:22] <smoser> bug 567334
[17:22] <ubot2> Launchpad bug 567334 in linux (Ubuntu) (and 1 other project) "blocked tasks delay cloud-init for 240 seconds (affects: 2) (heat: 27)" [Medium,Triaged] https://launchpad.net/bugs/567334
[17:23] <hallyn> looking around the wiki, but not finding:  if I want a valid kernel version for a custom natty tree, how can i name it?  2.6.37-2.10userns1 doesn't work.
[17:23] <smoser> do either of you feel like that might actually be bug 666211 ?
[17:23] <ubot2> Launchpad bug 666211 in linux (Ubuntu) "maverick on ec2 64bit ext4 deadlock (affects: 3) (heat: 28)" [High,Confirmed] https://launchpad.net/bugs/666211
[17:23] <smoser> or that they're the same issue
[17:23] <smb> hallyn, tried +userns1?
[17:23] <smb> smoser, It could be
[17:23] <smb> Not really sure about that, yet
[17:24] <smoser> ok, and we think we have that understood ?
[17:24] <smb> smoser, Though while you said it woul dbe both I only saw lucid feedback i think
[17:25] <hallyn> smb: no, i'd tried '-'.  (but i think that actually failed for a different reason).  '+' works - thanks!
[17:25] <smoser> yeah.. .i'm not sure , i'd have to look at logs again if i've seen it on maverick.  
[17:25] <jj-afk> smoser: I'm actually don't think it is 666211 but that they are related
[17:25] <smoser> ok. and do we think we're moving towards a fix for them ? 
[17:26] <smb> something io related seems to be at least very slow
[17:26] <smb> or deadlocked 
[17:26] <smoser> well, yeah, i think deadlocked.  nothing goes that slow.
[17:26] <smb> but this is not so easy to understeand
[17:26] <apw> smoser, why doesn't 2.6.37-2.10userns1 work, that fits a pattern i use comonly
[17:27] <smoser> hallyn, ^ apw, i think that was to him
[17:27] <apw> jj-afk, i cirtainly did merge that patch for natty, i did not merge it anywhere
[17:27] <smb> smoser, we got similar messages when lucid ext4 had writeback problems. Things would go away eventually but very very slowish
[17:27] <apw> hallyn, yep i meant you
[17:27] <smoser> smb, ok.
[17:27] <smoser> ok. so well, i'll let you move on that one, primarily looking at bug 666211
[17:27] <ubot2> Launchpad bug 666211 in linux (Ubuntu) "maverick on ec2 64bit ext4 deadlock (affects: 3) (heat: 28)" [High,Confirmed] https://launchpad.net/bugs/666211
[17:28] <smoser> and hoping that 651370 is related
[17:28] <smb> I am looking at that but as said progress is slow
[17:28] <apw> hallyn, can you tell me what goes wrong with that version number
[17:28] <smoser> smb, well, jay seems to be responding there, and it seems easily reproducible for him, so maybe we can get to a easy recreate scenario
[17:29] <jj-afk> hrmm, this one is going to be hard
[17:29] <smb> dpepends on how complex the backend with the sql-db is
[17:29] <hallyn> apw: sure, one sec
[17:29] <smoser> smb, right. 
[17:29] <smoser> but hoepfully closer at least.
[17:29] <smoser> bug 613273
[17:29] <ubot2> Launchpad bug 613273 in linux (Ubuntu) "kernel panic on ec2 in system_call_fastpath (affects: 1) (heat: 37)" [Medium,Confirmed] https://launchpad.net/bugs/613273
[17:30] <apw> hallyn, i use lpNNNN commonly as a postfix without issues
[17:30] <smoser> the subject on that is bad, and i'm not sure all my occurences of that should have been considered to be it.
[17:30] <hallyn> apw: solar flares, crack, or hasty mis-parsing of errors.  in any case, it does work now
[17:30] <smoser> but we see panics.  you have either of you have any thoughts on that ?
[17:31] <apw> hallyn, good, it was hurting my head that it might not work
[17:31] <hallyn> it must have all come down to my malformed email address in the trailer
[17:31] <hallyn> but i was sure it first complained about version #...
[17:31] <smb> smoser, I was thinking whether this is still true. cause the last comment was at least a bit older
[17:31] <hallyn> (guess not)
[17:32] <smoser> smb, i think i've seen it recently... i'll check logs 2010-09-16 was last comment, so that wasn't to long ago
[17:33] <smb> jj-afk, knowing the xen code a bit better, would this give some clue to you?
[17:33] <smb> Sort of all I would see it some interrupt handler failing which is the quite obvious
[17:33] <smoser> i'll try to attach more console logs for refernece.
[17:33] <jj-afk> their was something about irqs, I am trying to remember
[17:34] <jj-afk> I remember futzing with panics on fastpaths before
[17:34] <smb> jj-afk, The lost irq problem?
[17:34] <jj-afk> no, I don't think  so
[17:34] <jj-afk> I think it was machine specific
[17:35] <jj-afk> ie it would happen on some machines and not others, kind of like the intel_idle
[17:35] <jj-afk> I need to spend some time digging, and trying to recall
[17:35] <smoser> i'll try to get all logs i have on that, that will give more info for you to look at.
[17:35] <smoser> and then will ping jj-afk for some help (follow the bug)
[17:36] <smb> jj-afk, Agreed, hm. This at least seems to be related with some notify call
[17:36] <smoser> bug 634487
[17:36] <ubot2> Launchpad bug 634487 in sun-java6 (Ubuntu) (and 3 other projects) "t1.micro instance hangs when installing sun java (affects: 20) (dups: 1) (heat: 154)" [Undecided,New] https://launchpad.net/bugs/634487
[17:36] <smb> I think there were at least some useful comments in the bug
[17:36] <smoser> smb, jj-afk you're more than welcome (encouraged) to keep thinking about this, i'm just trying to get jj-afk back to afk and smb to his evening quicker.
[17:37] <smoser> smb, right. for the java b ug, there is some help from the amazon engineers.
[17:37] <smoser> also, the fedora and amazon linux AMIs do not have this issue
[17:37] <smb> By someone who apparently understands a bit more of the xen memory management than /me
[17:37] <jj-afk> right this one is weird, we just need to understand it more
[17:37] <smoser> you think looking at amazon kernel source would be helpful ?
[17:38] <jj-afk> yes
[17:38] <smoser> or you think its just likely too different to add much value
[17:38] <smoser> ok
[17:38] <jj-afk> configs too
[17:38] <smoser> well, please try that...
[17:38] <jj-afk> hehe, yes we will
[17:38] <smb> jj-afk, you need to show me next week how to do that
[17:38] <jj-afk> smb: okay
[17:39] <smoser> jj-afk, launch an ec2 ami from http://aws.amazon.com/amazon-linux-ami/
[17:39] <jj-afk> right
[17:39] <smoser> then, there is some command you can run to get source... it will give you a source rpm
[17:40] <smoser> i forget hwat command , but its in their docs
[17:40] <jj-afk> yep its just remembering the command :)
[17:40] <smoser> bug 614853
[17:40] <ubot2> Launchpad bug 614853 in linux-ec2 (Ubuntu) (and 1 other project) "kernel panic divide error: 0000 [#1] SMP (affects: 2) (heat: 22)" [Undecided,New] https://launchpad.net/bugs/614853
[17:40] <smb> deja vu?
[17:40] <smoser> http://aws.amazon.com/ec2/faqs/#Can_I_view_the_source_code_to_the_Amazon_Linux_AMI
[17:40] <smoser> deja vu indeed
[17:41] <smoser> bug 586530
[17:41] <ubot2> Launchpad bug 586530 in linux-ec2 (Ubuntu) "kernel BUG at /build/buildd/linux-ec2-2.6.32/fs/ext4/inode.c:1852! (affects: 1) (heat: 22)" [Undecided,New] https://launchpad.net/bugs/586530
[17:41] <smb> That seems so old that it could already be resolved
[17:42] <smb> The upstream bug was never really closed due to the reporter there vanishing
[17:42] <smb> But since then a huge pile of ext4 updates went into lucid
[17:42] <smoser> yea... that is what concerned me, is that there seemed a legit upstream bug
[17:42] <smoser> ok.
[17:42] <smoser> i think we close that one as incomplete for now
[17:42] <smb> So we probably should close it with a omment
[17:43] <smb> yeah, I would do that
[17:43] <smoser> well, 2.6.32-305-ec2 is kernel version shown
[17:43] <smb> This was roughly 2.6.32.11 level
[17:43] <smb> were at .25 nowish
[17:43] <smoser> ok. i'll trust you know more on this. i've never seen this one... so, incomplete and move on
[17:44] <smb> bug 660163
[17:44] <ubot2> Launchpad bug 660163 in linux (Ubuntu) "ec2 kernel hang on XENBUS: Waiting for devices to initialize (affects: 1) (heat: 152)" [Low,New] https://launchpad.net/bugs/660163
[17:44] <jj-afk> right this one is I believe a lost interrupt
[17:45] <smb> I am not sure what to say on this one other than strange. ah ok
[17:45] <smb> might be an explanateion
[17:45] <smoser> and do we have fix for that?
[17:45] <smoser> i thought jj-afk had patches or ideas.
[17:45] <smb> I was wondering whether the dom0 xenbus process could be at fault
[17:45] <jj-afk> hrmm, there was a patch that went into stable that I thought would help
[17:46] <jj-afk> smb: possible
[17:46] <jj-afk> the xen devices are split into front and backend and communicate over the xen bus
[17:47] <smb> and iirc that correctly that was some user-space process in dom0?
[17:47] <smb> smoser, how often did you see this?
[17:47] <jj-afk> hrmm, no I think its kernel
[17:47] <smoser> i've never seen this one
[17:47] <smoser> but i do not hit network io hard
[17:47] <smoser> so can one of you at least try to freshen your memory on that one (reading the links posted) and see if you think it might be reasonable to close at this point as "maybe fixed"
[17:47] <jj-afk> that is the problem its rare
[17:48] <smoser> i think maybe i did see it once
[17:48] <smb> smoser, Oh, I assumed as you reported it
[17:48] <jj-afk> smoser: yeah, I'll look again since I was chasing it and thought the patch would come in from stable
[17:48] <smoser> no, if i had reported it it would have kernel version info :)
[17:48] <smoser> jj-afk, thanks.
[17:48] <jj-afk> the big problem again is verifying
[17:49]  * smb wonders whether he looks at the right bug
[17:49] <jj-afk> smb: XENBUS: ...
[17:49] <smb> seeing a reported by scott moser and not any links
[17:49] <smoser> oops
[17:50] <smoser> i was confusing with https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/648721
[17:50] <ubot2> Launchpad bug 648721 in linux-ec2 (Ubuntu) "page allocation failure on machines under heavy network load (affects: 1) (heat: 77)" [Undecided,New]
[17:50] <smb> Oh that one I would say is not a bug
[17:50] <smb> more of a mis-configuration for much network traffic
[17:50] <smb> sort of
[17:51] <smoser> i've only seen the XENBUS once, maybe twice ever , and i think once.
[17:51] <jj-afk> right that is how I was leaning too
[17:51] <smoser> hm..
[17:51] <smoser> so what does that mean ?
[17:51] <smb> jj-afk, I wonder whether the min_free_pages should be modified for instances a bit
[17:52] <smoser> user error ?
[17:52] <jj-afk> basically allocating order 5 is guarenteed to fail at some point
[17:52] <jj-afk> smb: min free pages can be tweaked but that won't help an order 5 allocation when there isn't 32 contiguous pages
[17:53] <smb> That is true. 
[17:53] <smb> Question is why a network thing needs such a huge area
[17:53] <smb> relatively
[17:53] <apw> is that for firmware ?
[17:53] <jj-afk> apw: no, its a nf hook
[17:53] <smb> apw, no maybe nf
[17:53] <smb> netfilter
[17:54] <smb> ?
[17:54] <jj-afk> yep
[17:54] <smoser> ok. so one or both of you update that bug please
[17:54] <smoser> bug 669496
[17:54] <ubot2> Launchpad bug 669496 in linux (Ubuntu) "natty kernel fails to mount root on ec2 (affects: 1) (heat: 437)" [Critical,Confirmed] https://launchpad.net/bugs/669496
[17:55] <jj-afk> works
[17:55] <smoser> ?
[17:55] <smoser> really ?
[17:55] <smb> jj-afk, i try to understand it better and then update tomorry (previous bug)
[17:55] <jj-afk> yep
[17:55] <smb> for me too
[17:55] <smoser> ami ?
[17:55] <smb> at least as described by installing current natty in maverick
[17:56] <smb> used the first one of the dailies showing up...
[17:56] <smb> oh actually I wrote it in the bug I think?
[17:56] <smoser> right, and i tried to reproduce that and it failed for me
[17:56] <smb> or not?
[17:56] <jj-afk> smoser: I used the natty kernel on maverick daily last week and smb booted it today
[17:56] <smoser> i dont come back up at all (using t1.micro though)
[17:56] <smoser> and its not user space in natty
[17:56] <smoser> see my most recent comments in that bug
[17:56] <smb> I used a m1.large
[17:57] <smb> ami-00877069
[17:57] <smoser> right. so i did that with t1.micro 3 times this moring and it never came back up.
[17:57] <smoser> (and no console messages either... our lovely friend for that)
[17:58] <jj-afk> smoser: okay we will give it another round of testing
[17:58] <smb> We can trie again with a t1.micro I guess
[17:58] <jj-afk> yep
[17:58] <smoser> but look at the console logs
[17:58] <smoser> the volume gets mounte dread-write
[17:58] <smoser> and cloud-init even does some work
[17:58] <smoser> but then bad things happen
[17:58] <smoser> and kernel remounts ro
[17:58] <smb> because of io error
[17:58] <smb> that much is understandable
[17:59] <smb> but not really why those io errors happen
[17:59] <smoser> right... so i dont understand how you could suggest that  that is user space or plubming
[17:59] <smoser> nothing should cause that
[17:59] <smb> because it booted for me
[17:59] <smoser> booted once
[17:59] <smb> and I was tinking of something (like udev) in userspace needing to adapt the size of the blkdev
[17:59] <smoser> maybe check that natty isn't runing ureadahead.
[18:00] <smb> as it seems to change from 0 to its actual size somewhere
[18:00] <smoser> ...
[18:00] <smoser> but the poitn at which it goes bad is *so* far up in the boot process
[18:00] <smoser> cloud-init runs at mounted=/ and network up
[18:00] <smoser> so much is already functional at that point
[18:01] <smoser> i just would have thought that any udev issues related to the above would have been past
[18:02] <smb> Lacking the exact details if the init i sort of assumed things went wrong roughly where we pivot over to the real root device
[18:02] <smoser> yeah... i had thought htat too
[18:02] <smoser> but its much further up , now seeing the cloud-init messages there.
[18:03] <smoser> the root device was functional, and lots of things happened before it goes bad
[18:03] <smoser> hmm... 
[18:03] <smoser> but then i see
[18:04] <smoser> "An error occurred while mounting /
[18:04] <smoser> Press S to skip mounting or M for manual recovery
[18:04] <smoser> "
[18:04] <smoser> which i would htink is coming from mountall
[18:04] <smb> Hm, ok. Sadly we only see half of the picture
[18:04] <smoser> i'll poke ther e abit also
[18:04] <smoser> i'll try turning on mountall debug
[18:04] <smb> It could be also from remounting / rw
[18:04] <smb> after the fs ckeck step
[18:04] <smoser> and note, this occurs both on instance store and on ebs
[18:05] <smb> But press s sounds like mountall
[18:05] <smoser> which are different devices in the back
[18:05] <smoser> ok. 
[18:06] <smoser> well, smb jj-afk thanks for your help. 
[18:06] <smb> Ok, so I'll poke around ext4 deadlock, the order 5 allocation and the natty kernel on ec2 more tomoorow
[18:06] <smoser> i'll poke at the natty early next week from the user sapce side.
[18:06] <smoser> i'll send you all my notes too.
[18:07] <jj-afk> alright I'm out of here for the weekend
[18:07] <jj-afk> if there is anything pressing send me a mail it will be checked a few times
[18:07] <smb> jj-afk, You should formulate that more like tim
[18:07] <smb> ;-)
[18:07] <jj-afk> lol
[18:23] <smb> ogasawara, are you around
[18:23] <ogasawara> smb: yep
[18:24] <smb> ogasawara, Just wanted to ask about one sru for maverick (Disable intel_idle). I think we got enough acks for it and it only affects the virtual config.
[18:24] <smb> I believe Brad and Steve are not around today and tomorrow
[18:25] <ogasawara> smb: cool.  yah, bjf has been handling Maverick SRU's and tree maintenance
[18:25] <smb> So just wanted to check with you whether i just can slip it into the tree tomorrow
[18:25] <ogasawara> smb: I'd be cool with that
[18:25] <ogasawara> smb: and I'm sure bjf[afk]  wouldn't mind
[18:25] <smb> And hopefully I won't get into the way of the new process
[18:26] <ogasawara> smb: ahhh right I forgot about the mew process and possibly reverting patches
[18:26] <ogasawara> smb: I think sconklin was planning on reverting any unverified patches on Monday
[18:27] <smb> yes, and we don't know the new process enough ourselves to know how that exactly goes.
[18:27] <smb> probably I should wait then till monday
[18:27] <ogasawara> smb: so he actually might not want new patches applied.  I recall him mentioning having a type of merge window for new SRU patches. 
[18:27] <smb> and write myself an email to make me remember
[18:27] <ogasawara> smb: probably a good idea if it can wait till Monday
[18:28] <smb> Depends on whom you ask as always ;) But I would say yes, it is not super urgent
[18:29] <ogasawara> smb: yah, I've got some Lucid patches I want to apply but am waiting for the green light to push.
[18:30] <smb> ogasawara, yup, feels safer that way
[18:30] <smb> ogasawara, I'll be writing reminder mail to all of us. So we all not forget. :)
[18:31] <ogasawara> smb: sounds good
[18:31]  * apw suspects that this new process is going to exacerbate the need for a next branch for stuff thats ready for the next sru cycle
[18:31] <smb> apw, could as well be done by modifying a proposed branch and merge it back
[18:31] <smb> But that is highly depending on personal taste
[18:31] <smb> iow, not mine to decide. :-O
[18:32] <smb> err meant :-P
[18:32] <smb> bloody o being too close to p
[18:32] <apw> yeah i suspect a next branch is easier process wise.  as we can automate the 'commited' state on rebasing it ... but hey
[18:33]  * smb shudders a bit when hearing rebasing
[18:34] <ogasawara> I really started to like rebasing in Maverick actually, but I think that was more because I was lazy and liked how I could easily edit/drop patches
[18:35] <apw> smb, only next never master, so ust the pending stuff
[18:35] <apw> so next is only a parking place for things with acks
[18:36] <smb> I guess it is really nice when you are the only one mangling the tree. It feels (just a feeling) a bit dirty for a released tree as it looses the info about what happened
[18:36] <smb> apw, Oh, ok. Sounds much better
[18:36]  * smb relaxes
[18:37] <smb> ogasawara, rebasing is a bit like teleporting trees. You are there now but you have no idea how you get there.
[18:38] <bjf> smb, it's still not clear to me how the process will work (i have a batch of upstream stable sitting in my personal repo ready to push), i think after monday's revert run we should be able to get your intel idle in
[18:38] <smb> apw, Reminds me, you see any potter fans queuing up to your place? :) I beleive it was today
[18:38] <apw> right, and only the pending patches which are currently not even seen as they are not anywhere
[18:38] <apw> smb heh not as yet
[18:38] <bjf> smb, I can add the idle patch to my tree as well if that would help
[18:39] <smb> bjf, Sounds cool. If you don't mind i just send that nag mail anyway. Given the state of post-uds memory of mine I forget what I was thinking till then
[18:45] <godber> Anyone have a recommendation for how to isolate this problem? VV
[18:45] <godber> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659422
[18:45] <ubot2> Launchpad bug 659422 in linux (Ubuntu) "Boot failure after upgrading kernel to 2.6.32-25-generic (affects: 4) (heat: 133)" [Undecided,New]
[18:45] <apw> gober idid you get that reproducible again ?
[18:46] <godber> absolutely
[18:46] <godber> I went back and made sure I started fresh on 10.04.1
[18:46] <godber> (I had accidentally started with an old lucid alpha iso)
[18:47] <godber> booting off the latest generic kernel fails
[18:47] <godber> generic-pae does not
[18:48] <godber> as I noted udevadm segfaults about half the time I run it when in the initramfs console
[18:49] <smb> fwiw, I did a i386 generic install just yesterday and got a booted 2.6.32-25-generic
[18:49] <godber> I compared the initramfses between the two versions and they match ... all but the kmodules of course
[18:49] <godber> on VMware ESX 4.1?
[18:49] <smb> no native
[18:49] <godber> works fine native
[18:49] <godber> AFAIK
[18:50] <smb> hm, something stepping on the toes of vmware...?
[18:51] <godber> _shrug_ I guess
[18:51] <godber> it also does not happen on VMware ESX 4.0
[18:52] <godber> I had thought of two possible ways for me to narrow it down
[18:52] <godber> I had considered either rebuilding the kernel eliminating the new patches one by one
[18:52] <godber> or, comparing the configuration differences between the generic and generic-pae kernels
[18:53] <apw> gober that'd be a bisect
[18:53] <godber> apw, thanks, I am somewhat new at this level
[18:54] <godber> is there a handy way to do that?
[18:55] <apw> git bisect does the trick
[18:55] <godber> ok, thanks
[19:16] <godber> is there like a candidate kernel for the next release in a PPA somewhere I can try?
[19:17]  * cking yawns
[19:21] <apw> ts
[19:22] <smb> godber, There is http://launchpad.net/~kernel.ppa
[19:22] <smb> err kernel-ppa
[19:22] <smb> but that is the same release. There is also the mainline kernels
[19:23] <smb> http://kernel.ubuntu.com/~kernel-ppa/mainline/
[19:48] <godber> If I get this isolated down to a specific patch, whats the odds of getting the attention of someone who knows how to fix it?
[21:00]  * ogasawara lunch
[22:43] <rlpb> Any help on getting a panic backtrace out of Ubuntu please? I've tried CrashdumpRecipe but can't seem to get the machine to reboot after panic. I've tried sysctl -w kernel.panic=15 but that didn't seem to work
[23:32] <camden> hi folks
[23:33] <camden> I'm interested in trying out a kernel with the bfs patches, found at http://ck.kolivas.org/patches/bfs/
[23:34] <camden> I'm having some trouble, in that I can't seem to get the patches to apply, I think because the minor version is different. is this something that someone around here has worked on?
[23:45] <camden> nobody?