Kernel crash on EFI system
Hello all!
I have Intel server based on S5500BC motherboard. After upgrading from 3.2.0 kernel to any higher version I have system crash during boot:
Begin: Running /scripts/
[ 38.213167] BUG: unable to handle kernel paging request at 000000008e34dd1c
[ 38.296766] IP: [<000000008e34d
[ 38.351108] PGD 2600e0067 PUD 0
[ 38.389939] Oops: 0010 [#1] SMP
[ 38.428772] Modules linked in: raid10 raid456 async_pq async_xor xor async_memcpy async_raid6_recov raid6_pq async_tx hid_generic raid1 e1000e raid0 ptp usbhid multipath ahci libahci hid pps_core linear
[ 38.646663] CPU 5
[ 38.668628] Pid: 469, comm: mount Not tainted 3.9.0-030900-
[ 38.794781] RIP: 0010:[<
[ 38.878262] RSP: 0018:ffff880263
[ 38.941860] RAX: ffff88008f5a7218 RBX: ffff88026367b408 RCX: ffff88026367b008
[ 39.027316] RDX: ffff88026367b408 RSI: ffff8802631f9d30 RDI: ffff88026367b008
[ 39.112773] RBP: ffff88026367b828 R08: ffff88026367b828 R09: ffff8802631f9d30
[ 39.198230] R10: 0000000000000000 R11: ffffffff81845560 R12: ffff880266bf4690
[ 39.283686] R13: ffffffff81f6b158 R14: ffff88026367b408 R15: ffff88026367b008
[ 39.369141] FS: 00007f34a59fa80
[ 39.466046] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 39.534851] CR2: 000000008e34dd1c CR3: 0000000260094000 CR4: 00000000000007e0
[ 39.620307] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 39.705762] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[ 39.791219] Process mount (pid: 469, threadinfo ffff8802631f8000, task ffff88025fdc9750)
[ 39.888122] Stack:
[ 39.912165] ffff88008e3697a3 ffffea00097e24c0 ffff880266c02700 0000000000000000
[ 40.001161] ffff88026383de47 0000000000000000 ffff8802631f9cb0 ffffffff81a74b7d
[ 40.090154] ffff8802631f9c78 ffff8802631f9c30 ffff88008e369768 ffff88026367b008
[ 40.179150] Call Trace:
[ 40.208408] [<ffffffff81055
[ 40.270966] [<ffffffff811b5
[ 40.334562] [<ffffffff811b5
[ 40.398162] [<ffffffff81054
[ 40.473213] [<ffffffff815a9
[ 40.548260] [<ffffffff815a9
[ 40.617064] [<ffffffff811a2
[ 40.682744] [<ffffffff815a9
[ 40.750507] [<ffffffff811a2
[ 40.813066] [<ffffffff811bb
[ 40.881869] [<ffffffff811bc
[ 40.950672] [<ffffffff811be
[ 41.017393] [<ffffffff811bf
[ 41.080994] [<ffffffff811bf
[ 41.143552] [<ffffffff8170d
[ 41.217556] Code: Bad RIP value.
[ 41.257432] RIP [<000000008e34d
[ 41.312810] RSP <ffff8802631f9bd8>
[ 41.354552] CR2: 000000008e34dd1c
[ 41.394212] ---[ end trace 3864a6ce97098ad5 ]---
[ 41.468067] Adding 9757564k swap on /dev/md1. Priority:-1 extents:1 across:9757564k
[ 41.598047] EXT4-fs (md0): re-mounted. Opts: errors=remount-ro
[ 41.863427] FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 42.054903] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
The only solution I have found is to add 'noefi' as kernel parameter.
I tried to find similar issues (crashes connected with EFI), but part of them is already fixed and other part relates to laptops problems.
Anybody known real solution without appending 'noefi' or similar params?
Question information
- Language:
- English Edit question
- Status:
- Solved
- For:
- Ubuntu Edit question
- Assignee:
- No assignee Edit question
- Solved by:
- N1ck 7h0m4d4k15
- Solved:
- Last query:
- Last reply: