soft lockup with zd1201 wlan chipset

Bug #212888 reported by atdt911
4
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

happens on feisty+gutsy+hardy beta (32bit, xp works fine).

I have a zd1201 based wireless USB dongle, and recently upgraded my hardware to a p35 mobo (gigabyte ga-pa35-ds3l (ich9 controller)).

I had feisty + gutsy installed and working without any problems in the past. since i installed my new hardware i have a problem with activating the zd1201 - gutsy/hardy will soft lock when trying to access the network or run something, for example if i run ifconfig it will just sit there doing nothing and any other issued command after it will lock , i can do alt+f1 and alt+ctrl+del and system will shutdown as normal but i cant do anything else.

sometimes i can get another terminal while a command is freezing but top shows nothing special, dmesg is normal & shows module as registered, lsmod & lspci list the module (usb_uhci in lsmod), nothing in logs etc...when i try to manually unload/load the module i get the lockup during modprobe zd1201.

plugging & unplugging the dongle does not help, only message i get sometimes from dmesg is "rx urb failed: -84" after unplugging (got that also before the hardware change).

other usb devices i have are working as expected (thumb drives).

I tried reinstalling and installing hardy beta + playing with bios settings and changing usb ports - best i could get is a working system randomly (in about 1/10 tries) and even then it sometimes hangs after an arbitrary amount of time.

Since the dongle worked on my previous hardware configuration i suspect it has something to do with ich9 bios settings or the ich9 controller.

Revision history for this message
atdt911 (ori-ab) wrote :
Revision history for this message
atdt911 (ori-ab) wrote :
Revision history for this message
atdt911 (ori-ab) wrote :
Revision history for this message
atdt911 (ori-ab) wrote :
Revision history for this message
atdt911 (ori-ab) wrote :

additional info :

system works well when usb is plugged before loading ubuntu.
if i plug the usb after ubuntu/kernel loads system hangs.

Revision history for this message
atdt911 (ori-ab) wrote :

more info :

discovered that sometimes i get device descriptor error when this halt occurs : device descriptor read/64, error -110.
then kernel will try to give it another address, will fail again, etc...

dmesg log is attached - problem can be seen in messages regarding usb 2-2 (lines 25,26,41,56 etc...)

Revision history for this message
atdt911 (ori-ab) wrote :

I found out that when there is a device descriptor error like the above my usb mouse doesnt work till I unplug the wireless dongle : it seems it is not getting power (no light).
the dongle does light on despite the error.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux the kernel for Hardy Heron.

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
atdt911 (ori-ab) wrote :

after not having this problem for quite a while latest update caused lockups again :
ubuntu locks after logging in to gnome with the error about "gnome settings daemon not responding".
system will respond to alt+ctrl+del only after removing the usb dongle.

I can get to gnome only if i boot without the dongle and then plugging it, but even then sometimes i get the lockups.

thinking it was a kernel issue i went back to 2.6.24-16 from 2.6.24-17 but it didnt help, so it may be a recent package update.

Revision history for this message
atdt911 (ori-ab) wrote :

after another update I cant login into gnome anymore - it locks if the dongle is connected during boot (responds only to alt+ctrl+del or commands like : ls,more, etc... after i disconnect the dongle) and shows an error : "could not start gnome-setting-daemon...did not receive a response...etc..."
if the dongle is not connected gnome will load but would lock after connecting the dongle. if i disconnect the dongle after the lockup i get about 1-2 seconds of activity and lockup will resume afterward. no error is shown in any log file. i suspected dhcdbd or avahi-daemon and reinstalled them but it didnt help. it seems like the dongle causes dbus not to respond.

Revision history for this message
atdt911 (ori-ab) wrote :

I had managed to get the stick to work for one session - i booted as usual without the usb stick plugged & after gnome was up I plugged it and it somehow worked for 1 session.
So I did an upgrade to 2.6.24-19 and rebooted, but it didnt solve the problem - i still get soft lockups when the device is plugged & randomly it works in about 1/10 tries
I tried running some commands with strace after i got the lock up and i can see it stalls every time when calling ioctl.

any suggestions how to debug?

Revision history for this message
atdt911 (ori-ab) wrote :

I managed to activate the wlan by booting with irqpoll/irq=routeirq but it will only work if the device is not plugged during the boot process.

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
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged 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: Triaged → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, 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-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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