From: Ivo van Doorn <ivdoorn@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: David Miller <davem@davemloft.net>,
andrea_monta@inwind.it, linux-kernel@vger.kernel.org,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
stable@kernel.org
Subject: Re: OOPS bug KERNEL LINUX- Version 2.6.26
Date: Tue, 23 Sep 2008 09:04:31 +0200 [thread overview]
Message-ID: <200809230904.31382.IvDoorn@gmail.com> (raw)
In-Reply-To: <20080922234649.GA26219@tuxdriver.com>
On Tuesday 23 September 2008, John W. Linville wrote:
> On Tue, Sep 23, 2008 at 12:32:36AM +0200, Ivo van Doorn wrote:
> > On Tuesday 23 September 2008, John W. Linville wrote:
> > > On Tue, Sep 23, 2008 at 12:25:03AM +0200, Ivo van Doorn wrote:
> > > > Hi,
> > > >
> > > > > > 1. Problem with usb-wireless-key
> > > > > > 2. I can't find my device typing ifconfig -a or iwconfig I don't find any wireless attached device. But I have my usb wireless connected. A belkin usb wireless key.Before, with the kernel 2.6.25 all worked well
> > > > > > 3. nothing
> > > > > > 4. Linux version 2.6.26 (root@clementino) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Mon Sep 22 15:57:45 CEST 2008
> > > > > > 5.
> > > >
> > > > You missed the message from rt2x00 2 lines above this trace, which undoubtly have said something like:
> > > > "Invalid RT chipset detected."
> > > > which is triggered when rt73usb is loaded for a device it does not support
> > > >
> > > > The current workaround for this issue is blacklisting rt73usb and making sure the driver
> > > > which is required for your driver is loaded instead.
> > > >
> > > > I'll look into the reason why this actually triggers a NULL pointer, since that is obviously a nasty bug.
> > >
> > > -stable needs a patch similar to the one here:
> > >
> > > http://people.redhat.com/linville/kernels/rhel5/patches/jwltest-rt2x00lib-probe-fail.patch
> >
> > Ah yes, that would be a good one.
> > I kind of assumed it was already merged, and hadn't actually verified that yet. ;)
>
> Well the code in 2.6.27 is different, this patch is no longer necessary
> (and doesn't apply).
Yeah, but it was send to stable@kernel.org as merge request for 2.6.26 stable only. :)
Ivo
prev parent reply other threads:[~2008-09-23 7:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <K7M9ZI$69A44BBF23D86D612A80B0EA98EEEE6B@libero.it>
[not found] ` <K7M9ZI$69A44BBF23D86D612A80B0EA98EEEE6B-VGgt2q2+T+FeoWH0uzbU5w@public.gmane.org>
2008-09-22 22:16 ` OOPS bug KERNEL LINUX- Version 2.6.26 David Miller
[not found] ` <20080922.151635.200306286.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-09-22 22:25 ` Ivo van Doorn
[not found] ` <200809230025.03680.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-09-22 22:27 ` John W. Linville
2008-09-22 22:32 ` Ivo van Doorn
[not found] ` <200809230032.37255.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-09-22 23:47 ` John W. Linville
2008-09-23 7:04 ` Ivo van Doorn [this message]
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=200809230904.31382.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=andrea_monta@inwind.it \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=stable@kernel.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).