Kernel panic due atheros driver after finalsync (Was: VIA VT6103 support (VIA EPIA PD))

Jan Mikael Melen jan at
Sun Oct 9 08:27:26 PDT 2005


I have the D-Link DWL-G520 which has the atheros 5212 chip. When rebooting the 
FreeBSD 6.0-BETA5 after the final sync kernel panics. If the if_ath module has 
not been loaded in to the memory all works fine. Does anyone have any good 
idea how to get rid of this problem? Unloading the kernel module will cause 
the whole system to halt totally, the system does not respond to anything 
except power button and reset ;)

The output from vmcore:
<118>Oct  9 16:52:46 bullgw syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Waiting (max 60 seconds) for system process `syncer' to stop...
Syncing disks, vnodes remaining...8 4 4 3 2 2 0 0 0 done
All buffers synced.
Uptime: 16m6s
ukphy0: detached
miibus0: detached
kernel trap 12 with interrupts disabled

Fatal trap 12: page fault while in kernel mode
fault virtual address   = 0x24
fault code              = supervisor read, page not present
instruction pointer     = 0x20:0xc06588d0
stack pointer           = 0x28:0xd341dc6c
frame pointer           = 0x28:0xd341dc80
code segment            = base 0x0, limit 0xfffff, type 0x1b
                        = DPL 0, pres 1, def32 1, gran 1
processor eflags        = resume, IOPL = 0
current process         = 22 (irq11: vr0 ath0++)
trap number             = 12
panic: page fault
Uptime: 16m6s

Dmesg shows:
ath0: <Atheros 5212> mem 0xde000000-0xde00ffff irq 11 at device 20.0 on pci0
ath0: Ethernet address: 00:11:95:94:29:08
ath0: mac 7.9 phy 4.5 radio 5.6

ath0 at pci0:20:0: class=0x020000 card=0x3a131186 chip=0x0013168c rev=0x01 

On Tuesday 27 September 2005 11:07, Jan Mikael Melen wrote:
> Other weird thing is that I get a kernel panic after final sync when
> halting system, I've investigated that this propably doesn't have anything
> to do with the VIA EPIA motherboard and I think the problem has something
> do either with bridging or the atheros wireless driver.

More information about the freebsd-net mailing list