[00:23] <phillw> Hi, any kernel team still around?
[01:08] <phillw> F.Y.I following https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
[01:08] <phillw> ubuntu-bug linux
[01:08] <phillw> in 13.10 reports back "The problem cannot be reported:
[01:08] <phillw> This is not an official Ubuntu package. Please remove any third party package and try again."
[01:17] <RAOF> phillw: Do you have a non-standard kernel itstalled?
[01:18] <phillw> RAOF: root@piglet:~# uname -a
[01:18] <phillw> Linux piglet 3.11.0-3-generic #8-Ubuntu SMP Fri Aug 23 16:49:15 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
[01:18] <phillw> I hope not!
[01:29] <infinity> phillw: You are, however, out of date.
[01:31] <phillw> infinity: that was this evening apt-get dist-upgrade ?
[01:31] <infinity> Have you rebooted since?  You should be on 3.11.0-4-generic
[01:31] <phillw> supposed to be on -4 but it borked.
[01:32] <infinity> Ahh.
[01:32] <phillw> config-3.11.0-4-generic is queued up.
[01:33] <infinity> It might have some issues with that case.  'ubuntu-bug linux-image-3.11.0-4-generic' should work.
[01:33] <phillw> but there was an error message which I have discussed with Dan Letzeisen re: bug 1183777 re-appearing 
[01:33] <ubot2`> Launchpad bug 1183777 in linux-firmware (Ubuntu) "Possible missing firmware /lib/firmware/radeon in mainline 3.10 - 999 ubuntu kernel" [Medium,Fix released] https://launchpad.net/bugs/1183777
[01:34] <phillw> And, he has advised I raise a bug with the details of the email he sent me.
[01:34] <phillw> s/error/warning/
[01:40] <phillw> infinity: that worked :D bug report on its way. I'll add in the contents of the email chat I had
[01:45] <phillw> infinity: bug 1218691 - Please be gentle, 1st kernel bug report :)
[01:45] <ubot2`> Launchpad bug 1218691 in linux (Ubuntu) "Possible missing firmware /lib/firmware/radeon/KAVERI" [Undecided,New] https://launchpad.net/bugs/1218691
[02:00] <infinity> phillw: Didn't the bug you mentioned above specifically state that kaveri was missing intentionally for now?
[02:01] <phillw> infinity: it also said there was no proposed date for release?
[02:01] <infinity> "Kaveri will not be shipping to OEMs until Q4 2013, with first public availability in the desktop component channel in early in Q1 2014. Mobile Kaveri products will be available later in the first half of 2014. I doubt we will see firmware files before Q1 2014."
[02:01] <infinity> "Other than Kaveri, all of the other radeon firmware is included as of linux-firmware 1.113, so I'm going to mark this fix released."
[02:01] <infinity> Though, perhaps still a minor kernel bug that it shouldn't reference the firmware until it's shipped.
[02:02] <phillw> infinity: no warnings is better than warnings... saves everyone's time :)
[02:03] <infinity> phillw: Anyhow, that was no reason not to reboot.  You said you hadn't rebooted because the -4 installation "blew up". :P
[02:03] <phillw> I was just being vigilant and reporting back what I saw.
[02:03] <infinity> Or, rather, your word was "borked".
[02:04] <jk-> hey infinity
[02:04] <infinity> jk-: Fancy seeing you around here, traitor. ;)
[02:04] <infinity> jk-: I mean, hi!
[02:04] <jk-> hehe
[02:04] <phillw> infinity: I did then do s/error/warning/
[02:05] <phillw> virtual box and the recent kernel is a whole different can of worms!
[02:05] <phillw> 1 bug at a time :)
[02:05] <infinity> There are no bugs in our kernels.  It's all user error.
[02:05] <infinity> Clearly. :)
[02:06] <phillw> I wish we would just 'sack' virtual box and have people use KVM... but, meh :P
[02:06] <infinity> Who's "we"?  I've never used virtualbox, except to test virtualbox.
[02:07] <phillw> we as in ubuntu :D
[02:08] <infinity> We, as in Ubuntu, certainly don't recommend virtualbox.
[02:08] <infinity> It's non-free junk in multiverse.
[02:08] <phillw> Any ways, thanks for your reply. If someone during the testing phase of the testers flags it up as an issue, I can let them know that it can be safely ignored.
[02:09] <phillw> +1 from me :)
[02:09] <phillw> the Kaveri warning; not virtual box :D
[02:12] <phillw> I'll leave you all in peace.
[03:23] <snadge> im trying to install ubuntu 12.04.3 on an embedded board thingy with a pentium m cpu
[03:23] <snadge> and it fails to boot saying that pae is not supported
[03:23] <snadge> does the cpu really not support pae? or is that a bug?
[03:24] <mjg59> Early Pentium M has no PAE
[03:25] <snadge> i guess my next question is.. what can I do about it?
[03:25] <snadge> the hardware is an embedded board, and I just wanted to update it to a supported version of ubuntu
[03:27] <snadge> install xubuntu seems the simplest option
[03:29] <snadge> is xubuntu lts a supported thing by canonical? (last offtopic question i promise ill go away) :P
[03:29] <ohsix> are non-pae kernels still built? should be a matter of installing those
[03:29] <snadge> yeah.. i wanted a working installer though
[03:30] <ohsix> hm
[03:30] <ohsix> that would mean storing two kernels on an image, or going with the one without pae
[03:43] <ohsix> somewhat relevant: i just lost a hibernate image cuz i upgraded the kernel image (old one was still there) a few weeks ago and it booted the wrong one, is there an easy place to fix that? or is setting the name of the one true kernel in /etc/default/grub the way to do it
[04:01] <infinity> ohsix: Hibernation should probably set an on-next-boot one-time kernel selection.
[04:01] <infinity> ohsix: Not sure who best to file that bug against, but it's not the kernel's fault.  pm-utils or something, perhaps.
[04:02] <infinity> snadge: Use the non-pae netinst CD?
[04:02] <infinity> snadge: Keeping in mind that precise was the last release we supported non-pae, so you're going nowhere from there without building your own kernels.
[04:03] <infinity> snadge: http://archive.ubuntu.com/ubuntu/dists/precise-updates/main/installer-i386/current/images/netboot/non-pae/mini.iso
[04:08] <ohsix> infinity: well, pm-utils isn't installed; maybe that was it, and ya i know it wasn't the kernels fault, just wondering what to do to make it work
[04:09] <infinity> ohsix: Oh, I'm not suggesting that pm-utils DOES this, just that it probably should.
[04:09] <infinity> (maybe it does, maybe something else does, maybe it's a bug that it isn't hooked up, or the bug is that nothing does it at all)
[04:10] <infinity> hibernation is, sadly, not a commonly-tested codepath these days, when most people suspend to RAM.
[04:10] <ohsix> it sounds vaguely familiar, i read all the pm-utils scritps once ;D
[04:10] <ohsix> i've used it to replace network cards and stuff, it works surprisingly well
[04:11] <ohsix> if i'm fast enough it doesn't even drop my irc connection
[04:12] <ohsix> hrm, all i see is a hook that forbids hibernate if /var/run/do-not-hibernate exists
[04:13] <ohsix> yea, kernel postinsts has touch /var/run/do-not-hibernate in it
[04:18] <ohsix> i don't mind having to intervene with a config file on an upgrade i actually want to do, i just don't want to block all installs _or_ be surprised later
[04:21] <ohsix> the wiki is looking a bit creaky in places
[04:22] <ohsix> i can't believe tux on ice and swsusp are still even talked about ;D
[04:23] <ohsix> apparently hibernation was just flat blocked for 12.04
[04:25] <ohsix> https://help.ubuntu.com/12.04/ubuntu-help/power-hibernate.html heh, the doesn't work link doesn't link to anything that says why
[04:26] <ohsix> aside from possibly failing while attempting to hibernate, if there's not enough swap or whatever; how is it different than just suspending? (assuming the kernel can identify the resume image in the swap)
[04:26] <mjg59> You're resuming with running hardware rather than quiescent hardware
[04:27] <ohsix> well, consider that i'm speaking from a position of never having seen it fail, too :p
[04:27] <mjg59> http://lists.freedesktop.org/archives/dri-devel/2012-March/020747.html for instance
[04:28] <ohsix> thanks
[04:28] <ohsix> my laptop failed a hibernate the other day, actually; it seemed fine when it came back but stuff started faulting in junk or something
[04:29] <ohsix> after having used it maybe 100 times
[04:29] <ohsix> hah that was probably what did it too, i'm running pretty old stuff
[04:31] <ohsix> hm that could explain some once upon a time disk corruption too, guess i'll have to not do that until it runs newer stuff
[04:34] <ohsix> i'll just fudge grub to make the kernel sticky
[04:45] <ohsix> yea just setting the grub default looks like it'll work
[04:47] <ohsix> heheh [21031.743563] mpu401 00:0c: disabled
[05:25] <ppisati> moin
[07:13] <lluise70> Hello, I'd like to submit a bug report for linux kernel 3.10.9,  BUG: soft lockup - CPU#0 stuck for 62s! [kswapd0:48] ,  INFO: rcu_sched detected stalls on CPUs/tasks:
[07:13] <lluise70> is there an automated way?
=== smb` is now known as smb
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
[08:38]  * apw yawns
[09:02] <RAOF> apw: Do I need to send a nice box of bees?
[09:03] <ohsix> can you buy nice boxes of bees?
[09:03] <RAOF> Yeah.
[09:03] <RAOF> Containing six packs of bottled bees.
[09:06] <apw> http://linitx.com/product/mikrotik-routerboard-250gs-5-port-gigabit-managed-switch-with-eu-power-supply/13136
[09:06] <apw> RAOF, yeah please
=== fmasi_afk is now known as fmasi
[09:18] <apw> http://www.amazon.co.uk/gp/product/B0098Y338K/ref=ox_sc_sfl_title_5?ie=UTF8&psc=1&smid=A1RBLI8BU7UB9Y
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
[10:12] <apw> rbasak, this sstream-query thing you talked about yesterday ... it seems to need a GPG key pulling down to make it not barf, is that being handled in the packages ?
[10:12] <apw> smoser, ^^
[10:13] <rbasak> apw: yes. smoser uploaded a package that holds the keyring. So that is the plan, but I'm not sure the current status is for it.
[10:14] <apw> rbasak, cool thanks
[10:14] <rbasak> apw: the key is in doc/examples/keys or somewhere like that
[10:14] <apw> rbasak, i found it from the .gpg signature, but it wasn't obvious
[10:15] <rbasak> Agreed. I had the same problem when I first tried it.
[10:15] <apw> i suppose i was expecting it to be in the ubuntu keyring, but whatever works
[10:15] <rbasak> I believe smoser asked about that. I'm not sure what the conclusion was.
=== jibel_ is now known as jibel
[11:31] <joncram> I'm getting a kernel oops under Ubuntu 13.04 running kernel 3.8.13.5. I know very little about this subject. Where's the best place to submit a bug report and/or see if there is an existing bug report?
[11:32] <apw> joncram, the command 'ubuntu-bug linux' will file a bug for the kernel, if you are seeing an oops that is the appropriate place
[11:36] <joncram> apw awesome, thanks
[12:20] <hallyn_> must be around ff time - laptop won't boot :(
[12:24]  * henrix -> lunch
=== fmasi is now known as fmasi_afk
[12:57] <hallyn_> what are the odds that usb-creator-gtk is working these days.  (can't burn a rescue cd, my only laptop with a cd is the one that won't boot)  let's see
[12:58] <ogra_> just use dd
[13:04] <smb> hallyn_, With being about FF who can say. From slightly older experience creating 64bit versions seemed to be working more than 32bit (from 64bit) though that was probably back in Raring
[13:07] <ogra_> is tim on vacation ?
[13:09] <henrix> ogra_: yep, he's out today
[13:09] <ogra_> ah, k 
[13:12] <smb> ogra_, And Monday is (no) Labour Day
[13:12] <ogra_> hmpf
[13:12] <ogra_> root@ubuntu-phablet:/# modprobe nf_conntrack
[13:12] <ogra_> ERROR: could not insert 'nf_conntrack': Exec format error
[13:12] <ogra_> root@ubuntu-phablet:/# dmesg|tail -1
[13:12] <ogra_> [ 3083.256927] nf_conntrack: disagrees about version of symbol module_layout
[13:13] <ogra_> seems the mast maguro build is kind of screwed 
[13:13] <ogra_> *lat
[13:13] <ogra_> bah
[13:13] <ogra_> *last
[13:15] <ogra_> oh, ignore that 
[13:16] <smb> Would have been a bit weird
[13:16]  * smb ignores
[13:18] <ogra_> yeah, the android package wasnt rebuilt after the kernel upload ... so we end up with out of date modules 
[13:29] <hallyn_> smb: no my laptops almost never break, but almost always do right after ff...
[13:30] <smb> hallyn_, How else you could be sure it is that time in the cycle... ;)
[13:35] <hallyn_> smb: yup it's quite handy :)  
[14:10] <hallyn_> does "udevadm trigger is not permitted while udev is unconfigured" ring any bells?
=== fmasi_afk is now known as fmasi
[14:15] <smb> hallyn_, no particular ones... 
[14:17] <smb> Could that be a udev version that gets shoved in temporarily for update/install? I believe there have been rare cases that remained after
[14:17] <bjf> smb, ogra_, tim is out until 9/4
[14:17] <ogra_> thanks !
[14:18] <smb> bjf, Thanks should have noted the calendar entries further down
[14:18] <smb> Or in fact remembered what he said yesterday
[14:19]  * smb is mentally flying back home after UDS...
[14:19]  * ogra_ is home already but heavily vJetlagged
[14:22] <smb> ogra_, That is my plan for Monday
[14:22] <ogra_> ah, clever !
[14:35] <cking> the vUDS google hangout lag is the killer
[14:40] <hallyn_> smb: hm?  so i should maybe apt-get install --reinstall dbus?
[14:41] <hallyn_> well, first trying to hand-build a /dev in the initrd.  unfortunately unity just locked up from my sauc installer image
[14:41] <cking> ogra_, if I use phablet-flash cdimage-touch on my LG Nexus 4, it reboots and I get the android on it's back looking dead image, and idea how to fix this?
[14:42] <smb> hallyn_, Not a good day. Well I cannot say for this this is it. Maybe try apt-get install --reinstall udev... or maybe apt-get install -f starts something
[14:43] <ogra_> cking, hmm, sergiuens is probably better for debugging that 
[14:43] <ogra_> (he maintains phablet-tools)
[14:44] <cking> ogra_, ok, thanks
[14:44] <ogra_> i tend to flash manually :)
[14:46] <rsalveti> cking: that usually means it failed to flash when flashing the device, got corrupted somehow
[14:46] <rsalveti> cking: can you boot to the recovery at least?
[14:46]  * cking tries that
[14:47] <cking> rsalveti, recovery mode shows the same dead android
[14:47] <rsalveti> then you need a complete clean flash, was it running android before?
[14:47] <rsalveti> with fastboot
[14:47] <rsalveti> you can flash our recovery with fastboot
[14:48] <rsalveti> get into the bootloader, then flash http://cdimage.ubuntu.com/ubuntu-touch/daily-preinstalled/current/saucy-preinstalled-recovery-armel+mako.img
[14:48] <cking> rsalveti, I did a clean reflash back to android earlier, and then got this issue with phablet-flash
[14:48] <rsalveti> fastboot flash recovery saucy-preinstalled-recovery-armel+mako.img
[14:48] <cking> ack
[14:48] <ogra_> yeah
[14:48] <cking> will try that
[14:48] <rsalveti> right, that usually happens when you flash before unlocking or doing factory reset or similar
[14:48] <rsalveti> I had that issue a few times
[14:49] <rsalveti> actually, you unlock or do factory reset but you don't boot the device
[14:49] <rsalveti> then if you flash before that, it'd get in a broken state iirc
[14:49] <cking> ahah
[14:50] <cking> yay, that fixes the dead android
[14:50] <rsalveti> flash recovery, boot into recovery, and then phablet-flash cdimage-touch -b -d mako --pending
[14:59] <cking> rsalveti, that's fixed it - thanks! :-) \o/
[14:59] <rsalveti> cking: awesome
[14:59] <cking> happy dance
[15:07] <hallyn_> smb: eh, tried a bunch of stuff, finally "apt-get autoremove" seemed to kick-start a bunch of stuff.  I'm back in business!
[15:08] <smb> Yay... :)
[15:08] <hallyn_> thanks for the moral support :)
[16:07]  * smb → vHangover™
[16:28] <jhenke> somebody here to take a look at bug 1218995 ?
[16:28] <ubot2`> Launchpad bug 1218995 in linux (Ubuntu) "Hyper-V Synthetic Video Frame Buffer Driver not working" [Undecided,New] https://launchpad.net/bugs/1218995
=== gavin__ is now known as gavinguo
[17:28]  * henrix -> EOW
=== fmasi is now known as fmasi_afk
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== jdstrand_ is now known as jdstrand
[19:54] <aquarius> (question from the other day, because I had to leave before I could wait for an answer) My machine locks up solid on a fairly regular basis - Ubuntu 13.10 and up-to-date, unresponsive to keypresses, and not listening to the network. I think this might be a kernel thing because once I happened to be on a virtual console when it happened and got a bunch of lines saying "BUG: soft lockup - CPU#n stuck for 23s! 
[19:54] <aquarius> [some-process:12345]" (with n in 0, 1, 2, 3). I don't know how to further diagnose, because it's locked up -- I have to powercycle to get the machine back, by which time logs and so on are gone, so I don't know how to file a bug about it. What should I do?
=== fmasi_afk is now known as fmasi
=== fmasi is now known as fmasi_afk
=== kentb is now known as kentb-out
[22:22] <phillw> hi good people, sorry to be back so soon... Is there a apt-get method (or any fairly simple) method for some one to pull in the   3.11.0-3 kernels for someone who has managed to remove it via the auto-clean so that they can investigate a possible regression?
[22:51] <infinity> phillw: It's gone from the mirrors, so no.
[22:52] <infinity> phillw: One could wget the linux-image and linux-image-extra debs from https://launchpad.net/ubuntu/+source/linux/3.11.0-3.8/+build/4901000 and manually install them with dpkg -i
=== fmasi_afk is now known as fmasi
[22:55] <phillw> infinity: thanks, it's far too early to report a bug, but one of the guys affected doesn't have the -3 to roll back to.
=== fmasi is now known as fmasi_afk
[22:55] <infinity> (The above is assuming they're on amd64, since that was a link to the amd64 build)
[22:59] <phillw> thanks, it may be a driver issue as it seems to have also popped it head back up in the latest 12.04.3 update, but as ever with 'unexpected lock ups' and no data trail left in crash reports; it's going to be a PITA to get enough data to file a bug.
[23:01] <phillw> infinity: is there a better way to get a crash report... My notebook stops responding right now. I've rebooted in recovery and
[23:01] <phillw> I found the /var/log/faillog filled with "^@^@" other logs looks fine
[23:01] <phillw> of for me.
[23:02] <phillw> this seems to be a re-occuring theme of the issue
[23:10] <phillw> i know this a split between -bugs and -kernel, but the people reporting are currently not able to reliable reproduce, nor do they seem to have crash reports.
[23:41] <olli> apw, ping