[06:40] <ppisati> moin
[07:04] <smb> ppisati, morning
[07:45] <smb> infinity, Still got a bunch of Xen uploads on my mind which are giving me headaches. For Saucy there is a FFE as well...
[07:55] <apw> xnox, when did we switch to upstart user sessions by default ?
[07:56] <xnox> apw: week1 of saucy
[07:56] <xnox> apw: raring had it available (~2-3 weeks after feature freeze), but needed a manual configuration file change.
[07:56] <xnox> to activate.
[07:57] <apw> xnox, i mean as a default option on a new image
[07:57] <apw> in saucy
[08:02] <xnox> apw: 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] <xnox> on server/tty there is still no user sessions.
[08:02] <smb> At least it would not explain the sudden rise of boot time
[08:03] <apw> smb, no?  would not early in teh cycle be june ?
[08:03] <smb> Oh hm
[08:05] <xnox> smb: 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] <apw> xnox, we don't use upstart if you type a password ?
[08:06] <smb> xnox, Hm, right, so I type in my password then its not upstart sessions?
[08:06] <xnox> apw: we use it, but it doesn't affect the bootchart.
[08:06] <apw> xnox, boot charts continue through a password ?
[08:06] <xnox> smb: apw: upstart user session is kicked off, after a graphical login.
[08:06] <apw> xnox, well to build the graphical login right ?
[08:07] <apw> xn
[08:07] <apw> xnox, it runs gnome-session etc
[08:07] <xnox> no. lightdm is running under system init, not session init.
[08:07] <apw> right .... in smb's case the new 'delay' is all after he hits return in the password prompt
[08:07] <xnox> maybe i'm not clear....
[08:07] <xnox> apw: oh.
[08:08] <xnox> so in /etc/X11/Xsession.d there is 00upstart & 99upstart, which is what starts user session.
[08:09] <xnox> i don't think we did any benchmarks / charts on how long the login takes with & without upstart user session.
[08:10] <smb> xnox, I just commented out what you said and rebooted the machine. Need to grab the new chart though
[08:11] <smb> From my feeling it still toook a while
[08:12] <xnox> apw: what's "pumbing" vs "xorg +plubming" vs "desktop" on http://reports.qa.ubuntu.com/bootspeed/machine/2/amd64/
[08:13] <apw> xnox, 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 starts
[08:14] <apw> xnox, you can see by following the lines down to where they coincide with a specific process start
[08:14] <smb> xnox, Ok, so it seems its still about 15s
[08:14] <smb> maybe 2s less
[08:15] <xnox> well one can twiddle the init line in the 99upstart script to increase verbosity (e.g. --debug or --verbose).
[08:16] <xnox> to get all events... but the culprit might not be an upstart managed process =/
[08:17] <apw> xnox, indeeed, smb lets do a few runs on each to make sure it is real i guess
[08:22] <smb> apw, 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 start
[08:23] <smb> err
[08:23]  * smb looks at the empty space where all the indicators *should* be
[08:26] <xnox> hm. 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:27] <xnox> good: from june https://jenkins.qa.ubuntu.com/job/bootspeed-saucy-desktop-amd64-acer-veriton-02/27/artifact/11/bootchart.svg
[08:27] <xnox> bad: current https://jenkins.qa.ubuntu.com/job/bootspeed-saucy-desktop-amd64-acer-veriton-02/117/artifact/11/bootchart.svg
[08:36] <smb> xnox, Just to make sure, after commenting out the "ubuntu" in /etc/upstart-xsessions, is none of the indicators coming up an expected result?
[08:37] <xnox> smb: yeap, looks like tedg migrated those to be upstart jobs only without any other way to activate them (e.g. no dbus activation)
[08:38] <smb> xnox, 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 delay
[08:40] <xnox> somehow 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:42] <ppisati> lool: any chance we can get an up to date flash-kernel in ubuntu? we are still stuck at 3.0 while debian has 3.10
[08:43] <ppisati> lool: and they have rudimentary support for contatenating kernel+dtb, something we need too
[08:46] <smb> xnox, 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 start
[08:48] <smb> xnox, 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 on
[08:50] <lool> ppisati: 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 time
[08:51] <ppisati> lool: ok, then i'll import the dtb thing support in ubuntu
[08:51] <lool> ppisati: ok
[08:51] <ppisati> lool: actually what debian has is _really_ trivial, but we can plug on it
[08:51] <lool> ppisati: and I would like too to see the two versions being closer or identical even  :-)
[08:52] <lool> ppisati: cool
[08:54] <ppisati> actually the ubuntu version is at 3.4/3.5
[08:55] <ppisati> but pkg version was never updated
[09:49] <apw> oh goody
[11:52]  * henrix -> food
[12:32] <nfk> what happened to xfs? it seems to have been removed from a kernel some weeks ago making my laptop unbootable
[12:48] <apw> nfk, from which kernel
[12:48] <apw> in which series even
[12:49] <apw> nfk, it is enabled in raring and saucy according to the configs for example
[12:57] <apw> nfk, ?
[13:41] <nfk> latest kubuntu
[13:41] <nfk> 3.8.30 or thereabout i think
[13:42] <nfk> apw, ^
[13:45] <apw> debian.master/config/config.common.ubuntu:CONFIG_XFS_FS=m
[13:45] <apw> nfk, so it is enabled there
[13:45] <apw> nfk, how can you tell the kernel doesn't supportit
[13:45] <nfk> and it was never disabled?
[13:46] <nfk> i think i managed to boot that kernel manually and it didn't list xfs partitions or something like that, let me try again
[13:46] <apw> indeed, it seems to have always been on for all of raring
[13:46] <nfk> while the previous kernel at least got to emergency shell (although didn't mount / as i didn't know how to specify that)
[13:47] <nfk> also unlike gentoo's dracut initrd that one seemed so basic it was unusable for recovery, derp
[13:47] <nfk> then again, maybe that was because it couldn't mount /
[13:50] <apw> nfk, it has enough bits to mount root in general and little more
[13:50] <apw> why would it have more
[13:51] <apw> so the previous kernel didn't work either ?
[13:51] <apw> has this system ever worked?
[13:51] <apw> and if so which kernel works there
[13:51] <apw> nfk, ^
[13:51] <nfk> yes, it's an upgrade from the last version that had alternative cd
[13:51] <nfk> the only way to install on lvm2
[13:54] <nfk> why is grub so hard to boot manually </rant>
[13:54] <nfk> for starters it's not even possible to read all of help
[13:54] <apw> nfk, i thought the live CD now did lvm
[13:54] <apw> pretty sure that is how i installed a machine on my desk here
[13:55] <apw> anyhow is this breaking at grub or at initrd
[13:56] <nfk> i have no idea at this point
[13:56] <nfk> i can't even manage to boot any kernel at this point
[13:56] <apw> they have rather different prompts
[13:56] <apw> grub i am pretty sure has grub> in its prompt
[13:56] <apw> and initramfs has a big splash when it drops there
[13:56] <nfk> even 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 grub2
[13:56] <apw> but if you arn't able to tell perhaps a photo?
[13:56] <nfk> ah, that, yeah, i'm stopping at grub
[13:57] <apw> and ls from there says what
[13:57] <nfk> nothing
[13:57] <nfk> it's the fucking grub
[13:57] <nfk> i bet it can't read its config or something
[13:57] <apw> so you ahve an emergency grub prompt ?
[13:57] <nfk> would be nice if i could tell it to load one
[13:57] <nfk> yes
[13:57] <apw> what sort of LVM config do you have
[13:58] <apw> ie, what is /boot
[13:58] <nfk> i have no idea, it's legacy from fedora 16 or something
[13:58] <nfk> and last time grub at least read out lvm volumes but not this time
[13:58] <nfk> horrible thing
[13:58] <apw> making this easy arn't we
[13:59] <apw> grub can grok lvm nominally it does on many of mine
[13:59] <nfk> it did so last time for me too
[13:59] <nfk> but not this time
[13:59] <apw> nfk, so, your prompt looks like grub> yes ?
[13:59] <nfk> yes
[13:59] <apw> and ls produces absolutly no output
[14:00] <nfk> and i'd apply a brick by now to that promt if i didn't feel sorry for the laptop
[14:00] <nfk> let's restart
[14:00] <nfk> it does produce output, it's listing files on /
[14:00] <apw> ok ls for me shows me the partitions only
[14:00] <nfk> no, ls lists files on /
[14:01] <apw> ls with no parameters doesn't do that for me on my grub> prompt her
[14:01] <apw> it says like *
[14:01] <apw> (hd0) (hd1) ...
[14:01] <nfk> rebooted, grub only states the version and gives generic information about the prompt
[14:01] <nfk> yeah, now it does that for me too
[14:01] <nfk> where's my brick?
[14:02] <apw> and does it list your lvm things
[14:02] <nfk> yeah
[14:03] <nfk> arp, if i do ls <any letter><tab> then it starts to list /
[14:04] <apw> nfk, so i htink you can then do 'configfile /boot/grub/grub.cfg'
[14:04] <apw> and then perhaps hitting ESC will get you your menu
[14:04] <nfk> so i managed to make it read the configfile and nothing really happened except now it only shows grub>
[14:04] <nfk> ah
[14:04] <nfk> let's try esc
[14:05] <nfk> nope, esc didn't help
[14:05] <apw> nothing at all ?
[14:05] <nfk> yeah, boot tells me to load a kernel first
[14:05] <nfk> so i guess it didn't like the configfile
[14:05] <apw> i mean when you hit ESC you didnt get any sort of output
[14:05] <nfk> assuming cat works... the fucking file is empty
[14:06] <nfk> yeah, grubenv prints ############## so i guess the config is empty
[14:06] <nfk> sorry for bothering you
[14:06] <nfk> i guess i may have booted those last two kernels differently back then
[14:07] <apw> cat works ok here
[14:07] <apw> so ... you need to make up the config by hand
[14:08] <apw> linux /vmlinuz
[14:08] <apw> initrd /initrd
[14:08] <apw> boot
[14:08] <nfk> shouldn't kernel something root=label=herpes
[14:08] <apw> might work
[14:08] <nfk> initrd something
[14:08] <nfk> yeah
[14:08] <nfk> i'm fairly sure it won't boot without /
[14:08] <nfk> but let's try
[14:09] <apw> root=<SOMETHNG> which you likely need to know
[14:09] <nfk> yep
[14:09] <nfk> didn't work out without root
[14:09] <apw> if it is lvm it might be easu
[14:09] <nfk> i have no idea how to specify it except for label or uuid (no way) but ic can't make grub print them out this time
[14:09] <apw> root=/dev/mapper/<vgname>-<volume>
[14:10] <apw> if you are using lvm
[14:10] <nfk> oh, i see why i thought xfs was removed
[14:10] <apw> (which it cannot be as we are at grub not the kernel)
[14:10] <nfk> the latest kernel says that it tried ext3 ext4 vfat fuseblk
[14:11] <nfk> apw, actually grub should be able to do it, i just don't know how
[14:11] <apw> i thought grub didn't have a working config
[14:12] <apw> how did it even get to the kernel to say that
[14:12] <nfk> i set kernel and initrd
[14:12] <apw> bear in mind i can see the 26 lines of what you typed and nothing else
[14:13] <apw> i think that implies it didn't load an initrd
[14:13] <apw> as you don't get that error unless the kernel is itself trying to mount /
[14:13] <apw> and from its point of view / is the initramfs
[14:13] <apw> nfk, ^^
[14:14] <apw> and it will only try the ones it can do direct which are the builtins, and wouldn't include anything in lvm regardless
[14:14] <apw> nfk, if your grub.cfg is 0 length then perhaps so is your initrd
[14:14] <apw> try rebooting to grub and loading a much older kernel
[14:15] <nfk> leet's see
[14:15] <apw> and its associated initrd
[14:15] <nfk> that might explain why trying to boot the previous kernel at least got me to the emergency shell
[14:15] <apw> if you are unable to boot that, i would then say you need a recovery image, a live USB stick or something 
[14:15] <apw> so we have some more tooling to look at the image
[14:16] <nfk> if i had that, i'd be installing opensuse about now
[14:16] <nfk> i don't have capabilities to write cd/dvds at this point
[14:16] <nfk> and my only usb stick is a known buggy kingston that boots only when threated with violence and 220V
[14:17] <apw> shame you are making life hard for oneself
[14:17] <apw> anyhow try and older kernel
[14:18] <apw> with the matched initramfs
[14:18] <nfk> this box had a cd/dvd writer but it literally bite the dust and went crazy
[14:18] <nfk> had to remove it
[14:19] <nfk> *bit
[14:19] <nfk> the *old in / didn't work out, let's try the ones in /boot
[14:19] <apw> yeah pick a pair in /boot
[14:20] <apw> nfk, now, i assume the mesasge you saw with the latest kernel was:
[14:20] <apw> List of all partitions:
[14:20] <apw> stuff
[14:20] <apw> No filesystem could mount root, tried: <filesystem names>
[14:21] <nfk>  kernel panic - not syncing...
[14:21] <nfk> after that
[14:21] <nfk> yeah
[14:21] <apw> yeah so that is kernel side, which means it did not load initrd correctly
[14:21] <apw> so that implies initramfs is also broke, perhaps 0 length
[14:22] <nfk> anyway, even 3.8.28 didn't work and i'm certain it got to emergency shell last time
[14:22] <nfk> i guess it didn't like root=/dev/mapper/vg_my-root
[14:22] <apw> did it fail with the same message as before or by dopping to busybox
[14:22] <apw> if you didn't get a busy box you didn't get an initrd
[14:22] <nfk> maybe ubuntu uses real_root not root for the actual /?
[14:22] <nfk> yeah, same message as before
[14:23] <apw> then your issue is your initramfs somehow
[14:23] <apw> you would not get that message with a valid one
[14:23] <apw> you would get a busybox shell, and if you do not have an initrd
[14:23] <apw> you cannot ever boot an lvm system, full stop
[14:23] <apw> as it is the proggies in there which find it
[14:23] <apw> so we 
[14:23] <apw> so, we have to be suspicious of your initrd contents there
[14:24] <nfk> let's cat it
[14:24] <apw> how many kernels do you have in there
[14:24] <nfk> printing a lot
[14:24] <nfk> still cat'ing
[14:24] <apw> but its not loading right somehow
[14:24] <nfk> and still
[14:24] <apw> else the kernel would mount it
[14:24] <apw> and not spew its root not found thing
[14:24] <apw> (as root in its world should be the initrd)
[14:25] <nfk> stil lgoing and not even all zeroes
[14:25] <apw> yep
[14:25] <nfk> i have quite a fe
[14:25] <nfk> w
[14:25] <nfk> including something like 3.2
[14:25] <apw> if it is real then its 40MB
[14:25] <nfk> what?
[14:25] <apw> if the initrd is real then it is not tiny
[14:26] <nfk> 2,8M    /boot/initramfs-3.9.10-gentoo.img
[14:26] <nfk> 2,8M    /boot/initramfs-3.9.11-gentoo-r1.img
[14:26] <nfk> 5,6M    total
[14:26] <nfk> those boot this system
[14:26] <apw> depends if they are minimal ones, or default ones
[14:26] <nfk> this /boot is merely 30 MB
[14:26] <apw> minimal ones are much smaller
[14:26] <apw> look i don't want to argue about how big the world can or is
[14:27] <nfk> though i'm migrating to 100M one someday this month
[14:27] <nfk> anyway, still cat'ing
[14:27] <nfk> i'd say the initrd looks legit
[14:28] <apw> ls -l would have worked btw
[14:28] <apw> and which kernels have you tried, what filenames
[14:28] <nfk> cat is more fun and i never knew they were that large
[14:28] <nfk> i'm used to few MB files
[14:28] <apw> even 1MB is going to take 'some time' through that emulated output channel
[14:29] <nfk> the kernels are larger than their initrds
[14:29] <nfk> right, ^C didn't work, fun times
[14:29] <nfk> thanks ibm for the 3 finger salute
[14:30] <nfk> oh, ls -l actually prints UUIDs
[14:30] <nfk> so... root or real_root or what?
[14:30] <apw> as i keep saying, if you are seeing the kernel panic on mount
[14:30] <apw> you are not getting an initrd
[14:31] <apw> root is a kernel command line, and not going to help
[14:31] <apw> and we use root=
[14:31] <apw> does boot show it loading both at the top ?
[14:31] <nfk> both?
[14:31] <apw> vmlinx and initrd
[14:31] <nfk> it read RAMDISK and then EOF and go uncompression error
[14:32] <apw> and uncompression error
[14:32] <apw> that sounds bad
[14:32] <apw> how big did you say it was, ls -l on it
[14:32] <nfk> let's reboot again
[14:32] <apw> an uncompresson error from the kernle, will bin the initrd as if it isn't there
[14:33] <apw> did we have a nasty crash or odd behavior before the boot which didn't work ?
[14:33] <nfk> 9.62k if i'm worth any salt
[14:34] <nfk> the system was often low on free space on / but i'm fairly sure after latest updates it had 400M free
[14:34] <apw> 9.62 k ?
[14:34] <apw> that is definatly not an initrd
[14:34] <nfk> although 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] <apw> nfk, so do you have any initrd's which are bigger
[14:35] <apw> -rw-r--r-- 1 root root  31M Aug 24 22:23 initrd.img-3.8.0-29-generic
[14:35] <apw> that is a generci one, one which is portable, and the default options make these sort of sizes
[14:35] <nfk> both -28 and -29 are around 32M
[14:35] <apw> ok boot one of that pair with its paired kerenl image
[14:36] <apw> and then rebuild your initrd for the latest kernel
[14:36] <nfk> i'm fairly sure i have tried them
[14:36] <nfk> no dice
[14:36] <nfk> but let's try again
[14:36] <apw> as a test i just booted a kernel with just
[14:36] <nfk> no root=, correct?
[14:36] <apw> linux /boot/vmlinux-VER
[14:36] <apw> initrd /boot/initrd-VER
[14:36] <apw> boot
[14:36] <apw> and it fails, because there is no root=
[14:36] <apw> but ... it drops me correclty to the (initramfs) busybox prompt
[14:37] <nfk> erp
[14:37] <nfk> i may have cocked up, didn't find a valid RAMDISk
[14:39] <nfk>               wow
[14:39] <nfk> got to the emergency shell
[14:39] <nfk> finally
[14:40] <nfk> anyway, where's the fstab? shouldn't an initrd have one so that it knows what to mount?
[14:41] <apw> heh no
[14:42] <apw> so you should be able to use lvm commands now
[14:42] <apw> via the lvm wrapper
[14:42] <apw> to confirm the name of the disk
[14:42] <nfk> disk?
[14:42] <apw> the voluem
[14:42] <nfk> grub already told me both pv and lv names
[14:43] <apw> well the key i was trying to achieve was finding a working initrd
[14:43] <apw> so you have a pair there, i believe if you reboot usingf those
[14:43] <nfk> and i did set them as root=/dev/mapper/vg_my-root
[14:43] <apw> while there have a look in /dev/mapper
[14:43] <apw> ls /dev/mapper
[14:43] <apw> and you can see the actual name you need to use in root=
[14:44] <nfk> yeah
[14:44] <nfk> vg_my-root
[14:44] <apw> there is some odd mapping with s/-/--
[14:44] <apw> so you booted these linux/initrd combination with root=/dev/mapper/vg_my-root
[14:44] <apw> and still ended up at (initramfs)
[14:45] <nfk> i used it for linux command
[14:45] <apw> cat /proc/cmdline
[14:45] <nfk> should i have set it for initrd too?
[14:45] <apw> nope you did it right in theory
[14:45] <nfk> not this time
[14:45] <nfk> else i'd get the lovely not syncing error
[14:45] <apw> ?
[14:46] <nfk> what?
[14:46] <apw> nfk you could try mounting it now
[14:46] <apw> mount /dev/mapper/vg_my-root /root
[14:46] <nfk> to where?
[14:46] <apw> and if that works you could hit ^D
[14:46] <apw> and see if it boots
[14:48] <nfk> invalid argument
[14:48] <nfk> wtf
[14:48] <nfk> replacing mount with ls seems to work so the path have to be right
[14:48] <nfk> wait
[14:48] <nfk> are you sure you know lvm?
[14:49] <apw> ?
[14:49]  * xnox raises an eyebrow and goes to fetch more coffee.
[14:49] <nfk> i mean, is this really how lvm is mounted?
[14:49] <apw> nfk, it and i are not intimate in the bedroom departement but i have perhaps 6 systems with lvm on it
[14:49] <nfk> i'm about to lower my head and fetch something stronger
[14:50] <apw> yes lvm is mounted out of initrd, cause the kernel doesn't know how
[14:50] <jsalisbury> **
[14:50] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[14:50] <jsalisbury> **
[14:50] <apw> which is why you have dmsetup in your initrd to hadle it
[14:50] <apw> nfk, what did cat /proc/cmdline say before you tried that
[14:51] <nfk> the expected
[14:51] <nfk> BOOT_IMAGE=blablabla
[14:51] <nfk> nothing about root as i didn't set it
[14:51] <apw> ok so .. redo the boot with the same pair but adding root=
[14:51] <nfk> and set to what?
[14:52] <apw> root=/dev/mapper/vg_my-root
[14:52] <apw> if that is what your root is called
[14:52] <nfk> my is actually something more personal but yeah
[14:53] <nfk> kernel panick
[14:53] <nfk> -k
[14:53] <nfk> as usual
[14:53] <nfk> and couldn't find a valid ramdisk
[14:53] <nfk> what on earth
[14:54] <apw> and without root= it worked, that makes no sense
[14:54] <nfk> let's try again, maybe i'm just too tired
[14:57] <nfk> so it worked out this time
[14:57] <apw> so if you get logged in
[14:57] <nfk> i may have set the wrong initrd by accident
[14:57] <nfk> so slow that it might be booting
[14:57] <apw> then you want to rebuild the initrd, adn grub cfg
[14:57] <apw> update-initramfs -u; update-grub
[14:57] <apw> then you might be able to reboot again
[14:58] <apw> if that works we know it was the space issue
[14:58] <nfk> ah, so it's network that's making my startup so slow always
[14:58] <nfk> anyway, apw, hi5
[14:58] <nfk> it booted
[14:58] <nfk> now time to regenerate the config
[14:58] <nfk> it was only grub being horrible, at lesat i hope so
[14:58] <nfk> *least
[14:59] <apw> note to self: don't reboot after runnig out of space, without checvking you ahve a valid kernle/initrd/grub.cfg
[15:00] <nfk> i did check that there were like 400M free and that there were no errors while finishing up updating
[15:00] <nfk> oh
[15:00] <nfk> my bad, 1.3G free
[15:00] <nfk> that can't be from running out of free space
[15:01] <apw> depends how many old kernels you ripped
[15:01] <apw> they are pretty huge including headers
[15:01] <nfk> unless 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] <apw> anyhow, i presume you can recover this into normality
[15:01] <apw> not an installer expert, though dpkg is pretty careful normally
[15:01] <nfk> yeah, though i'm wondering if it won't repeat itself
[15:02] <apw> though initramfs and grub.cfg are not 'updated' per-se
[15:02] <apw> those are generated on the system
[15:02] <apw> you don't have a separate /boot here
[15:02] <nfk> oh my HARUHI
[15:02] <nfk> the grub config now cats just fine
[15:02] <nfk> what on... i dunno, hell?
[15:03] <apw> lvm tended to have a separae partition for /boot 
[15:03] <nfk> it previously didn't print anything from grub prompt but now it's looking fine
[15:03] <apw> which would show up in df obviously
[15:03] <nfk> it's on /
[15:03] <nfk> also i could access kernels and initrds just fine
[15:04] <apw> i would be installing grub again as well just to be sure
[15:04] <nfk> and env is catting as ################# even from GUI
[15:04] <apw> you know your latest initrd is short i think ?
[15:04] <nfk> actually, i'll reboot and we'll see again
[15:04] <nfk> hmm..
[15:05] <apw> i'd check that before though
[15:05] <nfk> the ones in / are indeed 0
[15:06] <nfk> but the ones in /boot are all fine
[15:06] <nfk> including -30
[15:08] <nfk> apw, sudo update-initramfs -u only touched the -30 in /boot not the ones in /
[15:08] <nfk> also even vmlinuz in / are 0
[15:08] <apw> the ones in / are links
[15:08] <apw> lrwxrwxrwx   1 root root    29 Aug 24 22:23 vmlinuz -> boot/vmlinuz-3.8.0-29-generic
[15:08] <nfk> well, time to re boot
[15:08] <apw> lrwxrwxrwx   1 root root    32 Aug 24 22:23 initrd.img -> boot/initrd.img-3.8.0-29-generic
[15:09] <nfk> the grub config is 24k from GUI
[15:10] <nfk> and now i can cat it just fine
[15:10] <nfk> the only thing i did was sudo update-initramfs -u (which rebuilt the initrd for -30) and rebooted
[15:10] <nfk> i have no idea what is going on anymore
[15:11] <nfk> apw, anyway, thanks a lot
[15:11] <nfk> i was ready to go opensuse or even arch
[15:13] <apw> have fun with that
[15:13] <nfk> no thanks
[15:14] <nfk> i dislike suse and arch is incompatible with me
[15:15] <apw> ppisati, how important is this ABUS ADT compatibility change ?
[15:15] <apw> ppisati, as it sure as hell doesn't work right
[15:16] <ppisati> apw: abus adt?
[15:16] <apw>     UBUNTU: [Config] ARM_ATAG_DTB_COMPAT=y
[15:16] <apw> ppisati, ^ that bag of untested crap
[15:17] <ppisati> apw: that is working, but we need a flash-kernel capable of appending the dtb at the end of the kernel
[15:18] <apw> ppisati, kernel doesn't build on armhf for me with it turned on
[15:18] <apw> how did you test it
[15:18] <ppisati> apw: let me try it
[15:18] <ppisati> apw: was using vanilla rc7
[15:18] <apw> ppisati, try and build the tip of master-next on saucy
[15:19] <ppisati> apw: let me try
[15:19] <apw> fails for me with a linking error on a stackprotector symbol
[15:21] <apw> ppisati, so you never tried this option against our tree before, so i am not going ma
[15:21] <apw> mad
[15:22] <ppisati> apw: if it's preventing the kernel from building, rip it off
[15:22] <ppisati> apw: i'll follow p with another patch
[15:23] <apw> ppisati, it does seem to be, i am tracking it now, mips seems to have had the same issue
[15:23] <apw> i am trying their solutio
[15:23] <apw> give me 10m before i give up and throw it back at you
[15:29] <nfk> apw, guess three times what happened after i updated and used autoclean or whatever removed unneeded packages
[15:30] <nfk> i'm starting to suspect file system not getting synced or something
[15:31] <apw> nfk, well it naturally syncs after 30s and you are rebooting which natrually syncs
[15:31] <apw> as it unmounts at least
[15:44] <nfk> apw, yeah, mounted manually, booted just fine, rebooted and now it works right from POST
[15:44] <nfk> err
[15:44] <nfk> not mounted but booted manually
[15:54] <apw> ppisati, ok i think i have a recipe to make this compile
[15:55] <apw> ppisati, will confirm and get back to you
[15:57] <ppisati> apw: cool, thanks
[16:20] <apw> jsalisbury, 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/1219660
[16:21] <jsalisbury> apw, I haven't done anything with that bug, since it was assigned to Anthony.
[16:22] <apw> jsalisbury, ok ta
[16:25] <jsalisbury> apw, I usually just give a bug assinged to someone a quick review, but then assume they are working it.  
[16:25] <apw> jsalisbury, understood
[16:57] <jsalisbury> ##
[16:57] <jsalisbury> ## Kernel team meeting in 2 minutes
[16:57] <jsalisbury> ##
[17:02] <apw> ppisati, are you able to test the concatenated dtb stuff locally if i have a kernle which builds ?
[17:02] <ppisati> apw: yep
[17:03] <apw> ppisati, ok, i've pushed a preliminary master-next for the next upload, could you test that on something arm for me
[17:03] <ppisati> apw: i'll do
[17:03] <apw> ppisati, thanks
[17:04] <apw> ppisati, i am hoping to upload it real soon if/when you are happy
[17:04] <ppisati> apw: i'm a build away from testing, hold on
[17:04] <apw> ppisati, heh i am not in that much of a hurry, but i know it is beer-o-clock for you
[17:05] <ppisati> apw: i wanna stay sober tonight :)
[17:05] <apw> False
[17:05] <apw> (want_to_stay_sober_p)
[17:05] <apw> nil
[17:44] <apw> yo
[17:46] <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?