/srv/irclogs.ubuntu.com/2013/09/03/#ubuntu-kernel.txt

=== emma is now known as em
ppisatimoin06:40
=== smb` is now known as smb
smbppisati, morning07:04
=== fmasi_afk is now known as fmasi
smbinfinity, Still got a bunch of Xen uploads on my mind which are giving me headaches. For Saucy there is a FFE as well...07:45
apwxnox, when did we switch to upstart user sessions by default ?07:55
xnoxapw: week1 of saucy07:56
xnoxapw: raring had it available (~2-3 weeks after feature freeze), but needed a manual configuration file change.07:56
xnoxto activate.07:56
apwxnox, i mean as a default option on a new image07:57
apwin saucy07:57
xnoxapw: yeah, saucy desktop cd booted very early in the cycle into upstart user sessions by default. On touch it's different story, as there was no lightdm, so it took some time before it gained upstart user session support.08:02
xnox(there is a package done by ogra integrating that in)08:02
xnoxon server/tty there is still no user sessions.08:02
smbAt least it would not explain the sudden rise of boot time08:02
apwsmb, no?  would not early in teh cycle be june ?08:03
smbOh hm08:03
xnoxsmb: apw: in /etc/upstart-xsessions comment out your session (e.g. ubuntu) and reboot. If there is no automatic user login enabled, then upstart user sessions do not kick in at all....08:05
apwxnox, we don't use upstart if you type a password ?08:05
smbxnox, Hm, right, so I type in my password then its not upstart sessions?08:06
xnoxapw: we use it, but it doesn't affect the bootchart.08:06
apwxnox, boot charts continue through a password ?08:06
xnoxsmb: apw: upstart user session is kicked off, after a graphical login.08:06
apwxnox, well to build the graphical login right ?08:06
apwxn08:07
apwxnox, it runs gnome-session etc08:07
xnoxno. lightdm is running under system init, not session init.08:07
apwright .... in smb's case the new 'delay' is all after he hits return in the password prompt08:07
xnoxmaybe i'm not clear....08:07
xnoxapw: oh.08:07
xnoxso in /etc/X11/Xsession.d there is 00upstart & 99upstart, which is what starts user session.08:08
xnoxi don't think we did any benchmarks / charts on how long the login takes with & without upstart user session.08:09
smbxnox, I just commented out what you said and rebooted the machine. Need to grab the new chart though08:10
smbFrom my feeling it still toook a while08:11
xnoxapw: what's "pumbing" vs "xorg +plubming" vs "desktop" on http://reports.qa.ubuntu.com/bootspeed/machine/2/amd64/08:12
apwxnox, so basically plumbing is done when root is mounted and we move to real /, Xorg is started when X the process is running, desktop starts when the session starts08:13
apwxnox, you can see by following the lines down to where they coincide with a specific process start08:14
smbxnox, Ok, so it seems its still about 15s08:14
smbmaybe 2s less08:14
xnoxwell one can twiddle the init line in the 99upstart script to increase verbosity (e.g. --debug or --verbose).08:15
xnoxto get all events... but the culprit might not be an upstart managed process =/08:16
apwxnox, indeeed, smb lets do a few runs on each to make sure it is real i guess08:17
smbapw, ack. from the bootchart it seesm a bit like compiz is doing something a lot and I can see something about the time that gets less frantic and the gtk-decorators start08:22
smberr08:23
* smb looks at the empty space where all the indicators *should* be08:23
xnoxhm. we added upstart support startpar, thus for each init.d script we take penalty of it checking weather there is upstart jobs or init.d script.08:26
xnoxgood: from june https://jenkins.qa.ubuntu.com/job/bootspeed-saucy-desktop-amd64-acer-veriton-02/27/artifact/11/bootchart.svg08:27
xnoxbad: current https://jenkins.qa.ubuntu.com/job/bootspeed-saucy-desktop-amd64-acer-veriton-02/117/artifact/11/bootchart.svg08:27
=== fmasi is now known as fmasi_afk
smbxnox, Just to make sure, after commenting out the "ubuntu" in /etc/upstart-xsessions, is none of the indicators coming up an expected result?08:36
xnoxsmb: yeap, looks like tedg migrated those to be upstart jobs only without any other way to activate them (e.g. no dbus activation)08:37
smbxnox, Ok, so its not a complete fair comparison, but at least it seems to indicate that the indicators are not the main reason for the delay08:38
xnoxsomehow on the bootchart.svg i linked above Xorgs comes up 5 seconds later, despite the first inital stage (networking? it's aligned with hostname job) finishing 2 seconds earlier.08:40
ppisatilool: any chance we can get an up to date flash-kernel in ubuntu? we are still stuck at 3.0 while debian has 3.1008:42
ppisatilool: and they have rudimentary support for contatenating kernel+dtb, something we need too08:43
smbxnox, One of the "advantages" I got with having to log in is that I get that a bit more separated between coming up to the greeter and when hitting enter and see those ending and the session to start08:46
smbxnox, It looks at least like 9s between compiz starting and until gtk-windows-decorators starting and I believe that is about when the screen is turned on08:48
loolppisati: I haven't had time to work on it in the Debian side for a while, and the Ubuntu one had tons of delta that I couldn't safely rework without a lot of time08:50
ppisatilool: ok, then i'll import the dtb thing support in ubuntu08:51
loolppisati: ok08:51
ppisatilool: actually what debian has is _really_ trivial, but we can plug on it08:51
loolppisati: and I would like too to see the two versions being closer or identical even  :-)08:51
loolppisati: cool08:52
ppisatiactually the ubuntu version is at 3.4/3.508:54
ppisatibut pkg version was never updated08:55
apwoh goody09:49
* henrix -> food11:52
nfkwhat happened to xfs? it seems to have been removed from a kernel some weeks ago making my laptop unbootable12:32
apwnfk, from which kernel12:48
apwin which series even12:48
apwnfk, it is enabled in raring and saucy according to the configs for example12:49
apwnfk, ?12:57
=== psivaa is now known as psivaa-lunch
=== kentb-out is now known as kentb
=== kentb is now known as kentb-afk
=== psivaa-lunch is now known as psivaa
nfklatest kubuntu13:41
nfk3.8.30 or thereabout i think13:41
nfkapw, ^13:42
apwdebian.master/config/config.common.ubuntu:CONFIG_XFS_FS=m13:45
apwnfk, so it is enabled there13:45
apwnfk, how can you tell the kernel doesn't supportit13:45
nfkand it was never disabled?13:45
nfki think i managed to boot that kernel manually and it didn't list xfs partitions or something like that, let me try again13:46
apwindeed, it seems to have always been on for all of raring13:46
nfkwhile the previous kernel at least got to emergency shell (although didn't mount / as i didn't know how to specify that)13:46
nfkalso unlike gentoo's dracut initrd that one seemed so basic it was unusable for recovery, derp13:47
nfkthen again, maybe that was because it couldn't mount /13:47
apwnfk, it has enough bits to mount root in general and little more13:50
apwwhy would it have more13:50
apwso the previous kernel didn't work either ?13:51
apwhas this system ever worked?13:51
apwand if so which kernel works there13:51
apwnfk, ^13:51
nfkyes, it's an upgrade from the last version that had alternative cd13:51
nfkthe only way to install on lvm213:51
nfkwhy is grub so hard to boot manually </rant>13:54
nfkfor starters it's not even possible to read all of help13:54
apwnfk, i thought the live CD now did lvm13:54
apwpretty sure that is how i installed a machine on my desk here13:54
apwanyhow is this breaking at grub or at initrd13:55
nfki have no idea at this point13:56
nfki can't even manage to boot any kernel at this point13:56
apwthey have rather different prompts13:56
apwgrub i am pretty sure has grub> in its prompt13:56
apwand initramfs has a big splash when it drops there13:56
nfkeven though i'm also glancing at the grub config of this gentoo box and have booted grub1 many times manually and at least once also grub213:56
apwbut if you arn't able to tell perhaps a photo?13:56
nfkah, that, yeah, i'm stopping at grub13:56
apwand ls from there says what13:57
nfknothing13:57
nfkit's the fucking grub13:57
nfki bet it can't read its config or something13:57
apwso you ahve an emergency grub prompt ?13:57
nfkwould be nice if i could tell it to load one13:57
nfkyes13:57
apwwhat sort of LVM config do you have13:57
apwie, what is /boot13:58
nfki have no idea, it's legacy from fedora 16 or something13:58
nfkand last time grub at least read out lvm volumes but not this time13:58
nfkhorrible thing13:58
apwmaking this easy arn't we13:58
apwgrub can grok lvm nominally it does on many of mine13:59
nfkit did so last time for me too13:59
nfkbut not this time13:59
apwnfk, so, your prompt looks like grub> yes ?13:59
nfkyes13:59
apwand ls produces absolutly no output13:59
nfkand i'd apply a brick by now to that promt if i didn't feel sorry for the laptop14:00
nfklet's restart14:00
nfkit does produce output, it's listing files on /14:00
apwok ls for me shows me the partitions only14:00
nfkno, ls lists files on /14:00
apwls with no parameters doesn't do that for me on my grub> prompt her14:01
apwit says like *14:01
apw(hd0) (hd1) ...14:01
nfkrebooted, grub only states the version and gives generic information about the prompt14:01
nfkyeah, now it does that for me too14:01
nfkwhere's my brick?14:01
apwand does it list your lvm things14:02
nfkyeah14:02
nfkarp, if i do ls <any letter><tab> then it starts to list /14:03
apwnfk, so i htink you can then do 'configfile /boot/grub/grub.cfg'14:04
apwand then perhaps hitting ESC will get you your menu14:04
nfkso i managed to make it read the configfile and nothing really happened except now it only shows grub>14:04
nfkah14:04
nfklet's try esc14:04
nfknope, esc didn't help14:05
apwnothing at all ?14:05
nfkyeah, boot tells me to load a kernel first14:05
nfkso i guess it didn't like the configfile14:05
apwi mean when you hit ESC you didnt get any sort of output14:05
nfkassuming cat works... the fucking file is empty14:05
nfkyeah, grubenv prints ############## so i guess the config is empty14:06
nfksorry for bothering you14:06
nfki guess i may have booted those last two kernels differently back then14:06
apwcat works ok here14:07
apwso ... you need to make up the config by hand14:07
apwlinux /vmlinuz14:08
apwinitrd /initrd14:08
apwboot14:08
nfkshouldn't kernel something root=label=herpes14:08
apwmight work14:08
nfkinitrd something14:08
nfkyeah14:08
nfki'm fairly sure it won't boot without /14:08
nfkbut let's try14:08
apwroot=<SOMETHNG> which you likely need to know14:09
nfkyep14:09
nfkdidn't work out without root14:09
apwif it is lvm it might be easu14:09
nfki have no idea how to specify it except for label or uuid (no way) but ic can't make grub print them out this time14:09
apwroot=/dev/mapper/<vgname>-<volume>14:09
apwif you are using lvm14:10
nfkoh, i see why i thought xfs was removed14:10
apw(which it cannot be as we are at grub not the kernel)14:10
nfkthe latest kernel says that it tried ext3 ext4 vfat fuseblk14:10
nfkapw, actually grub should be able to do it, i just don't know how14:11
apwi thought grub didn't have a working config14:11
apwhow did it even get to the kernel to say that14:12
nfki set kernel and initrd14:12
apwbear in mind i can see the 26 lines of what you typed and nothing else14:12
apwi think that implies it didn't load an initrd14:13
apwas you don't get that error unless the kernel is itself trying to mount /14:13
apwand from its point of view / is the initramfs14:13
apwnfk, ^^14:13
apwand it will only try the ones it can do direct which are the builtins, and wouldn't include anything in lvm regardless14:14
apwnfk, if your grub.cfg is 0 length then perhaps so is your initrd14:14
apwtry rebooting to grub and loading a much older kernel14:14
nfkleet's see14:15
apwand its associated initrd14:15
nfkthat might explain why trying to boot the previous kernel at least got me to the emergency shell14:15
apwif you are unable to boot that, i would then say you need a recovery image, a live USB stick or something 14:15
apwso we have some more tooling to look at the image14:15
nfkif i had that, i'd be installing opensuse about now14:16
nfki don't have capabilities to write cd/dvds at this point14:16
nfkand my only usb stick is a known buggy kingston that boots only when threated with violence and 220V14:16
apwshame you are making life hard for oneself14:17
apwanyhow try and older kernel14:17
apwwith the matched initramfs14:18
nfkthis box had a cd/dvd writer but it literally bite the dust and went crazy14:18
nfkhad to remove it14:18
nfk*bit14:19
nfkthe *old in / didn't work out, let's try the ones in /boot14:19
apwyeah pick a pair in /boot14:19
apwnfk, now, i assume the mesasge you saw with the latest kernel was:14:20
apwList of all partitions:14:20
apwstuff14:20
apwNo filesystem could mount root, tried: <filesystem names>14:20
nfk kernel panic - not syncing...14:21
nfkafter that14:21
nfkyeah14:21
apwyeah so that is kernel side, which means it did not load initrd correctly14:21
apwso that implies initramfs is also broke, perhaps 0 length14:21
nfkanyway, even 3.8.28 didn't work and i'm certain it got to emergency shell last time14:22
nfki guess it didn't like root=/dev/mapper/vg_my-root14:22
apwdid it fail with the same message as before or by dopping to busybox14:22
apwif you didn't get a busy box you didn't get an initrd14:22
nfkmaybe ubuntu uses real_root not root for the actual /?14:22
nfkyeah, same message as before14:22
apwthen your issue is your initramfs somehow14:23
apwyou would not get that message with a valid one14:23
apwyou would get a busybox shell, and if you do not have an initrd14:23
apwyou cannot ever boot an lvm system, full stop14:23
apwas it is the proggies in there which find it14:23
apwso we 14:23
apwso, we have to be suspicious of your initrd contents there14:23
nfklet's cat it14:24
apwhow many kernels do you have in there14:24
nfkprinting a lot14:24
nfkstill cat'ing14:24
apwbut its not loading right somehow14:24
nfkand still14:24
apwelse the kernel would mount it14:24
apwand not spew its root not found thing14:24
apw(as root in its world should be the initrd)14:24
nfkstil lgoing and not even all zeroes14:25
apwyep14:25
nfki have quite a fe14:25
nfkw14:25
nfkincluding something like 3.214:25
=== kentb-afk is now known as kentb
apwif it is real then its 40MB14:25
nfkwhat?14:25
apwif the initrd is real then it is not tiny14:25
nfk2,8M    /boot/initramfs-3.9.10-gentoo.img14:26
nfk2,8M    /boot/initramfs-3.9.11-gentoo-r1.img14:26
nfk5,6M    total14:26
nfkthose boot this system14:26
apwdepends if they are minimal ones, or default ones14:26
nfkthis /boot is merely 30 MB14:26
apwminimal ones are much smaller14:26
apwlook i don't want to argue about how big the world can or is14:26
nfkthough i'm migrating to 100M one someday this month14:27
nfkanyway, still cat'ing14:27
nfki'd say the initrd looks legit14:27
apwls -l would have worked btw14:28
apwand which kernels have you tried, what filenames14:28
nfkcat is more fun and i never knew they were that large14:28
nfki'm used to few MB files14:28
apweven 1MB is going to take 'some time' through that emulated output channel14:28
nfkthe kernels are larger than their initrds14:29
nfkright, ^C didn't work, fun times14:29
nfkthanks ibm for the 3 finger salute14:29
nfkoh, ls -l actually prints UUIDs14:30
nfkso... root or real_root or what?14:30
apwas i keep saying, if you are seeing the kernel panic on mount14:30
apwyou are not getting an initrd14:30
apwroot is a kernel command line, and not going to help14:31
apwand we use root=14:31
apwdoes boot show it loading both at the top ?14:31
nfkboth?14:31
apwvmlinx and initrd14:31
nfkit read RAMDISK and then EOF and go uncompression error14:31
apwand uncompression error14:32
apwthat sounds bad14:32
apwhow big did you say it was, ls -l on it14:32
nfklet's reboot again14:32
apwan uncompresson error from the kernle, will bin the initrd as if it isn't there14:32
apwdid we have a nasty crash or odd behavior before the boot which didn't work ?14:33
nfk9.62k if i'm worth any salt14:33
nfkthe system was often low on free space on / but i'm fairly sure after latest updates it had 400M free14:34
apw9.62 k ?14:34
apwthat is definatly not an initrd14:34
nfkalthough i had to do them via apt-* as GUI just outright crashed because it ran out of free space (removing older kernels freed up 2G, btw)14:34
apwnfk, so do you have any initrd's which are bigger14:34
apw-rw-r--r-- 1 root root  31M Aug 24 22:23 initrd.img-3.8.0-29-generic14:35
apwthat is a generci one, one which is portable, and the default options make these sort of sizes14:35
nfkboth -28 and -29 are around 32M14:35
apwok boot one of that pair with its paired kerenl image14:35
apwand then rebuild your initrd for the latest kernel14:36
nfki'm fairly sure i have tried them14:36
nfkno dice14:36
nfkbut let's try again14:36
apwas a test i just booted a kernel with just14:36
nfkno root=, correct?14:36
apwlinux /boot/vmlinux-VER14:36
apwinitrd /boot/initrd-VER14:36
apwboot14:36
apwand it fails, because there is no root=14:36
apwbut ... it drops me correclty to the (initramfs) busybox prompt14:36
nfkerp14:37
nfki may have cocked up, didn't find a valid RAMDISk14:37
nfk              wow14:39
nfkgot to the emergency shell14:39
nfkfinally14:39
nfkanyway, where's the fstab? shouldn't an initrd have one so that it knows what to mount?14:40
apwheh no14:41
apwso you should be able to use lvm commands now14:42
apwvia the lvm wrapper14:42
apwto confirm the name of the disk14:42
nfkdisk?14:42
apwthe voluem14:42
nfkgrub already told me both pv and lv names14:42
apwwell the key i was trying to achieve was finding a working initrd14:43
apwso you have a pair there, i believe if you reboot usingf those14:43
nfkand i did set them as root=/dev/mapper/vg_my-root14:43
apwwhile there have a look in /dev/mapper14:43
apwls /dev/mapper14:43
apwand you can see the actual name you need to use in root=14:43
nfkyeah14:44
nfkvg_my-root14:44
apwthere is some odd mapping with s/-/--14:44
apwso you booted these linux/initrd combination with root=/dev/mapper/vg_my-root14:44
apwand still ended up at (initramfs)14:44
nfki used it for linux command14:45
apwcat /proc/cmdline14:45
nfkshould i have set it for initrd too?14:45
apwnope you did it right in theory14:45
nfknot this time14:45
nfkelse i'd get the lovely not syncing error14:45
apw?14:45
nfkwhat?14:46
apwnfk you could try mounting it now14:46
apwmount /dev/mapper/vg_my-root /root14:46
nfkto where?14:46
apwand if that works you could hit ^D14:46
apwand see if it boots14:46
nfkinvalid argument14:48
nfkwtf14:48
nfkreplacing mount with ls seems to work so the path have to be right14:48
nfkwait14:48
nfkare you sure you know lvm?14:48
apw?14:49
* xnox raises an eyebrow and goes to fetch more coffee.14:49
nfki mean, is this really how lvm is mounted?14:49
apwnfk, it and i are not intimate in the bedroom departement but i have perhaps 6 systems with lvm on it14:49
nfki'm about to lower my head and fetch something stronger14:49
apwyes lvm is mounted out of initrd, cause the kernel doesn't know how14:50
jsalisbury**14:50
jsalisbury** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting14:50
jsalisbury**14:50
apwwhich is why you have dmsetup in your initrd to hadle it14:50
apwnfk, what did cat /proc/cmdline say before you tried that14:50
nfkthe expected14:51
nfkBOOT_IMAGE=blablabla14:51
nfknothing about root as i didn't set it14:51
apwok so .. redo the boot with the same pair but adding root=14:51
nfkand set to what?14:51
apwroot=/dev/mapper/vg_my-root14:52
apwif that is what your root is called14:52
nfkmy is actually something more personal but yeah14:52
nfkkernel panick14:53
nfk-k14:53
nfkas usual14:53
nfkand couldn't find a valid ramdisk14:53
nfkwhat on earth14:53
apwand without root= it worked, that makes no sense14:54
nfklet's try again, maybe i'm just too tired14:54
nfkso it worked out this time14:57
apwso if you get logged in14:57
nfki may have set the wrong initrd by accident14:57
nfkso slow that it might be booting14:57
apwthen you want to rebuild the initrd, adn grub cfg14:57
apwupdate-initramfs -u; update-grub14:57
apwthen you might be able to reboot again14:57
apwif that works we know it was the space issue14:58
nfkah, so it's network that's making my startup so slow always14:58
nfkanyway, apw, hi514:58
nfkit booted14:58
nfknow time to regenerate the config14:58
nfkit was only grub being horrible, at lesat i hope so14:58
nfk*least14:58
apwnote to self: don't reboot after runnig out of space, without checvking you ahve a valid kernle/initrd/grub.cfg14:59
nfki did check that there were like 400M free and that there were no errors while finishing up updating15:00
nfkoh15:00
nfkmy bad, 1.3G free15:00
nfkthat can't be from running out of free space15:00
apwdepends how many old kernels you ripped15:01
apwthey are pretty huge including headers15:01
nfkunless it ran out of free space on the GUI update, crapped itself but marked updates as finished (can't happen on gentoo but maybe it can on kubunu/ubuntu)15:01
apwanyhow, i presume you can recover this into normality15:01
apwnot an installer expert, though dpkg is pretty careful normally15:01
nfkyeah, though i'm wondering if it won't repeat itself15:01
apwthough initramfs and grub.cfg are not 'updated' per-se15:02
apwthose are generated on the system15:02
apwyou don't have a separate /boot here15:02
nfkoh my HARUHI15:02
nfkthe grub config now cats just fine15:02
nfkwhat on... i dunno, hell?15:02
apwlvm tended to have a separae partition for /boot 15:03
nfkit previously didn't print anything from grub prompt but now it's looking fine15:03
apwwhich would show up in df obviously15:03
nfkit's on /15:03
nfkalso i could access kernels and initrds just fine15:03
apwi would be installing grub again as well just to be sure15:04
nfkand env is catting as ################# even from GUI15:04
apwyou know your latest initrd is short i think ?15:04
nfkactually, i'll reboot and we'll see again15:04
nfkhmm..15:04
apwi'd check that before though15:05
nfkthe ones in / are indeed 015:05
nfkbut the ones in /boot are all fine15:06
nfkincluding -3015:06
nfkapw, sudo update-initramfs -u only touched the -30 in /boot not the ones in /15:08
nfkalso even vmlinuz in / are 015:08
apwthe ones in / are links15:08
apwlrwxrwxrwx   1 root root    29 Aug 24 22:23 vmlinuz -> boot/vmlinuz-3.8.0-29-generic15:08
nfkwell, time to re boot15:08
apwlrwxrwxrwx   1 root root    32 Aug 24 22:23 initrd.img -> boot/initrd.img-3.8.0-29-generic15:08
nfkthe grub config is 24k from GUI15:09
nfkand now i can cat it just fine15:10
nfkthe only thing i did was sudo update-initramfs -u (which rebuilt the initrd for -30) and rebooted15:10
nfki have no idea what is going on anymore15:10
nfkapw, anyway, thanks a lot15:11
nfki was ready to go opensuse or even arch15:11
apwhave fun with that15:13
nfkno thanks15:13
nfki dislike suse and arch is incompatible with me15:14
apwppisati, how important is this ABUS ADT compatibility change ?15:15
apwppisati, as it sure as hell doesn't work right15:15
ppisatiapw: abus adt?15:16
apw    UBUNTU: [Config] ARM_ATAG_DTB_COMPAT=y15:16
apwppisati, ^ that bag of untested crap15:16
ppisatiapw: that is working, but we need a flash-kernel capable of appending the dtb at the end of the kernel15:17
apwppisati, kernel doesn't build on armhf for me with it turned on15:18
apwhow did you test it15:18
ppisatiapw: let me try it15:18
ppisatiapw: was using vanilla rc715:18
apwppisati, try and build the tip of master-next on saucy15:18
ppisatiapw: let me try15:19
apwfails for me with a linking error on a stackprotector symbol15:19
apwppisati, so you never tried this option against our tree before, so i am not going ma15:21
apwmad15:21
ppisatiapw: if it's preventing the kernel from building, rip it off15:22
ppisatiapw: i'll follow p with another patch15:22
apwppisati, it does seem to be, i am tracking it now, mips seems to have had the same issue15:23
apwi am trying their solutio15:23
apwgive me 10m before i give up and throw it back at you15:23
nfkapw, guess three times what happened after i updated and used autoclean or whatever removed unneeded packages15:29
nfki'm starting to suspect file system not getting synced or something15:30
apwnfk, well it naturally syncs after 30s and you are rebooting which natrually syncs15:31
apwas it unmounts at least15:31
nfkapw, yeah, mounted manually, booted just fine, rebooted and now it works right from POST15:44
nfkerr15:44
nfknot mounted but booted manually15:44
apwppisati, ok i think i have a recipe to make this compile15:54
apwppisati, will confirm and get back to you15:55
ppisatiapw: cool, thanks15:57
apwjsalisbury, hey ... bug #1219660 that anthony is asking about, i think we expect lts backport kernels to carry that additional firmware, is this a bug you are aware ?16:20
ubot2`Launchpad bug 1219660 in linux (Ubuntu) "Bluetooth device 0cf3:0036 is not supported" [Undecided,Confirmed] https://launchpad.net/bugs/121966016:20
jsalisburyapw, I haven't done anything with that bug, since it was assigned to Anthony.16:21
apwjsalisbury, ok ta16:22
jsalisburyapw, I usually just give a bug assinged to someone a quick review, but then assume they are working it.  16:25
apwjsalisbury, understood16:25
jsalisbury##16:57
jsalisbury## Kernel team meeting in 2 minutes16:57
jsalisbury##16:57
apwppisati, are you able to test the concatenated dtb stuff locally if i have a kernle which builds ?17:02
ppisatiapw: yep17:02
apwppisati, ok, i've pushed a preliminary master-next for the next upload, could you test that on something arm for me17:03
ppisatiapw: i'll do17:03
apwppisati, thanks17:03
apwppisati, i am hoping to upload it real soon if/when you are happy17:04
ppisatiapw: i'm a build away from testing, hold on17:04
apwppisati, heh i am not in that much of a hurry, but i know it is beer-o-clock for you17:04
ppisatiapw: i wanna stay sober tonight :)17:05
apwFalse17:05
apw(want_to_stay_sober_p)17:05
apwnil17:05
=== jsalisbury changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Ubuntu Kernel Team Meeting - Tues September 10th, 2013 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
apwyo17:44
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! 17:46
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?17:46
=== kentb is now known as kentb-afk
=== kentb-afk is now known as kentb
=== kentb is now known as kentb-out
=== sergiuse1s is now known as sergiusens

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!