[00:00] <Kano> but i dont get why newer kernels instantly crash with lenny
[00:04] <Kano> i do not compile anything,but atoms need really long to recompress
[00:08] <jjohansen> back on later
[03:22] <Logan_> Anybody here good with XHCI issues?  There's a bug that has "Fix released," but I find that I still need to use a workaround to fix suspending on my USB 3.0 laptop.
[04:29] <jjohansen> Logan_: update the bug with the information
[08:39] <smb> morning
[08:47] <apw> smb, moin
[08:47] <smb> apw, Got past the signals?
[08:48] <apw> smb, yeah about 20 mins sitting on the rail for nothing while they counted trains
[08:48]  * smb hopes "sitting on the rail" is different from "sitting on the rails"
[08:49] <smb> But yeah, some are very "secure"
[08:50] <smb> One here lets you wait quite long before anything happens. Then with another of those you got 5s between the barrier being down and the train being there.
[08:54] <apw> heh me too
[11:39]  * ppisati -> out for food
[11:43] <cking> download .ddebs -> need a faster pipe
[13:36] <ppisati> apw: btw, i tested the image used by Michael and it's working ok on my panda
[13:37] <ppisati> apw: so, faulty hw or a new hw revision
[13:39] <apw> ppisati, the oneiric one you mean ?
[13:40] <ppisati> apw: uhm... no, it was a natty iirc
[13:40] <ppisati> apw: but natty and oneiric omap4-wise are the same
[13:41] <apw> ppisati, well actually no at the moment oniric is behind natty (which it shouldn't be) ... i am looking at fixing that right now
[13:41] <ppisati> ah ok
[14:04] <apw> ppisati, yeah i am just testing a setup for it like mvl-dove 
[14:18] <apw> tgardner, so we are starting to get excessive skew between natty and oneiric ti-ompa4.  as officially oneiric should be updated before we can SRU, but also becuase we know we are getting an update for Oneiric "shortly" i am proposing we do a mvl-dove style forward port to oneiric.   as an experiment i am looking to do it the same way we do fro the lucid bacports, ie with oneirici1 (no ~) on the end of the version
[14:18] <apw> tgardner, this is starting to skew testing in oneiric it seems
[14:19] <tgardner> apw, TI has promised to come up with a 2.6.39 kernel. we ought to ask Bryan where that is before we put too much effort into it.
[14:20] <cking> apw, ping
[14:20] <apw> tgardner, from waht i can tell, its a ways away, i think we can do this for very little effort, ie effectivly pass it to stable to handle -- once i have this tested.  so far i've spent just 10 mins on setting up an update-from-xxx style tree for it
[14:21] <apw> and its looking like it works ok
[14:21] <tgardner> apw, ok, but does it run on the HW ?
[14:21] <apw> ppisati, any idea how far out the .39 kernel is for ti ?
[14:22] <smoser> smb, https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/614853 . user reporting that they're still seeing that issue with a kernel that should have been fixed
[14:22] <ubot2> Ubuntu bug 614853 in linux-ec2 "kernel panic divide error: 0000 [#1] SMP" [Medium,Fix released]
[14:22] <apw> tgardner, well that is part of the issue, there are compiler issues in the mix here, and unless we're building in the right series the testing is actually useless
[14:22] <tgardner> apw, well, yhou can build in the c-k-t PPA as a test
[14:23] <apw> tgardner, if the priinciple seems sound to you, then yes that is cirtainly the sensible next test step
[14:23] <ppisati> apw: that was yesterday topic and the answer is... unknown
[14:23] <tgardner> apw, if its not too much work then I'm fine with it
[14:23] <ppisati> apw: well, actually linaro has already a .39 kernel
[14:23] <apw> ppisati, your feel?  still at least weeks out ?
[14:24] <cking> apw, want to book those flights before matt closes for business?
[14:24] <apw> cking, yeah if there is a generall arival that saturday before then i guess so
[14:25] <tgardner> cking, apw: plumbers ?
[14:25] <cking> I will book mine and CC you and ask matt to book yours too
[14:25] <cking> tgardner, yep
[14:25] <cking> and pre-kernel sprint too
[14:25] <apw> tgardner, yeah kernel sprint ... what he said
[14:25] <tgardner> cking, ah, I have not encountered tha in my email yet
[14:25] <apw> tgardner, you can practically walk there :)
[14:25] <smb> smoser, Hm, both patches should be in that kernel. Need to check whether it is the exact same place
[14:25] <cking> dude, you need to keep up with your inbox  :-)
[14:25] <ppisati> apw: we won't get it for A2 unfortunately (end of month)
[14:25] <tgardner> apw, its a surprising pain in the ass for me to get there
[14:26] <smoser> smb, i'm commenting. 
[14:26] <tgardner> cking, 6 days off produced over 700 emails. blech
[14:26] <ppisati> apw: jcrigby has a .39 linaro kernel
[14:26] <apw> ppisati, blimey ... 
[14:26] <ppisati> apw: but that doesn't even boot on my board
[14:26] <apw> ppisati, and that is no good for our use ?
[14:26] <apw> BAH
[14:26] <ppisati> apw: actually i would like to get t ASAP
[14:26] <cking> tgardner, that's why I loathe taking a vacation ;-)
[14:27]  * apw goes away to VENT about how useless that makes the linaro kernel
[14:27] <tgardner> cking, I usually keep up while traveling, but wilderness rafting doesn't really lend itself to electronic communications.
[14:27] <smoser> smoser, commented. i think its user error, or at very least there is user error involved
[14:27]  * cking nods
[14:29] <smb> smoser, Wait... that trace is from -312 and the patch went into -313
[14:31] <smb> smoser, Ok, saw you commented the same...
[15:25] <sforshee> tgardner, could you accept my natty nomination on bug #767192 ?
[15:25] <ubot2> Launchpad bug 767192 in linux "Wireless flaky on Acer Aspire 5100 after installing Natty" [Medium,Fix released] https://launchpad.net/bugs/767192
[15:28] <tgardner> sforshee, done
[15:53] <ppisati> nuntio vobis gaudium magnun: it _seems_ we are going to get 3.0 for oneiric/ti-omap4 too
[15:54] <ppisati> but no ETA yet
[16:46] <sconklin> smb: Your email about the xenmotion and patch, is that a recommendation to publish it or to not publish it? 
[16:46] <smb> sconklin, To publish. Actually there has been one verification by now
[16:46] <sconklin> or rather to verify or not to verify, upon which publishing will be decided
[16:47] <sconklin> ok, thanks!
[16:47] <sconklin> I'll nudge that along
[16:47] <smb> Cool thanks
[17:36] <smoser> smb, do you have thoughts on bug 784937 ? I'd rather have hte kernel "fixed" than work around it.
[17:36] <ubot2> Launchpad bug 784937 in cloud-init "/mnt not mounted, swap not used, disk is xvde" [Medium,Confirmed] https://launchpad.net/bugs/784937
[17:37] <smb> smoser, The only thought currently is that I had not thought much about that one...
[17:37]  * smb looks
[17:37] <smoser> verified its still in Ubuntu 3.0-0.1-virtual 3.0.0-rc2
[17:39] <smb> smoser, Could this be something related to that unplug unnecessary thing? That it does not give you sda because it would be the same as xvda...
[17:40] <smb> And the other thing would be, why directly specifying devices, and not uuid or label?
[17:40] <smoser> i dont know. i suppose it could be.
[17:41] <smoser> well, 2 things lead me to care about a name
[17:41] <smoser> a.) xen is stupid, amazon followed xen's lead, and they allow a user to specify "--device" when they attach a volume.
[17:42] <smoser>   the expectation is that that device, will then be what appears in the guest
[17:43] <smoser> b.) in this init case (trying to mount swap), cloud-init is reading the metadata service for "swap", which says "sda2".  It then translates that to xvda2 if there is no sda2.
[17:43] <smoser> but i'd like to avoid more hacks and translations
[17:45] <smb> Ok, I can understand that. Hm, at least the start it odd at first glance... But need to read a bit more details...
[17:59]  * apw calls its a day ... have a good weekend all
[18:00] <smb> apw, same thing
[19:04] <highvoltage> howdy, is there a kernel parameter I could use to disable scsi emulation for usb mass storage devices?
[19:04] <jjohansen> sconklin: could you accept nomination for Bug#798860 and Bug#789409
[19:04] <sconklin> jjohansen: sure, stand by
[19:05] <highvoltage> (I have a sd card reader that shows up as sda on some laptops and it's messing with my d-i mojo since it's preseeded to install to sda)
[19:05] <sconklin> #798860 #789409
[19:05] <jjohansen> sconklin: thanks, you can ignore the accidental oneiric tick, sadly I can't delete nomination mistakes
[19:06] <sconklin> got the first one, there is no 789409
[19:07] <jjohansen> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/789409
[19:07] <ubot2> jjohansen: Error: <Bugtracker.plugin.Launchpad instance at 0x8d65a2c> bug 789409 not found
[19:07] <sconklin> doesn't look good
[19:07] <jjohansen> sconklin: there really is, I am looking at it the browser
[19:07] <charlie-tca> Is it private?
[19:08] <jjohansen> ah yes, but its not supposed to be
[19:08] <jjohansen> sconklin: try now
[19:09] <vish> hi, while building the kernel deb, i get a lot of questions (y/n) or (M/n)  … is it OK if I choose 'y' for all and 'M' when y is not available?
[19:09] <sconklin> jjohansen: all done, I went ahead and declined the Oneiric one so it wouldn't be hanging
[19:09] <jjohansen> vish: maybe, its usually safe to choose the default
[19:10] <jjohansen> sconklin: thanks
[19:10] <jjohansen> vish: if you just hit enter you get the default
[19:10] <vish> jjohansen: how do i know which is default? 
[19:10] <vish> jjohansen: ah ok.. :)
[19:10] <jjohansen> vish: it will be the one that is capitalized
[19:10] <vish> thx..
[19:10] <jjohansen> highvoltage: none that I know of
[19:11] <vish> k..
[19:11] <highvoltage> jjohansen: ok thanks
[19:12] <sforshee> tgardner, for the rt2800 firmware updates I started on last week, I discovered that hardy lbm does not include the drivers. Are we no longer updating compat-wireless in hardy? Because if not there's no point in adding the firmware.
[19:14] <tgardner> sforshee, I don't think I ever bothered with Hardy compat-wireless. Lucid shold be sufficient;y old enough for CW backports
[19:16] <sforshee> tgardner, ack. I'll send out the pull requests for lucid and maverick shortly.
[19:23] <tgardner> sconklin, do we have a test victim for the USB 3.0 regression? it should be fixed in 2.6.38.8, right?
[19:25] <sconklin> tgardner: I can't remember, but I think there may still be another patch required after .8. I haven't worried about it because we just reverted it all. We'll circle back after we get these releases out.
[19:27] <sconklin> tgardner: the last time I checked was a week or so ago and one of the fix patches wasn't even in Linus's tree yet
[19:28] <tgardner> sconklin, ok, I'll roll a 2.6.38.8 without the xhci patches
[19:40] <vish> check-config: FAIL: value CONFIG_SECURITY_YAMA y
[19:40] <vish> check-config: FAIL: value CONFIG_DEFAULT_SECURITY_APPARMOR y
[19:40] <vish> check-config: 26/28 checks passed -- exit 1
[19:40] <vish> make: *** [config-prepare-check-generic] Error 1
[19:40] <vish> while building i get that^ error; how do i fix that? 
[19:40] <vish> building kernel*
[19:45] <vish> i could probably comment it out of /config/enforce , but Apparmor is required for security right?
[19:52] <jjohansen> vish: define required.  It is required for apparmor make, but you still have unix DAC without it
[19:52] <jjohansen> vish: what kernel are you building?  I assume upstream?
[19:53] <vish> jjohansen: required as in; "if i dont have it, bad men will take control of my system" :D
[19:53] <vish> jjohansen: maverick, trying to bisect between .35 and .34
[19:54] <jjohansen> vish: ah, if you are bisecting and debugging I wouldn't worry about yama, or apparmor, they are added near the end of the stack of commits so they will disappear
[19:55] <vish> jjohansen: ok, cool, thanks.. will comment it out.. (the problem started between those kernel and persists even in .39 , so trying to figure out the commit)
[19:55] <jjohansen> vish: you can build without those by putting skipconfig=true on the command line
[19:55] <jjohansen>  eg.  skipconfig=true fakeroot debian/rules binary
[19:56] <vish> oh, k. will do that for the next build.. i just commented it out and its building \o/
[19:56] <jjohansen> you may also need skipmodule=true skipabi=true
[19:57]  * vish makes note
[19:57] <jjohansen> vish there are also files you can touch/modify to get the same effect but if you aren't building a ppa, just putting those on the command line is good enough
[19:58] <vish> jjohansen: nah, not in ppa, just local build
[20:00] <vish> lp hates me atm, i dput the upload and it stops at the last 1 kb and just gets stuck forever, did that like 5 times already o.0
[20:09] <jjohansen> vish: sadly that happens to more than just you
[20:10] <jjohansen> or maybe not so sadly, depending on your pov.  ie. lp hates more than just you :)
[20:10] <vish> lol!!
[21:56] <CarlFK> natty loaded snd-hda-intel - todays oneiric 3.0-1 does not, so no sound.  
[21:56] <CarlFK> should I report this somewhere?