RT61 driver hangs net, if interface accessed while down

Bug #48087 reported by Peter Parkkali
20
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Binary package hint: linux-source-2.6.15

The "rt61" driver for Ralink's RT2600 chipset has a bug where it'll jam all (future) processes using the network, like i[wf]config, umount, etc. and refuse to be unloaded. Eventually it's necessary to power-cycle the machine because some shutdown script(s) will hang.

This bug is triggered if one tries to set or even read the interfaces' status while the i/f is in down. Running:

  modprobe rt61
  # link is now *not* set "up"
  # list wireless interfaces:
  iwconfig

after inserting the (PCMCIA) card is enough to demonstrate this.

To work around it's currently necessary to run "ip link set ra0 up" before *any* command that touches the interface.

My wifi card is a PC Card, D-Link DWL-G630, P/N EWLG630EU.E1, H/W ver. E1, F/W ver. 5.00

Revision history for this message
Aldous Peñaranda (dous) wrote :

From my experience, I was able to make a wireless card work using this driver (rt61) on one laptop but then on another laptop, it hangs and I get a kernel oops.

This is what we did on the current laptop:

1. Installed dapper
2. Dapper loads the rt61 module on its own
3. Upon running iwconfig, the terminal "hangs"
4. Checking dmesg reveals an oops message

Unfortunately, I don't have the information about the message right now but I do remember something about a NULL (de)reference error or something similar. Once the kernel oopses, it would be necessary to power-cycle the machine. It's a mystery to me as to why this happens since I was able to make the driver work on another laptop. Perhaps some details about the hardware are different?

Revision history for this message
Ben Collins (ben-collins) wrote : Re: [Bug 48087] Re: RT61 driver hangs net, if interface accessed while down

> 1. Installed dapper
> 2. Dapper loads the rt61 module on its own
> 3. Upon running iwconfig, the terminal "hangs"
> 4. Checking dmesg reveals an oops message

Please obtain this oops, and attach it to the bug report (via the web
interface, do not paste into a comment).

Thanks

Revision history for this message
Aldous Peñaranda (dous) wrote :

Hi,

We've just experienced this on the laptop where Dapper worked out of the box (initially). My girlfriend wanted to try connecting via dial-up and enabled her modem. When she rebooted, the laptop won't boot properly anymore. Gdm will still show up but when you log in, it will hang at some point when Gnome is starting.

Here's the dmesg log.

Revision history for this message
Warbo (warbo) wrote :

I found the same issue as Aldous D. Peñaranda with a PCI card. The system would come up with GDM, but not log in (just stop loading before the desktop comes up, mouse pointer still movable).
Switching to a console and running top showed "iwlist" as taking over 90% CPU power. (Pressing ctrl-alt-f8 to see the boot messages had the last as starting DHCP server, although I don't know whether was just because it was the last task)
iwlist was not killable since trying to use sudo would hang the terminal, so I had to boot into recovery mode and move iwlist out of $PATH. After doing that Ubuntu booted fine (I have reinstalled since, so I may not be able to reproduce it)

Revision history for this message
Bruce Miller (brm0423) wrote :

I have the same experience with an AirLink 101 AWLC3026T PCMCIA card which uses the rt61 driver.

Revision history for this message
Javier Jardón (jjardon) wrote :

Change status and assigned to ubuntu-kernel-team (https://wiki.ubuntu.com/KernelTeamBugPolicies)

Changed in linux-source-2.6.15:
assignee: nobody → ubuntu-kernel-team
status: Unconfirmed → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this linux-source-2.6.15 kernel bug to the new "linux" package. We appreciate your patience and understanding as we make this transition. Also, if you would be interested in testing the upcoming Intrepid Ibex 8.10 release, it is available at http://www.ubuntu.com/testing . Please let us know your results. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Launchpad Janitor (janitor) wrote : Kernel team bugs

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

Revision history for this message
kernel-janitor (kernel-janitor) wrote :

This bug report was marked as Confirmed a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-triage
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

switched status to invalid. Please adjust the status back to New if this is in error.

-JFo

Changed in linux (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

should have been Won't Fix. Adjusted the status.

-JFo

Changed in linux (Ubuntu):
status: Invalid → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.