Re: kern/128917: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic
Synopsis: [wpi] [panic] if_wpi and wpa+tkip causing kernel panic State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Wed Dec 22 08:42:16 UTC 2010 State-Changed-Why: Is that still an issue on a recent release? Responsible-Changed-From-To: freebsd-net->bschmidt Responsible-Changed-By: bschmidt Responsible-Changed-When: Wed Dec 22 08:42:16 UTC 2010 Responsible-Changed-Why: over to me http://www.freebsd.org/cgi/query-pr.cgi?pr=128917 ___ 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/133613: [wpi] [panic] kernel panic in wpi(4)
Synopsis: [wpi] [panic] kernel panic in wpi(4) State-Changed-From-To: open->closed State-Changed-By: bschmidt State-Changed-When: Wed Dec 22 08:43:48 UTC 2010 State-Changed-Why: After talking to cpercia who no longer has access to the AP and this PR being a duplicate of kern/128917, close it. Responsible-Changed-From-To: freebsd-net->bschmidt Responsible-Changed-By: bschmidt Responsible-Changed-When: Wed Dec 22 08:43:48 UTC 2010 Responsible-Changed-Why: over to me http://www.freebsd.org/cgi/query-pr.cgi?pr=133613 ___ 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/144987: [wpi] [panic] injecting packets with wlaninject using Intel 3945ABG wireless card gives kernel panic
The following reply was made to PR kern/144987; it has been noted by GNATS. From: Bernhard Schmidt To: bug-follo...@freebsd.org, gabrielquad...@hotmail.com Cc: Julian Elischer Subject: Re: kern/144987: [wpi] [panic] injecting packets with wlaninject using Intel 3945ABG wireless card gives kernel panic Date: Wed, 22 Dec 2010 09:58:34 +0100 On Monday 20 December 2010 15:10:02 Bernhard Schmidt wrote: > Hi, > > The issue here is that you've tried to use wlaninject with a VAP in sta > mode. As soon as wlaninject tries to set up the interface, net80211 will > start to do a scan which means constant channel switches until it finds > something to associate. wlaninject itself is not aware of that and happily > injects frames no matter what the current channel state is, as the above > trace shows, you hit a point where no channel is set between 2 scan > interations. > > wlaninject is supposed to be used with VAPs in ahdemo mode and wpi(4) does > not support that mode. Therefore I tend to close this PR. Looking closer I might have been a bit wrong. There are several issue here.. One being that ni_chan is used in the TX path which should and can actually be replaced by ic_curchan. This will fix the panic reported above, though, this does no longer obscure other issues. For examples, we are allowed to pass in frames of arbitrary length, extremely short frames will be discarded early due to an overflow checking the length (the message to long error). But, if the length is just long enough to reach the driver it might still be shorter then the header for a 802.11 frame. This will result in another panic() in m_copydata() as we try to copy over the header to firmware.. I'll try to find a useful solution for that. -- Bernhard ___ 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: misc/153308: em interface use 100% cpu
The following reply was made to PR kern/153308; it has been noted by GNATS. From: Gleb Smirnoff To: Yusuf Ozbilgin Cc: freebsd-gnats-sub...@freebsd.org Subject: Re: misc/153308: em interface use 100% cpu Date: Wed, 22 Dec 2010 17:31:12 +0300 On Mon, Dec 20, 2010 at 02:25:29PM +, Yusuf Ozbilgin wrote: Y> >Synopsis: em interface use 100% cpu ... Y> e...@pci0:1:0:0: class=0x02 card=0x8086 chip=0x10d38086 rev=0x00 hdr=0x00 Y> vendor = 'Intel Corporation' Y> class = network Y> subclass = ethernet Y> cap 01[c8] = powerspec 2 supports D0 D3 current D0 Y> cap 05[d0] = MSI supports 1 message, 64 bit enabled with 1 message Y> cap 10[e0] = PCI-Express 1 endpoint max data 128(256) link x1(x1) Y> cap 11[a0] = MSI-X supports 5 messages in map 0x1c Y> Y> top Y> Y> PID USERNAMETHR PRI NICE SIZERES STATE C TIME WCPU COMMAND Y> 1592 root 1 1120 3348K 1316K RUN 0 0:38 85.09% natd Y> 1899 postfix 1 40 24600K 21336K kqread 0 0:06 0.00% qmgr Y> 1762 root 1 440 39132K 36772K select 0 0:03 0.00% perl This doesn't seem related to em(4). Do you mind if I change synopsis of PR to "natd consumes 100% CPU"? Have you tried same setup on 8-STABLE? -- Totus tuus, Glebius. ___ 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: lagg/lacp poor traffic distribution
On 21.12.2010 21:57, Fabien Thomas wrote: >> irq262: igb0:que 0 157354922 7927 >> irq263: igb0:que 1577369 29 >> irq264: igb0:que 2280207 14 >> irq265: igb0:que 3241826 12 >> irq266: igb0:link 2 0 >> irq267: igb1:que 0 164620363 8293 >> irq268: igb1:que 1238678 12 >> irq269: igb1:que 2248478 12 >> irq270: igb1:que 3762453 38 >> irq271: igb1:link 3 0 >> cpu2: timer 39576052 1993 >> cpu3: timer 39576095 1993 >> cpu1: timer 39575913 1993 >> Total 989503327 49849 >> >> It seems I have four queues per igb card but only one of them works? > > Yes. > > Jack will certainly confirm but it seems that RSS hash does not seems to take > vlan in account and default to queue0 ? I've just read "Microsoft Receive-Side Scaling" documentation, http://download.microsoft.com/download/5/d/6/5d6eaf2b-7ddf-476b-93dc-7cf0072878e6/ndis_rss.doc RSS defines that hash function may take IP and optionally port numbers only, not vlan tags. In case of PPPoE-only traffic this card's ability to classify traffic voids. Then, unpatched lagg fails to share load over outgoing interface ports. It seems, we really need sysctl disabling lagg's use of flows, don't we? Eugene Grosbein ___ 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/143874: [wpi] Wireless 3945ABG error. wpi0 could not allocate memory resource
On Mon, 20 Dec 2010 12:53:30 +0100 Bernhard Schmidt wrote: > On Monday 20 December 2010 12:06:24 Patrick Ale wrote: > > Hi, > > > > Not sure if this is useful information for you but here goes: > > I have exactly the same problem on my Acer Aspire laptop with the > > same network card but then under Solaris 10 and Opensolaris, both > > 64 bit. > > > > The only way for me to get rid of this error and get the card > > working is to reduce my memory from 4GB to <= 3GB. > > I got told it has to do with the PCI to PCI-X bridge masquarading > > some memory addresses.. > > > > I am not a kernel/driver/code guru but I thought one of you might > > get some pointers out of this.. > > There have been a few changes to PCI bridge code lately which might > well fix that issue. If anyone could give a recent stable/8 or > 8.2-BETA a shot, I'd really appreciate that. > > > On Sun, Dec 19, 2010 at 6:10 PM, Oliver Ebert > > > wrote: > > > The following reply was made to PR kern/143874; it has been noted > > > by GNATS. > > > > > > From: Oliver Ebert > > > To: Bernhard Schmidt > > > Cc: bug-follo...@freebsd.org > > > Subject: Re: kern/143874: [wpi] Wireless 3945ABG error. wpi0 > > > could not allocate memory resource > > > Date: Sun, 19 Dec 2010 10:39:47 -0600 > > > > > > On Sun, 19 Dec 2010 11:49:27 +0100 > > > Bernhard Schmidt wrote: > > > > > > > On Sunday 12 September 2010 05:30:10 oliver.sola...@gmail.com > > > > wrote: > > > > > I have the same issue with a Toshiba Satellite P105: > > > > > > > > > > Sep 11 21:46:13 kernel: wpi0: > > > > 3945ABG> irq 17 at device 0.0 on pci3 > > > > > Sep 11 21:46:13 kernel: wpi0: Driver Revision 20071127 > > > > > Sep 11 21:46:13 kernel: wpi0: 0x1000 bytes of rid 0x10 res > > > > > 3 failed (0, 0xf fff). > > > > > Sep 11 21:46:13 kernel: wpi0: could not allocate memory > > > > > resource Sep 11 21:46:13 kernel: device_attach: wpi0 attach > > > > > returned 6 > > > > > > > > > > Please let me know if I can help out to track this issue > > > > > down. > > > > > > > > Is this still an issue on a recent stable/8 or 8.2-BETA1? > > > > > > > 8.2-PRERELEASE > > > With 8.1 it is but I didn't had a chance to check with 8.2 beta. > I just upgraded to 8.2-PRERELEASE and it seems that the issue is still persistent: Now wlan0 device shows up. The device is available when booting with ACPI disabled. ___ 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"
