/srv/irclogs.ubuntu.com/2016/10/07/#ubuntu-kernel.txt

=== JanC is now known as Guest21552
=== JanC_ is now known as JanC
=== cpaelzer_ is now known as cpaelzer
jtaylorwhere should I file bugs for the lts-yakkety from the ppa?08:07
apwjtaylor, https://bugs.launchpad.net/ubuntu/+source/linux-lts-yakkety/+filebug i guess08:16
apwjtaylor, but do tell us the bug # here08:16
jtaylorhm is launchpad broken?08:27
jtaylorget an oops on submit ...08:27
apwlovely... try fileing it against linux itself, and i'll sort it out afterwards08:28
apwjtaylor, ^08:28
jtaylorapw: bug 163129808:31
ubot5bug 1631298 in linux (Ubuntu) "lts-yakkety 4.8 cannot mount lvm raid1" [Undecided,New] https://launchpad.net/bugs/163129808:31
apwjtaylor, can i assume this is installing into an existing working system ...  if so could you pastebin me a lsinitamfs of the working and not working initrds please08:34
jtaylor4.8 http://paste.ubuntu.com/23288094/08:36
jtaylor4.4 (working) http://paste.ubuntu.com/23288095/08:36
apwthanks08:37
apwjtaylor, could you boot up this test kernel for me so we can find out what the heck the feature flags are set to ... http://people.canonical.com/~apw/lts-backport-yakkety-xenial/10:08
apwjtaylor, not expecting it to fix anything but should drop an APW: in the dmesg with some info10:09
apwjtaylor, ok naive testing of raid1s created on 4.4 and booted with 4.8 seem to assemble for me10:23
jtaylorapw: my raid is probably a lot older10:23
apwjtaylor, so we need to get that debug output to see what differs on yours to mine10:23
jtaylormaybe 3.13 or more ;)10:23
apwjtaylor, probabally and that is a little scarey :)10:23
jtaylorI'll reboot soon10:23
apwjtaylor, thanks10:23
jtaylorapw: hm all zeros http://paste.ubuntu.com/23288447/10:35
apwjtaylor, oh you are right i have the same error, and yet the lv is there, oh but is it running10:37
jtaylorit is displayed but not active10:38
jtaylorthough I haven't tried activating it manually, I just figured if it puts me in an emergency shell that doesn't work10:38
apwi would doubt it will start10:38
jtaylorI actually forgot to mention that, the system doesn't boot, despite / and /boot being there10:38
apwok i am reproducing in fact, just not seeing what it is saying10:38
apwjtaylor, i am going to assume the data you ahve in your raid1 is something you care about (given it is raid1d)10:46
apwjtaylor, ie this is not something you can trivially test :/10:46
jtayloryes, though I have backups10:47
jtaylorbut destroying it would still be inconvinient10:47
apwjtaylor, do you have a test environment at all?  obviously i can test a fix here but this is pretty scarey code to change10:47
apwjtaylor, anyhow i have a theory and i am testing it, and if that works i'll ask upstream for safety10:48
jtaylorno, this is my home setup I only have this one raid1 system10:49
apwjtaylor, though i guess in theory we could pull off one of the mirrors as a backup, hrm anyho10:50
apwlets get to that once we have any idea if this is right10:50
jtaylorif you are reasonably confident in a fix I can update my backups and test it10:50
=== mhcerri_ is now known as mhcerri
om26erjsalisbury: updated comments on the bug report. The last kernel is good, second-last is bad.13:56
jsalisburyom26er, great, I'll build the next one.  Only one or two left.13:59
om26erjsalisbury: ack.13:59
manjortg, something going on with tangerine ? compiling arm64  Error: selected processor does not support `staddlh w0,[x1]'15:38
manjortg, looks like assembler messages from xenial-amd64 chroot 15:40
manjobjf, apw ^^ anyone know ? trying to build 4.8.0-21.2315:43
manjoI am also seeing ==> Error: attempt to move .org backwards15:45
manjobuild works fine with yakkety-amd64 chroot.. .something broken with xenial-amd64 chroot ? 15:47
om26erjsalisbury: Hi! that's a good kernel.15:56
jsalisburyom26er, ack15:56
om26erjsalisbury: how big is the diff from this stage ? (or number of commits)15:58
jsalisburyom26er, this next kernel will narrow it down between 5 sched commits:16:01
jsalisbury55e16d3 sched/fair: Rework throttle_count sync16:01
jsalisbury599b484 sched/core: Fix sched_getaffinity() return value kerneldoc comment16:01
jsalisbury8663e24 sched/fair: Reorder cgroup creation code16:01
jsalisbury3d30544 sched/fair: Apply more PELT fixes16:01
jsalisbury7dc603c sched/fair: Fix PELT integrity for new tasks16:01
om26erjsalisbury: I am betting on the first one16:02
jsalisburyom26er, :-)  We shall know shortly16:03
jsalisburyom26er, next kernel is posted16:45
om26erjsalisbury: that's a bad kernel17:24
om26erjsalisbury: do we finally have a commit blame ?17:30
=== om26er is now known as om26er1
=== om26er1 is now known as om26er
jsalisburyom26er, we have to test only one more.  Then I'll bulild a test kernel with the reported commit reverted.  The next kernel should be done in a few moments18:20
georgioshi. i saw gresurity related utilities but no grsecurity kernel. how so?18:20
om26erjsalisbury: great18:20
jsalisburyom26er, next test kernel is posted18:42
om26erjsalisbury: thanks, testing it now.18:42
jsalisburyom26er, ack18:42
om26erjsalisbury: that's a good one.18:49
jsalisburyom26er, The bisect reports this as the offending commit:18:49
jsalisburycommit 3d30544f02120b884bba2a9466c87dba980e3be518:49
jsalisburyAuthor: Peter Zijlstra <peterz@infradead.org>18:49
jsalisburyDate:   Tue Jun 21 14:27:50 2016 +020018:49
jsalisbury    sched/fair: Apply more PELT fixes18:49
jsalisburyom26er, I'll build a test kerne with it reverted to see if it fixes the bug.18:50
om26erjsalisbury: you mean 4.8 release minus that commit ?18:51
jsalisburyom26er, I'll build a yakkety kernel, minus that commit18:51
om26erjsalisbury: great18:51
om26erfeels like a small diff https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip/+/3d30544f02120b884bba2a9466c87dba980e3be5%5E%21/18:54
jsalisburyom26er, kernel posted.  Note with this kernel, you need to install both the linux-image and linux-image-extra .deb packages.19:19
om26erjsalisbury: that's it.19:30
om26erlatest kernel is good19:30
jsalisburyom26er, good news.  I'm going to ping upstream and the patch author and get their feedback19:30
om26erjsalisbury: ok, the test case is `stress -c $your_total_cpu_cores`19:31
jsalisburyom26er, thanks.  Can you post that in the bug?  I'll be pointing upstream there.19:32
=== leftyfb_ is now known as leftyfb
om26erdone.19:34
=== sts is now known as Guest59171
=== xnox_ is now known as xnox
=== Darcy is now known as Spydar007
=== kloeri_ is now known as kloeri
=== bdmurray_ is now known as bdmurray

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