=== tkamppeter_ is now known as tkamppeter [07:10] morning .+ [07:12] morning [07:33] hey smb, abogani. [07:33] jk-, dude! :) [07:33] dhuuuuude [07:34] White Russian? [07:34] <_ruben> jk-: thanks for the tip on posting my ataX -> sdY issue on askubuntu.com .. it got a decent looking response, havent had a chance to verify it yet tho ;) [07:35] _ruben: oh, no problem. Sorry I couldn't help directly. [07:35] _ruben: got a URL? [07:35] bug #818177 [07:35] Launchpad bug 818177 in udev "boot failures caused by udev race" [High,Confirmed] https://launchpad.net/bugs/818177 [07:36] <_ruben> jk-: http://askubuntu.com/questions/64351/how-to-match-ata4-00-to-the-apropriate-dev-sdx-or-actual-physical-disk [07:36] _ruben: thanks [07:37] looks sensible [07:38] <_ruben> indeed [10:46] cyphermox, ogasawara, isn't there a fix in the batch on stable 3.0.6 something to do with failing to load builtin firmware on resume an ordering issue [11:41] What is the function of the process »netns«? http://lxr.linux.no/#linux+v2.6.35.8/Documentation/ :Filename search: netns did not enlighten me. === yofel_ is now known as yofel [12:19] bullgard4, I think that is related to cleaning up network namespaces. Since that is time consuming it is done by a helper in batches. [12:19] sconklin, bjf - is there a tag i can rely on to find bugs that were regressions caused by -proposed kernels? [12:23] smb: Thank you very much for explaining. [12:24] bullgard4, glad if it helps [12:24] Yes, it does. [12:32] brendand: regressions in -proposed should be tagged as regression-proposed, not sure everything is being tagged correctly though [12:38] herton - yeah, i got some though now. thanks === bigbash is now known as zz_bigbash [13:18] is anyone able to tell me i'm a complete moron, and this is not possible https://bugs.launchpad.net/ubuntu/+source/linux/+bug/845864 [13:18] Launchpad bug 845864 in linux "painfully slow recharge time" [Undecided,Confirmed] [13:18] or at least that it could not be kernel related. [13:19] i would not have thought it could be, but I utlemming and both noticed this on our laptops during oneiric. [13:22] smoser, perhaps its a good question for cking [13:24] if someone else had not started seeing the same thing, i would hvae thought that my battery was just beginning to fail. [13:24] smoser, I wonder what role the EC has in charging your battery? [13:25] EC ? [13:25] * cking looks at the bug [13:25] smoser, its an embedded controller that does a lot of stuff behind the scenes. [13:27] I'd suggest recharging it when the machine is off and seeing what happens - if it still charges slowly it's a battery problem [13:29] otherwise, if it's running and slowly charges I expect some process or kernel power management feature is sucking power causing the recharge to take forever [13:29] cking, that would explain the differences between kernel versions [13:30] cking, well, 'top' doesn't show anything, and the system does not otherwise appear heavily loaded at all. [13:30] the other option is to boot with an older kernel and use the oneiric user space to factor out if it's a kernel issue or not [13:30] yeah. [13:30] cking, thanks. [13:31] but first I'd see how long it takes to charge when not running - that's an easy test and will show you if it's H/W related [13:31] well, yeah, except turning it off means i can't use it for work. [13:31] but it is a nice day here, and golf could fill that time :) [13:31] :-) [13:32] see how it charges at the end of the working day ;-) [13:34] smoser, the data from /proc/acpi/battery/ comes from the ACPI _BST, _BIX and _BIF methods and these basically read the battery status via the EC, so I doubt that this is broken [13:35] ..it's fairly straight forward code in the kernel. The only explanation is the either something is chewing up the power or the EC is doing the wrong thing [13:35] ..or the battery is not happy [13:37] cking, yeah. i would have assumed bad battery. but utlemming complained about this to me right after he upgraded to oneiric without me leading him at all. [13:37] but, i'll check when power off and such. [13:37] thanks for your help. [13:54] hrm, gitweb is sucky and slow today on zinc [13:55] swapping like crazy [13:56] cking, yeah, zinc is kinda under powered for some things [13:57] well, it's all blocked in I/O and swapping like mad, so more memory would be handy for it [13:58] cking, indeed [14:10] * ogasawara back in 20 [14:52] brendand: no, at this time there really isn't [15:02] apw, smb: have either of you tried installing this linux-image-extra virtual package? [15:02] not since you integrated it, no, whats up [15:02] ogasawara, Not yet [15:02] seems to have dependency issues [15:02] ogasawara, But it should be a relative quick exercise to try [15:03] ogasawara, what happens [15:03] luckily its an opt in package, so even if its bust it can wait till the first SRU upload [15:03] $ sudo apt-get install linux-image-extra-3.0.0-12-virtual [15:03] Reading package lists... Done [15:03] Building dependency tree [15:03] Reading state information... Done [15:03] Some packages could not be installed. This may mean that you have [15:03] requested an impossible situation or if you are using the unstable [15:03] distribution that some required packages have not yet been created [15:03] or been moved out of Incoming. [15:03] The following information may help to resolve the situation: [15:03] The following packages have unmet dependencies: [15:03] linux-image-extra-3.0.0-12-virtual : Depends: linux-image-3.0.0-12-virtual (= 3.0.0) but 3.0.0-12.19 is to be installed [15:04] em: Unable to correct problems, you have held broken packages. [15:04] only discovered it cuz I was trying to test out a meta package for it [15:04] Hm, linux-image shoudl exist... [15:05] ogasawara, i am unsure how that didn't happen to me, but it looks plain wrong [15:05] it should be the other version in teh control.in [15:06] ogasawara, you gonna look at it or should i [15:06] apw: I can investigate [15:06] ogasawara, ok get the same here [15:07] i think its a single line change to control.stub.in or stub.d/virtual [15:07] apw: am also gonna send out a patch for an -extra's meta package [15:07] to switch the version number round [15:09] apw, So to get the -12.19 added? [15:09] yeah, it must mention the wrong version variable there [15:11] probably adding ABINUM helps [15:11] hm no [15:11] would only be 12... [15:11] it looks right to me [15:11] I'm missing something [15:11] there is a proper [15:12] there is a proper longer version number isn't there? [15:12] apw: must be, now to find the variable name for it [15:13] bjf: well, https://wiki.ubuntu.com/Kernel/BugFocus bugs says regressions in -proposed should be tagged as regression-proposed [15:13] (refering to brendand's question) [15:18] ogasawara, doesn't look like we have the specific version as a variable, only PKGVER and ABINUM [15:18] ogasawara, the headers depedancy is just to the unversions package name, we could do the same i suspect and be fine [15:19] Depends: ${misc:Depends}, coreutils | fileutils (>= 4.0), SRCPKGNAME-headers-PKGVER-ABINUM, ${shlibs:Depends} [15:19] apw: ack, I'll try that and test [15:19] apw, Its likely new that you need to be in lockstep with a specific kernel version... [15:19] smb, likely though its officially abi compliant, so it shouldn't matter in theory [15:20] herton: that may be, but who has been doing the tagging? [15:20] apw, Probably loadable. Though it may have strange behaviour as they are really tightly coupled [15:20] apw, On the other hand every build will produce both anyway [15:23] bjf: no one that I know, that's why I told probably not everything is tagged correctly. I guess we should be doing it when we identify a regression [15:24] ogasawara, it wouldn't be hard to add a variable too [15:25] herton, and that's why i replied that at this time there isn't one, no one is applying it [15:26] bjf: shouldn't we be applying it anyway? [15:28] * smb detects major water damage... [15:28] -> security shutdown [15:28] smb !?! [15:29] * ogasawara guesses a split beer [15:29] heh [15:29] where one half is split onto his keyboard [15:33] bjf, herton - does regression-proposed get added by apport if a user is running the -proposed kernel? === zz_bigbash is now known as bigbash === kamalmostafa is now known as kamal [15:35] brendand: i don't think so, http://people.canonical.com/~kernel/reports/regressions-proposed-report.html shows bugs marked regression-proposed [15:35] brendand: there just aren't enough on that list for it to be accurate [15:36] bjf - true, there's only 39 there last time i checked === bigbash is now known as zz_bigbash [15:44] ok not beer, but an actual waterfall coming through his fuse box!!! so i think smb will be away for some time [15:44] ogasawara, tgardner ^^ [15:45] whoa, that's not good [15:45] bjf - btw, we have a session at UDS about improving coverage of certification testing for SRUs. Your feedback is welcome : https://blueprints.launchpad.net/certify-planning/+spec/hardware-p-cert-sru-coverage [15:46] sconklin too ^ [15:46] apw, did local construction efforts redirect a local river into his house ? [15:46] bjf - i got your feedback on the wiki page [15:47] brendand, thanks, subscribed [15:49] brendand: subscribed [15:49] sconklin, bjf - do you guys have some time for a brainstorm about where our efforts might be best focused? [15:50] sconklin, bjf - we're already sort of set on improving wireless, video and audio coverage so we'd be focusing on identifying use-cases within those areas [15:50] brendand: the three areas users have the most issues with: wireless, audio, graphics [15:51] bjf - agreed then [15:51] +1 [15:52] brendand: you should be working with QA, they should be hitting the same areas, i'd expect the two teams to be able to share tests, they may be focused on depth while your focus is breadth [15:53] bjf - yes, fewer tests but on a broader variety of hardware [15:54] sconklin, bjf - are you guys ok with taking some time tomorrow afternoon to discuss this then? we'll engage with QA, but also looking for your input [15:55] brendand: i'm pretty much always available to talk about testing the kernel [15:56] brendand: are you thinking mumble, irc or email ? [15:56] brendand: i personally like a "paper" trail [15:57] what he said [15:57] bjf - i'd go for IRC [15:59] brendand, how about in the #ubuntu-kernel channel [16:00] sconklin - no reason not to keep it public [16:01] bjf, sconklin - i'll schedule something tomorrow just to make sure everyone's in the same place at the same time (there are other folks from my team interested in participating) [16:01] brendand: sounds good, should be able to pop in here and start anytime, unless there's some hot discussion raging :-) [16:02] sounds great, looking forward to it. [18:01] * tgardner -> lunch === BenC__ is now known as BenC [19:48] * jjohansen -> lunch [20:20] GrueMaster: Do you care if I just close bug 758486 rather than leaving it in Incomplete. You can always re-open it should it re-appear. [20:20] Launchpad bug 758486 in linux-ti-omap4 "omapdss DISPC error on Panda platform" [Medium,Confirmed] https://launchpad.net/bugs/758486 [20:24] GrueMaster: eh, I've closed it and posted it a comment. === ayan_ is now known as ayan [21:21] ogasawara: Works for me. === zz_bigbash is now known as bigbash [21:54] I had a kernel panic using both ubuntu and kubuntu 11.04amd64-bit on an x120e thinkpad machine. it froze, so I'm going to have to power it off, but I want to know if you can derive anything useful before I do so === Linkmaster is now known as Crash_Override === Crash_Override is now known as Linkmaster