--uAKRQypu60I7Lcqm
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,

I went to try out hostapd, and I had this Ultra 10 lying around, so
I built 3.99.18 for it.  I used ath(4) on an Ultra 5 soon after it
was first reported working (3.99.16 or so) and didn't have problems
with it.  Now I'm getting a kernel panic during the detection of ath0.

ppb1 at pci0 dev 1 function 0: Sun Microsystems Simba PCI bridge (rev. 0x13)
pci2 at ppb1 bus 2
pci2: i/o space, memory space enabled
ath0 at pci2 dev 4 function 0
ath0: interrupting at ivec 1c
data error type 32 sfsr=441421 sfva=fffffeb7d7beffff afsr=84000000 afva=1ff00108000 tf=0x1c08560
data fault: pc=11514a4 addr=fffffeb7d7beffff sfsr=441421<ASI=44,NFO,A,SECONDCTX>
kernel trap 32: data access error
Stopped in pid 0.1 (swapper) at netbsd:ath_hal_reg_read+0x44:   srl             %
g1, 0x0, %o0
db>

A backtrace reveals:

db> bt
zz016e1251(1, 1, 2208000, 220aa84, ffffffffffffffff, 220aa84) at netbsd:zz016e12
51+0x48
zz0005b622(2208000, 9818, 2208000, 2207300, 1c08bfc, 1c08be8) at netbsd:zz0005b6
22+0x38
zz0005b6b2(2208000, 2206000, 20c1d00, 2208000, 1c08bfc, 1c08ca8) at netbsd:zz000
5b6b2+0x7e8
ath_hal_attach(13, 2206000, 20c1d00, 2207300, 1c08bfc, 1e) at netbsd:ath_hal_att
ach+0x10c
ath_attach(13, 2206000, 2206000, 1143fe0, 2206000, d) at netbsd:ath_attach+0x68
ath_pci_attach(2205000, 2206000, 1c08ea0, 2045300, 0, d) at netbsd:ath_pci_attac
h+0x130
config_attach_loc(2206000, 180b938, 1c08e90, 1c08ea0, 0, 1815000) at netbsd:conf
ig_attach_loc+0x34c
pci_probe_device(2205000, f008a79800022000, 0, 0, 0, 1) at netbsd:pci_probe_devi
ce+0x284
sparc64_pci_enumerate_bus(2205000, 149a738, 0, 21, 40, 1599400) at netbsd:sparc6
4_pci_enumerate_bus+0x318
pcirescan(2205000, 155ef10, 149a738, 2205037, 0, d) at netbsd:pcirescan+0x10
config_attach_loc(2205000, 180b938, 0, 1c09360, 2, 1815000) at netbsd:config_att
ach_loc+0x34c
ppbattach(21d1000, 20c0f80, 1c09560, 2045320, 0, d) at netbsd:ppbattach+0xec
config_attach_loc(20c0f80, 180b938, 1c09550, 1c09560, 1, 1815000) at netbsd:conf
ig_attach_loc+0x34c
pci_probe_device(21d1000, f006079c00000800, 0, 0, 0, 1) at netbsd:pci_probe_devi
ce+0x284
sparc64_pci_enumerate_bus(1, 149a738, 0, 42, 40, 1599400) at netbsd:sparc64_pci_
enumerate_bus+0x318
pcirescan(21d1000, 155ef10, 149a738, 21d1037, 0, d) at netbsd:pcirescan+0x10
config_attach_loc(21d1000, 180b938, 0, 1c09960, 0, 1815000) at netbsd:config_att
ach_loc+0x34c
mainbus_attach(0, 20c1e80, 0, 20c1ebb, 1599400, 13be800) at netbsd:mainbus_attac
h+0x330
config_attach_loc(20c1e80, 180b938, 0, 0, 0, 1815000) at netbsd:config_attach_lo
c+0x34c
cpu_configure(1591800, 14, 1595358, 0, 0, 1593f68) at netbsd:cpu_configure+0x34
configure(1, 1, 1899800, 3f, 189bc20, 40000000) at netbsd:configure+0x58
main(0, 12781e0, 189e400, 18a4800, 400000000, 1009448) at netbsd:main+0xdc
print_itlb(fffa9c10, fffa9a00, fffa9b30, f00673e8, 0, 0) at netbsd:print_itlb+0x
1bc
db>

I've tried placing the card in both slot 1 and slot 4, and get the same
error.  Could the "JSCAN RING ENDPOINT" jumpers JP1-4 affect this?
Does there appear to be something wrong with the HAL, as the backtrace
starts in unusually cryptic subroutine names?  Behold the fun of
debugging a "tainted" kernel. :P  Or, does there appear to be something
wrong with my hardware?

	Jonathan Kollasch

--uAKRQypu60I7Lcqm
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFESDvoOjx1ye3hmokRAlDfAJ43yI2nRfLPZ0nFiQ2MzxvnjH1VPgCffTXS
RT9B6tBQ18DGsSKHtUMhpQE=
=K7ud
-----END PGP SIGNATURE-----

--uAKRQypu60I7Lcqm--