ath_hal problems on sparc64
Sascha Luck
sascha at eirconnect.net
Fri Mar 17 00:48:59 UTC 2006
[moved to -current as this panic happens on:
FreeBSD 7.0-CURRENT #0: Tue Feb 14 17:16:58 GMT 2006
root at cheetah.c4inet.net:/usr/obj/usr/src/sys/CHEETAH-DEBUG-ATH
On Thursday 16 March 2006 22:32, Sam Leffler wrote:
> There's something bogus in the hal.o; I will need to figure out what
> happened and respin it. It's not going to happen immediately; sorry.
and here is the kdb trace:
db> trace
Tracing pid 0 tid 0 td 0xc03f7518
panic() at panic+0xf0
trap() at trap+0x414
-- data access exception sfar=0x32000000010 sfsr=0x41029 %o7=0xc02ef5cc
--
ath_hal_reg_read() at ath_hal_reg_read+0x10
zz016e1251() at zz016e1251+0x38
zz0005b6b2() at zz0005b6b2+0x34
ath_hal_attach() at ath_hal_attach+0x10c
ath_attach() at ath_attach+0xc8
ath_pci_attach() at ath_pci_attach+0x274
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
bus_generic_attach() at bus_generic_attach+0x10
ofw_pcibus_attach() at ofw_pcibus_attach+0x1a0
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
bus_generic_attach() at bus_generic_attach+0x10
apb_attach() at apb_attach+0x174
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
bus_generic_attach() at bus_generic_attach+0x10
ofw_pcibus_attach() at ofw_pcibus_attach+0x1a0
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
bus_generic_attach() at bus_generic_attach+0x10
psycho_attach() at psycho_attach+0xa6c
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
bus_generic_attach() at bus_generic_attach+0x10
nexus_attach() at nexus_attach+0x23c
device_attach() at device_attach+0x60
device_probe_and_attach() at device_probe_and_attach+0x118
root_bus_configure() at root_bus_configure+0x18
configure() at configure+0x4
mi_startup() at mi_startup+0x12c
btext() at btext+0x34
Hope this helps with finding what's wrong. If you need any more info,
let me know, I can reliably reproduce the panic.
> Sam
cheers,
s.
More information about the freebsd-current
mailing list