[02:01] <tyf> linux-generic-lts-quantal package is really not a PAE kernel?
[02:01] <infinity> tyf: It's PAE, what makes you think it's not?
[02:01] <infinity> tyf: We don't have non-pae in quantal and above.
[02:03] <tyf> after i installed it in precice, i do uname -r, the name doesn't show "pae". so i went to the packages.ubuntu.com, browse through the quantal's kernel packages, found some kernels named with -pae
[02:03] <infinity> tyf: The name has nothing to do with it.
[02:03] <infinity> tyf: From quantal forward, we don't have a non-pae kernel.  Hence, generic is now pae.
[02:04] <tyf> ok, thanks for the info, btw, is there a definite way to check whether the kernel is compiled with PAE enabled?
[02:06] <infinity> (precise-i386)root@cthulhu:~# grep PAE /boot/config-3.5.0-19-generic 
[02:06] <infinity> CONFIG_X86_PAE=y
[02:07] <infinity> Of course, there's also the simple "does your computer have a ton of RAM, and does the kernel see it?" :P
[02:07] <infinity> You'd know pretty quickly if you booted a non-pae kernel.
[02:13] <tyf> ok, that's understandable, but here I have exactly 4GB of RAM but i don't know how much video RAM is in the intel hd4000 and the nvidia gt630M. 
[02:14] <tyf> When i booted up with a non-pae kernel, which RAM will be "truncated" first? or the kernel will refuse to boot?
[02:20] <tyf> The Ethernet controller "AR8162 Fast Ethernet" is still not supported by any kernel modules in the quantal kernel 3.5...
[02:23] <tyf> Very weird, the wlan is properly detected and used, but  still have to compile the "alx" module myself in order to use the ethernet port, as occured to me when using kernel 3.2 and 3.4 too
[02:23] <tyf> maybe I should blame myself for buying this laptop :(
[04:18] <infinity> tyf_: Looks like you're going to need compat-wireless, see: http://ubuntuforums.org/showthread.php?t=2050126
[04:21] <infinity> tyf_: Oh, actually, if you go back to using the precise kernel, there are claims that linux-backports-modules-3.2.0 has the driver you need.
[04:22] <infinity> tyf_: See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/927782 for more details.
[04:22] <ubot2> Launchpad bug 927782 in linux (Ubuntu Raring) "integrate the Atheros AR8131/AR8151/AR8152/AR8161/AR8162 Ethernet driver with Jockey" [Medium,Confirmed]
[04:47] <tyf_> fyi, i have uninstalled the jockey since i first installed the OS in this laptop...it always crashes and very annoying during startup
[04:49] <tyf_> and, the recent updates of the kernel 3.2 has caused very random complete lockup in my computer
[04:50] <tyf_> so i decided not to use the kernel 3.2 for some time
[04:51] <tyf_> btw, i heard that the quantal kernel is going to be included in the 12.04.2 release...hence, I will just wait for that...:P
[06:13] <infinity> tyf_: The quantal kernel that will be included in 12.04.2 is the one I already had you install.
[06:13] <infinity> tyf_: (linux-generic-lts-quantal)
[06:14] <infinity> apw: Do we need to be doing lbm-lts-quantal as well for the backport stack?  Without it, people who need cw for obscure/new hardware support kinda get shafted.
[06:14] <infinity> apw: Specifically thinking of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/927782 which is fixed in lbm, but not in the quantal kernel itself (hence, not in lts-quantal).
[06:14] <ubot2> Launchpad bug 927782 in linux (Ubuntu Raring) "integrate the Atheros AR8131/AR8151/AR8152/AR8161/AR8162 Ethernet driver with Jockey" [Medium,Confirmed]
[09:21] <apw> infinity, i think we were hoping not to, but you may well raise an important point
[10:52] <ppisati> apw: why do you keep the low latency branch in a separate tree instead of being a topic branch (like ti-omap4) of our main tree?
[10:56] <apw> ppisati, because in theory it is maintained by people outside of the kernel-team who cannot write there
[10:56] <ppisati> apw: ok
[10:56] <apw> ppisati, though i cannot deny it would make sense to have it mirrored into there, same for ppc
[10:57] <ppisati> apw: and do you plan to backport the fix for lp1029730 back to P/Q?
[10:57] <ppisati> bug 1029730
[10:57] <ubot2> Launchpad bug 1029730 in linux-ti-omap4 (Ubuntu) "linux-image-$(uname -r) should suggest linux-headers-$(uname -r)" [Medium,Confirmed] https://launchpad.net/bugs/1029730
[10:58] <apw> i believe the fixes for dpkg are planned for backport so we would have to indeed
[10:58] <ppisati> ok
[13:12] <jamesh20000> hello
[13:13] <jamesh20000> Hi, I'm about to install a linux based OS for the first time ... a shop is going to do this for me
[13:13] <jamesh20000> Someone told me not to get a kernel that's much higher than 2.6.27
[13:13] <jamesh20000> do I have a selection of kernels when I install Ubuntu ?
[13:13] <jamesh20000> I don't know how Ubuntu works
[13:15] <tyf_> it is hard to answer what kernel is best for you, but generally if you have newer hardware, go for a higher-versioned kernel
[13:16] <tyf_> you don't have to worry about the kernel version first, just install a version that you like to use....I recommend the LTS versions, i.e. the 10.04 and 12.04
[13:16] <tyf_> somehow i still love to use 10.04 for its stability
[13:22] <jamesh20000> I'm going to install Ubuntu next to win7 -- How much space is reasonable for the Ubuntu partition?
[13:32]  * henrix -> lunch
[13:34] <jamesh20000> I'm going to install Ubuntu next to win7 -- How much space is reasonable for the Ubuntu partition?
[13:40] <xnox> jamesh20000: support at -> #ubuntu channel.
[14:16] <xnox> bug 1085958
[14:16] <ubot2> Launchpad bug 1085958 in linux (Ubuntu Raring) "FTBFS linux-libc-dev fails to compile iptables" [High,Confirmed] https://launchpad.net/bugs/1085958
[14:37] <tyf_> Guess the linux-backports-modules-cw will not be available for the linux-generic-lts-quantal kernels?
[14:50] <ppisati> brb
[15:10] <arges> apw: https://wiki.ubuntu.com/KernelTeam/BuildKernelWithChroot
[15:51]  * ogasawara back in 20
[17:04] <jsalisbury> bjf, herton, henrix Seems like allot of people are affected by bug 1080530
[17:04] <ubot2> Launchpad bug 1080530 in v86d (Ubuntu) "v86d prevents suspend from completing" [Medium,Confirmed] https://launchpad.net/bugs/1080530
[17:07] <bjf> jsalisbury, ack
[17:09]  * ppisati -> gym
[17:26] <rtg> jsalisbury, maybe 'freezer: exec should clear PF_NOFREEZE along with PF_KTHREAD' ?
[17:27] <rtg> otherwise you're gonna have to bisect. there are a boatload of patches twixt those 2 releases
[17:28] <jsalisbury> rtg, looks like an easy thing to revert.  I'll build a test kernel and request that they test.
[17:54] <shnatsel> Hello
[17:54] <shnatsel> I see Precise seeds have been converted to using 3.5 kernel backported from Quantal by default for x86 architectures. I wonder if I should use 3.2 or 3.5 for a derivative distro? I'm primarily concerned by two things: 1) for how long will it be supported and 2) will hardware support patches be backported to 3.5 like they are being backported to 3.2?
[18:00] <xnox> shnatsel: the support path from quantal-lts kernels will be the raring-lts kernels.
[18:00] <xnox> shnatsel: so the quantal-lts kernel will have the support timeframe of quantal release.
[18:01] <xnox> shnatsel: so there is an option of getting newer kernels throughout precise release.
[18:04] <shnatsel> xnox: I see. It seems there's no metapackage that points to the latest backported kernel, so anybody who had their system shipped with the Quantal-backported one will automatically have the support time of Quantal itself, not the LTS 5 years? Or raring-lts will provide a dummy transitional package for quantal-lts?
[18:07] <xnox> shnatsel: I don't know how this will be done when the raring kernels will come around.
[18:07] <xnox> shnatsel: but do note that we do not auto-upgrade people to quantal-lts kernel, the install images for 12.04.2 will switch to quantal-lts.
[18:08] <xnox> shnatsel: note that raring-lts kernels will be available only well after raring release.
[18:09] <shnatsel> xnox: yes, I'm aware of that. I'm wondering what will happen to people who will use 12.04.2, because the Quantal kernel will be supported for a much shorter period than the rest of the Precise system
[18:09] <xnox> hopefully somebody else can answer that.
[18:13] <shnatsel> okay, I'll try asking in #ubuntu-devel :)
[18:13] <shnatsel> but I take it 3.2 is going to be supported for 5 years?
[18:14] <shnatsel> also, is hardware support really being backported to it or it's just me? (e.g. does it work with Ivy Bridge?)
[18:16] <bjf> shnatsel, yes, it is supported for 5 years
[18:17] <bjf> shnatsel, the purpose of the lts-hwe kernels is specifically for supporting newer HW
[18:17] <shnatsel> bjf: but the lts-backports are not supported for 5 years? If not, is there an upgrade path?
[18:20] <shnatsel> okay, I trust you won't abandon the people who installed 12.04.2 XD
[18:20] <shnatsel> final question:
[18:21] <bjf> shnatsel, you are correct that they are not supported for 5 years. if you are on lts-hwe-quantal, you will be automatically upgraded to the 14.04 (T) lts-hwe kernel when that releases
[18:21]  * rtg -> lunch
[18:21] <shnatsel> bjf: oh, good to know. Thanks!
[18:22] <shnatsel> Final question: bug 1034099 is a stable release regression that leads to a kernel panic, but it's been unattended for some time. Happens in Precise and Quantal. Is there anything I can do to help get it fixed?
[18:22] <ubot2> Launchpad bug 1034099 in ulatencyd (Ubuntu) "Kernel panic with ulatencyd on kernel 3.2.0-29-generic" [Undecided,Confirmed] https://launchpad.net/bugs/1034099
[18:23] <shnatsel> I'm not a 1337 haxx0r myself, just a script kitty and an architect for an Ubuntu-derived distro
[18:25] <bjf> shnatsel, all i can tell you at this point is it will need further investigation and probably some bisect work to see if we can find the regression
[18:25] <shnatsel> so bisecting the exact patch should help?
[18:25] <bjf> shnatsel, absolutely
[18:26] <shnatsel> the bug appeared after an update and there were 3 or 4 patches in it; getting someone to bisect it shouldn't be too hard :)
[18:30] <bjf> shnatsel, there are 109 commits between 3.2.0-28.45 and 3.2.0-29.46
[18:30] <shnatsel> I see the debian changelog wasn't that precise
[18:30] <shnatsel> where can I find that branch?
[18:31] <shnatsel> also, is "debuild" enough for building the packages? or should I use something else?
[18:33] <bjf> shnatsel, i'm looking at the git repo at: git://kernel.ubuntu.com/ubuntu/ubuntu-precise.git
[18:35] <bjf> shnatsel, these are the instructions i normally point folks at: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel 
[18:36] <shnatsel> bjf: thanks! I'll try to get somebody on bisecting it :)
[18:37] <bjf> shnatsel, debuild does alsow work :-)
[18:55] <shnatsel> bjf: is there a way to list all the commits between those two tags, for ease of bisecting?
[18:55] <shnatsel> I can't obtain it (I'm a noob at git)
[18:55] <bjf> shnatsel, have you ever used git to help do a bisect?
[18:55] <shnatsel> no
[18:56] <bjf> jsalisbury, can I hand this off to you ? ^
[18:56] <bjf> shnatsel, we have a wiki page that will help
[18:56] <shnatsel> oh, great!
[18:56] <jsalisbury> bjf, sure
[18:56] <shnatsel> and I'm instructing another person instead of doing it myself, so I'll invite them here
[18:56] <jsalisbury> shnatsel, I can perform the bisect for you, and post test kernels.
[18:58] <jsalisbury> shnatsel, is this for bug 1034099 ?
[18:58] <ubot2> Launchpad bug 1034099 in linux (Ubuntu) "Kernel panic with ulatencyd on kernel 3.2.0-29-generic" [High,Confirmed] https://launchpad.net/bugs/1034099
[18:58] <bjf> jsalisbury, between 3.2.0-28.45 and 3.2.0-29.46
[18:58] <jsalisbury> bjf, ack
[18:59] <shnatsel> jsalisbury: to clarify, I have no skills to fix the bug, I just tried to help getting it fixed by bisecting the exact commit that causes the regression. But that'd be great anyway :)
[19:00] <jsalisbury> shnatsel, I'd be more than happy to do the bisect.  I'll start a bisect between  3.2.0-28.45 and 3.2.0-29.46 and post a link to a test kernel in bug 1034099
[19:00] <ubot2> Launchpad bug 1034099 in linux (Ubuntu) "Kernel panic with ulatencyd on kernel 3.2.0-29-generic" [High,Confirmed] https://launchpad.net/bugs/1034099
[19:00] <shnatsel> jsalisbury: oh, that'd be great! Thanks a lot!
[19:01] <jsalisbury> shnatsel, np.  It sounds like this is pretty easy to reproduce.  It just requires ulatencyd installed on Precise?
[19:02] <shnatsel> jsalisbury: yes. The kernel panics on every boot.
[19:02] <shnatsel> In Quantal, too
[19:02] <shnatsel> and in Precise
[19:02] <shnatsel> I have no data about Raring yet
[19:03] <jsalisbury> shnatsel, ok.  Let me see if I can also reproduce it.  If I can, that will greatly speed up the bisect process.
[19:08] <shnatsel> It should be easily reproducible. It was the most reported bug in our distro, ever :)
[19:08] <shnatsel> All the machines I've seen were bricked by this update.
[19:11]  * henrix -> EOD
[19:15] <jsalisbury> shnatsel, I'll try to reproduce the bug.  If I can, I'll perform a bisect to find the bad commit.  If I can't reproduce the bug, I'll post an update the bug and ask for help testing.
[19:16] <shnatsel> jsalisbury: thanks!
[19:16] <shnatsel> I've found the wiki page on bisecting and arranged bisecting with a guy who experiences it, just in case
[19:17] <jsalisbury> shnatsel, great, thanks.
[19:56]  * apw calls it a day ... no ... more ... config ... review
[19:58] <rtg> hallyn, did you ever get any traction on your patch at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/comments/15 ?
[19:58] <ubot2> Launchpad bug 1065589 in lxc (Ubuntu) ""initctl list" shows 11974 instances of network-interface-security after two days of uptime" [Medium,Triaged]
[20:06] <rtg> bjf, linux-generic-lts-quantal
[20:27] <rtg> herton, do you think bc78c57388e7f447f58e30d60b1505ddaaaf3a7d is a candidate for stable? 3.2+
[20:29] <herton> rtg, looking
[20:32] <herton> rtg, yeah, looks something that can go in 3.2
[20:32] <rtg> herton, looks like it applied to all stables through 3.6
[20:34] <herton> rtg, hmm, can't find it here applied on other stables
[20:35] <rtg> I meant to say that it _should_ be applied to other stables as well
[20:37] <herton> true
[20:38]  * rtg has had enough fun for one day
[20:55] <hallyn> rtg: hm, no, it got an ack from dlezcano, and died there
[20:57] <hallyn> rtgso an ack from Eric and Daniel - I'll resend with those
[21:22] <bjf> bryce, i just pinged sconklin about the video switch gadget he developed and he's indicating that he'll send one to you
[21:23] <sconklin> bryce: I just pulled one (the last assembled one) and I'll have it out to you ASAP
[21:55] <bryce> sconklin, bjf oh great, thanks!
[22:26] <strcrzy_> does anyone know of issues with SSDs and I/O errors on 3.2.0?
[22:29] <strcrzy_> we just upgraded from 11.10 to 12.04.1 and now about 10 of our 50 machines started vomiting up disk I/O errors
[22:40] <arges> strcrzy_, I would recommend filing a bug, so we can see logs and what error messages there are
[23:29] <infinity> henrix_: Another shankbot request.  Currently, I think 'promote-to-security' keys off of jjo's 'security-signoff', but for rebase/derivative/community kernels, I'd like this to also intersect with "is/was the master being/been promoted to security?"
[23:30] <infinity> henrix_: (Security team already gave me the go-ahead to promote derivative kernels that cover CVEs, but it's a bit of a pain to manually cross-reference every time).
[23:35] <herton> infinity, ok, me or henrix_ will do