ivtv module needs unload/load at suspend/resume

[Brian J. Murrell]

Binary package hint: pm-utils

The "ivtv" module needs to be unloaded and reloaded through the suspend/resume cycle. The following in /etc/pm/config.d/ivtv seems to work:

# ivtv module needs to be removed/added on suspend/resume
SUSPEND_MODULES="ivtv"

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: pm-utils 1.3.0-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: ksplice_ecokb0ql_vmlinux_new ksplice_ecokb0ql ksplice_783pkukt_vmlinux_new ksplice_783pkukt ksplice_8n71bzhp ksplice_749zva78_vmlinux_new ksplice_749zva78 ksplice_7vzmez4k_vmlinux_new ksplice_7vzmez4k nvidia
Architecture: i386
Date: Mon Jul 12 10:29:08 2010
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.utf8
 SHELL=/bin/bash
SourcePackage: pm-utils

[Chow Loong Jin (hyperair)]

On Monday 12,July,2010 10:36 PM, Brian J. Murrell wrote:
> The "ivtv" module needs to be unloaded and reloaded through the
> suspend/resume cycle. The following in /etc/pm/config.d/ivtv seems to
> work:
>
> # ivtv module needs to be removed/added on suspend/resume
> SUSPEND_MODULES="ivtv"

What happens if you don't? Does it fail to suspend, or fail to resume, or does
the ivtv module stop working?

--
Kind regards,
Chow Loong Jin

[Brian J. Murrell (brian-interlinx)]

On Wed, 2010-07-14 at 08:18 +0000, Chow Loong Jin wrote:
>
> What happens if you don't? Does it fail to suspend, or fail to resume, or does
> the ivtv module stop working?

ivtv fails to be functional after the resume. Reading from /dev/video0
for example, fails.

[Chow Loong Jin (hyperair)]

Reassigning to linux, seems to be a driver issue.

[Brian J. Murrell (brian-interlinx)]

On Fri, 2010-07-16 at 07:58 +0000, Chow Loong Jin wrote:
> Reassigning to linux, seems to be a driver issue.

Yes, ultimately, this is a driver issue. But what's going to be the
result of this reassignment to linux? Likely this issue will be
acknowledged over in the linux component and then just languish (likely
for a long time) until the ivtv developers fix the problem.

In the meanwhile ivtv users will continue to have problems suspending
and resuming while waiting for somebody to do something (that nobody is
likely interested in working on).

Wouldn't it be much more useful to your users to install my suggested
work-around in the pm-utils package until the upstream driver is fixed?
After-all, most users couldn't give a rat's ass which package a problem
is in. Most users just want things to work and don't care about the
bureaucracy of what the cause of a problem is, who owns a problem and
what the "proper" fix is.

Ultimately, it should be the teams goal to resolve user specified
problems as fast as possible. Yes, that might mean installing a less
than desirable work-around until a better solution is available. But
that's what serving "customers" is all about.

[Jeremy Foshee (jeremyfoshee)]

Hi Brian,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

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

[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 development release http://cdimage.ubuntu.com/daily-live/current/ . 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.]