Re: kern/138739: [wpi] wpi(4) does not work very well under 8.0-BETA4

2010-12-27 Thread bschmidt
Synopsis: [wpi] wpi(4) does not work very well under 8.0-BETA4 State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Mon Dec 27 10:22:42 UTC 2010 State-Changed-Why: Can you retry with a recent 8.2-RC1, stable/8 or head? I expect recent changes might solved this. R

Re: kern/140564: [wpi] Problem with Intel(R) PRO/Wireless 3945ABG

2010-12-27 Thread bschmidt
Synopsis: [wpi] Problem with Intel(R) PRO/Wireless 3945ABG State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Mon Dec 27 10:25:14 UTC 2010 State-Changed-Why: Can you retry with a recent 8.2-RC1, stable/8 or head? I think that some recent changes might have fixed

Re: kern/145777: [wpi] Intel 3945ABG driver breaks the connection after about 10 minutes of inactivity

2010-12-27 Thread bschmidt
Synopsis: [wpi] Intel 3945ABG driver breaks the connection after about 10 minutes of inactivity State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Mon Dec 27 10:27:29 UTC 2010 State-Changed-Why: What is the state of the PR, does that still happen? Also with a re

Re: kern/147862: [wpi] Possible bug in the wpi driver. Network Manager sporadically drops wifi signal

2010-12-27 Thread bschmidt
Synopsis: [wpi] Possible bug in the wpi driver. Network Manager sporadically drops wifi signal State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Mon Dec 27 10:30:09 UTC 2010 State-Changed-Why: Does that still happen with a recent 8.2-RC1, stable/8 or head setu

Current problem reports assigned to freebsd-net@FreeBSD.org

2010-12-27 Thread FreeBSD bugmaster
Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker

Re: kern/153255: 8.2-PRERELEASE repeatable kernel panic under heavy network load

2010-12-27 Thread Eugene Grosbein
The following reply was made to PR kern/153255; it has been noted by GNATS. From: Eugene Grosbein To: bug-follo...@freebsd.org Cc: Subject: Re: kern/153255: 8.2-PRERELEASE repeatable kernel panic under heavy network load Date: Mon, 27 Dec 2010 17:18:13 +0600 Hi! I've rebuilt kernel of one

Re: bin/152716: hostapd(8) fails to authenticate after 2010-11-03 update

2010-12-27 Thread bschmidt
Synopsis: hostapd(8) fails to authenticate after 2010-11-03 update State-Changed-From-To: open->feedback State-Changed-By: bschmidt State-Changed-When: Mon Dec 27 11:23:36 UTC 2010 State-Changed-Why: feedback has been requested Responsible-Changed-From-To: freebsd-net->bschmidt Responsible-Chan

Re: kern/140564: [wpi] Problem with Intel(R) PRO/Wireless 3945ABG

2010-12-27 Thread Leonardo Santagostini
I have not anymore this computer to test it. By the way, someone at the list has this hardware to try. Thanks in advance Leonardo Santagostini 2010/12/27 > Synopsis: [wpi] Problem with Intel(R) PRO/Wireless 3945ABG > > State-Changed-From-To: open->feedback > State-Changed-By: bschmidt > State

CFT/CFR, possible fix for ifconfig scan hang

2010-12-27 Thread Bernhard Schmidt
Hi, I recently received some complains about the infamous 'ifconfig scan hang' issue again. Finally looking into that I noticed a bunch of inconsistences, the most obvious one is that ifconfig(8) is talking about doing a background scan by default, which is simply not true according to the impl

Re: CFT/CFR, possible fix for ifconfig scan hang

2010-12-27 Thread Brandon Gooch
On Mon, Dec 27, 2010 at 1:24 PM, Bernhard Schmidt wrote: > Hi, > > I recently received some complains about the infamous 'ifconfig scan hang' > issue again. Finally looking into that I noticed a bunch of inconsistences, > the most obvious one is that ifconfig(8) is talking about doing a background

Re: CFT/CFR, possible fix for ifconfig scan hang

2010-12-27 Thread Attilio Rao
2010/12/27 Bernhard Schmidt : > Hi, > > I recently received some complains about the infamous 'ifconfig scan hang' > issue again. Finally looking into that I noticed a bunch of inconsistences, > the most obvious one is that ifconfig(8) is talking about doing a background > scan by default, which is