Sebastian Neuper [pha...@gmx.de] wrote: > Hello, > > I can't figure out what causes this panic. Second time > I see this. I think I have to replace the NIC or the disk. > Can anyone point me in the right direction? > > uvm_fault(0xd6c73184, 0xb5cbd000, 0, 3) -> e > kernel: page fault trap, code=0 > Stopped at ieee80211_newstate+0x28d: addb %cl,0xc0832434(%ecx) ... > ieee80211_newstate(f548ad30,3f8,f548ad58,d6e21e04,f548aebc) at > ieee80211_newstate+0x28d > VOP_LOOKUP(d6e21e04,f548aebc,f548aed0,d042f358,d6c73188) at VOP_LOOKUP+0x2f > vfs_lookup(f548aea8,d6c69400,400,f548aec4,d6c73188) at vfs_lookup+0x27d > namei(f548aea8,823a2001,0,2,0) at namei+0x221 > dofstatat(d6c6c2e8,ffffff9c,81c25b08,cfbf6cdc,0) at dofstatat+0x5d > sys_stat(d6c6c2e8,f548af64,f548af84,f548afa8,d6c73184) at sys_stat+0x38 > syscall() at syscall+0x227
There's no sense in this backtrace. VOP_LOOKUP calling ieee80211_newstate? You problably are suffering from a hardware failure (RAM, cache, etc).
