Only 0.44 (always) days of uptime with ciss (w/HP SA P812)

Nagy, Attila bra at fsn.hu
Wed Mar 26 08:23:48 UTC 2014


On 03/24/14 13:32, Sean Bruno wrote:
>
> Can you open a p/r on this?  I'd like to keep tracking ciss(4) issues.
> It seems like there is something odd with our driver when using multiple
> controllers.
>
Update on this: I've disabled the P410i (previously I wrote P411, but 
this is not a separate card in this machine) and it crashes the same 
way, so it's not related to multiple controllers:

ciss0: ADAPTER HEARTBEAT FAILED


Fatal trap 1: privileged instruction fault while in kernel mode
cpuid = 0; apic id = 00
instruction pointer     = 0x20:0xfffffe0c578b295d
stack pointer           = 0x28:0xfffffe0baf1ab9d0
frame pointer           = 0x28:0xfffffe0baf1aba20
code segment            = base 0x0, limit 0xfffff, type 0x1b
                         = DPL 0, pres 1, long 1, def32 0, gran 1
processor eflags        = interrupt enabled, resume, IOPL = 0
current process         = 12 (swi4: clock)
trap number             = 1
panic: privileged instruction fault
cpuid = 0
KDB: stack backtrace:
db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 
0xfffffe0baf1ab560
kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0baf1ab610
panic() at panic+0x155/frame 0xfffffe0baf1ab690
trap_fatal() at trap_fatal+0x3a2/frame 0xfffffe0baf1ab6f0
trap() at trap+0x794/frame 0xfffffe0baf1ab910
calltrap() at calltrap+0x8/frame 0xfffffe0baf1ab910
--- trap 0x1, rip = 0xfffffe0c578b295d, rsp = 0xfffffe0baf1ab9d0, rbp = 
0xfffffe0baf1aba20 ---
(null)() at 0xfffffe0c578b295d/frame 0xfffffe0baf1aba20
softclock_call_cc() at softclock_call_cc+0x16c/frame 0xfffffe0000e5c120
kernphys() at 0xffffffff/frame 0xfffffe0000e5cd20
kernphys() at 0xffffffff/frame 0xfffffe0000e5d200
kernphys() at 0xffffffff/frame 0xfffffe0000e5d920
Uptime: 10h34m30s
(da0:ciss0:0:0:0): SYNCHRONIZE CACHE(10). CDB: 35 00 00 00 00 00 00 00 
00 00
(da0:ciss0:0:0:0): CAM status: Command timeout
(da0:ciss0:0:0:0): Error 5, Retries exhausted
(da0:ciss0:0:0:0): Synchronize cache failed
[...]


More information about the freebsd-scsi mailing list