From: Larry Finger <Larry.Finger@lwfinger.net>
To: Mohammed Gamal <m.gamal005@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-wireless@vger.kernel.org
Subject: Re: Fw: [Oops] b43 driver on 2.6.26
Date: Sun, 27 Jul 2008 16:32:11 -0500 [thread overview]
Message-ID: <488CE95B.2090606@lwfinger.net> (raw)
In-Reply-To: <52d4a3890807271402n792dbaces52555f545a7bfa46@mail.gmail.com>
Mohammed Gamal wrote:
> On Sun, Jul 27, 2008 at 11:58 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
>>
>> Begin forwarded message:
>>
>> Date: Wed, 23 Jul 2008 01:03:24 +0300
>> From: "Mohammed Gamal" <m.gamal005@gmail.com>
>> To: linux-net@vger.kernel.org
>> Cc: linux-kernel@vger.kernel.org
>> Subject: [Oops] b43 driver on 2.6.26
>>
>>
>> I get the following oops with b43 driver on scanning for wireless networks.
>> ----
>> [...]
>
> Ignore this, I'm no longer getting this oops on the latest git tree.
This message came from a BUG_ON statement in __netif_schedule(). A subsequent
commit changed it to a WARN_ON, and finally commit 5b3ab1d removed it completely
as the tested condition was essentially harmless.
You should be aware that wireless has not worked since commit
175f9c1bba9b825d22b142. See the thread at
http://www.ussg.iu.edu/hypermail/linux/kernel/0807.3/0936.html for details. This
problem is not yet formally entered at bugzilla as a regression.
Larry
next prev parent reply other threads:[~2008-07-27 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 20:58 Fw: [Oops] b43 driver on 2.6.26 Andrew Morton
2008-07-27 21:02 ` Mohammed Gamal
2008-07-27 21:32 ` Larry Finger [this message]
2008-07-27 21:44 ` Mohammed Gamal
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=488CE95B.2090606@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=akpm@linux-foundation.org \
--cc=linux-wireless@vger.kernel.org \
--cc=m.gamal005@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.