[feisty] regression: rtl8180 card worked on fresh edgy install, but not on feisty or gutsy

[Cyphase]

Binary package hint: linux-source-2.6.22

My RTL8180L 802.11b WiFi card worked out-of-the-box while running Edgy, but ever since I've been using Feisty I've had to use ndiswrapper. I've also tried Gutsy and it doesn't work there either.

[Casey Greene (casey-s-greene)]

I just duplicated this with a fresh edgy install last night. I was able to connect to the wireless network. Upgrade to feisty and it can no longer connect.

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8180L 802.11b MAC (rev 20)

[Ivan Wills (ivan-wills)]

I get a similar error in Gutsy. My card Realtek Semiconductor Co., Ltd. RTL8180L 802.11b MAC (rev 20) worked in Edgy (and in Feisty when an 'A' was appended to the ESSID as per another bug). But Gutsy I get a Kernel panic.

When I use the recovery option in grub I get approximately the following:

[ 31.308000] EIP: [<f8aac4ed>] prism2_wep_encrypt +0x19d/0x250 [ieee80211_rtl] SS:ESP 0068:f7831d50
[ 31.308000] Kernel panic - not syncing: Fatal execption in interrupt

Note this only occurs when I add the 'A' to the end of my ESSID in my case this reads 'mirandaA' if I don't add the 'A' ie 'miranda' I get no kernel panic but no network.

[Ivan Wills (ivan-wills)]

I have to add a correction I get a kernel panic weather I use 'miranda' or 'mirandaA' for the ESSID. The GUI must just have been slow in trying to use the settings when I first tried with just 'miranda'.

[Mike Perry (mike.perry)]

Unfortunately I am running into the kernel panic bug after a gusty upgrade. This is unfortunate, because this is the second bug that I have ran into in Gusty during the boot process. The first was because an improper initrd, and now that I can finally mount my drives I cannot load my nic drivers (which I could in Fiesty).

Anyway, this is not the correct forum to complain. I have tried the 386 and generic kernels to no avail. Ndiswrapper is not a solution because of the upload bug in it. Not too sure what else I can do at this point aside from getting a new nic card.

[esion (esion99)]

Got something working using previous kernel (2.6.20-16-generic)

[Leann Ogasawara (leannogasawara)]

Can you please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more
information regarding the kernel team bug policy, please refer to
https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we
appreciate your help and feedback.

[Ivan Wills (ivan-wills)]

I noticed that the dmesg log has no information about the kernel panic is there some way to give you a log of the kernel panic?

[esion (esion99)]

Well I've a pcmcia rtl8180L card.

Sorry for late feedback.

---
I hope answer from mailbox works.

[esion (esion99)]

Then, the attachment

[Andres Mujica (andres.mujica)]

Hi can you check this bug # 158176 in order to determine if these two are duplicates?

also can you provide us with

modinfo rtl8180

Thanks

[Curtis White (soaro77)]

I am getting this exact same error since I upgraded to Gutsy. It was working fine in Fiesty. I was using Ndiswrapper driver in Fiesty.

When I got the kernel panic, I went to recovery mode in Gutsy in a previous kernel and removed the ndis driver. That didn't help. I still get the kernel panic. I noticed that Gutsy replaced my blacklist file which had the r808x drivers in it. I had backed my Fiesty blacklist file just to be safe. I don't know if that has anything to do with this or not. I tried adding those back to the blacklist file and it changes it but instead of the kernel panic it just freezes in the middle of the boot. I'm not sure what else to try at this point other than to reinstall Fiesty.

[Ben James (something-for-the-pain)]

I have experienced the same symptoms and raised a (duplicate) bug here:

https://bugs.launchpad.net/ubuntu/+bug/164937

I would be interested to hear when a patch/workaround is developed.

[Ben James (something-for-the-pain)]

I have experienced the same kernel panic as many others when using the rtl8180 driver and ndiswrapper on Ubuntu 7.10.

After some searching I have found a number of duplicate bugs, so I thought it wise to add a comment to each with references to the others, such that once the bug is fixed all bug reports can be updated and/or consolidated.

Here are the open bugs I could find:

#164937 - new, undecided importance, unassigned
#158176 - incomplete, undecided importance, SEAQ - Andres Mujica
#132657 - incomplete, medium importance, unassigned

[Laurent Bigonville (bigon)]

I get the same problem with a realtek RTL-8139 card, (upgrade from feisty to gutsy)

[Laurent Bigonville (bigon)]

dmsg output with the working version (2.6.20)

[Laurent Bigonville (bigon)]

also see bug #156050

[Ben James (something-for-the-pain)]

Just installed Hardy Heron (8.04, non-beta) and this issue seems to be fixed - rtl8180 with ndiswrapper now works using the graphical ndiswrapper manager. At last! :-) I can also say that hibernate and suspend don't work (for me at least) - this may or may not be related to using ndiswrapper (I'll have to investigate...).

[Sergio Zanchetta (primes2h)]

The 18 month support period for Gutsy Gibbon 7.10 has reached its end of life -
http://www.ubuntu.com/news/ubuntu-7.10-eol . As a result, we are closing the
linux-ubuntu-modules-2.6.22 task.

[Barak (barak-naveh)]

Started happening after upgrading from 9.04 to 9.10. I have an ancient Sharp AR10 running Xubuntu with Edimax Wireless LAN cardbus model EW-7108PCg.

any ideas? workarounds?

[Barak (barak-naveh)]

Btw, it happens sporadically. took me some time to realize its the wireless card. if i take the card out, the system sometimes recovers, and then i can re-plug it and use it for a few more minutes before the problems happens again.

[Barak (barak-naveh)]

Here is a bit more info, tails of /var/log/kern.log

// inserting the pcmcia card

Dec 30 02:47:09 AR10 kernel: [ 4719.940084] pcmcia_socket pcmcia_socket1: pccard: CardBus card inserted into slot 1
Dec 30 02:47:09 AR10 kernel: [ 4719.940165] pci 0000:06:00.0: reg 10 32bit mmio: [0xffff8000-0xffffffff]
Dec 30 02:47:09 AR10 kernel: [ 4719.940621] rt61pci 0000:06:00.0: enabling device (0000 -> 0002)
Dec 30 02:47:09 AR10 kernel: [ 4719.940647] rt61pci 0000:06:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11
Dec 30 02:47:09 AR10 kernel: [ 4719.940667] rt61pci 0000:06:00.0: setting latency timer to 64
Dec 30 02:47:09 AR10 kernel: [ 4719.953814] phy8: Selected rate control algorithm 'minstrel'
Dec 30 02:47:09 AR10 kernel: [ 4719.957137] Registered led device: rt61pci-phy8::radio
Dec 30 02:47:09 AR10 kernel: [ 4719.957205] Registered led device: rt61pci-phy8::assoc
Dec 30 02:47:10 AR10 kernel: [ 4720.757375] rt61pci 0000:06:00.0: firmware: requesting rt2561s.bin
Dec 30 02:47:11 AR10 kernel: [ 4721.224288] ADDRCONF(NETDEV_UP): wlan0: link is not ready
Dec 30 02:47:20 AR10 kernel: [ 4730.493617] wlan0: authenticate with AP 00:1d:0f:ed:6e:46
Dec 30 02:47:20 AR10 kernel: [ 4730.497781] wlan0: authenticated
Dec 30 02:47:20 AR10 kernel: [ 4730.497800] wlan0: associate with AP 00:1d:0f:ed:6e:46
Dec 30 02:47:20 AR10 kernel: [ 4730.506860] wlan0: RX AssocResp from 00:1d:0f:ed:6e:46 (capab=0x431 status=0 aid=7)
Dec 30 02:47:20 AR10 kernel: [ 4730.506877] wlan0: associated
Dec 30 02:47:20 AR10 kernel: [ 4730.509972] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Dec 30 02:47:30 AR10 kernel: [ 4741.052041] wlan0: no IPv6 routers present

// Card started to work for a while, I could access the wireless network.

// Then the computer suddenly froze. When i took the card out i got the following:

Dec 30 02:49:16 AR10 kernel: [ 4846.148629] pcmcia_socket pcmcia_socket1: pccard: card ejected from slot 1
Dec 30 02:49:16 AR10 kernel: [ 4846.149204] phy8 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00002100, value=0xffffffff
Dec 30 02:49:16 AR10 kernel: [ 4846.149724] phy8 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x0000308c, value=0xffffffff
Dec 30 02:49:16 AR10 kernel: [ 4846.184887] phy8 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00002100, value=0xffffffff
Dec 30 02:49:16 AR10 kernel: [ 4846.185595] phy8 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00002100, value=0xffffffff
Dec 30 02:49:16 AR10 kernel: [ 4846.186183] phy8 -> rt2x00pci_regbusy_read: Error - Indirect register access failed: offset=0x00002100, value=0xffffffff
Dec 30 02:49:16 AR10 kernel: [ 4846.186240] wlan0: deauthenticating by local choice (reason=3)
Dec 30 02:49:16 AR10 kernel: [ 4846.440652] rt61pci 0000:06:00.0: PCI INT A disabled

I guess this is not telling much :(