Bug#884069: Kernel crash on boot on IBM BladeCenter HS22
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
Reply to: