From: Larry Finger <Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
To: Michael Buesch <mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Cc: netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Johannes Berg <johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org>,
bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org
Subject: Re: [PATCH] bcm43xx-d80211: Init, shutdown and restart fixes
Date: Tue, 15 Aug 2006 10:40:12 -0500 [thread overview]
Message-ID: <44E1EADC.4030503@lwfinger.net> (raw)
In-Reply-To: <200608151730.26255.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
Michael Buesch wrote:
> On Tuesday 15 August 2006 17:23, Larry Finger wrote:
>> Michael,
>>
>> Michael Buesch wrote:
>>> Hi John,
>>>
>>> Please apply this to wireless-dev.
>>>
>>> --
>>>
>>> This fixes various bugs in the init and shutdown code
>>> that would lead to lockups and crashes.
>>> This is best reproducable by receiving a timeout from
>>> the netdev watchdog.
>> Is a similar bug likely to be the cause of the netdev watchdog timeouts in
>> bcm43xx-softmac? If so, will there be a patch for wireless-2.6?
>
> I don't know why the _timeouts_ itself happen, but maybe the
> lockup and crash bugs are in bcm43xx-softmac, too.
> I think it should be actually trivial to port this to bcm43xx-softmac.
> Care to do this, Larry?
I'll take a stab at it.
Larry
next prev parent reply other threads:[~2006-08-15 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-14 19:32 [PATCH] bcm43xx-d80211: Init, shutdown and restart fixes Michael Buesch
2006-08-15 15:23 ` Larry Finger
[not found] ` <44E1E6E6.9000804-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2006-08-15 15:30 ` Michael Buesch
[not found] ` <200608151730.26255.mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org>
2006-08-15 15:40 ` Larry Finger [this message]
2006-08-15 15:44 ` John W. Linville
2006-08-15 21:00 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44E1EADC.4030503@lwfinger.net \
--to=larry.finger-tq5ms3gmjblk1umjsbkqmq@public.gmane.org \
--cc=bcm43xx-dev-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
--cc=johannes-cdvu00un1VgdHxzADdlk8Q@public.gmane.org \
--cc=mb-fseUSCV1ubazQB+pC5nmwQ@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).