From: Larry Finger <Larry.Finger@lwfinger.net>
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:34:33 -0500 [thread overview]
Message-ID: <4FEA1CD9.4090307@lwfinger.net> (raw)
In-Reply-To: <4FE9FC2C.6040205@iki.fi>
On 06/26/2012 01:15 PM, 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.
This crash may be more general that the zd1211rw. I am also getting kernel
panics in __netif_schedule with b43legacy for kernels 3.4.0 and 3.5-rc3 from
wireless-testing. On this box, an RTL8187B works fine.
As reported here, the connection is OK until a heavy load is started. In my
case, it was a package update command for my openSUSE distro.
Is there a possibility that this is still related to the single output queue
problem, or does the zd1211rw have multiple queues?
Larry
prev parent reply other threads:[~2012-06-26 20:34 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
2012-06-26 20:34 ` Larry Finger [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=4FEA1CD9.4090307@lwfinger.net \
--to=larry.finger@lwfinger.net \
--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.