[01:16] <Redoubt> How does one go about testing a DRM module change? It's obviously always in use...
[02:56] <Devin_> hello whats up?
[02:57] <Devin_> I gotta a question if anyone thinks they can give me a hand?
[07:24] <smb> Morning
[07:24] <ppisati> moin Stef
[07:24] <smb> Ah Paolo, already awake?
[07:25] <ppisati> yep
[07:25] <smb> I am still on it... ;)
[07:25] <ppisati> :)
[07:25] <ppisati> woke up at 6:49 but it was so dark outside
[07:26] <ppisati> went back and forth from bed to kitchen a couple of times
[07:26] <ppisati> till i decided i was fully awake :P
[07:26] <smb> Not sure that helps with the daylight. :) Its ready to get winter ... or so...
[07:27] <ppisati> i like winter :)
[07:27] <ppisati> i like rain, mist and cloudy water
[07:27] <smb> you're weird... :-P
[07:27] <ppisati> yes i am :)
[07:28] <smb> unless... there is a plan behind it to have reasons to warm up somebody else... ;)
[07:29] <ppisati> :O
[07:29] <ppisati> no plan, and no one :)
[07:30] <smb> C'mon, you are Italian, there is always a plan and probably not a *single* one. :-P
[07:31] <ppisati> really
[07:31] <ppisati> no plan this time
[07:31] <ppisati> :)
[07:32] <smb> :) Oh well, alright. Let's stop the prejudice and wishful thinking for a bit.
[07:34]  * apw yawns
[07:34] <smb> apw, Morning sir
[07:34] <apw> morning
[08:51] <ppisati> bug 869198
[08:51] <ubot2> Launchpad bug 869198 in linux-ti-omap4 "CVE-2011-1021" [Medium,Invalid] https://launchpad.net/bugs/869198
[08:51] <ppisati> [flag@newluxor ubuntu-cve-tracker]$ grep launchpad retired/CVE-2011-1021  https://launchpad.net/bugs/869198
[08:51] <ubot2> ppisati: drivers/acpi/debugfs.c in the Linux kernel before 3.0 allows local users to modify arbitrary kernel memory locations by leveraging root privileges to write to the /sys/kernel/debug/acpi/custom_method file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4347. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1021)
[08:51] <ubot2> Launchpad bug 869198 in linux-ti-omap4 "CVE-2011-1021" [Medium,Invalid]
[08:51] <ppisati> ?!?!
[08:53] <ppisati> lp 869234
[08:53] <ubot2> Launchpad bug 869234 in linux-ti-omap4 "CVE-2011-2482" [Medium,Invalid] https://launchpad.net/bugs/869234
[08:53] <ppisati> [flag@newluxor ubuntu-cve-tracker]$ grep launchpad retired/CVE-2011-2482  https://launchpad.net/bugs/869234
[08:53] <ubot2> ppisati: ** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem.  When the candidate has been publicized, the details for this candidate will be provided. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2482)
[08:53] <ubot2> Launchpad bug 869234 in linux-ti-omap4 "CVE-2011-2482" [Medium,Invalid]
[08:54] <ppisati> ?!?!
[08:58] <ppisati> apw: CVE-2011-1021
[08:58] <ubot2> ppisati: drivers/acpi/debugfs.c in the Linux kernel before 3.0 allows local users to modify arbitrary kernel memory locations by leveraging root privileges to write to the /sys/kernel/debug/acpi/custom_method file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-4347. (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1021)
[09:20] <ogra_> ppisati, uuh, scary ... we should fix acpi asap on arm :P
[10:01] <Saviq> hey, I've encountered a bug with smbd using the kernel from ppa:ubuntu-x-swat/q-lts-backport
[10:01] <Saviq> would here be a good place to let someone know about it?
[10:01] <Saviq> https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1053414
[10:01] <ubot2> Launchpad bug 1053414 in samba "smbd crashed when trying to connect from Ubuntu" [Undecided,New]
[11:20] <tjaalton> smb: hey, still have issues with rs690m not working on quantal?
[11:23] <tjaalton> (bug 1029582)
[11:24] <ubot2> Launchpad bug 1029582 in xserver-xorg-video-ati "Unusable graphics with ATI RS690M" [High,Confirmed] https://launchpad.net/bugs/1029582
[12:18]  * henrix -> lunch
[12:40] <smb> tjaalton, I'd need to re-install quantal on that machine as I needed it for other testing. Last time I looked there were there. As well as the cirrus driver crashing when starting unity (since Xen would not use cirrusdrm+modeset)
[12:43] <rtg> henrix, rebooting gomeisa for kernel update
[12:44] <tjaalton> smb: ok, testing the daily livecd would be nice. looks though that it's a kernel bug :)
[12:45] <smb> tjaalton, how can accelerated X be a kernel bug if there is no kernel drm driver?
[12:45] <smb> Oh, well there is for the Dell
[12:46] <tjaalton> smb: no I mean the radeon one
[12:46] <smb> yeah
[12:51] <rtg> ayan, henrix: rebooting tangerine for kernel update
[12:51] <henrix> rtg: ack
[13:23] <rtg> jsalisbury, I bounced tangerine. but didn't notice until too late that you had a bunch of open sessions. hope I didn't wreck anything.
[13:24] <jsalisbury> rtg, nah
[13:42] <smb> tjaalton, Ok, so the daily cd still has some breakage on the dell 1521. Lets see whether I could get an install done... though hard with those randomly missing letters...
[13:44] <smb> "rom this ... r i you re ready, you can installl Ubuntu alongside or instead o your current operating system  his shouldn t take too long."
[13:52] <ppisati> rtg: didn't you have a mail exchange with rsalveti about this?
[13:52] <ppisati> lp 960770
[13:52] <ubot2> Launchpad bug 960770 in linux-ti-omap4 "Packages requiring dkms at Pandaboard (omap 4) will also pull linux-headers-generic because current dkms dependencies" [Medium,New] https://launchpad.net/bugs/960770
[13:52] <rtg> ppisati, not that I remember, but it's possible
[13:55] <rtg> ppisati, hmm, so I kind of vaguely remember something about this. how are you proposing to fix it  in the kernel packaging ?
[14:03] <apw> isn't that a dkms dep issue ?
[14:05] <ppisati> i remember i sent an email with a patch, but you rejected it and replied with another solution
[14:05] <ppisati> let me try to find it...
[14:11] <ppisati> http://ubuntu.5.n6.nabble.com/PATCH-0-2-P-omap4-debian-ti-omap4-control-housekeeping-td4644385.html
[14:11] <ppisati> rsalveti: ^
[14:11] <ppisati> rtg: ^
[14:15] <ppisati> and the threads stopped there, if you can agree on a solution, that would be good
[14:16] <rtg> ppisati, I think I agreed that its a dkms problem :)
[14:17] <ppisati> let see what rsalveti has to say so i can close the ti-omap4 side of it
[14:18] <ppisati> infinity: don't you use panda and P/omap4 for builders? do you use the ondemand governor? have you ever hit this?
[14:18] <ppisati> lp 971091
[14:18] <ubot2> Launchpad bug 971091 in linux-ti-omap4 "Pandaboard ES freezes with the default CPU scaling governor ondemand" [Medium,Confirmed] https://launchpad.net/bugs/971091
[14:21] <rsalveti> ppisati: rtg: yeah, it's a dkms problem
[14:22] <rsalveti> it shouldn't pull any specific headers, specially as it's smart enough to rebuild/build any module once a headers package is installed
[14:24] <ppisati> infinity: never mind
[14:25] <ppisati> rsalveti: lp bug status updated
[14:29] <ppisati> lp 1029730
[14:29] <ubot2> Launchpad bug 1029730 in linux "linux-image-$(uname -r) should suggest linux-headers-$(uname -r)" [Medium,In progress] https://launchpad.net/bugs/1029730
[14:29] <ppisati> apw: ^
[14:30] <apw> ppisati, yes ?
[14:30] <ppisati> apw: any update on that?
[14:35] <smb> tjaalton, Ok, since forcing on a 3.2 kernel to the quantal userspace fixes the graphics issues I changed the package to the kernel one. Not that that makes it less X guys domain thing for me. (And whoever renamed "older kernels" to "with additional options" in grub deserves a bit of a smack imo, just saying)
[14:43] <ppisati> the last Natty kernel has already been uploaded, right? so no more natty spins at all, right?
[14:43] <ppisati> herton: ^
[14:43] <ppisati> henrix: ^
[14:43] <herton> ppisati, yep
[14:43] <ppisati> cool
[14:43] <henrix> ppisati: right
[14:58]  * ogasawara back in 20
[14:59] <Devin_> Hey whats up
[15:03] <skaet> rtg, what changed with that lastest kernel update (-22)?   I just applied it,  and am black screen on boot up.
[15:04] <rtg> skaet, kamal's i915 patches are wrecking the world. we're working on it.
[15:05] <rtg> skaet, you're kind of late to the party. How often do you update ?
[15:06] <skaet> rtg, , daily.  But seem to have had some glitch on the updates.
[15:07] <rtg> skaet, have you booted with -21 to make sure its not an intermittent issue ?
[15:09]  * skaet experimenting
[15:25]  * kamal seriously considers just calling in sick today :-(    what a mess
[15:26] <kamal> skaet: questions if you could determine whether the problem is in .21 also, that would be *very* helpful (one set of i915 patches went into .21, then another went into .22 -- I'm hoping the problem is isolated to .22)
[15:26] <kamal> s/questions/questions:  #1/
[15:27] <kamal> skaet: question #2:  the black screen problem ... does it *stay* black, or does it light up again when it reaches the X login screen?
[15:28] <Devin> Hey can I get a hand compiling a kernel
[15:30] <skaet> kamal,  it stays black.        Trying get 15.21 on the system now. 
[15:31] <kamal> skaet: ok, thanks very much
[15:33] <tjaalton> smb: thanks for testing, now you could also check a newer mainline kernel to see if it's fixed there :)
[15:35] <smb> tjaalton, Yeah, yeah. Maybe when I get bored... iow not today. :-P
[15:36] <tjaalton> smb: heh, sure
[15:43] <Devin> Hello, whats up, anyone around that could give me a hand with kernel compiling and update
[15:50] <jjohansen> ogasawara: hey so I am not going to request IMA for quantal, it forces tpm on, and there have been issues in the past that cause slow boot and suspend/resume failures. They are most likely dealt with but there isn't enough information, and its too late to be testing with this release
[15:50] <jjohansen> instead I am just going to set up a ppa and point people to that
[15:51] <rtg> jjohansen, there appears to be some effort going into IMA for 3.6 (and I assume 3.7).
[15:51] <jjohansen> rtg: yep, there is the ima appraisal stuff, and a few other patches
[15:52] <rtg> jjohansen, IMA is on my list of things to get smart about for ubuntu-r
[15:56] <jjohansen> rtg: ah mine too
[15:57] <rtg> jjohansen, I'm convinced that its gonna be required in certain scenarios. The fed already has an attestation specification that I was reading about last week.
[15:59] <jjohansen> rtg: yeah I think so too
[15:59] <ogasawara> jjohansen: ack, thanks
[16:08]  * ppisati -> gym
[16:11] <cking> just hope IMA doesn't suck loads of memory like it used to
[16:12] <rtg> cking, lets hope it doesn't just plain suck like it used to :)
[16:13]  * herton -> lunch
[16:13] <cking> heh
[16:13] <jjohansen> cking: that has been fixed, enabling it does have some overhead, it expands the inode some, but the radix tree has been replaced with an rbtree, and there have been several locking improvements as well
[16:14] <cking> jjohansen, ah good, the radix tree was a memory hogger
[16:15] <jjohansen> cking: yep, and so was having to track each inode externally. Expanding the inode reduced the total overall cost at the expense of chewing up 16 or so bytes/inode even if ima is not in use
[16:16] <cking> jjohansen, ok, so some minor impact on small memory systems then
[16:17] <jjohansen> cking: yes unfortunately
[16:18] <jjohansen> cking: this isn't exactly what is there now but it is a pretty good guide to how the fixes changed it https://lkml.org/lkml/2010/10/18/644
[16:19] <cking> nice
[16:26] <Redoubt> Hello all. Is there a standard way to test a new direct rendering manager module?
[16:28] <Redoubt> I can't simply unload the currently running module, as it's in use. But lsmod doesn't tell me what's using it
[16:29] <mjg59> echo 0 >/sys/class/vtconsole/vtcon1/bind
[16:29] <mjg59> The console is running on it
[16:29] <mjg59> You'll want to do that over ssh
[16:32] <Redoubt> mjg59: Thank you!
[16:32] <hggdh> ogra_: bug 1054143 is still there today
[16:32] <ubot2> Launchpad bug 1054143 in debian-installer "armhf-omap4: 20120921 daily server image fails to install with "no kernels found"" [High,New] https://launchpad.net/bugs/1054143
[16:33] <ogra_> hmpf
[16:33] <ogra_> hggdh, ok. will look into it 
[16:34] <genii-around> Has usbcore module been superceded by wusbcore?
[16:36] <genii-around> Or, rather, what module to use now to globally disable autosuspend for USB instead of usbcore which seems not to exist anymore.
[16:47] <ogra_> hggdh, hmm, seems the whole pool is missing on the arm images 
[16:49] <hggdh> ogra_: not published?
[16:49] <ogra_> http://cdimage.ubuntu.com/ubuntu-server/daily/current/quantal-server-amd64.manifest vs http://cdimage.ubuntu.com/ubuntu-server/daily/current/quantal-server-armhf+omap4.list
[17:04] <skaet> rtg,  .21 was even worse (black screen, no sound).   been working with  kamal,    Going back to 14 gets my desktop working again.
[17:05] <kamal> rtg: ... and given that, I'm afraid we'll probably need to revert *both* sets of backlight patches :-(
[17:06] <rtg> kamal, I'm OK with that given the carnage they have caused. lets make sure skaet's machine works well without them first, OK ?
[17:06] <kamal> rtg: I'm going to prep a test kernel of that for skaet
[17:06] <kamal> yeah.  that.
[17:07] <skaet> rtg,  kamal, - am standing by to test
[17:07] <kamal> skaet: thanks for your help (and sorry for the mess!)
[17:26]  * rtg -> lunch
[17:46] <skaet> kamal,  rtg - bug 1055665 opened to track issue
[17:46] <ubot2> Launchpad bug 1055665 in linux "After applying update to 3.5.0-15.22, black screen on boot." [High,New] https://launchpad.net/bugs/1055665
[18:11] <skaet> kamal,  confrim http://people.canonical.com/~kamal/backlightrevert/ boots up ok on the acer
[18:12] <kamal> skaet: ok, thanks
[18:12] <kamal> rtg: ok, what's the procedure for the revert?  should I file a pull request with the reverts, or do you just drop the offending commits, or what?
[18:12]  * cking ~=+> EOD
[18:13] <rtg> kamal, just send a pull request with the reverts. we might rebase them out of existence on a subsequent upload, but for now we'll likely keep the reverts in this upload in order to be clear about what we're doing.
[18:13] <skaet> rtg, kamal,  also what sort of ETA on when we can have the new version uploaded?   Will want this included in the candidate images
[18:14] <rtg> skaet, likely today.
[18:14] <rtg> ogasawara, agreed ? ^^
[18:14] <ogasawara> rtg: yep, we can get it in today
[18:15] <skaet> infinity, ^ trigger for the images.
[18:15] <ogasawara> skaet, infinity: would you prefer we upload straight to the release pocket, or still cycle through -proposed
[18:15] <kamal> rtg: excellent plan
[18:16] <skaet> ogasawara, unless infinity feels strongly otherwise go to release pocket.
[18:16] <ogasawara> skaet: ack
[18:16] <rtg> ogasawara, looks like the reverts shouldn't be an ABI bumper
[18:16] <ogasawara> rtg: ok good
[18:18] <ogasawara> rtg: I'm only going to upload these reverts and hold everything else that's already on master-next until post Beta-2
[18:18] <infinity> ogasawara: If it's an ABI bump, toss it to proposed, so I can get my ducks in a row.
[18:18] <infinity> ogasawara: If the reverts don't break ABI, release is dany.
[18:18] <rtg> ogasawara, um, I think we need the EFI handover protocol patch, don't we ?
[18:18] <infinity> dandy, too.
[18:19] <ogasawara> rtg: apw and I discussed that we'd prefer not to shove that up until we let it cook a bit
[18:19] <ogasawara> rtg: it's completely untested at this time
[18:19] <rtg> ogasawara, ok, works for me
[18:24]  * rtg starts MB replacement...
[18:31] <ogasawara> kamal: if you can, ping me when you've sent the pull request so I know to immediately begin prepping the upload
[18:32] <kamal> ogasawara: sure will
[19:03] <kamal> ogasawara: just sent the pull-request (cc'd you)
[19:03] <kamal> rtg ^^
[19:03] <ogasawara> kamal: thanks
[19:09] <rtg> ogasawara, if you're doing the packaging, then I'll go back to my MB upgrade....
[19:09] <ogasawara> rtg: yep, I'm on it already
[20:23] <ogasawara> skaet, infinity: kernel is uploaded, I'll need it approved in the queue.
[20:23] <ogasawara> kamal, rtg: fyi ^^
[20:24] <rtg> ogasawara, ack
[20:24] <ogasawara> infinity: it's not an ABI bumper, so I uploaded straight to the release pocket
[20:25] <kamal> ogasawara: thanks -- sorry for the kaffuffle
[20:26]  * rtg thinks kamal has a beer debt :)
[20:27] <kamal> rtg: its gonna be a lot of beer, but I know the kernel team will be up to the task.
[20:28] <rtg> kamal, you coming to Denmark ?
[20:29] <kamal> rtg: nope, I'll have to pay off my debt next time.   geez, how much will I owe by *then*?
[20:29] <rtg> compounded interest...
[20:43]  * rtg -> EOD
[20:45] <jwi> kamal: oh, backlight series went boom? that didn't take long :)
[20:47] <kamal> jwi: sadly, no, not long at all.  (and not just the two extra patches you pointed out -- the biggest failure involved the first set I tried to jam in)
[20:51] <jwi> kamal: if you're planning to give it another shot at some point, maybe throw 770c1231 on top. afair the commit msg doesn't really tell the whole story.
[20:51] <kamal> jwi: I definitely am planning to give it another shot, so thanks -- I'll have a look
[20:52] <jwi> and fwiw, the biggest failure is intel backlight in general ;). i think they still have that whole inverted backlight thing to fix.
[22:52] <skaet> rtg, kamal - new built kernel was available for updates,   did the update, applied it,  and system booted up fine. 
[22:52]  * kamal exhales ... thanks skaet!
[22:52] <skaet> :)