kern/182665: [wlan] Kernel panic when creating second wlandev.

[Adrian Chadd]

what's wlan0 setup as?



-a


On 11 October 2013 00:28, Peter Ankerstål <peter at pean.org> wrote:

> Hi!
>
> Here is a new crash.
>
> I have wlan0 set up with ath0 as wlandev and then when I run:
>
> # ifconfig wlan1 create wlanmode hostap wlandev ath1
>
>
> the machine crashes with this message:
>
> Oct 11 09:25:00 gw syslogd: kernel boot file is /boot/kernel/kernel
> Oct 11 09:25:00 gw kernel:
> Oct 11 09:25:00 gw kernel:
> Oct 11 09:25:00 gw kernel: Fatal trap 12: page fault while in kernel mode
> Oct 11 09:25:00 gw kernel: cpuid = 1; apic id = 01
> Oct 11 09:25:00 gw kernel: fault virtual address        = 0x0
> Oct 11 09:25:00 gw kernel: fault code           = supervisor read, page
> not present
> Oct 11 09:25:00 gw kernel: instruction pointer  = 0x20:0xc0800600
> Oct 11 09:25:00 gw kernel: stack pointer                = 0x28:0xe8d879e0
> Oct 11 09:25:00 gw kernel: frame pointer                = 0x28:0xe8d879e8
> Oct 11 09:25:00 gw kernel: wlan1: Ethernet address: b0:48:7a:d5:fe:a2
> Oct 11 09:25:00 gw kernel: code segment         = base 0x0, limit 0xfffff,
> type 0x1b
> Oct 11 09:25:00 gw kernel: = DPL 0, pres 1, def32 1, gran 1
> Oct 11 09:25:00 gw kernel: processor eflags     = interrupt enabled,
> resume, IOPL = 0
> Oct 11 09:25:00 gw kernel: current process              = 2968 (bsnmpd)
> Oct 11 09:25:00 gw kernel: trap number          = 12
> Oct 11 09:25:00 gw kernel: panic: page fault
> Oct 11 09:25:00 gw kernel: cpuid = 1
> Oct 11 09:25:00 gw kernel: KDB: stack backtrace:
> Oct 11 09:25:00 gw kernel: #0 0xc078bfc2 at kdb_backtrace+0x52
> Oct 11 09:25:00 gw kernel: #1 0xc07567f1 at panic+0x121
> Oct 11 09:25:00 gw kernel: #2 0xc0a4ffb9 at trap_fatal+0x339
> Oct 11 09:25:00 gw kernel: #3 0xc0a5024a at trap_pfault+0x27a
> Oct 11 09:25:00 gw kernel: #4 0xc0a4fa46 at trap+0x5a6
> Oct 11 09:25:00 gw kernel: #5 0xc0a3a20c at calltrap+0x6
> Oct 11 09:25:00 gw kernel: #6 0xc083f635 at ieee80211_ioctl_getstainfo+**
> 0x55
> Oct 11 09:25:00 gw kernel: #7 0xc083b244 at ieee80211_ioctl_get80211+0x434
> Oct 11 09:25:00 gw kernel: #8 0xc08650b8 at in_control+0x228
> Oct 11 09:25:00 gw kernel: #9 0xc080df53 at ifioctl+0x1943
> Oct 11 09:25:00 gw kernel: #10 0xc07a7d5c at soo_ioctl+0x30c
> Oct 11 09:25:00 gw kernel: #11 0xc07a0b4b at kern_ioctl+0x19b
> Oct 11 09:25:00 gw kernel: #12 0xc07a0969 at sys_ioctl+0xe9
> Oct 11 09:25:00 gw kernel: #13 0xc0a50823 at syscall+0x363
> Oct 11 09:25:00 gw kernel: #14 0xc0a3a271 at Xint0x80_syscall+0x21
>
>
>
> On 10/11/2013 12:31 AM, Adrian Chadd wrote:
>
>> what's the backtrace from the kernel crash?
>>
>> That's a bit odd.. :-)
>>
>>
>>
>> -adiran
>>
>>
>>
>> On 10 October 2013 11:38, Peter Ankerstål <peter at pean.org
>> <mailto:peter at pean.org>> wrote:
>>
>>     Sorry, had to rebuild kernel with debug symbols.
>>
>>     Heres the output:
>>
>>     (kgdb) list *0xc0800110
>>     0xc0800110 is in jenkins_hash32
>>     (/usr/src/sys/libkern/jenkins_**hash.c:177).
>>     172       switch(length)                     /* all the case
>>     statements fall through */
>>     173       {
>>     174       case 3 : c+=k[2];
>>     175       case 2 : b+=k[1];
>>     176       case 1 : a+=k[0];
>>     177         final(a,b,c);
>>     178       case 0:     /* case 0: nothing left to add */
>>     179         break;
>>     180       }
>>     181       /*----------------------------**--------------------------
>>     report the result */
>>
>>
>>     On Oct 9, 2013, at 11:18 PM, Adrian Chadd <adrian at freebsd.org
>>     <mailto:adrian at freebsd.org>> wrote:
>>
>>      > Hi,
>>      >
>>      > Is there a backtrace for this? Iv'e not seen this before.
>>      >
>>      >
>>      > -adrian
>>
>>
>>
>>
>