Some tuner cards will not resume after suspend/hibernate

[CaptainSeabag]

Binary package hint: mythtv

Hi. There seems to be an issue with some tuner cards not waking up after a suspend or hibernate. My motherboard is an Asus A7V400-MX, and I've tried it with the Hauppauge WinTV PVR-150MCE PCI tv tuner card, as well as the Hauppauge Wintv-PVR-USB2 usb external tuner card. I have also tried the PCI card in my brother's nForce board, with the same results. (These boards resume from suspend/hibernate fine otherwise.)

After resuming, using the command "mplayer /dev/video0" will not display a TV channel window at all, as it is does after a fresh restart.

I believe it just may be certain motherboards, as plenty of other people have these cards and seem to be fine with them. I'll try it on other boards.

Superm1 on the ubuntu-mythtv IRC channel suggested going into /etc/defaults/acpi-support and adding a few modules to the module list, such as ivtv and ivtv2. This suspends the modules before a suspend/hibernate, and resumes them upon resume. After adding these to the file, I hibernated the machine, and using the command "mplayer /dev/video0" displayed the TV channel window, but the entire window was blue.

The twist: The screen is blue, but the sound is functional! Weirder yet, when I pull up another app, such as rhythmbox, and move the rhythmbox around, the video flickers while it redraws the rhythmbox window, and for a split second you see the video window for the tuner displaying a show!!!

[CaptainSeabag (captainseabag)]

After experiencing the strange "tv only for a split second while moving a window in front of it" phenomenon, I had an inkling it was a video driver issue. So, I Ctrl_Alt_Backspaced it and restarted the X server. I logged back in and after running mplayer again, the picture shows up perfectly! Hmmmm...

[CaptainSeabag (captainseabag)]

To be more specific, when I said "will not display a TV channel window at all," after resume if you run mplayer /dev/video0 it will hang. Restarting the X server and trying again removes the hanging problem, but then it just says, "Playing /dev/video0. Win32 LoadLibrary failed to load: avisynth.dll, /usr/lib/win32/avisynth.dll, /usr/local/lib/win32/avisynth.dll
Seek failed."

I have a feeling this just means, "Can't find the card." As I said before, this issue is remedied when I put "ivtv ivtv2" into MODULES in the acpi-support file, so this part is already solved.

[CaptainSeabag (captainseabag)]

Sorry for all the updates. I keep finding more information about this.
Even under normal behavior it says Win32 LoadLibrary failed to load. It's just that the process freezes right after that apparently normal notification.

[CaptainSeabag (captainseabag)]

I learned some more about this. Apparently placing the ivtv and ivtv2 modules in acpi-support solve the tuner wakeup issue: After coming back from suspend, uou can still tell mythtv to record things, and it records them properly. You just need to restart in order to view them properly. I guess now the only request I have here is, that someone put the ivtv and ivtv2 module insertion into an install script somewhere for the mythtv-ubuntu package? I'll also create another bug report for the video card.

[Mario Limonciello (superm1)]

I'm going to reclass this against acpi-support, since the ivtv drivers need to be reloaded upon suspend and are not currently right now.

[CaptainSeabag (captainseabag)]

Thanks Mario; that sounds good. I just gave up on having my box sleep.
I just leave it on 24/7 because come to find out, after fixing this
tuner waking up issue, the video card just displays blue until another
program (ie. Totem) is run, or the X server is restarted... then it
clears it up somehow.

Marc

On 24/09/2007, Mario Limonciello <email address hidden> wrote:
> I'm going to reclass this against acpi-support, since the ivtv drivers
> need to be reloaded upon suspend and are not currently right now.
>
> ** Changed in: acpi-support (Ubuntu)
> Sourcepackagename: mythtv => acpi-support
>
> --
> Some tuner cards will not resume after suspend/hibernate
> https://bugs.launchpad.net/bugs/130194
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Matthew Garrett (mjg59)]

Reassigning against the kernel. We can't just unload/load these drivers, since that will fail if anything has the tuner device open at suspend time. The drivers need to be fixed in the kernel.

[Leann Ogasawara (leannogasawara)]

Hi CaptainSeabag,

I noticed your last comment was from a while ago. We're currently almost at the kernel freeze for Hardy Heron 8.04. Just curious if you'd be able to test against the latest Hardy Beta kernel - 2.6.24-12.22 and verify if this is still an issue? See http://www.ubuntu.com/testing for more information. If the issue does still exist, care to attach the following information to this bug report:

* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

It would also be helpful to wait to capture your dmesg output after you do a suspend/resume cycle as outlined here: https://wiki.ubuntu.com/DebuggingKernelSuspend .

For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

[CaptainSeabag (captainseabag)]

Hi guys,
Well, I figured out that restarting the X server allows you to watch
the video again. Apparently it was my video card drivers... I haven't
upgraded from Feisty for a number of reasons so I can't help much
there...
Thanks
Marc

On 27/03/2008, Leann Ogasawara <email address hidden> wrote:
> Hi CaptainSeabag,
>
> I noticed your last comment was from a while ago. We're currently
> almost at the kernel freeze for Hardy Heron 8.04. Just curious if you'd
> be able to test against the latest Hardy Beta kernel - 2.6.24-12.22 and
> verify if this is still an issue? See http://www.ubuntu.com/testing for
> more information. If the issue does still exist, care to attach the
> following information to this bug report:
>
> * cat /proc/version_signature > version.log
> * dmesg > dmesg.log
> * sudo lspci -vvnn > lspci-vvnn.log
>
> It would also be helpful to wait to capture your dmesg output after you
> do a suspend/resume cycle as outlined here:
> https://wiki.ubuntu.com/DebuggingKernelSuspend .
>
> For more information regarding the kernel team bug policy, please refer
> to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we
> appreciate your help and feedback.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
>
> --
> Some tuner cards will not resume after suspend/hibernate
> https://bugs.launchpad.net/bugs/130194
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Mario Limonciello (superm1)]

The tuners though themselves, are alright? You can capture video post
suspend?

On Thu, Mar 27, 2008 at 4:13 PM, CaptainSeabag <email address hidden>
wrote:

> Hi guys,
> Well, I figured out that restarting the X server allows you to watch
> the video again. Apparently it was my video card drivers... I haven't
> upgraded from Feisty for a number of reasons so I can't help much
> there...
> Thanks
> Marc
>
> On 27/03/2008, Leann Ogasawara <email address hidden> wrote:
> > Hi CaptainSeabag,
> >
> > I noticed your last comment was from a while ago. We're currently
> > almost at the kernel freeze for Hardy Heron 8.04. Just curious if
> you'd
> > be able to test against the latest Hardy Beta kernel - 2.6.24-12.22 and
> > verify if this is still an issue? See http://www.ubuntu.com/testingfor
> > more information. If the issue does still exist, care to attach the
> > following information to this bug report:
> >
> > * cat /proc/version_signature > version.log
> > * dmesg > dmesg.log
> > * sudo lspci -vvnn > lspci-vvnn.log
> >
> > It would also be helpful to wait to capture your dmesg output after you
> > do a suspend/resume cycle as outlined here:
> > https://wiki.ubuntu.com/DebuggingKernelSuspend .
> >
> > For more information regarding the kernel team bug policy, please refer
> > to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we
> > appreciate your help and feedback.
> >
> > ** Changed in: linux (Ubuntu)
> > Status: New => Incomplete
> >
> >
> > --
> > Some tuner cards will not resume after suspend/hibernate
> > https://bugs.launchpad.net/bugs/130194
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
> --
> Some tuner cards will not resume after suspend/hibernate
> https://bugs.launchpad.net/bugs/130194
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Mario Limonciello
<email address hidden>

[CaptainSeabag (captainseabag)]

Yes, it records it. When I go to play it back though, the mplayer
shows up but a blue block covers the entire picture. After restarting
the X server, I can play back the port-suspend recordings just fine.
Thanks!
Marc

On 27/03/2008, Mario Limonciello <email address hidden> wrote:
> The tuners though themselves, are alright? You can capture video post
> suspend?
>
> On Thu, Mar 27, 2008 at 4:13 PM, CaptainSeabag <email address hidden>
> wrote:
>
>
> > Hi guys,
> > Well, I figured out that restarting the X server allows you to watch
> > the video again. Apparently it was my video card drivers... I haven't
> > upgraded from Feisty for a number of reasons so I can't help much
> > there...
> > Thanks
> > Marc
> >
> > On 27/03/2008, Leann Ogasawara <email address hidden> wrote:
> > > Hi CaptainSeabag,
> > >
> > > I noticed your last comment was from a while ago. We're currently
> > > almost at the kernel freeze for Hardy Heron 8.04. Just curious if
> > you'd
> > > be able to test against the latest Hardy Beta kernel - 2.6.24-12.22 and
> > > verify if this is still an issue? See http://www.ubuntu.com/testingfor
> > > more information. If the issue does still exist, care to attach the
> > > following information to this bug report:
> > >
> > > * cat /proc/version_signature > version.log
> > > * dmesg > dmesg.log
> > > * sudo lspci -vvnn > lspci-vvnn.log
> > >
> > > It would also be helpful to wait to capture your dmesg output after you
> > > do a suspend/resume cycle as outlined here:
> > > https://wiki.ubuntu.com/DebuggingKernelSuspend .
> > >
> > > For more information regarding the kernel team bug policy, please refer
> > > to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we
> > > appreciate your help and feedback.
> > >
> > > ** Changed in: linux (Ubuntu)
> > > Status: New => Incomplete
> > >
> > >
> > > --
> > > Some tuner cards will not resume after suspend/hibernate
> > > https://bugs.launchpad.net/bugs/130194
> > > You received this bug notification because you are a direct subscriber
> > > of the bug.
> > >
> >
> > --
> > Some tuner cards will not resume after suspend/hibernate
> > https://bugs.launchpad.net/bugs/130194
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
>
>
>
> --
> Mario Limonciello
> <email address hidden>
>
>
> --
>
> Some tuner cards will not resume after suspend/hibernate
> https://bugs.launchpad.net/bugs/130194
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Leann Ogasawara (leannogasawara)]

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.

[CaptainSeabag (captainseabag)]

Hi Leann,At the moment I've stopped using Ubuntu/MythTV- I'm concentrating
on other things in life right now. However, a friend and I came up with a
good MythTV plugin over the last year- whom should I talk to about it?
Marc

2008/8/29 Leann Ogasawara <email address hidden>

> 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.
>
> ** Tags added: cft-2.6.27
>
> --
> Some tuner cards will not resume after suspend/hibernate
> https://bugs.launchpad.net/bugs/130194
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Michele Mangili (mangilimic)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[xxMcBainxx (xxmcbainxx)]

I have a Hauppauge WinTV PVR-150 PCI running Ubuntu 13.04 and I have this problem.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 130194

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[xxMcBainxx (xxmcbainxx)]

I ran "apport-collect 130194" and I recieved an error.

[quote]
*** Error: Updating problem report

You are not the reporter or subscriber of this problem report, or the report is a duplicate or already closed.

Please create a new report using "apport-bug".
[/quote]

[penalvch (penalvch)]

CaptainSeabag, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]