Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #59593 > unrolled thread

Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

Back to article view | Back to linux.debian.kernel

Contents

  Bug#884069: Kernel crash on boot on IBM BladeCenter HS22 Rolandas Naujikas <rolandas.naujikas@mif.vu.lt> - 2017-12-11 08:30 +0100
    Bug#884069: Kernel crash on boot on IBM BladeCenter HS22 Bernhard Schmidt <berni@birkenwald.de> - 2017-12-11 08:40 +0100
    Bug#884069: system cannot boot after upgrade to Debian 8.10 Rolandas Naujikas <rolandas.naujikas@mif.vu.lt> - 2017-12-11 08:40 +0100
    Bug#884069: the same problem on different hardware Rolandas Naujikas <rolandas.naujikas@mif.vu.lt> - 2017-12-11 08:40 +0100
    Bug#884069: Kernel crash on boot on IBM BladeCenter HS22 Thomas Martin <tmartincpp@gmail.com> - 2017-12-11 09:30 +0100
    Bug#884069: Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems Chris Hofstaedtler <zeha@debian.org> - 2017-12-14 13:00 +0100

#59593 — Bug#884069: Kernel crash on boot on IBM BladeCenter HS22

Package: linux-image-3.16.0-4-amd64
Version: 3.16.51-2

Loading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
[    0.604128] general protection fault: 0000 [#1] SMP
[    0.609303] Modules linked in:
[    0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W
3.16.0-4-amd64 #1 Debian 3.16.51-2
[    0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077,
BIOS -[P9E163AUS-1.24]- 09/17/2014
[    0.631141] task: ffff8803731392d0 ti: ffff88037313c000 task.ti:
ffff88037313c000
[    0.638684] RIP: 0010:[<ffffffff8109be3d>]  [<ffffffff8109be3d>]
build_sched_domains+0x72d/0xcf0
[    0.647609] RSP: 0000:ffff88037313fdf8  EFLAGS: 00010216
[    0.652982] RAX: 0000ffff00000000 RBX: 0000000000000000 RCX:
0000000000000012
[    0.660175] RDX: 0000000000016f48 RSI: 0000000000000000 RDI:
0000000000000200
[    0.667372] RBP: ffff880372f5d698 R08: ffff880372f5e0e0 R09:
0000000000000139
[    0.674566] R10: 0000000000000000 R11: ffff88037313fb06 R12:
ffff880372f5e0c0
[    0.681761] R13: 0000000000000200 R14: ffff880672e640c0 R15:
0000000000000200
[    0.688958] FS:  0000000000000000(0000) GS:ffff88037fc00000(0000)
knlGS:0000000000000000
[    0.697110] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b

[    0.702914] CR2: ffff88067ffff000 CR3: 0000000001813000 CR4:
00000000000007f0
[    0.710109] Stack:
[    0.712183]  ffff880600000000 ffff880372f5e0d8 ffff880372f5d600
ffff880672e640c0
[    0.719940]  0000000000000000 0000000000000000 0000000000000000
ffff880372f53e00
[    0.727715]  0000000000000000 000000000000f1c8 ffffffff00000000
0000000000000000
[    0.735501] Call Trace:
[    0.738022]  [<ffffffff8192332c>] ? sched_init_smp+0x398/0x452

[    0.743930]  [<ffffffff815244de>] ? mutex_lock+0xe/0x2a
[    0.749229]  [<ffffffff81069b23>] ? put_online_cpus+0x23/0x80

[    0.755050]  [<ffffffff810f284c>] ? stop_machine+0x2c/0x40

[    0.760618]  [<ffffffff8190415e>] ? kernel_init_freeable+0xdd/0x1e1

[    0.766963]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
[    0.772264]  [<ffffffff81512c0a>] ? kernel_init+0xa/0xf0

[    0.777652]  [<ffffffff81525c58>] ? ret_from_fork+0x58/0x90

[    0.783298]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
[    0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75

[    0.812501] RIP  [<ffffffff8109be3d>] build_sched_domains+0x72d/0xcf0

[    0.819101]  RSP <ffff88037313fdf8>
[    0.822668] ---[ end trace b6ea7a8f78a6ba93 ]---
[    0.827375] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[    0.827375]
[    0.836621] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x0000000b
[    0.836621]

[toc] | [next] | [standalone]

#59594

Control: severity -1 critical

On Mon, Dec 11, 2017 at 09:14:27AM +0200, Rolandas Naujikas wrote:

Hi,

> Package: linux-image-3.16.0-4-amd64
> Version: 3.16.51-2
> 
> Loading Linux 3.16.0-4-amd64 ...
> Loading initial ramdisk ...
> [    0.604128] general protection fault: 0000 [#1] SMP
> [    0.609303] Modules linked in:
> [    0.612493] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W
> 3.16.0-4-amd64 #1 Debian 3.16.51-2
> [    0.621685] Hardware name: IBM BladeCenter HS22 -[7870SGX]-/68Y8077,
> BIOS -[P9E163AUS-1.24]- 09/17/2014
> [    0.631141] task: ffff8803731392d0 ti: ffff88037313c000 task.ti:
> ffff88037313c000
> [    0.638684] RIP: 0010:[<ffffffff8109be3d>]  [<ffffffff8109be3d>]
> build_sched_domains+0x72d/0xcf0
> [    0.647609] RSP: 0000:ffff88037313fdf8  EFLAGS: 00010216
> [    0.652982] RAX: 0000ffff00000000 RBX: 0000000000000000 RCX:
> 0000000000000012
> [    0.660175] RDX: 0000000000016f48 RSI: 0000000000000000 RDI:
> 0000000000000200
> [    0.667372] RBP: ffff880372f5d698 R08: ffff880372f5e0e0 R09:
> 0000000000000139
> [    0.674566] R10: 0000000000000000 R11: ffff88037313fb06 R12:
> ffff880372f5e0c0
> [    0.681761] R13: 0000000000000200 R14: ffff880672e640c0 R15:
> 0000000000000200
> [    0.688958] FS:  0000000000000000(0000) GS:ffff88037fc00000(0000)
> knlGS:0000000000000000
> [    0.697110] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> 
> [    0.702914] CR2: ffff88067ffff000 CR3: 0000000001813000 CR4:
> 00000000000007f0
> [    0.710109] Stack:
> [    0.712183]  ffff880600000000 ffff880372f5e0d8 ffff880372f5d600
> ffff880672e640c0
> [    0.719940]  0000000000000000 0000000000000000 0000000000000000
> ffff880372f53e00
> [    0.727715]  0000000000000000 000000000000f1c8 ffffffff00000000
> 0000000000000000
> [    0.735501] Call Trace:
> [    0.738022]  [<ffffffff8192332c>] ? sched_init_smp+0x398/0x452
> 
> [    0.743930]  [<ffffffff815244de>] ? mutex_lock+0xe/0x2a
> [    0.749229]  [<ffffffff81069b23>] ? put_online_cpus+0x23/0x80
> 
> [    0.755050]  [<ffffffff810f284c>] ? stop_machine+0x2c/0x40
> 
> [    0.760618]  [<ffffffff8190415e>] ? kernel_init_freeable+0xdd/0x1e1
> 
> [    0.766963]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
> [    0.772264]  [<ffffffff81512c0a>] ? kernel_init+0xa/0xf0
> 
> [    0.777652]  [<ffffffff81525c58>] ? ret_from_fork+0x58/0x90
> 
> [    0.783298]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
> [    0.788595] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
> a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
> 8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75
> 
> [    0.812501] RIP  [<ffffffff8109be3d>] build_sched_domains+0x72d/0xcf0
> 
> [    0.819101]  RSP <ffff88037313fdf8>
> [    0.822668] ---[ end trace b6ea7a8f78a6ba93 ]---
> [    0.827375] Kernel panic - not syncing: Attempted to kill init!
> exitcode=0x0000000b
> [    0.827375]
> [    0.836621] ---[ end Kernel panic - not syncing: Attempted to kill
> init! exitcode=0x0000000b
> [    0.836621]

Seeing the same on two Dell R610 after the point release.

Bernhard

[toc] | [prev] | [next] | [standalone]

#59595 — Bug#884069: system cannot boot after upgrade to Debian 8.10

Severity: critical

[toc] | [prev] | [next] | [standalone]

#59596 — Bug#884069: the same problem on different hardware

Loading Linux 3.16.0-4-amd64 ...
Loading initial ramdisk ...
[    0.349165] general protection fault: 0000 [#1] SMP
[    0.352000] Modules linked in:
[    0.352000] CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W
3.16.0-4-amd64 #1 Debian 3.16.51-2
[    0.352000] Hardware name: Sun Microsystems Sun Fire X2200 M2
                /S39              , BIOS S39_3B27 02/04/2009


[    0.352000] task: ffff88021b4dd2d0 ti: ffff88021b4f0000 task.ti:
ffff88021b4f0000
[    0.352000] RIP: 0010:[<ffffffff8109be3d>]  [<ffffffff8109be3d>]
build_sched_domains+0x72d/0xcf0
[    0.352000] RSP: 0000:ffff88021b4f3df8  EFLAGS: 00010216

[    0.352000] RAX: 0000ffff00000000 RBX: 0000000000000000 RCX:
0000000000000002
[    0.352000] RDX: 0000000000016cc8 RSI: 0000000000000000 RDI:
0000000000000200
[    0.352000] RBP: ffff88021b5d1d98 R08: ffff88021b5d0760 R09:
00000000000000f4
[    0.352000] R10: 0000000000000000 R11: ffff88021b4f3b06 R12:
ffff88021b5d0740
[    0.352000] R13: 0000000000000200 R14: ffff88021b58cac0 R15:
0000000000000200
[    0.352000] FS:  0000000000000000(0000) GS:ffff880223c00000(0000)
knlGS:0000000000000000
[    0.352000] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b

[    0.352000] CR2: ffff880323fff000 CR3: 0000000001813000 CR4:
00000000000007f0
[    0.352000] Stack:
[    0.352000]  ffff880200000000 ffff88021b5d0758 ffff88021b5d1d00
ffff88021b58cac0
[    0.352000]  0000000000000000 0000000000000000 0000000000000000
ffff880323418e00
[    0.352000]  0000000000000000 000000000000f1c8 ffffffff00000000
0000000000000000
[    0.352000] Call Trace:
[    0.352000]  [<ffffffff8192332c>] ? sched_init_smp+0x398/0x452

[    0.352000]  [<ffffffff815244de>] ? mutex_lock+0xe/0x2a
[    0.352000]  [<ffffffff81069b23>] ? put_online_cpus+0x23/0x80

[    0.352000]  [<ffffffff810f284c>] ? stop_machine+0x2c/0x40

[    0.352000]  [<ffffffff8190415e>] ? kernel_init_freeable+0xdd/0x1e1

[    0.352000]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
[    0.352000]  [<ffffffff81512c0a>] ? kernel_init+0xa/0xf0

[    0.352000]  [<ffffffff81525c58>] ? ret_from_fork+0x58/0x90

[    0.352000]  [<ffffffff81512c00>] ? rest_init+0x80/0x80
[    0.352000] Code: c0 0f 85 46 05 00 00 48 8b 74 24 08 48 c7 c2 00 dd
a6 81 bf ff ff ff ff e8 91 78 21 00 48 98 49 8b 56 10 48 8b 04 c5 a0 1e
8e 81 <48> 8b 14 10 b8 01 00 00 00 49 89 54 24 10 f0 0f c1 02 85 c0 75

[    0.352000] RIP  [<ffffffff8109be3d>] build_sched_domains+0x72d/0xcf0

[    0.352000]  RSP <ffff88021b4f3df8>
[    0.352006] ---[ end trace 68d23c2290c77ca9 ]---
[    0.356017] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[    0.356017]
[    0.360000] ---[ end Kernel panic - not syncing: Attempted to kill
init! exitcode=0x0000000b
[    0.360000]

[toc] | [prev] | [next] | [standalone]

#59600

On Mon, 11 Dec 2017 08:37:30 +0100 Bernhard Schmidt <berni@birkenwald.de> wrote:
> Control: severity -1 critical
>

Same issue for us with Dell PowerEdge R630.


Regards,
Thomas

[toc] | [prev] | [next] | [standalone]

#59655 — Bug#884069: Bug#883938: RFT: Candidate fix for boot failure of Debian 8.10 on various x86 systems

[Multipart message — attachments visible in raw view] — view raw

Hi,

* Ben Hutchings <ben@decadent.org.uk> [171214 11:37]:
> Apologies for this regression.  Salvatore Bonaccorso has tracked down
> which change in 3.16-stable triggers the crash, and I identified some
> related upstream changes which appear to fix it.  An updated package is
> available at:
> 
> https://people.debian.org/~benh/packages/jessie-pu/linux-image-3.16.0-4-amd64_3.16.51-3~a.test_amd64.deb

We just ran into this same issue inside Proxmox VE 5.1-38 on a KVM
guest with 2 Sockets with NUMA enabled.
I can confirm that the test kernel makes the guest boot again.

Many thanks,
Chris

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web