Date: Sun, 13 Jul 2014 15:37:13 +0100 (BST) From: Anton Shterenlikht <mexas@bris.ac.uk> To: freebsd-sparc64@freebsd.org Subject: isp driver causes panic in 10-stable Message-ID: <201407131437.s6DEbDuP005266@mech-cluster241.men.bris.ac.uk>
next in thread | raw e-mail | index | archive | help
isp0: <Qlogic ISP 2422 PCI FC-AL Adapter> port 0x300-0x3ff mem 0x100000-0x100fff at device 3.0 on pci1 I used this card for years on ia64, from 8-current to 11-current. Now that ia64 is not supported, I wanted to move it into sparc64 10-stable box (SunBlade 1500 silver workstation). The card is recognised, see above, but shortly after I get this panic (single user mode): isp0: <Qlogic ISP 2422 PCI FC-AL Adapter> port 0x300-0x3ff mem 0x100000-0x100fff at device 3.0 on pci1 nexus0: <i2c> mem 0x4000fc64000-0x4000fc6400f type i2c (no driver attached) nexus0: <syscons> type unknown (no driver attached) rtc0: <Real-Time Clock> at port 0x70-0x71 on isa0 uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 44 on isa0 uart0: console (9600,n,8,1) uart1: <16550 or compatible> at port 0x2e8-0x2ef irq 44 on isa0 WITNESS: unable to allocate a new witness object Timecounter "tick" frequency 1503000000 Hz quality 1000 Timecounter "stick" frequency 12000000 Hz quality 1000 Event timer "tick" frequency 1503000000 Hz quality 1000 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 panic: trap: memory address not aligned (kernel) KDB: stack backtrace: vpanic() at vpanic+0xfc panic() at panic+0x20 trap() at trap+0x5cc -- memory address not aligned sfar=0x1001ee021 sfsr=0x40029 %o7=0xc0137bac -- userland() at isp_get_ridacq+0x118 user trace: trap %o7=0xc0137bac pc 0xc0137cb8, sp 0xd766e851 done KDB: enter: panic [ thread pid 12 tid 100031 ] Stopped at kdb_enter+0x80: ta %xcc, 1 db> Is this a known problem? with bt I get an endless stream of: KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc -- kernel stack fault %o7=0xc00c60b0 -- db_read_bytes() at db_read_bytes+0x44 KDB: reentering KDB: stack backtrace: kdb_reenter() at kdb_reenter+0x5c trap() at trap+0x2fc that never finishes. Please advise Thanks Anton
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201407131437.s6DEbDuP005266>