(re-adding linux-kernel.)
Larry Finger wrote:
> Would you please test the attached patch that should be applied to a
> vanilla 2.6.18? I'm currently running it, but only for a few minutes. It
> comes up fine and I ran it through several ifdown/ifup cycles without
> any problem.
Okay, this is far
Ray Lee wrote:
Rafael J. Wysocki wrote:
2.6.18 vanilla and 2.6.18 with your patch both lock my system hard
with bcm43xx. I've got an HP/Compaq nx6125 laptop. Symptoms are that
it will associate fine on its own and send traffic to/fro upon ifup,
but when I do an iwconfig, ifdown, ifup to change t
Rafael J. Wysocki wrote:
>> 2.6.18 vanilla and 2.6.18 with your patch both lock my system hard
>> with bcm43xx. I've got an HP/Compaq nx6125 laptop. Symptoms are that
>> it will associate fine on its own and send traffic to/fro upon ifup,
>> but when I do an iwconfig, ifdown, ifup to change the acc
On Saturday, 23 September 2006 08:03, Ray Lee wrote:
> On 9/22/06, Larry Finger <[EMAIL PROTECTED]> wrote:
> > When we found the cause of NETDEV watchdog timeouts in the wireless-2.6
> > code,
> > I knew that the 2.6.18 release code would cause a serious regression.
>
> I don't know if this is th
On 9/22/06, Larry Finger <[EMAIL PROTECTED]> wrote:
When we found the cause of NETDEV watchdog timeouts in the wireless-2.6 code,
I knew that the 2.6.18 release code would cause a serious regression.
I don't know if this is the lockup you're trying to address, but
2.6.18's bcm43xx has definitel
Erik Mouw wrote:
On Fri, Sep 22, 2006 at 08:20:08AM -0500, Larry Finger wrote:
This patch, which was originally sent to John Linville on 9/14/06,
has been taken against 2.6.18. It changes more lines
than would be absolutely necessary to affect the fix; however, it
ends up with this section looki
On Fri, Sep 22, 2006 at 08:20:08AM -0500, Larry Finger wrote:
> This patch, which was originally sent to John Linville on 9/14/06,
> has been taken against 2.6.18. It changes more lines
> than would be absolutely necessary to affect the fix; however, it
> ends up with this section looking exactly l
When we found the cause of NETDEV watchdog timeouts in the wireless-2.6 code, I knew that the 2.6.18
release code would cause a serious regression. I immediately prepared and tested a patch to fix
this; however, I was unable to get it pushed into the stable code before release of 2.6.18. The
fol
