Comment 24 for bug 273323

Hi Christian,

I've install a new set of several kernel modules(em28xx-new) because
the old ones not only caused the resume problem but also worked not so
stable with my device. That was done before I could read your last
message, so I haven't tried your method of blacklisting the driver(s).
 However, the resume/suspend hasn't had any problem since I installed
the new driver.

I would be trying your method by reversing the kernel modules. But
since the device will load several kernel modules, should I blacklist
them all? Is there any efficient way of detecting which one of the
modules actually causes the resume problem?

Cheers,
P.D.

On Fri, Oct 3, 2008 at 12:34 AM, Christian Schuerer <email address hidden> wrote:
> Hello P.D.
>
> On Thursday 02 October 2008, Peng Deng wrote:
>> Christian, I guess I wouldn't blacklist the driver if I want to use
>> the device, plus I am not sure actually which driver to block (the
>> device will load several modules). However, I would try to replace it
>> with another em28xx-new driver, which seems more reliable, I just need
>> time to compile the latter.
>>
>> No matter if the device is plugged in or not, sudo pm-suspend behaves
>> as the same as from the menu item here.
>
> I meant that you blacklist it from suspend[1], which would mean that the
> driver is removed prior suspend and then loaded again. If you don't blacklist
> it, then the system tries to suspend the device, which can cause problems if
> the device and/or the driver do not properly support it. Thus removing it
> before suspend and loading it again afterwards can have a different behavior.
>
> [1] e.g. in /etc/pm/config.d/config:
> SUSPEND_MODULES="$SUSPEND_MODULES snd_hda_intel"
>
> Kind regards,
> Christian
>
> --
> Regression: Intrepid - 2.6.27 hangs on resume
> https://bugs.launchpad.net/bugs/273323
> You received this bug notification because you are a direct subscriber
> of the bug.
>