Re: isp driver causes panic in 10-stable

John Baldwin <[email protected]>
Newsgroups gmane.os.freebsd.devel.sparc
Message-ID <[email protected]>
On Sunday, July 13, 2014 10:37:13 am Anton Shterenlikht wrote:
> 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

Can you run gdb against the kernel.debug file from this kernel and do
'l *isp_get_ridacq+0x118'?

-- 
John Baldwin
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.