Hi Todd
I'm getting a similar call trace, but with Supermicro X10DRL-CT.
It has an onboard 3108 LSI RAID Controller and I'm also using a NON-RAID AOC-SAS2LP-MV8.
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386453] CPU: 4 PID: 8544 Comm: MegaCli Tainted: G D O 3.10.80-oe64-00000-g65a37f9 #75
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386453] Hardware name: Supermicro Super Server/X10DRL-CT, BIOS 2.0 12/18/2015
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386454] task: ffff88046b7f3480 ti: ffff88043bf36000 task.ti: ffff88043bf36000
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386459] RIP: 0010:[<ffffffffa00c181f>] [<ffffffffa00c181f>] megasas_mgmt_compat_ioctl+0x11f/0x200 [megaraid_sas]
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386459] RSP: 0000:ffff88043bf37e88 EFLAGS: 00010246
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386460] RAX: 0000000000000000 RBX: 00000000087e5508 RCX: 0000000000000000
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386461] RDX: 0000000000000004 RSI: 00000000087e5514 RDI: 00000000ffe11bec
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386462] RBP: fffffffffffffff2 R08: 00000000087e5514 R09: 0000000000000000
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386462] R10: 0000000000000000 R11: 0000000000000001 R12: 00000000087e5508
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386463] R13: 00000000ffe11be0 R14: 0000000000000000 R15: fffffffffffffff7
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386464] FS: 0000000000000000(0000) GS:ffff88047fc80000(0063) knlGS:00000000f750f6c0
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386465] CS: 0010 DS: 002b ES: 002b CR0: 0000000080050033
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386465] CR2: 00000000ffe11bf0 CR3: 000000043bcd5000 CR4: 00000000003407e0
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386466] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386466] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386467] Stack:
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386468] 0000000040000010 00000000087e5508 ffff880420441300 0000000000000003
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386469] 00000000c1144d01 ffffffff8114d879 00000000577ac87b ffffffff8101281f
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386470] ffffffff81012885 0000000000000096 ffff88046b7f3480 ffffffff81071fb6
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386471] Call Trace:
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386474] [<ffffffff8114d879>] ? compat_sys_ioctl+0xc9/0x1190
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386477] [<ffffffff8101281f>] ? native_sched_clock+0xf/0x70
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386479] [<ffffffff81012885>] ? sched_clock+0x5/0x10
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386481] [<ffffffff81071fb6>] ? get_vtime_delta+0x16/0x80
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386482] [<ffffffff81072760>] ? vtime_account_user+0x50/0x70
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386485] [<ffffffff81016cfa>] ? syscall_trace_enter+0x1a/0x1f0
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386487] [<ffffffff816d0519>] ? ia32_do_call+0x13/0x13
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386500] Code: 00 e8 96 ac 25 e1 48 85 c0 0f 85 21 ff ff ff 49 8d 74 24 08 49 8d 7d 08 ba 04 00 00 00 e8 7a ac 25 e1 48 85 c0 0f 85 05 ff ff ff <41> 8b 45 10 85 c0 74 28 41 8b 45 0c 49 8d 4c 05 14 48 89 c8 e8
Jul 4 17:35:18 [kern.alert] kernel: [ 6081.386504] RIP [<ffffffffa00c181f>] megasas_mgmt_compat_ioctl+0x11f/0x200 [megaraid_sas]
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386504] RSP <ffff88043bf37e88>
Jul 4 17:35:18 [kern.err] kernel: [ 6081.386505] CR2: 00000000ffe11bf0
Jul 4 17:35:18 [kern.warning] kernel: [ 6081.386506] ---[ end trace d20de65479607a92 ]---
Could I try this new installer?
Best Regards
Check your inbox here
Gr
this is what I am seeing, too (Supermicro X11SSH-F with Megaraid 9271), how to fix?
Other question: we are an OEM, building HW, installing open-e and the license gets registered to the customer. So I can't open a case?
I also see this message (X11SSH with Megaraid 9271).
How is the correct way to open a case if we are an OEM and the license gets registered to our customer- so I can't open a case for that?
and about this thing?
BUG: unable to handle kernel paging request at 00000000000f6a84380