User1: 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.
User1: Could you give me some advices?
User2: I think that it's highly unlikely this is a kernel problem; looking further up the stack is probably what you need to do.
User1: Hi RAOF , thanks for your reply. I want to add MPEG format  to the V4L2 Driver. Do you have any ideas?
User2: User1 Is the V4L2 layer currently incapable of forwarding mpeg streams on?  It's not a problem further up?
User1: In linux driver layer, V4l2 does not support the H264 format.
User2: It surely can't be too hard to add that :)
User2: 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?
User1: i get data from usb dev.
User1: by the command usb-devices, the MJPEG interface can mount the dirver, but the MPEG interface can not mount the driver.
User3: 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
User4: akgraner, bah i hate that machine
User3: me too
User3: just want to give you a heads up
User3: as soon as I figure the trigger part - I'll file a bug :-)
User5: sconklin: https://bugs.launchpad.net/ubuntu/+source/linux-linaro/+bug/654590
User6: 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]
User7: User4 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
User4: tseliot i believe this is patch is currently missing as it failed to apply
User4: its on my list to fix
User4: tseliot, seeing issues ?
User7: User4 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
User4: could easily be the issue, i have a crap load of patches on the floor at the moment
User7: User4 I'll work on it as otherwise I really wouldn't know what could be causing the issue
User4: want me to have a peek ?
User4: tseliot, ^^
User7: User4 yes, please, help would be welcome :)
User7: User4 BTW here's what I get in the X log (i.e. it fails to open /dev/dri/card0): http://pastebin.ubuntu.com/530053/
User8: jj-afk, smb if you're both about (i realize jj-afk is afk) then we can chat a bit whenever
User8: smb, ?
User9: Got here
User9: Is it 6pm utc ?
User8: cool
User8: no. not for another 50 minutes, but if we're here and available we can get it out of the way
User9: sounds good
User9: just got another cup of tea
User8: ok. you want to just do it here ?
User8: i see no reason not to, unless others are annoyed by it
User9: Nah, they are mostly on holiday anyway. :)
User8: ok
User8: walking through http://paste.ubuntu.com/530110/
User8: bug 614853
User6: 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
User8: jj-afk, it looks like we've got a functional patch there ?
User8: ok. so you are who supplied the kernel, that wasn't apparent to me
User8: really ?
User8: http://launchpadlibrarian.net/58956370/lp614853.patch ?
User8: kind of looks SRUable to me :)
User9: Main question about sru ability is whether upstream takes it
User9: have you asked?
User8: well, this is quite common, so we need to get a fix in for it.
User8: who do we/I have to beg ?
User9: I think what jj-afk means is that it only covers things, but does not fix the main issue
User9: jj-afk, Though he usually wil reject it when there is no upstream
User9: yeah
User8: i've not seen this on maverick (ie, newer kernels)
User8: possibly still there, but we dont see it. only on linux-ec2.
User9: We will probably need to see who is upstream for that bit and see whether it is acceptable as temp solution
User9: until they find the real fix
User8: well, ok. so will one of you push on that (and put these comments in the bug) ?
User8: push on that == SRU
User8: jj-afk, where is that kernel ?
User8: ok. jj-afk get me a link to your kernel builds for that and i'll get them uploaded
User8: next bug
User8: bug 651370
User6: 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
User9: I think were only waiting for it to be applied to maverick
User8: i think we have that ready to go.
User9: (disabling intel_idle for virtual)
User8: so its in kernel teams tree ?
User9: not yet I believe
User9: mostly due to uds and plumbers
User8: and when would the next sru kernel come ?
User9: I think it was for natty
User9: yeah
User8: ie, when can we have this in ?
User8: for maverick, when can we have it in.
User9: I ll chat with ogasawara  about it
User8: ok. thanks.
User8: next bug
User9: basically I could as well as the acks are there but I don't wan to mess
User8: bug 567334
User6: 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
User10: 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.
User8: do either of you feel like that might actually be bug 666211 ?
User6: Launchpad bug 666211 in linux (Ubuntu) "maverick on ec2 64bit ext4 deadlock (affects: 3) (heat: 28)" [High,Confirmed] https://launchpad.net/bugs/666211
User8: or that they're the same issue
User9: hallyn, tried +userns1?
User9: smoser, It could be
User9: Not really sure about that, yet
User8: ok, and we think we have that understood ?
User9: smoser, Though while you said it woul dbe both I only saw lucid feedback i think
User10: User9 no, i'd tried '-'.  (but i think that actually failed for a different reason).  '+' works - thanks!
User8: yeah.. .i'm not sure , i'd have to look at logs again if i've seen it on maverick.
User8: ok. and do we think we're moving towards a fix for them ?
User9: something io related seems to be at least very slow
User9: or deadlocked
User8: well, yeah, i think deadlocked.  nothing goes that slow.
User9: but this is not so easy to understeand
User4: smoser, why doesn't 2.6.37-2.10userns1 work, that fits a pattern i use comonly
User8: hallyn, ^ apw, i think that was to him
User4: jj-afk, i cirtainly did merge that patch for natty, i did not merge it anywhere
User9: smoser, we got similar messages when lucid ext4 had writeback problems. Things would go away eventually but very very slowish
User4: hallyn, yep i meant you
User8: smb, ok.
User8: ok. so well, i'll let you move on that one, primarily looking at bug 666211
User6: Launchpad bug 666211 in linux (Ubuntu) "maverick on ec2 64bit ext4 deadlock (affects: 3) (heat: 28)" [High,Confirmed] https://launchpad.net/bugs/666211
User8: and hoping that 651370 is related
User9: I am looking at that but as said progress is slow
User4: hallyn, can you tell me what goes wrong with that version number
User8: 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
User9: dpepends on how complex the backend with the sql-db is
User10: User4 sure, one sec
User8: smb, right.
User8: but hoepfully zlynch@example.com.
User8: bug 613273
User6: 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
User4: hallyn, i use lpNNNN commonly as a postfix without issues
User8: the subject on that is bad, and i'm not sure all my occurences of that should have been considered to be it.
User10: User4 solar flares, crack, or hasty mis-parsing of errors.  in any case, it does work now
User8: but we see panics.  you have either of you have any thoughts on that ?
User4: hallyn, good, it was hurting my head that it might not work
User10: it must have all come down to my malformed email address in the trailer
User10: but i was sure it first complained about version #...
User9: smoser, I was thinking whether this is still true. cause the last comment was at least a bit older
User10: (guess not)
User8: 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
User9: jj-afk, knowing the xen code a bit better, would this give some clue to you?
User9: Sort of all I would see it some interrupt handler failing which is the quite obvious
User8: i'll try to attach more console logs for refernece.
User9: jj-afk, The lost irq problem?
User8: i'll try to get all logs i have on that, that will give more info for you to look at.
User8: and then will ping jj-afk for some help (follow the bug)
User9: jj-afk, Agreed, hm. This at least seems to be related with some notify call
User8: bug 634487
User6: 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
User9: I think there were at least some useful comments in the bug
User8: 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.
User8: smb, right. for the java b ug, there is some help from the amazon engineers.
User8: also, the fedora and amazon linux AMIs do not have this issue
User9: By someone who apparently understands a bit more of the xen memory management than /me
User8: you think looking at amazon kernel source would be helpful ?
User8: or you think its just likely too different to add much value
User8: ok
User8: well, please try that...
User9: jj-afk, you need to show me next week how to do that
User8: jj-afk, launch an ec2 ami from http://aws.amazon.com/amazon-linux-ami/
User8: then, there is some command you can run to get source... it will give you a source rpm
User8: i forget hwat command , but its in their docs
User8: bug 614853
User6: 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
User9: deja vu?
User8: http://aws.amazon.com/ec2/faqs/#Can_I_view_the_source_code_to_the_Amazon_Linux_AMI
User8: deja vu indeed
User8: bug 586530
User6: 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
User9: That seems so old that it could already be resolved
User9: The upstream bug was never really closed due to the reporter there vanishing
User9: But since then a huge pile of ext4 updates went into lucid
User8: yea... that is what concerned me, is that there seemed a legit upstream bug
User8: ok.
User8: i think we close that one as incomplete for now
User9: So we probably should close it with a omment
User9: yeah, I would do that
User8: well, 2.6.32-305-ec2 is kernel version shown
User9: This was roughly 91.69.162.6 level
User9: were at .25 nowish
User8: ok. i'll trust you know more on this. i've never seen this one... so, incomplete and move on
User9: bug 660163
User6: 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
User9: I am not sure what to say on this one other than strange. ah ok
User9: might be an explanateion
User8: and do we have fix for that?
User8: i thought jj-afk had patches or ideas.
User9: I was wondering whether the dom0 xenbus process could be at fault
User9: and iirc that correctly that was some user-space process in dom0?
User9: smoser, how often did you see this?
User8: i've never seen this one
User8: but i do not hit network io hard
User8: 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"
User8: i think maybe i did see it once
User9: smoser, Oh, I assumed as you reported it
User8: no, if i had reported it it would have kernel version info :)
User8: jj-afk, thanks.
User9: seeing a reported by scott moser and not any links
User8: oops
User8: i was confusing with https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/648721
User6: Launchpad bug 648721 in linux-ec2 (Ubuntu) "page allocation failure on machines under heavy network load (affects: 1) (heat: 77)" [Undecided,New]
User9: Oh that one I would say is not a bug
User9: more of a mis-configuration for much network traffic
User9: sort of
User8: i've only seen the XENBUS once, maybe twice ever , and i think once.
User8: hm..
User8: so what does that mean ?
User9: jj-afk, I wonder whether the min_free_pages should be modified for instances a bit
User8: user error ?
User9: That is true.
User9: Question is why a network thing needs such a huge area
User9: relatively
User4: is that for firmware ?
User9: apw, no maybe nf
User9: netfilter
User9: ?
User8: ok. so one or both of you update that bug please
User8: bug 669496
User6: 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
User8: ?
User8: really ?
User9: jj-afk, i try to understand it better and then update tomorry (previous bug)
User9: for me too
User8: ami ?
User9: at least as described by installing current natty in maverick
User9: used the first one of the dailies showing up...
User9: oh actually I wrote it in the bug I think?
User8: right, and i tried to reproduce that and it failed for me
User9: or not?
User8: i dont come back up at all (using t1.micro though)
User8: and its not user space in natty
User8: see my most recent comments in that bug
User9: I used a m1.large
User9: ami-00877069
User8: right. so i did that with t1.micro 3 times this moring and it never came back up.
User8: (and no console messages either... our lovely friend for that)
User9: We can trie again with a t1.micro I guess
User8: but look at the console logs
User8: the volume gets mounte dread-write
User8: and cloud-init even does some work
User8: but then bad things happen
User8: and kernel remounts ro
User9: because of io error
User9: that much is understandable
User9: but not really why those io errors happen
User8: right... so i dont understand how you could suggest that  that is user space or plubming
User8: nothing should cause that
User9: because it booted for me
User8: booted once
User9: and I was tinking of something (like udev) in userspace needing to adapt the size of the blkdev
User8: maybe check that natty isn't runing ureadahead.
User9: as it seems to change from 0 to its actual size somewhere
User8: ...
User8: but the poitn at which it goes bad is *so* far up in the boot process
User8: cloud-init runs at mounted=/ and network up
User8: so much is already functional at that point
User8: i just would have thought that any udev issues related to the above would have been past
User9: Lacking the exact details if the init i sort of assumed things went wrong roughly where we pivot over to the real root device
User8: yeah... i had thought htat too
User8: but its much further up , now seeing the cloud-init messages there.
User8: the root device was functional, and lots of things happened before it goes bad
User8: hmm...
User8: but then i see
User8: "An error occurred while mounting /
User8: Press S to skip mounting or M for manual recovery
User8: "
User8: which i would htink is coming from mountall
User9: Hm, ok. Sadly we only see half of the picture
User8: i'll poke ther e abit also
User8: i'll try turning on mountall debug
User9: It could be also from remounting / rw
User9: after the fs ckeck step
User8: and note, this occurs both on instance store and on ebs
User9: But press s sounds like mountall
User8: which are different devices in the back
User8: ok.
User8: well, smb jj-afk thanks for your help.
User9: Ok, so I'll poke around ext4 deadlock, the order 5 allocation and the natty kernel on ec2 more tomoorow
User8: i'll poke at the natty early next week from the user sapce side.
User8: i'll send you all my notes too.
User9: jj-afk, You should formulate that more like tim
User9: ;-)
User9: ogasawara, are you around
User11: User9 yep
User9: 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.
User9: I believe Brad and Steve are not around today and tomorrow
User11: User9 cool.  yah, bjf has been handling Maverick SRU's and tree maintenance
User9: So just wanted to check with you whether i just can slip it into the tree tomorrow
User11: User9 I'd be cool with that
User11: User9 and I'm sure bjf[afk]  wouldn't mind
User9: And hopefully I won't get into the way of the new process
User11: User9 ahhh right I forgot about the mew process and possibly reverting patches
User11: User9 I think sconklin was planning on reverting any unverified patches on Monday
User9: yes, and we don't know the new process enough ourselves to know how that exactly goes.
User9: probably I should wait then till monday
User11: User9 so he actually might not want new patches applied.  I recall him mentioning having a type of merge window for new SRU patches.
User9: and write myself an email to make me remember
User11: User9 probably a good idea if it can wait till Monday
User9: Depends on whom you ask as always ;) But I would say yes, it is not super urgent
User11: User9 yah, I've got some Lucid patches I want to apply but am waiting for the green light to push.
User9: ogasawara, yup, feels safer that way
User9: ogasawara, I'll be writing reminder mail to all of us. So we all not forget. :)
User11: User9 sounds good
 * 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
User9: apw, could as well be done by modifying a proposed branch and merge it back
User9: But that is highly depending on personal taste
User9: iow, not mine to decide. :-O
User9: err meant :-P
User9: bloody o being too close to p
User4: yeah i suspect a next branch is easier process wise.  as we can automate the 'commited' state on rebasing it ... but hey
 * smb shudders a bit when hearing rebasing
User11: 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
User4: smb, only next never master, so ust the pending stuff
User4: so next is only a parking place for things with acks
User9: 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
User9: apw, Oh, ok. Sounds much better
 * smb relaxes
User9: ogasawara, rebasing is a bit like teleporting trees. You are there now but you have no idea how you get there.
User12: 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
User9: apw, Reminds me, you see any potter fans queuing up to your place? :) I beleive it was today
User4: right, and only the pending patches which are currently not even seen as they are not anywhere
User4: smb heh not as yet
User12: smb, I can add the idle patch to my tree as well if that would help
User9: 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
User13: Anyone have a recommendation for how to isolate this problem? VV
User13: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/659422
User6: Launchpad bug 659422 in linux (Ubuntu) "Boot failure after upgrading kernel to 2.6.32-25-generic (affects: 4) (heat: 133)" [Undecided,New]
User4: gober idid you get that reproducible again ?
User13: absolutely
User13: I went back and made sure I started fresh on 10.04.1
User13: (I had accidentally started with an old lucid alpha iso)
User13: booting off the latest generic kernel fails
User13: generic-pae does not
User13: as I noted udevadm segfaults about half the time I run it when in the initramfs console
User9: fwiw, I did a i386 generic install just yesterday and got a booted 2.6.32-25-generic
User13: I compared the initramfses between the two versions and they match ... all but the kmodules of course
User13: on VMware ESX 4.1?
User9: no native
User13: works fine native
User13: AFAIK
User9: hm, something stepping on the toes of vmware...?
User13: _shrug_ I guess
User13: it also does not happen on VMware ESX 4.0
User13: I had thought of two possible ways for me to narrow it down
User13: I had considered either rebuilding the kernel eliminating the new patches one by one
User13: or, comparing the configuration differences between the generic and generic-pae kernels
User4: gober that'd be a bisect
User13: apw, thanks, I am somewhat new at this level
User13: is there a handy way to do that?
User4: git bisect does the trick
User13: ok, thanks
User13: is there like a candidate kernel for the next release in a PPA somewhere I can try?
 * cking yawns
User4: ts
User9: godber, There is http://launchpad.net/~kernel.ppa
User9: err kernel-ppa
User9: but that is the same release. There is also the mainline kernels
User9: http://kernel.ubuntu.com/~kernel-ppa/mainline/
User13: 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?
 * ogasawara lunch
User14: 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
User15: hi folks
User15: I'm interested in trying out a kernel with the bfs patches, found at http://ck.kolivas.org/patches/bfs/
User15: 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?
User15: nobody?
ubuntu-kernel
Ubuntu IRC