=== JanC is now known as Guest37740
=== JanC_ is now known as JanC
[09:37] <mowthegrass> Hi There - Anyone facing issues with 3.19 /4.2 kernel, All DELL servers running on 3.19/4.2 kernel on reboot does not boot and gets stuck with message random: LVM unrandom read with 33 bits of entropy available 
[09:37] <mowthegrass> is it a BUG 
[09:44] <apw> mowthegrass, i'd say it is likely a bug indeed.  that last message doesn't look to be anything other than a warning about early use of entropy before it is really very random; from my reading it is not a blocker
[09:46] <apw> mowthegrass, well it _might_ indicate we are triggering transfer of ral randomness into urandom, so it might indicate a block, very hard to be sure
[09:46] <apw> mowthegrass, do the machines come out of it after some time? 
[09:47] <apw> mowthegrass, but either way, you should file a bug "ubuntu-bug linux" and add the details
[10:22] <mowthegrass> apw:No they dont come up 
[10:23] <apw> mowthegrass, do they come up from cold, or do you have to boot an older kernel
[10:23] <mowthegrass> it just drops to switched clocksource tsc
=== ogra_ is now known as ogra
[12:33] <mowthegrass> apw,Thanks on your input 
[13:14] <fg_> afaict, xenial's kernel is not affected by CVE-2016-6187 (the apparmor setprocattr oops) because the causing commit bb646cdb12e75d82258c2f2e7746d5952d3e321a is not contained in the 4.4 stable kernels - is that correct?
[13:36] <arges> https://people.canonical.com/~ubuntu-security/cve/2016/CVE-2016-6187.html looks like it
[13:39] <fg_> arges: thanks, I only looked at / knew about http://kernel.ubuntu.com/reports/kernel-cves.html (which does not list CVE's that don't affect)
[13:43] <fg_> arges: although your link also says "needs-triage" for some of the entries (e.g., source: linux) ;)
[13:45] <arges> tyhicks: ^^^
[14:40] <tyhicks> fg_: hello
[14:40] <tyhicks> fg_: that's correct (xenial is not affected)
[14:41] <fg_> tyhicks: thanks!
[14:41] <tyhicks> fg_: since I populated the break-fix line with the git hashes of the commit that introduced the flaw and the commit that fixed the flaw, a bot will come through and update the status of all the kernels
[14:42] <tyhicks> fg_: I left it as 'needs-triage' intentionally because of that
[14:49] <fg_> tyhicks: okay - that sounds reasonable ;) thanks for clearing it up!
[14:53] <tyhicks> no problem :)
[15:56] <dmj_s76> is it still possible to get a patch for a nasty bug in the nouveau driver?
[15:57] <dmj_s76> in time for the kernel cycle on the 16.04.1 iso?
[15:57] <apw> dmj_s76, is it in the kernel itself ?  the last kernel has been uploaded (in theory)
[15:58] <apw> dmj_s76, though depending on severity and recoverablility, you never know
[15:58] <dmj_s76> apw: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/tree/drivers/gpu/drm/nouveau/nouveau_drm.c
[15:58] <apw> dmj_s76, what is the bug number
[15:59] <dmj_s76> apw: It prevents installation and booting until you install the nvidia proprietary drivers with Pascal (There is a workaround, but it involves the user knowing about modelines and vga modes)
[16:00] <dmj_s76> apw, looking that up now
=== infinity_ is now known as infinity
[16:30] <dmj_s76> apw: couldn't find a bug report so filed one: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602340
[16:30] <ubot5> Launchpad bug 1602340 in linux (Ubuntu) "nouveau: boot hangs at blank screen with unsupported graphics cards" [Undecided,Incomplete]
[16:30] <apw> dmj_s76, and is there a fix yet ?
[16:31] <apw> dmj_s76, i assume the code thinks it supports those cards
[16:31] <dmj_s76> apw: I believe so.  Ben Skeggs worked on one yesterday, which I'm planning to test today.
[16:31] <apw> dmj_s76, could you add any information you have on the fix to the bug as well pls
[16:32] <dmj_s76> apw: https://github.com/skeggsb/nouveau/commit/11fcd1624b0a1c73fe3b2fa15c3cc45816da0470
[16:35] <dmj_s76> apw: added
[16:38] <apw> dmj_s76, thanks ...
[16:39] <apw> dmj_s76, and ... keep that bug updated with your testing too pls
[16:42] <dmj_s76> Will do, really hoping to get this in the iso, since it's an issue that will make most users consider Ubuntu uninstallable if they have a recent GPU.
=== JanC is now known as Guest1477
=== JanC_ is now known as JanC
[17:00] <apw> dmj_s76, i assume you have a range of affected and non-affected GPUs you could test this on to make sure it does not regress older kit
[17:02] <apw> dmj_s76, would a test kernel help your testing ?
[17:13] <dmj_s76> apw: Yes, we have 9 series and 7 series to test for regression
[17:13] <apw> dmj_s76, cool, could you document that in the bug as well
[17:42] <kamal> dmj_s76, I've built a Xenial test kernel with the nouveau patch applied: http://people.canonical.com/~kamal/lp1602340/ ... does that advance your testing efforts?
[20:16] <dmj_s76> apw: Thanks for the build.  I've tested the patched kernel on our hardware and it allows clean installs to boot into unity without trouble.
[20:16] <dmj_s76> No regressions on the older nvidia hardware we have.
[21:51] <apw> kamal, ^
[22:08] <dmj_s76> kamal: thanks for the build...fixes boot issues with current gen nvidia gpus nicely
[22:09] <dmj_s76> If we can get that into the iso, it'll save quite a bit of systems from being effectively uninstallable.
[22:11] <kamal> dmj_s76, yes, saw your feedback, thanks -- we are indeed going to get it into the Xenial ISO for ya
[22:22] <dmj_s76> kamal: Thanks...that'll really help make the Ubuntu install experience better.
[22:24] <kamal> dmj_s76, we agree!  thanks very much for your work on this.