[08:09] RAOF_, was that another i915.powersave i saw you handing out? [08:09] (on #ubuntu-devel ?) [08:44] apw: Frustratingly slowly, yes. [08:44] heh ... i did see some teeth being pulled [08:44] RAOF, what was it on ... [08:45] A 4 series card. Let me grab the bug. I'm pretty sure it'll be covered by our existing stuff. [08:45] * apw bounces [08:45] I can still get a nouveau noaccel quirk into the kernel, can't I? [08:46] The final kernel upload is tomorrow morning? [08:50] apw: Yeah, there it is. GM45. https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/555503 [08:50] Malone bug 555503 in xserver-xorg-video-intel "screen flickers at least once every few minutes" [Medium,Confirmed] [08:50] RAOF, and that is already covered ... ? why didn't the user have it [08:52] They were on the -19 kernel. Have we pushed the powersave quirk to the -20 kernel? [08:56] * apw actually has lost track after the kitten killer yesterday [08:56] * apw checks [08:56] I can't see anything in the changelog. [08:57] RAOF, no the change was to disable FBC for those sets not powersave [08:58] Ah, right. [08:58] bug #538648 is what I'm thinking of. [08:58] Malone bug 538648 in xserver-xorg-video-intel "[gm45] Irregular sync flashes with compiz on (Lenovo T500)" [Medium,Triaged] https://launchpad.net/bugs/538648 [09:01] the bug there does not have the upstream infor on powersave in it does it? [09:02] hrm thats oddd, its longer now, much longer ... launchpad what are you up to? [09:03] RAOF, so in short if they need powersave = 0 we arn't expecting to need to fix them [09:04] Because the symptoms are insufficiently bad? [09:04] RAOF, no simply because we are unaware the issues still exist and have no bugs open on linux (that i am aware of) to change it, and no patch out there for testing [09:05] Ok. [09:05] final freeze kernels close today ... so i don't know if we can get it in before release [09:05] as its not stopping them booting it can easily be an SRU after release of course [09:05] Yeah. [09:06] and indeed has a simple work around, which we could releasenote [09:20] apw: Will the nouveau acceleration disabling patch make it into lucid? Are you waiting for anything from me for that? Splitting it into the components looks like an excelent idea. [09:20] https://lists.ubuntu.com/archives/kernel-team/2010-April/009884.html and its follow ups. [09:21] RAOF, i already split it up and pushed it back for review. i hope it has all the required ack and [09:21] am intending on merging it today ... for the final kernel [09:21] its all a bit behind due to yesterdays thinkpad debackle [09:21] Yeah, that was mad. [09:22] we tend to get at least one a cycle ... its hard to avoid [09:22] i am very glad it was this week and not next [09:22] OOoooh, yes. [09:23] and in part was why i pushed half the update last friday instead .. [09:23] Can I add an extra quirk - bug #542950 would like GeForce 6100 cards (pciid 0242) quirked. [09:23] Malone bug 542950 in linux "[Needs noaccel quirk] Screen corruption on startup" [High,Confirmed] https://launchpad.net/bugs/542950 [09:30] RAOF, do we have a patch for that? [09:30] We don't; I can generate one easily though. [09:31] can you test the final patch ? [09:31] I cannot. However, setting nouveau.noaccel=0 has been reported to work by multiple people. [09:32] thats tricky ... after yesterday i am nuvous of breaking people ... get the patch out ... and we can look it over. i am sure it'll be 'ovvious' [09:32] if you get it out i presume on top of the other one (that was nouveau right) [09:32] then i can make a kernel and ask for testing ... and we can make a decision later today [09:34] It'll be an extra patch on top of your existing 3 in the series. Is there an easy way to apply them on ubuntu-lucid? [09:42] save them into a mailbox and git am the mailbox [10:47] * apw wonders if akgraner tested that kernel [10:48] i'd like to get that patch into the kernel and some testing feedback would help [10:55] hi there [11:11] hi [11:15] apw: is it to late for include a driver in the initrd [11:15] Bug #530361 [11:15] Malone bug 530361 in linux "Support for DELL H200/H700/H800 SAS cards is missing in the CD/DVD installer for Lucid (mpt2sas)" [Undecided,New] https://launchpad.net/bugs/530361 [11:17] jjohansen, you know just how late it is in the cycle! [11:17] as its a CD driver for a dell server we might be able to do something [11:17] as they are likely just hosed without it [11:17] however, that is predicated on it being a simple fix [11:17] if its 'whole replacement driver' its not going to make the release images imo [11:18] apw: yes, and I expect no but I just got the Q in my inbox and figured I'd ask [11:18] looking at the bug i don't see anything other than 'its broken' so its hard to evaluate whether there is a possibility or not [11:19] finally it may just be that the driver is not in the udebs [11:19] jjohansen, do we have someone who has one who can answer some of these questions? [11:19] from the bug that we actually ship the driver its just not in the initrd [11:20] not that I know of but I'll poke and see [11:22] it does appear that we have the driver building [11:22] debian.master/config/config.common.ubuntu:CONFIG_SCSI_MPT2SAS=m [11:22] obj-$(CONFIG_SCSI_MPT2SAS) += mpt2sas.o [11:23] it appears to be called mpt2sas [11:23] and we don't appear to put it in the installer stuff [11:23] yep, there are reports of using it to "fix" the problem, its just not in the initrd [11:23] right, or the installer [11:23] so if that the only issue then it is fixable i'd say ... but why the hell can't people ask last week not this [11:24] jjohansen, so who asked [11:25] ttx [11:25] ttx should know better [11:25] i even sent out an email last week saying the deadline was here [11:26] right, but everyone else is focused on a thursday deadline, so that gets forgotten [11:28] the thurday deadline doesn't mean thursday for _anyone_ really [11:28] * apw needs more brown brain fuel [13:16] Hello there [13:21] hello [13:30] It's probably not the right place to ask for help but I'm trying to build NetworkManager from the upstream source tree and I'm having trouble with the wireless-tools [13:30] http://pastebin.com/rmUedvqs [13:36] mirsal, that normall implies there is a -dev package [13:36] you probabally want to ask about that on #nm on this server [13:37] apw, yeah, usually there is, but I can't find it [13:37] apw, I just asked there. No reply so far :) [13:37] * apw swears ... that updated EC fix works for dells and doesn't break thinkpads ... but still breaks damn macs [13:38] (your last two words summarize an awful lot of issues) [13:39] apw, very odd [13:39] apw, ah ! found it, thanks [13:39] libiw-dev - Wireless tools - development files [13:40] go figure ;x [13:40] mirsal, 'so' obvious [13:46] hmm, why I did not think about apt-get build-dep is another story... [13:53] smb: Hi Stefan! I'm wondering if you could sponsor me (for PPU right on linux-rt package https://wiki.ubuntu.com/AlessioIgorBogani/linux-rtPPUApplication) adding your comments about Feisty-Gutsy-Hardy period... [13:55] abogani, I guess I can, but you better mail me a reminder to look at it. I am currently at the airport and I'd rather do it with a bit more time later [13:55] smb: Of course, thanks! [15:34] hm, is there a way to get dev_dbg() statements in usb to display on console? [15:35] maybe just pass 'debug' on the kernel command line? [15:36] achiang, do they not appear in dmesg output? [15:37] if they are in there you probabally can get them on the console direct via loglevel, if i've understood [15:37] apw: haven't confirmed, i'm just doing some drive-by triaging on https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/433438 [15:37] Malone bug 433438 in linux "device descriptor read/64, error -110" [Medium,Confirmed] [15:38] apw: in my 5 minutes of reading, that message is due to an urb timeout of some sort [15:38] so i was just going to suggest something that the bug reporters could do to get some more info before someone who's really on the kernel team can take a look [15:39] soz can't be more authorative on that [15:41] "soz" ? [15:54] short for sorry [15:54] heh, thanks [16:48] Hello all. Amitk suggested it would be a good idea to say hello to you all and introduce myself. My name is Lee Jones. I have recently accepted a role within Canonical as an Arm Kernel Engineer, with a view to start at the beginning of May. [16:53] kaouthia, awesome ! i see you are also in #ubuntu-arm already :) [16:54] Yes, and ubuntu-meeting (a bit too keen me thinks) ;) [16:58] I would like to pick your brains if I may. I have to purchase a laptop and I’m finding it difficult to choose. I would like something which compiles Kernels quickly and is going to last. Do any of you have any suggestions you’d like to make? I hear a lot of you like ThinkPads - anything in particular? [16:59] * ogra doesnt lkie thinkpads ... i tend to buy whitebox systems to be able to replace parts if they get outdated ... but then i'm not a kernel guy i just happen to hang around here to annoy apw for ARM stuff :) [16:59] *like [17:00] kaouthia: building kernels quickly requires lots of cores and fast I/O, so something with Core i7 and an SSD would be good [17:02] generally i don't build on my laptop, the disk is just too slow [17:02] your best bet is probably getting a fast desktop and a cheap laptop for travel, actually [17:02] yeah i have a "desktop replacement" latop i use as my 'home machine' a 10" laptop for travel, and use remote machines for build generally [17:03] apw: distcc? [17:03] fast local CPUs + fast I/O + ccache generally outperforms distcc, at least in my experience [17:04] abogani, nothing so sophisticated, just porters really [17:04] apw: right [17:05] achiang: Obviously ccache and distcc have different goals so I don't think that you can compare these. [17:05] i am more of a ccache user myself [17:06] not that i see a whole heap of difference to be fran [17:06] frank [17:09] I already have a Sony laptop, which I really like, but I can't put Linux on it. It is the only Windows based machine in the house now. If I put Linux on it, the girlfriend will BSOD. [17:10] kaouthia, heh this is the time of equal rights, she can buy her own windows laptop [17:12] That could be a cheap alt - I'll buy her a cheap laptop to surf the web and I'll have the Sony back - great suggestion! [17:13] kaouthia, now you are thinking [17:13] if you have a desktop and the sony u are likely sorted [17:13] though i suspect none of your buttons will work ... you can fix that :) [17:19] Buttons? [17:19] brightness up/down volume up/down eject, that sort of button [17:19] hotkeys is prolly a better description [17:19] Couldn't possibly, it doesn't have an Arm Core ;) [17:21] nothing a hammer and soldering iron couldnt fix :) [17:22] What would you want to solder a hammer to? ;) [17:22] the old CPU to get it ripped out more easily :) [17:23] Hotkeys ought to work by default on all Sonys now [17:24] mjg59, heh that'd be nice [17:24] Nothing a few extra volts and a cup of liquid nitrogen wouldn't fix [17:25] Support for the new-style systems went in a year ago [17:28] mjg59, yeah i admit i've not heard any whining about them for a while :) [17:29] apw: The fun bit was writing it without any of the actual hardware [17:29] qudos for that for sure [18:39] I used to be able to see my SD card (karmic, inspiron 1520). Now it's not there... wtf? [18:40] lamont: what kernel [18:41] 2.6.32-17-generic [18:41] though I guess I could reboot into -19 [18:42] lamont: -20 is the current kernel [18:43] meh === yofel_ is now known as yofel [19:21] jjohansen, or anyone, can i disable the function-f2 (disable wireless) button easily ? [19:21] smoser: depends [19:22] smoser: on some machines its a key press the kernel sees and triggers events, on others the kernel doesn't even see it [19:22] well this one sees it [19:23] it probably gets routed to gnome-power-manager, right ? [19:24] smoser: well does it see the keypress or just propagate an event after the fact [19:24] the event goes through and my wirelss drops [19:26] smoser: right, but there are a couple ways it can go through, and that will determine whether the kernel see it early enough to stop it [19:28] smoser: basic key debugging is start with xev, see it shows up there, then move to show keys and then acpi_listen [19:28] but it also could be handled by the ec [19:30] ok. i'll poke at it sometime [19:30] but thanks. i was hoping something easy. i keep accidently hitting it [19:38] Anybody wanna take a look at Bug #183461, it's not fully triaged yet, but I think it should have importance high as it makes a default installation unusable for some users. This is a very old bug, and I think it could use a pair of kernel-eyes by now. [19:38] Malone bug 183461 in opensuse "ksoftirqd/1 using 50% CPU or above" [Unknown,In progress] https://launchpad.net/bugs/183461 [19:40] anoteng: I think that's several dozen different bugs [19:42] I was thinking the same to, should I make the reporters file separate bugs? [19:46] anoteng, there are several thousand old bugs that need a look. it is just not currently possible to look at them all [19:46] but yes, the reporter needs to file separate bugs [19:46] as much as it pains me to say it :) [19:47] I will put this one on my list for review [19:53] thanks. I asked everybody to file their own bugs with apport-bug -p linux. === amitk is now known as amitk-afk