From: "John W. Linville" <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
To: Ivo van Doorn <ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
andrea_monta-e7mAqy1nzl5eoWH0uzbU5w@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
stable-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: Re: OOPS bug KERNEL LINUX- Version 2.6.26
Date: Mon, 22 Sep 2008 18:27:16 -0400 [thread overview]
Message-ID: <20080922222716.GI3660@tuxdriver.com> (raw)
In-Reply-To: <200809230025.03680.IvDoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
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
John
--
John W. Linville Linux should be at the core
linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org of your literate lifestyle.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-09-22 22:27 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 [this message]
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
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=20080922222716.GI3660@tuxdriver.com \
--to=linville-2xusbdqka4r54taoqtywwq@public.gmane.org \
--cc=andrea_monta-e7mAqy1nzl5eoWH0uzbU5w@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=ivdoorn-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=stable-DgEjT+Ai2ygdnm+yROfE0A@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).