LOR ath

From: Volker <volker_at_vwsoft.com>
Date: Sun, 17 Oct 2004 03:52:12 +0200
Hi folks!

Yesterday I've tried to kldload the if_ath module. On the serial console
I caught the following while loading the module:

ath0: <Atheros 5212> mem 0xdffe0000-0xdffeffff irq 19 at device 11.0 on pci0
ath0: [GIANT-LOCKED]
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
ath0: Ethernet address: 00:09:5b:96:ed:90
ath0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
ath0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps
24Mbps 36M
bps 48Mbps 54Mbps
ahc0: <Adaptec aic7815 RAID memory controller> port 0xc800-0xc8ff mem
0xdf800000
-0xdfbfffff,0xdfefe000-0xdfefefff irq 18 at device 0.0 on pci2
RAID functionality unsupported
device_attach: ahc0 attach returned 6

Whenever if_ath is loaded or unloaded, the ahc0 driver enters the game.

After that (kldload), my kernel told me about a LOR:

lock order reversal
  1st 0xc1a1bc58 ath0 (network driver) _at_
/usr/src/sys/modules/ath/../../dev/ath/i
f_ath.c:893
  2nd 0xc184f620 user map (user map) _at_ /usr/src/sys/vm/vm_map.c:2997
KDB: stack backtrace:
kdb_backtrace(0,ffffffff,c0728ee8,c072a388,c06d17ec) at kdb_backtrace+0x29
witness_checkorder(c184f620,9,c06a7966,bb5) at witness_checkorder+0x540
_sx_xlock(c184f620,c06a7966,bb5) at _sx_xlock+0x50
_vm_map_lock_read(c184f5dc,c06a7966,bb5,2000000,c16f3e8c) at
_vm_map_lock_read+0
x3b
vm_map_lookup(cc7a29dc,8055000,2,cc7a29e0,cc7a29d0) at vm_map_lookup+0x26
vm_fault(c184f5dc,8055000,2,8,c15907d0) at vm_fault+0x69
trap_pfault(cc7a2aa4,0,8055000) at trap_pfault+0xf2
trap(18,10,10,8055000,c16cae00) at trap+0x351
calltrap() at calltrap+0x5
--- trap 0xc, eip = 0xc0641c70, esp = 0xcc7a2ae4, ebp = 0xcc7a2b18 ---
slow_copyout(c1a1b000,cc7a2c60,c1a1ba08,c0286938,0) at slow_copyout+0x4
ieee80211_ioctl(c1a1b000,c0286938,cc7a2c60,0,cc7a2c60) at
ieee80211_ioctl+0xbc
ath_ioctl(c1a1b000,c0286938,cc7a2c60,c051a0d4,c074dc60) at ath_ioctl+0x14d
ifhwioctl(c0286938,c1a1b000,cc7a2c60,c15907d0,c072aa68) at ifhwioctl+0x88e
ifioctl(c189b510,c0286938,cc7a2c60,c15907d0,0) at ifioctl+0xc5
soo_ioctl(c182cbb0,c0286938,cc7a2c60,c14dee00,c15907d0) at soo_ioctl+0x2b1
ioctl(c15907d0,cc7a2d14,3,2,292) at ioctl+0x3e0
syscall(2f,2f,2f,8055000,3) at syscall+0x22b
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (54, FreeBSD ELF32, ioctl), eip = 0x280d08af, esp =
0xbfbfec7c, ebp
= 0xbfbfecd8 ---

Is this LOR safe to be ignored or has it to be hacked?

This has been yesterday and I can't remember if I dramatically changed
the setup or something at the kernel configuration. Today when
kldloading if_ath, no LOR is being displayed but the ath0 interface
isn't functioning (it doesn't show the ethernet address or the 11b/11g
rates on the console).

Today, it just comes up with the following error message:
ath0: mac 5.6 phy 4.1 5ghz radio 1.7 2ghz radio 2.3
ath0: failed to allocate descriptors: 12
device_attach: ath0 attach returned 12

I've not checked the WLAN connection whether or not it has been
operational (yesterday) - I just tried to kldload and checked for the
results.

Greetings,

Volker


-- 
GPG/PGP fingerprint:
FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1
Received on Sat Oct 16 2004 - 23:53:04 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:17 UTC