From: "John W. Linville" <linville@tuxdriver.com>
To: Juho-Mikko Pellinen <juho-mikko.pellinen@iki.fi>
Cc: linux-wireless@vger.kernel.org, Daniel Drake <dsd@gentoo.org>,
Ulrich Kunitz <kune@deine-taler.de>
Subject: Re: Kernel Oops with 3.5-rc4 and zd1211rw (regression)
Date: Tue, 26 Jun 2012 15:05:07 -0400 [thread overview]
Message-ID: <20120626190506.GC32503@tuxdriver.com> (raw)
In-Reply-To: <4FE9FC2C.6040205@iki.fi>
On Tue, Jun 26, 2012 at 09:15:08PM +0300, Juho-Mikko Pellinen wrote:
> Hi!
>
> I just got this kernel oops the first time I compiled and booted 3.5-rc4
> . Oops message: http://i.imgur.com/oyIhy.jpg
> 3.4.x-series work just fine.
>
> The Oops happens when I log in to gdm. At that time Network Manager is
> already up and connected to network because I can ssh to the computer.
> Naturally after the crash wlan goes down and the computer is unreachable.
>
> The zd1211rw is an usb network card. I have also wlan card with the chip
> 'rtl8192ce' installed, but not activated because I'm experiencing
> problems with it.
>
> Attached are lspci, lsusb and dmesg from kernel 3.4.3.
> I will investigate later on the possibility of setting up netconsole and
> logging dmesg just before the crash.
>
> -Juho-Mikko Pellinen
I noticed that you are using CONFIG_CFG80211_INTERNAL_REGDB, but you
have an empty db.txt file. Please turn-off that option and install
a proper CRDA setup. Alternatively, at least give it an up-to-date
db.txt file to use for regulatory rules.
You are getting a lot of CR_REG1 timeouts from your zd1211rw device.
Are you certain that the device is still functioning properly?
The zd1211rw driver isn't exactly changing rapidly. I do see that
commit e1f12eb6ba6f1e74007eb01ed26fad7c5239d62b touches it. You might
try reverting that one? And, of course, you could try to do a git
bisect between 3.4 and 3.5-rc4 -- as a Gentoo user, I'm sure you are
up to the task! :-)
Does any of that move the ball for us?
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2012-06-26 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-26 18:15 Kernel Oops with 3.5-rc4 and zd1211rw (regression) Juho-Mikko Pellinen
2012-06-26 19:05 ` John W. Linville [this message]
2012-06-26 20:34 ` 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=20120626190506.GC32503@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dsd@gentoo.org \
--cc=juho-mikko.pellinen@iki.fi \
--cc=kune@deine-taler.de \
--cc=linux-wireless@vger.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 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.