[TOSHIBA PORTEGE M400] suspend/resume failure with edimax rtl wifi card inserted

[Vincenzo Ciancia]

I had my system in suspended state, I resumed it but I inserted my edimax "Bus 001 Device 004: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter" before. My system is never able to resume properly from suspend or hibernation if I insert that card before.

ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/share/apport/apportcheckresume
Failure: suspend/resume
InterpreterPath: /usr/bin/python2.6
MachineType: TOSHIBA PORTEGE M400
Package: linux-image-2.6.28-11-generic 2.6.28-11.39
ProcAttrCurrent: unconfined
ProcCmdLine: root=UUID=4f832810-3f9c-4135-b077-4a08190e957a ro quiet splash
ProcCmdline: /usr/bin/python /usr/share/apport/apportcheckresume
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.28-11.39-generic
SourcePackage: linux
Tags: resume suspend
Title: [TOSHIBA PORTEGE M400] suspend/resume failure
UserGroups:

[Dirk F (fieldhouse)]

Bug 274780 may be related and work-arounds are listed there that might be applicable.

[Jim Lieb (lieb)]

Bug 274780 relates to removing a device before resume. As I read you description, you plug in a new device prior to resume, correct? What happens if you wait until the resume is complete and then plug in the device? These drivers depend on the system sensing the device being inserted/removed, something it cannot do if it has powered off the socket. Please let us know the result. Thanks.

[Vincenzo Ciancia (vincenzo-ml)]

It works if I insert it after resume. Is there any machinery to have a usb device virtually unplugged and re-plugged when suspend or hibernate is used?? So that the edimax card could be made a special case? I think just removing the module before suspend and reloading at resume should work.

[Jim Lieb (lieb)]

In your case, the module was not loaded at suspend time so there is no unload to do. What is needed is a bus scan at some point (at the end?) in resume. That is effectively what you did by plugging it in after resume. When the system starts up, it does a bus scan and generates the needed events to trigger the hotplug. Doing this at resume is harder because it has to 'diff' the assumed prior state with the new state.

Thanks for the additional info. Let me do some research...

[Vincenzo Ciancia (vincenzo-ml)]

Il 11/07/2009 02:21, Jim Lieb ha scritto:
> In your case, the module was not loaded at suspend time so there is no
> unload to do. What is needed is a bus scan at some point (at the end?)
> in resume. That is effectively what you did by plugging it in after
> resume. When the system starts up, it does a bus scan and generates the
> needed events to trigger the hotplug. Doing this at resume is harder
> because it has to 'diff' the assumed prior state with the new state.
>
> Thanks for the additional info. Let me do some research...
>

Indeed, the card breaks resume if it is plugged in before suspend, but
in the same way as if I insert it after suspend and before resume. One
thing that I didn't mention anywhere is that the system deadlocks and I
have to hard-reboot when the card is inserted before resume.

[Vincenzo Ciancia (vincenzo-ml)]

It seems fixed in the latest 2.6.30 kernel in karmic. The latest 2.6.31 breaks the driver of this card, due to a different bug which already has a patch, when a patched kernel is out I will test it too.

[Jim Lieb (lieb)]

Can you confirm this issue exists with the most recent Karmic Koala 9.10 Beta release? ISO CD images are available at http://cdimage.ubuntu.com/releases/karmic/ . If the issue remains with Karmic it would be great to then also test the latest upstream mainline kernel available. This will allow additional upstream developers to examine this issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Thanks in advance.

[Jeremy Foshee (jeremyfoshee)]

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.]