date:20131011

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

2013-10-11 Thread Peter Ankerstål


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 
0xf, 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 mailto:pe...@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 mailto:adr...@freebsd.org>> wrote:

 > Hi,
 >
 > Is there a backtrace for this? Iv'e not seen this before.
 >
 >
 > -adrian





___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2013-10-11 Thread Adrian Chadd

what's wlan0 setup as?



-a


On 11 October 2013 00:28, Peter Ankerstål  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 0xf,
> 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 > > 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 > > wrote:
>>
>>  > Hi,
>>  >
>>  > Is there a backtrace for this? Iv'e not seen this before.
>>  >
>>  >
>>  > -adrian
>>
>>
>>
>>
>
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: igb driver does not support altq

2013-10-11 Thread Karim Fodil-Lemelin


On 10/10/2013 5:56 AM, h bagade wrote:

Hi all,

I have problem with running altq on igb cards. When trying to run altq on
these cards, it outputs an error, driver does not support altq.

I have FreeBSD 8.3-stable and tried to fix the problem, after searching in
forums, by applying changes made to igb driver through following links:

http://svnweb.freebsd.org/base?view=revision&revision=248906
http://svnweb.freebsd.org/base?view=revision&revision=249339
http://lists.freebsd.org/pipermail/svn-src-stable/2013-July/019491.html

But it doesn't help and I still have problem with running altq on igb!

Does anybody know from which revision the problem is solved?
Any hints would be of great help.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Hi,

Those modifications require that you define IGB_LEGACY_TX in the driver 
code to get ALTQ running on igb.


Regards,

Karim.
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

2013-10-11 Thread Peter Ankerstål


Its a hostap. (What im trying to do is to set up a legacy 2.4GHz network on the 
other interface)

> On 11 okt 2013, at 17:20, Adrian Chadd  wrote:
> 
> what's wlan0 setup as?
> 
> 
> 
> -a
> 
> 
>> On 11 October 2013 00:28, Peter Ankerstål  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 0xf, 
>> 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 >> > 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 >> > wrote:
>>> 
>>>  > Hi,
>>>  >
>>>  > Is there a backtrace for this? Iv'e not seen this before.
>>>  >
>>>  >
>>>  > -adrian
> 
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: Intel 82580 lagg(4) problem

2013-10-11 Thread mybsd

Set net.link.lagg.0.use_flowid=0 not solve the problem.

My system is freebsd 8.4, use the e1000 driver from freebsd 8.3 solves this 
problem . 
Should confirm that the problem is driver

I have already submitted the BUG.
http://www.freebsd.org/cgi/query-pr.cgi?pr=182917

___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: igb driver does not support altq

2013-10-11 Thread h bagade

On Fri, Oct 11, 2013 at 6:53 PM, Karim Fodil-Lemelin <
fodillemlinka...@gmail.com> wrote:

> On 10/10/2013 5:56 AM, h bagade wrote:
>
>> Hi all,
>>
>> I have problem with running altq on igb cards. When trying to run altq on
>> these cards, it outputs an error, driver does not support altq.
>>
>> I have FreeBSD 8.3-stable and tried to fix the problem, after searching in
>> forums, by applying changes made to igb driver through following links:
>>
>> http://svnweb.freebsd.org/**base?view=revision&revision=**248906
>> http://svnweb.freebsd.org/**base?view=revision&revision=**249339
>> http://lists.freebsd.org/**pipermail/svn-src-stable/2013-**
>> July/019491.html
>>
>> But it doesn't help and I still have problem with running altq on igb!
>>
>> Does anybody know from which revision the problem is solved?
>> Any hints would be of great help.
>> __**_
>> freebsd-net@freebsd.org mailing list
>> http://lists.freebsd.org/**mailman/listinfo/freebsd-net
>> To unsubscribe, send any mail to 
>> "freebsd-net-unsubscribe@**freebsd.org
>> "
>>
> Hi,
>
> Those modifications require that you define IGB_LEGACY_TX in the driver
> code to get ALTQ running on igb.
>
> Regards,
>
> Karim.
>

I did so but It was not successful! I may missed something but I don't know
what it may be!
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

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

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

Re: igb driver does not support altq

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

Re: Intel 82580 lagg(4) problem

Re: igb driver does not support altq

6 matches

Site Navigation

Mail list logo

Footer information