[02:06] <phillw> hi good people.. i seem to have builds
[02:06] <phillw> ali@amjjawad:~/src/linux-3.13$ ls /boot/*3.13*
[02:06] <phillw> /boot/config-3.13      /boot/initrd.img-3.13.0  /boot/vmlinuz-3.13
[02:06] <phillw> ali@amjjawad:~/src/linux-3.13$ 
[02:06] <phillw> what is the nest step?
[02:07] <phillw> ali@amjjawad:~/src/linux-3.13$ ls -al /boot/*3.13*
[02:07] <phillw> -rw-r--r-- 1 root root    161299 Jan 20 21:13 /boot/config-3.13
[02:07] <phillw> -rw-r--r-- 1 root root   2116315 Jan 20 21:14 /boot/initrd.img-3.13
[02:07] <phillw> -rw-r--r-- 1 root root 131261285 Jan 20 23:08 /boot/initrd.img-3.13.0
[02:07] <phillw> -rw-r--r-- 1 root root   2475801 Jan 20 21:13 /boot/System.map-3.13
[02:07] <phillw> -rw-r--r-- 1 root root   5357936 Jan 20 21:12 /boot/vmlinuz-3.13
[02:07] <phillw> sorry, missed the file sizes
[02:09] <phillw> oops.. runs away.. this was a debian installer issue... sorry.
[07:49] <ppisati> yup
[08:56] <apw> ppisati, yupper ?
[08:56]  * apw yawns at the moon
[08:58] <Faux> bug #1270818 apw: That new kernel is delicious and seems fine, thanks.
[08:58] <ubot2`> Launchpad bug 1270818 in linux (Ubuntu) "nouveau(?) breaks or hangs in 3.13.0-4, -2, but not -1 on GK107GLM [Quadro K2000M]" [Medium,Incomplete] https://launchpad.net/bugs/1270818
[08:58] <Faux> I commented the ticket.
[08:58] <ppisati> apw: can you still see the moon over there?
[08:59]  * ppisati is reading kernelnewbies 3.13 summary...
[09:06] <apw> ppisati, a laudible goal ... and no, no actual moon
[10:08] <smb> apw, Ok, that was painful but you got the second ack for henrix cve patch now
[10:09] <henrix> \o/
[10:10] <smb> apw, About the resize problem... I wonder whether I should maybe sit back until the the 3.13 rebase is in the daily so the percpu counting thing has not chance to have another weird effect
[10:21] <apw> yeah possible
[10:21] <apw> smb, ack ta
[10:29] <Kano> Hi, why is 3.13 final without .orig.tar.xz?
[10:39] <apw> lazyness
[12:54] <apw> smb, -5 just hit -release
[12:57] <xnox>  -5 solved my boot problems (compared to -4) so I'm happy =) thanks everyone.
[14:16] <apw> xnox, great
[14:22] <smb> apw, Ok, kinda failed replacing the kernel inside the cloud.image and did the resize with the -4 kernel. This surprisingly worked though leaving a 30G image pretending to be almost full (so ext4 suffered as well at that point). Reboot with -5 made things look good again. So there is a chance that resize is working except with that ugly kernel
[14:23] <apw> smb, yeah sounds plausible
[14:30] <brendand> bjf, those -proposed kernels still held up?
[15:06] <smb> apw, Ah I found the resolution about the resize problem in the past. It was the journal overflowing (when creating the image small and then resize to quite large). Not sure whether the kernel can or actually does better recovery for that now but in general it should be avoided by the cloud-images now being created with an explicit journal size large enough to handle the resize
[15:07] <smb> SpamapS, ^ But your issues may have been related to the percpu counters madness (if you used the 3.13.0-4 kernel
[15:55] <jsalisbury> **
[15:55] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[15:55] <jsalisbury> **
[16:55] <jsalisbury> ##
[16:55] <jsalisbury> ## Kernel team meeting in 5 minutes
[16:55] <jsalisbury> ##
[17:46] <SpamapS> smb: regarding resize issues.. I do have a very large resize reserved because I am making cloud images where I don't know how big the root will be...
[17:46] <SpamapS> bin/disk-image-create:MKFS_OPTS="$MKFS_OPTS -E resize=274877906944"
[17:46] <SpamapS> smb: but, as yet, I have not recreated the problem
[18:37]  * apw reboots to get a kernel which can add up right
[18:44] <apw> that makes a heck of a difference, some 28G of space was mia
[19:41] <jsalisbury> op #ubuntu-kernel
[19:46] <sforshee> hallyn: anyone I should cc when I send this tty patch upstream? Right now I have you and ebiederm.
[20:13] <hallyn> sforshee: that's probably good...  since alan cox gave up on tty i'm not sure;  maybe greg kh.
[20:13] <hallyn> but eric and me + lkml is good
[20:19] <sforshee> hallyn: greg is one of the maintainers so he'll be included
[20:19] <sforshee> should be going out soon
[20:25] <hallyn> sforshee: great, thanks.  whatever happened to tracking down who's pinning the console?
[20:26] <sforshee> hallyn: I updated the bug earlier. lxc sets /dev/kmsg as a symlink to /dev/console, and upstart opens /dev/kmsg.
[20:27] <hallyn> sforshee: aaah.  interesting.  last night i looked to see if lxc could be to blame and i noticed the kmsg handling but figured that was just a bind mount and couldn't be it :)
[20:29] <sforshee> hallyn: I'm not really sure if lxc needs to do something different or if upstart needs to realize that kmsg might be a symlink and use O_NOCTTY. I'll let you and jodh fight that one out ;-)
[20:30] <hallyn> sforshee: i'm probably ok saying that we just don't redirect kmsg for unprivileged containers;  but then if the kernel patch goes through it's moot.
[20:31] <sforshee> hallyn: I think it's an undesirable situation with or without the kernel patch
[21:10] <apw> sforshee, are you sending this patch to "us" as well ?
[21:11] <sforshee> apw: yes after upstream validates its correctness
[21:12] <sforshee> apw: I added cc stable anyway, so assuming it's acceptible it will get to us one way or another
[21:14] <apw> sforshee, sounds perfect thanks
[23:34] <bdmurray> xnox, cjwatson: given the precise branches of ubiquity are out of date how should I submit a fix for bug 1051935 for 12.04.4?
[23:34] <ubot2`> Launchpad bug 1051935 in ubiquity (Ubuntu Precise) "Fails with SystemError when too many files are open" [High,Triaged] https://launchpad.net/bugs/1051935
[23:38] <cjwatson> bdmurray: https://code.launchpad.net/~ubuntu-installer/ubiquity/precise-proposed looks up to date to me
[23:38] <cjwatson> we don't care about the UDD ones
[23:39] <bdmurray> cjwatson: ah, okay thanks