kernel-packages team mailing list archive

[Mike Waychison <mikew@xxxxxxxxxx>]

Here's the fragment of Oops I have demonstrating the crash.  If I'm
understanding the versioning here, it looks like the issue may now have
been fully addressed by that patch alone?  :(

[    0.104000] CR2: ffff8807bffff000 CR3: 0000000001c13000 CR4: 00000000001406f0
[    0.104000] Stack:
[    0.104000]  0000000000000000 ffff880796773ea0 ffffffff8176bc39 ffff8807965d3140
[    0.104000]  ffff8807a1001b00 ffffffff81098810 0000000000000000 0000000000000000
[    0.104000]  ffff880796773f48 ffffffff810915f2 0000000000000001 0000000000000001
[    0.104000] Call Trace:
[    0.104000]  [<ffffffff8176bc39>] ? schedule+0x29/0x70
[    0.104000]  [<ffffffff81098810>] ? SyS_setgroups+0x180/0x180
[    0.104000]  [<ffffffff810915f2>] kthread+0xd2/0xf0
[    0.104000]  [<ffffffff81091520>] ? kthread_create_on_node+0x1c0/0x1c0
[    0.104000]  [<ffffffff8176fbd8>] ret_from_fork+0x58/0x90
[    0.104000]  [<ffffffff81091520>] ? kthread_create_on_node+0x1c0/0x1c0
[    0.104000] Code: 89 fa 48 0f a3 11 19 d2 31 f6 85 d2 40 0f 95 c6 ff d0 4c 89 e7 e8 62 de 11 00 48 83 c4 18 31 c0 5b 41 5c 41 5d 41 5e 41 5f 5d c3 <0f> 0b 0f 0b 66 66 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 
[    0.104000] RIP  [<ffffffff810989af>] smpboot_thread_fn+0x19f/0x1b0
[    0.104000]  RSP <ffff880796773e88>
[    0.104028] ---[ end trace b59b90c026f24b92 ]---
[    0.104734] ------------[ cut here ]------------
[    0.105486] kernel BUG at /build/linux-lts-utopic-p81gRk/linux-lts-utopic-3.16.0/kernel/smpboot.c:134!
[    0.106799] invalid opcode: 0000 [#2] SMP 
[    0.107528] Modules linked in:
[    0.108000] CPU: 0 PID: 29 Comm: ksoftirqd/1 Tainted: G      D       3.16.0-55-generic #74~14.04.1-Ubuntu
[    0.108000] Hardware name: Google Google, BIOS Google 01/01/2011
[    0.108000] task: ffff8807966f7010 ti: ffff880796778000 task.ti: ffff880796778000
[    0.108000] RIP: 0010:[<ffffffff810989af>]  [<ffffffff810989af>] smpboot_thread_fn+0x19f/0x1b0
[    0.108000] RSP: 0000:ffff88079677be88  EFLAGS: 00010202
[    0.108000] RAX: 0000000000000000 RBX: ffff8807966f7010 RCX: 0000000000000000
[    0.108000] RDX: ffff88079677bfd8 RSI: ffff8807966f7010 RDI: 0000000000000001
[    0.108000] RBP: ffff88079677bec8 R08: ffff880796778000 R09: 0000000000000246
[    0.108000] R10: ffffffff8106b17c R11: ffffea001e59d800 R12: ffff8807a1001b20
[    0.108000] R13: ffffffff81c40d20 R14: ffff8807966f7010 R15: ffff8807966f7010
[    0.108000] FS:  0000000000000000(0000) GS:ffff8807bfc00000(0000) knlGS:0000000000000000
[    0.108000] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.108000] CR2: ffff8807bffff000 CR3: 0000000001c13000 CR4: 00000000001406f0
[    0.108000] Stack:
[    0.108000]  0000000000000000 ffff88079677bea0 ffffffff8176bc39 ffff8807965d3140
[    0.108000]  ffff8807a1001b20 ffffffff81098810 0000000000000000 0000000000000000
[    0.108000]  ffff88079677bf48 ffffffff810915f2 0000000000000001 0000000000000001
[    0.108000] Call Trace:
[    0.108000]  [<ffffffff8176bc39>] ? schedule+0x29/0x70
[    0.108000]  [<ffffffff81098810>] ? SyS_setgroups+0x180/0x180
[    0.108000]  [<ffffffff810915f2>] kthread+0xd2/0xf0
[    0.108000]  [<ffffffff81091520>] ? kthread_create_on_node+0x1c0/0x1c0

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1527748

Title:
  lts-utopic kernel needs boot-up race condition fix.

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  The underlying kernel bug was originally reported and fixed here:
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1508609

  The bug was fixed confirmed not present in the original trusty kernel
  and has been fixed in vivid and wily, but was not addressed in utopic
  as it has EOL.

  If my understanding is correct, while Utopic has EOL, the lts-utopic
  hwe kernel is expected to be supported until the final Trusty release
  (14.04.05) next summer.  Can we have the original kernel issue also
  addressed in lts-utopic (assuming it hasn't been already?).  We are
  seeing users running this kernel on trusty systems and they still
  appear to be affected.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1527748/+subscriptions