kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

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.

** Tags added: needs-kernel-logs needs-upstream-testing resume suspend

** Tags added: fiesty

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/130194

Title:
  Some tuner cards will not resume after suspend/hibernate

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  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!!!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/130194/+subscriptions