[00:53] jjohansen: not sure where this fits into the kernel/dev wiki docs (i didn't see any dups), but it may be helpful to someone someday: https://wiki.ubuntu.com/SergeHallyn_ppakernels [01:59] hallyn: thanks, I'm sure we can work it in [02:45] Hi, Someone recommended I use the desktop kernel on my server, as I'm running game servers, and the server version prioritizes throughput rather than latency, is this true? [02:45] FPS game server so extra milliseconds are good :p [06:23] kernel bug http://bit.ly/jpStCy line:2921 [06:27] kernel bug http://bit.ly/m2BtFD line:1401 [07:03] need help with btrfs bugs in 11.04 server x64 [07:07] zabyl: uh you do realize btrfs is still experimental? [07:07] yes it is fine in 10.10 /boot ext2 and / btrfs [07:08] I am trying to report kernel bug http://bit.ly/jpStCy line:2921 [07:08] and kernel bug http://bit.ly/m2BtFD line:1401 [07:13] zabyl: okay, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+filebug [07:14] will let you file a bug against the linux package [07:14] * jjohansen doesn't know why they make it so hard to find [07:16] I understand that this link is not for kernel bugs am I right? [07:26] thank you, filed it bug #776141 can you see it? [07:26] Launchpad bug 776141 in linux "kernel bug in 11.04 server x64 btrfs" [Undecided,New] https://launchpad.net/bugs/776141 [07:33] jjohansen: Because they'd prefer you use “ubuntu-bug linux”, which'll include all sorts of interesting information automatically :) [07:35] zabyl: That's not a particularly good bug report. Specifically, it doesn't actually say what went wrong, with what kernel version, or at what point. Including some description (like “the kernel panics with on boot”) and the full error message/kernel panic is likely to make it better. [07:37] do you know how to redirect / log kernel trace to some file in /boot [07:39] links provided in this bug report are from the console output and pointing to exact location in the source inode.c and extend-tree.c of the 11.04 build [07:46] Right. But don't contain the *actual error message* [07:47] Taking a photograph of the screen seems to be a reasonably common method of capturing early-boot panics. If the system mounts the drives - it's not at all clear from your bug report whether this is the case or not - then you'll find a full, unabridged log in /var/log. [07:53] zabyl, i can only seconf RAOF's comment, the bit that is missing is the stack trace of how we got to that line [07:57] Yes the system did not mount / and because CONFIG_BUG=y in /boot/config-2.6.38-8-server I was able to see the output of BUG_ON for these lines === yofel_ is now known as yofel [08:18] cking, morning [08:20] hiya [08:20] cking, enjoy the long weekend ? [08:20] hey apw [08:21] apw, yeah, lots of decorating and now lots of emails ;-) [08:21] apw, how about you? [08:21] jk-, hi ya [08:21] cking, lots of getting ready for the deluge of presents we expect today [08:21] heh [08:23] presents? === smb` is now known as smb [08:46] apw and cking, morning guys, how's the wedding party of prince william? [08:46] * smb did not know they were invited. :-P [08:47] smb: hey, man. how's going [08:48] cooloney, Alive and complaining. So good. :) How is you? [08:48] cooloney, very long, and still on repeat [08:48] smb: i'm good, my parents is visiting us in Shanghai, so i can eat very good food [08:49] slow-motion replay? [08:49] iiiiiiii dooooooooooooo [08:49] cooloney, How about learning to cook. Then everyday is a good food day. ;) [08:49] heh [08:49] apw, Wasn't the party the thing that was *not* on TV? [08:50] smb: yeah, i plan to start to learn something from my mom [08:50] cooloney, Good plan indeed. :) [08:54] apw: it should be a very big event in UK, [09:01] jk-, exactly ... yawn [09:02] smb, heh yeah perhaps, we had a party of our own [09:02] cooloney, it was indeed === cking is now known as cking-afk === TeTeT_ is now known as TeTeT === zz_eagles0513875 is now known as eagles0513875 === cking-afk is now known as cking === zyga-afk is now known as zyga [11:35] I am looking for some info on support for dual-Xeon (each 4 core) server grade machine on ubuntu [11:35] can someone help me on this? [11:43] <_ruben> nags_: should just work [11:44] _ruben, how do I confirm this? [11:45] _ruben, working is one part....but I am more interested to know if this can make use of the full potential of the HW [11:45] _ruben, because we are spending good amount of money on buying the server [11:45] _ruben, and we are going to use it for our development (Linux and Android build server) [11:45] <_ruben> nags_: the latter would completely depend on the software you run on it [11:46] <_ruben> if configured properly, a build server would use all those 8 cores just fine [11:46] <_ruben> you'll likely need to tell the build scripts/tools/etc to use 'em though [11:46] <_ruben> like make -j 8 [11:47] _ruben, sorry, if this is a dumb question...but when you say configure, do you mean re-compilation of ubuntu? [11:47] _ruben, ok...got it [11:47] <_ruben> no, ubuntu itself handles it just fine, it's the applications you want to use all cores which need to be told to do so [11:47] _ruben, we always use -j, but inherently is ubutntu using all the cores? [11:48] _ruben, the main problem today is the time it takes to build our Kernel and Android file system [11:48] _ruben, so I have asked for a good server.... [11:48] _ruben, at the same time want to make sure that the new server will solve my problem. [11:48] <_ruben> kernel builds highly benefit from multiple cores and scales to dual quad-core just fine [11:52] _ruben, ok...thanks [11:52] _ruben, is there a official source from where I can get this info? I need to give this proof to the management to get the approval for a server. Hope you understand. [11:59] <_ruben> smp support in the kernel has been there for ages, which is the most important part of it all [12:15] indeed.. I tried once with -j4 and -j27..it's a big big big difference [12:15] in term of compilation time [12:31] fairuz, it might be obvious...but can you elaborate on what you saw with j4 and j27? Sorry, if this is a dumb question. [12:34] nags_: I might say the output of compiled files is faster on j27.. which is normal because you have 27 files been compiled at once [12:35] fairuz, thanks. But, I believe it has only 8 cores (in the case of quad xeon) and I would expect only -j8 to make a difference and anything more than j8 behave the same? [12:42] <_ruben> i'd say the disk subsystem plays a fairly important role as well here, so either shove a ton of ram in it to cache a lot, or use really fast disks (ssds or it you want blazing fast: fusion-io) [12:43] nags_: yea i think if you only has 8 cores, anything more than j8 will behave the same [12:44] (afaik) === michaelh1|away is now known as michaelh1 [12:57] <_ruben> that's assuming each job would max out a core, which doesn't have have to be the case, so -j x, with x > 8 could be even faster .. takes a bit of experimenting to find the optimal number [12:57] <_ruben> some jobs might be disk intensive and hardly touch the cpu [13:06] hi, will todays daily kernel build for 32 bit or not [13:07] <_ruben> dunno, crystal ball is broken [13:09] for oss driver testing it would be really usefull === michaelh1 is now known as michaelh1|away [13:42] ## [13:42] ## No Kernel team meeting today @ 17:00 UTC [13:42] ## [13:42] :-) [13:44] * smb is not getting ready [13:51] apw, at your convenience, can you kick the cve tracker in the nads [14:05] JFo, dude [14:07] yessir? [14:08] JFo: can you give some love to bug 736490? I can test if you like. [14:08] Launchpad bug 736490 in linux "[natty][p54usb] wifi cannot connect to the ap" [Undecided,Confirmed] https://launchpad.net/bugs/736490 [14:08] amitk, looking [14:18] bjf again? wtf [14:18] apw, i think it likes it [14:19] bjf have you tried the syntax checker? i suspect its this: [14:19] active/CVE-2011-1182: karmic_linux has unknown state: 'ignore' [14:19] make: *** [pkgs] Error 1 [14:19] make: *** [tables] Error 1 [14:19] apw: ** 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-1182) [14:20] tgardner: do you package compat-wireless? (can't find it for natty) - Re: bug 736490 [14:20] Launchpad bug 736490 in linux "[natty][p54usb] wifi cannot connect to the ap" [Undecided,Confirmed] https://launchpad.net/bugs/736490 [14:20] amitk, there won't be a compat-wireless until 2.6.39 releases [14:21] for natty that is [14:21] apw, what do I need to run ? [14:25] apw, what did you run that produced that error? [14:34] apw, i think i want to run "check-syntax" working on getting that to run [14:42] yay! mumble is now working again on my laptop. [14:42] and I have no idea what fixed it [14:42] JFo, Did you say something? [14:43] smb, :) [14:45] ogasawara, did you have a lp script for matching duplicates ? [14:46] bjf: I think I had a script to mark a set of bugs as a duplicate to another bug [14:46] bjf: but not for matching dups [14:46] ogasawara, ok [14:47] * JFo still hasn't found it, but I keep getting sidetracked [14:48] JFo, i don't think it exists [14:51] apparently not [15:01] * ogasawara back in 20min [15:34] bjf sorry was packing for buda [15:34] speaking of which... [15:34] \/me checks on his laundry [15:38] apw, forgot you are part of the special indoctrination session [15:38] maybe is a "re-education camp" [15:39] heh [16:16] tgardner, any thoughts on bug 776438 ? [16:16] Launchpad bug 776438 in linux "Kernel error when connecting to WPA/WPA2 Enterprise" [Undecided,New] https://launchpad.net/bugs/776438 [16:16] broadcom out of the box install [16:21] JFo, I think there is a patch in -proposed or -preproposed that addresses this: 'b43: allocate receive buffers big enough for max frame len + offset' [16:21] cool, I'll ask him to test that [16:21] thanks for looking tgardner [16:21] JFo, nm, he's got problems with the wl driver [16:22] so, the b43 patch won't do him much good [16:22] think removing/reinstalling could help or could this be a hardware problem [16:22] ? === dimmortal1 is now known as dimmortal [16:23] like maybe something was just mis-configured on install? [16:23] JFo, hard to say since wl is a binary blob. [16:23] true [16:25] tgardner, I am not seeing any similar issues, so this looks isolated to this user [16:25] well, not any recent ones at least [16:26] JFo, possibly. I'm still trying to figure out who owns the package [16:26] ok [16:29] JFo, alright, this is the staging driver brcm80211 in 2.6.38, not the binary blob. I'm not seeing any stable updates, but it might not hurt to have him try -preproposed. [16:29] ok, will do [16:33] he will test that and get back to me. Thanks tgardner [16:34] JFo, ack [16:40] hallyn: I just saw https://wiki.ubuntu.com/SergeHallyn_ppakernels -- great guide! one thing though, you can pass -i -I to debuild instead of moving .git out of the way to ignore it in the build package [16:46] Sarvatt: that's awesome, thanks. I'll add that to the page. [16:46] Sarvatt: I ahven't done it yet, but I keep expecting to forget to move .git back :) [16:46] Sarvatt, something like dpkg-buildpackage -S -rfakeroot -I.bzr -I.git -I.gitignore -i"\.git.*" [16:46] -i -I removes all vcs files, no need to specify specific types anymore [16:47] Sarvatt, its backwards compatible to Hardy environments [16:47] ahh gotcha [16:49] tgardner: meaning '-i -I' will not work on hardy? [16:49] hallyn, I'd have to back and read the man page again to remember why. this has evolved a bit over 4 years [16:50] tgardner, preproposed solved him it seems [16:51] tgardner: thanks [16:51] JFo, whoa, that was fast [16:51] yeah, he enabled, tested and got back to me [16:53] JFo, enabled how? that kind of implies "proposed" to me [16:53] well, enabled/grabbed the driver [16:53] sorry for confusion [16:54] as he didn't 'enable' anything [16:54] JFo, ah, do we know what exactly he did? did he download and install the pre-proposed kernel? [16:54] one sec... [16:55] JFo, that would tell me that the fix is in the upstream stable commits which are on the master-next branch of natty and not what is currently in -proposed [16:56] bjf, which is why I suggested pre-proposed. there are a pile of stable updates in the queue [16:56] ok, I'll get clarification [16:56] tgardner, ack, i'd just like to know which batch it was in, what's on master-next isn't going to hit -proposed for 3 weeks [16:57] bjf, might be this one: mac80211: initialize sta->last_rx in sta_info_alloc [16:57] thats what the bitching in his log was about [17:01] tgardner, i wish we had our shit more together, such that we could quickly take that and turn it into a quick script that could look for the same issue in bugs and suggest the same action [17:01] tgardner, looks like it did not solve him in-fact. [17:01] tgardner, but we'll get there [17:01] dang [17:01] bjf, it was the pre-proposed kernel [17:01] he says it is diminished but still happens [17:01] JFo, good to know, that was the right one for him to try [17:02] so he is looking at http://ubuntuforums.org/showpost.php?p=10729117&postcount=135 [17:02] dunno what the difference is between that and pre-proposed [17:02] JFo, see if Henry Ptasinski has an LP account and assign the bug to him :) [17:02] heh [17:03] JFo, oh, I forgot about the firmware update [17:04] JFo, it needs to be linux-firmware 1.52 at least [17:04] ok [17:04] tgardner, think this is him? :-) https://edge.launchpad.net/~hptasins [17:05] JFo, yeah, I think so [17:05] want me to assign it to him? [17:05] for realz? :-) [17:05] JFo, 1.52 is the relased version in Natty, so thats OK [17:05] ok [17:05] JFo, yep, tell him I said so :) [17:06] will do :-) [17:07] done [17:07] :-) [17:08] it is bug 776438 in case you are interested :) [17:08] Launchpad bug 776438 in linux "Kernel error when connecting to WPA/WPA2 Enterprise" [Medium,Triaged] https://launchpad.net/bugs/776438 [17:08] or I may have told you that [17:51] bjf: hi! I saw your email; I'm about to get on a flight, but I'll reply as soon as I can. :) [17:51] kees, ack [17:52] kees, it's not holding me up, apw is just tired of dealing with my stupidity [17:52] bjf :) [18:04] After an upgrading to Natty on my ASUS M4A87TD/USB3 based computer there is a 150 sec pause in the boot sequence. The computer ran Maverick without problem before the upgrade. I think I have isolated the problem to the ACPI support, since disabling ACPI in the BIOS removes the pause (upgrading to the lastest BIOS did not solve it). I have also seen other users (in forums) with similar motherboards from ASUS with the same problem. How do I [18:13] ove, we didn't get your entire question, try adding a new line here or there, also, the first place to start is with filing a bug [18:14] After an upgrading to Natty on my ASUS M4A87TD/USB3 based computer there is a150 sec pause in the boot sequence. The computer ran Maverick without problem before the upgrade. I think I have isolated the problem to the ACPI support, since disabling ACPI in the BIOS removes the pause (upgrading to the lastest BIOS did not solve it). I have also seen other users (in forums) with similar motherboards from ASUS with the same problem. How do I r [18:14] ove, that didn't help [18:15] Sorry for the repeated text ... pressed the wrong button. [18:15] After an upgrading to Natty on my ASUS M4A87TD/USB3 based computer there is a150 sec pause in the boot sequence. [18:15] The computer ran Maverick without problem before the upgrade. [18:15] I think I have isolated the problem to the ACPI support, since disabling ACPI in the BIOS removes the pause (upgrading to the lastest BIOS did not solve it). [18:15] I have also seen other users (in forums) with similar motherboards from ASUS with the same problem. How do I report this bug properly? [18:15] (Hope that's better) [18:16] ove, start here: https://bugs.launchpad.net/ubuntu/+source/linux/+filebug [18:17] Thanks! I'll try that! Should I say "kernel" as the package? [18:18] ove, no, that link will get it filed against the correct package 'linux' [18:18] OK! I realise that now. Thanks again! [18:23] Would "ubuntu-bug linux", as mentioned on the web page, be a better choice ... since it collects a lot of information? [18:24] ove, yes, that would be better [18:24] OK, I'll do that. Thanks again! === bjf is now known as bjf[afk] [18:55] wow, no wonder I am hungry... [18:55] -grabbing lunch [19:06] * tgardner --> lunch === herton_ is now known as herton [19:57] * jjohansen -> lunch [20:02] * cking --> exit === bjf[afk] is now known as bjf