[06:50] <smb> morning
[06:55] <dileks> morning has broken, lalala
[06:56] <dileks> ahh, cat stevens
[06:58] <smb> Usually that is: Morning, I'm broken... :-P
[07:01] <dileks> I thought its mostly the software :-)
[07:13] <Nafallo> good morning :-)
[07:22] <smb> Nafallo, A visitor from the past or so... ;)
[07:25] <Nafallo> I never left the channels man :-)
[07:25] <Nafallo> but.. now I need to go to work ;-)
[07:25] <Nafallo> ttyl
[07:26] <smb> see you
[07:26] <smb> Nafallo, (and yeah but you know how invisible quiet people are) ;)
[07:44]  * apw yawns
[07:52] <ppisati> moin
[07:55] <Nafallo> lol
[08:18] <tjaalton> when is the precise-proposed kernel released to -updates?
[08:18] <tjaalton> it has some drm/i915 fixes I'd like to get in
[08:24] <smb> tjaalton, Seems it might wait on cert
[08:24] <smb> So maybe next week?
[08:24] <tjaalton> smb: ok, thanks
[08:24] <henrix> yeah, it should be there next week 
[08:25] <henrix> tjaalton: but you can test it before that :)
[08:25] <tjaalton> henrix: I've asked people to do that, bug 966631 and several dupe candidates :)
[08:25] <ubot2`> Launchpad bug 966631 in xserver-xorg-video-intel "[sandybridge-m-gt2] GPU lockup render.IPEHR: 0x7a000003 with Google Maps(WebGL) in Chromium" [Critical,Fix released] https://launchpad.net/bugs/966631
[08:26] <tjaalton> there are a couple of other commits too that have been verified elsewhere
[08:26] <tjaalton> fixing similar bugs
[08:26] <tjaalton> those can wait for the next iteration i guess
[08:27] <henrix> cool
[08:30] <tjaalton> btw, now that the wacom bamboo updates have been accepted adding intuos5 support is trivial (four commits). would that be accepted by the same criteria as the bamboo ones?
[08:33] <henrix> if these commits are in mainline, you may send them to the kernel-team ML.
[08:34] <tjaalton> yeah they got included in 3.5-rc1, missed the 3.4 queue because of a missing S-o-B :)
[08:35] <henrix> smb: any idea who's maintaining virtualbox?
[08:36] <smb> henrix, community (or virtualbox company)? What does changelog say?
[08:36] <henrix> smb: will check...
[08:36] <henrix> smb: yeah, it looks like its community supported
[08:37] <henrix> smb: there's a bug on it that's triggered by P in -proposed
[08:37] <smb> henrix, The dkms mod failing to compile due to some change?
[08:38] <henrix> smb: no, actually it prevents a shutdown: "unregister_netdevice: waiting for vboxnet0 to become free. Usage count = -1"
[08:38] <henrix> smb: it has been pointed out on the release tracking bug for the precise kernel
[08:39] <henrix> smb: not sure if this actually counts as a regression...
[08:39] <henrix> smb: bug #1009156 if you're curious :)
[08:39] <ubot2`> Launchpad bug 1009156 in linux "linux-3.2.0-25.40: unregister netdevice change breaks VirtualBox" [Medium,Incomplete] https://launchpad.net/bugs/1009156
[08:40] <smb> henrix, IMO I would retarget it to the virtualbox source package which likely produces the dkms which in turn creates the vboxnet module
[08:40] <henrix> smb: yeah, it's open against VB
[08:41] <henrix> smb: but the bug reporter commented on the tracking bug, that's how i found that bug
[08:42] <smb> Ah, ok. Is it obvious what change may have changed the netdev usage?
[08:43] <smb> The question is whether vbox relies on some broken assumption or whether the kernel changes something without knowing all implications.
[08:43] <henrix> yeah, there's a upstreams bug report and there's a patch for that already.
[08:43] <henrix> so, its just a matter of the maintainer picking this patch
[08:43] <smb> Ah ok... 
[08:44] <henrix> basically, its a change in one of the core network apis... which is always a pain for OOT modules :)
[08:44] <smb> henrix, So the history looks like it (vbox) usually is just a syc from Debian
[08:45] <henrix> smb: how can you tell that? by the "unstable" in each entry?
[08:45] <smb> from the version number not having a ubuntux
[08:45] <henrix> ok :)
[08:45] <smb> But also looking at https://launchpad.net/ubuntu/+source/virtualbox/+publishinghistory
[08:46] <smb> Which usually has copied from debian x
[08:46] <henrix> ok, i'll check if this is fixed on debian
[08:46] <dileks> smb: are you still maintaining drm-backports to linux-2.6.32?
[08:47] <smb> dileks, Yes
[08:47] <dileks> good guy - you are
[08:48] <smb> henrix, In the history with the last upload to precise there is an uploader email address which you may contact
[08:51] <smb> dileks, Thanks. :)
[08:52] <dileks> smb: BTW, whats your position to kernel-drm vs. libdrm? note: some Xorg and kernel devs wanted it to be at one place
[08:58] <dileks> oh happy world IPv6 day :-)
[08:58] <dileks> http://www.worldipv6launch.org/
[08:58] <smb> dileks, I do not really have a position there. Note that I maintain the tree (only). Which means adding patches that are asked to be added if the match stable change rules. I am as opinionated as any librarian: which is for the 2.6.32 tree not changing too much. ;)
[08:59] <dileks> best strategy for me in early kms days was - take all from GIT :-) linux-kernel, libdrm, mesa3d and xserver
[09:10] <apw> dileks, happy World IPv6 Launch Day indeed
[10:09] <dileks> hmm, German "Deutsche Telekom" seems to have IPv6
[10:09] <dileks> https://labs.ripe.net/Members/emileaben/growth-in-ipv6-capable-dns-infrastructure
[11:00]  * ppisati -> out for lunch
[11:36] <xnox> is there anything I can do, to help with bug 966248
[11:36] <ubot2`> Launchpad bug 966248 in linux "USB3.0 Ports Not Working" [Medium,Confirmed] https://launchpad.net/bugs/966248
[11:36] <xnox> It affects me and Daviey =)
[12:05] <apw> cooloney, are you really looking at the above bug ? ^^
[12:06] <apw> xnox, i assume you have a precise kernel on there, and that this is new behaviour, can you work out which kernel it did work on before
[12:06] <xnox> apw: I have quantal kernel
[12:08] <apw> xnox, it seems the issue appeared in an update in precise, so if you can test 3.2.0-20.32 and config it is also broken, and then step backwards on the 3.2.0 kernels till it comes back that would help a lot
[12:08] <apw> s/config/confirm
[12:09] <xnox> apw: ok. so do a 'bisect' =) easy way to download all the kernels?
[12:09] <apw> they are all linked from the version page for the kernels, but easy probabally not
[12:09] <xnox> ok
[12:10] <apw> https://launchpad.net/ubuntu/+source/linux
[12:10] <apw> links at the top right to the publishing history
[12:29]  * henrix reboots
[12:36] <[yates]> Hi all, is someone able to look at my acpitables.txt concerning bug #996782 ?
[12:36] <ubot2`> Launchpad bug 996782 in linux "ACPI Errors" [Medium,Confirmed] https://launchpad.net/bugs/996782
[12:50] <jwi> apw: is bug 974830 still on your radar?
[12:50] <ubot2`> Launchpad bug 974830 in xserver-xorg-video-intel "[sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x78170003 using Oracle SQL Developer" [High,Fix released] https://launchpad.net/bugs/974830
[12:57] <apw> jwi, nope lost track of that one completely.  will get the patch rebased and out for review
[13:04] <ppisati> is there a way to tell dpkg-buildpackage to skipabi?
[13:07] <ogra_> yes, its documented in the kernel build wiki :P
[13:07] <ogra_> some env var
[13:10] <ppisati> all the references i found used fakeroot not dpkg-...
[13:11] <ogra_> the vars should be the same though as they should apply to the in-package scripts
[13:40] <cooloney> apw and xnox, yeah, I'm working that USB 3.0 regressions issue
[13:41] <xnox> cooloney: ok cool. thanks =)
[13:41] <cooloney> xnox: sure, i guess you have usb 3.0 hardware, right? as apw pointed out, could you please try the kernel on your hardware
[13:42] <cooloney> xnox: and let us know which one works and which one doesn't
[13:42] <xnox> cooloney: kernel(s). ok.
[13:44] <cooloney> xnox: i really appreciate you can provide such information for us bisect. and please update that in the launchpad page
[13:58] <xnox> cooloney: apw: the publishing history, timesout to render on lp.net due to trying to linkify all 2000 bugs. Is there any other way I can easily get version numbers directly?
[13:59] <xnox> linux-meta timesout as well...
[13:59] <cooloney> xnox: what's kind of version number you want to get?
[13:59] <xnox> cooloney: as per apw: 3.2.0-20.32 and going backwards. Does that mean integer decrements down to 20.1?
[14:00] <xnox> cooloney: stuff that ever got published in precise-*
[14:00] <cooloney> xnox: oh, lp is down, sh*t
[14:00] <apw> xnox, the last number is an upload number so it decrements, but there are not 32 -20 versions
[14:00] <xnox> cooloney: not down, it fails to render linux package publishing history =)
[14:01] <apw> http://kernel.ubuntu.com/~kernel-ppa/info/kernel-version-map.html
[14:01] <xnox> If I grab the precise-proposed linux-meta, will the changelog show the version numbers?
[14:01] <apw> xnox, that above has the numbers which were valid
[14:01] <xnox> yeah! =)
[14:02] <xnox> apw: so I should work down the first table from 3.2.0-20.32?
[14:03] <apw> well assuming that that version fails yes ... 
[14:03] <cooloney> xnox: so you can try 3.2.0-19.31, if it fails, then continue
[14:04] <cooloney> until you find a kernel works on your hardware with USB 3.0
[14:06] <xnox> apw: cooloney: do we have a known version that did work with 3.0 usb hardware? maybe my laptop's usb3.0 didn't work, ever =)
[14:06] <xnox> then my bisect will be pointless
[14:06]  * xnox just got 3.0usb hardware in the mail
[14:07] <cooloney> xnox: actually I'm not sure about this, how about try the first 3.2.0 ubuntu kernel firstly, we can shrink the range then
[14:08] <cooloney> xnox: 3.2.0-8.14 is the first 3.2.0 kernel in Ubuntu
[14:08] <xnox> ok
[14:09] <xnox> cooloney: minimal amount of packages that I need to install?
[14:11] <cooloney> xnox: simply just install linux-image- package is good enough to test
[14:11] <xnox> I'm going with generic image and generic headers
[14:11] <xnox> oh ok.
[14:12] <xnox> Thankfully that is a stable-ish url https://launchpad.net/ubuntu/precise/amd64/linux-image-3.2.0-8-generic/3.2.0-8.14
[14:13] <cooloney> xnox: that's great, just let us know the result.
[14:14]  * xnox reboot
[14:14] <cooloney> in the bug 966248, kernel from 11.10 should works 
[14:14] <ubot2`> Launchpad bug 966248 in linux "USB3.0 Ports Not Working" [Medium,Confirmed] https://launchpad.net/bugs/966248
[14:15] <cooloney> so maybe you can try that kernel if 3.2.0-8.14 doesn't 
[14:15] <cooloney> work
[14:44] <cooloney> xnox: did it work?
[15:00] <xnox> cooloney: so 3.2.0-8.14 works. I am in a meeting now. will do reboots after the meeting.
[15:01]  * ogasawara back in 20
[15:16] <cooloney> xnox: great, thanks a lot. i have to go to sleep. please help to update LP 
[15:35] <apw> bjf, just a heads up i am doing the P highbank config review, so it'd be nice to not have any change in configs
[15:35] <bjf> apw, ack
[16:07]  * ppisati -> gym
[16:07] <tjaalton> is it possible to squeeze individual fixes in the precise-proposed kernel before it hits -updates next week?
[16:10] <henrix> tjaalton: usually these are queued into master-next branch, unless they are critical/security fixes i guess...
[16:10] <henrix> bjf: ^
[16:10] <tjaalton> for instance 80e829fade4e for bug 974830 has been confirmed quite some time ago
[16:10] <ubot2`> Launchpad bug 974830 in xserver-xorg-video-intel "[sandybridge-m-gt2+] GPU lockup render.IPEHR: 0x78170003 using Oracle SQL Developer" [High,Fix released] https://launchpad.net/bugs/974830
[16:12] <henrix> tjaalton: at the moment we have 2 days left for adding these fixes and going through packaging, testing, certification, etc again...
[16:13] <henrix> tjaalton: these fixes could be queued for next cycle and in 3 weeks they would be out in -updates
[16:13] <tjaalton> henrix: hmm ok, maybe that wouldn't be too far then
[16:13] <henrix> tjaalton: anyway, you may try to convince bjf that these fixes *really* need to go in this cycle :)
[16:13] <tjaalton> debian might go for drm from 3.4 :)
[16:14] <tjaalton> but that ship has sailed
[16:16] <tjaalton> henrix: ok, well maybe having some more time wouldn't hurt here
[16:19] <bjf> tjaalton: no, and you are close to missing the window for the next cycle
[16:19] <tjaalton> bjf: ok, when does it close?
[16:20] <bjf> tjaalton: we will start preping the next series of kernels next week
[16:21] <tjaalton> ok, there is now that one commit that has been verified being good, and two others that upstream says are good but not verified by the reporters yet
[16:21] <tjaalton> what is the procedure to get them in the next batch?
[16:22] <tjaalton> cherry-pick email on the list+
[16:22] <tjaalton> ?
[16:22] <bjf> tjaalton: there is a SRU format for patch requests ... https://wiki.ubuntu.com/Kernel/Dev/StablePatchFormat
[16:23] <tjaalton> ok, probably going via the stable queue/release would take too long?
[16:23] <tjaalton> i mean 3.2-stable
[16:24] <bjf> tjaalton: you should make the effort to request inclusion of the patches by upstream stable
[16:25] <tjaalton> yeah I'll do that regardless
[16:26] <bjf> tjaalton, also: https://wiki.ubuntu.com/KernelTeam/KernelUpdates
[16:28] <tjaalton> bjf: yeah, I realized my intuos5 cherry-pick email cut corners in various ways ;)
[16:28] <bjf> tjaalton, if we know ahead of time that you have something that you are trying to get into the next cadence cycle, we can delay the prep to the end of the week
[16:30] <tjaalton> yeah, I'll rebase my branch on top of -next and see how it works
[16:37] <jsalisbury> sforshee, Do you happen to have the type of hardware mentioned in bug 1006427
[16:37] <ubot2`> Launchpad bug 1006427 in linux "(PowerBookG4) Live image won't boot, stuck on "stdin: Not a typewriter"" [High,Confirmed] https://launchpad.net/bugs/1006427
[16:43] <ogra_> haha, entertaining error message though
[16:43] <sforshee> jsalisbury, no, all the mac kit I have uses intel
[16:43] <jsalisbury> sforshee, ahh, ok.  thanks
[16:59] <BenC> What kernel are you guys pushing for in quantal?
[16:59] <ogasawara> BenC: at least the 3.5 kernel, maybe 3.6 if the timing is right
[16:59] <ogra_> 3.5 at least ...probably 3.6 if its there in time
[16:59] <ogra_> snap :)
[16:59] <BenC> Nicely done :)
[17:00] <ogasawara> heh
[17:00] <BenC> Who handles the ports side of things?
[17:00] <BenC> IOW, powerpc
[17:00] <BenC> I want to get a new flavour and it's relevant patches added to the build for quantal
[17:02] <BenC> *its
[17:02] <ogasawara> BenC: it's technically in our tree but supposed to be community maintained/supported
[17:02] <BenC> Right, I want to be that community :)
[17:03] <BenC> Didn't know if there was a goto person for the powerpc kernel stuff
[17:03] <BenC> If not, then I'll be that person
[17:03] <ogasawara> BenC: no go to person that I'm aware of atm.
[17:04] <jussi> benc please! power PC has been missing leadership in an area for ages (IMHO)
[17:05] <BenC> Luckily, I won't be doing this as a community person…it's part of my job to get this stuff integrated, so I'll be able to devote a good bit of time toward it
[17:06] <jussi> BenC excellent :-)  
[17:27]  * henrix will be back in ~30min
[18:34]  * bjf -> dentist
[21:55] <bjf> ogasawara: around ?
[23:23] <jkyle> If I want the most recent, stable kernel would this be the recommended way, or just rolling my own? http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-precise/
[23:30] <bjf> jkyle: ht emost recent, stable kernel is in Precise
[23:31] <bjf> jkyle: if you are looking for the most recent, stable upstream kernel, then yes, that probably is a good one
[23:32] <jwi> 3.4.1 would be an even better one
[23:33] <dileks> looks like the one for quantal is built on a precise host
[23:33] <dileks> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.1-quantal/BUILT
[23:34] <bjf> in <version>-<series> i believe the <series> indicates the ubuntu series the configuration was taken from
[23:34] <bjf> so v3.4-precise used the precise config, v3.4.1-quantal used the quantal config
[23:36] <dileks> OK
[23:36] <dileks> make: *** No rule to make target `build-generic-pae'.  Stop.
[23:36] <dileks> make: *** No rule to make target `binary-generic-pae'.  Stop.
[23:37] <dileks> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.1-quantal/BUILD.LOG
[23:37] <dileks> wasnt -pae flavour dropped for Q?
[23:37] <bjf> dileks, i believe so because we don't support non-pae any more
[23:38] <dileks> might be a relict in the build-script
[23:39] <bjf> could be
[23:39] <dileks> apw: ^^
[23:42] <bjf> 3c06c9edb79d2c887d26b3977c183a2392700209 UBUNTU: [Config] Collapsed generic-pae into generic [i386]
[23:42] <bjf> dileks, ^
[23:44] <dileks> normally an UP machine can use a kernel with PAE support enabled, but I think the upgrade hook-script will not allow an installation
[23:48] <jkyle> jwi: yeah, 3.4.1 would need to be hand rolled though eh?
[23:49] <jwi> jkyle: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4.1-quantal/
[23:50] <jwi> (better install that -extra package as well though :o))