ath bridge panic

Sam Leffler sam at errno.com
Tue Aug 30 18:19:43 GMT 2005


Vitaly wrote:
> Vitaly ÐÉÛÅÔ:
> 
>> problem on FreeBSD 6.0-BETA1
>> ath0 is  bridge with fxp0
>> panic occured when i connect wireless client to my hostap, client -  
>> FujitsuSiemens PocketLOOX720 with internal 11b adapter
>>
>> when his connecting i get next messages
>>
>>> couldn't m_pullup
>>> couldn't m_pullup
>>> couldn't m_pullup
>>
>>
>>
>> and first ping kill my system
>> what i need to get more information about this?
>>
>>> Fatal trap 12: page fault while in kernel mode
>>> fault virtual address   = 0x10
>>> fault code              = supervisor read, page not present
>>> instruction pointer     = 0x20:0xc06bef70
>>> stack pointer           = 0x28:0xd274c85c
>>> frame pointer           = 0x28:0x0
>>> code segment            = base 0x0, limit 0xfffff, type 0x1b
>>>                         = DPL 0, pres 1, def32 1, gran 1
>>> processor eflags        = interrupt enabled, resume, IOPL = 0
>>> current process         = 27 (swi1: net)
>>> trap number             = 12
>>> panic: page fault
>>> Uptime: 4m41s
>>> Dumping 191 MB (2 chunks)
>>>   chunk 0: 1MB (159 pages) ... ok
>>>   chunk 1: 191MB (48893 pages) 176 160 144 128 112 96 80 64 48 32 16 
>>> ... ok
>>
>>
>>
>>
>>
>>> net.link.ether.bridge.enable: 0 -> 1
>>> net.link.ether.bfridge.config: xp0: promiscuous mode enabled
>>> ath0: promiscuous mode enabled
>>> fxp0: link state changed to UP
>>>  -> fxp0:2,ath0:2
>>> fxp1: link state changed to UP
>>> fxp0: 
>>> flags=18943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST,POLLING> 
>>> mtu 1500
>>>         options=48<VLAN_MTU,POLLING>
>>>         inet 192.168.7.1 netmask 0xffffff00 broadcast 192.168.7.255
>>>         ether 00:04:ac:d7:bd:24
>>>         media: Ethernet autoselect (100baseTX <full-duplex>)
>>>         status: active
>>> ath0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 
>>> 1500
>>>         ether 00:0f:3d:a9:4e:20
>>>         media: IEEE 802.11 Wireless Ethernet autoselect mode 11g 
>>> <hostap>
>>>         status: associated
>>>         ssid D2HOME channel 6 bssid 00:0f:3d:a9:4e:20
>>>         authmode OPEN privacy ON deftxkey 1
>>>         wepkey 1:104-bit
>>>         txpowmax 39 rtsthreshold 2346 protmode CTS dtimperiod 1 
>>> bintval 100
>>
>>
>>
> Problem still exists, what I must do?

Still exists with what version of the system?  If you haven't tried 
BETA3 then do that first.

To get something like this fixed you need to provide the steps needed to 
reproduce the problem.

	Sam


More information about the freebsd-current mailing list