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
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
[email protected] might be all we have. Be ready.
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
