Bug 69351 - saa7134 - 3.12.8 warning during resume from s3
Summary: saa7134 - 3.12.8 warning during resume from s3
Status: RESOLVED MOVED
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(Other) (show other bugs)
Hardware: i386 Linux
: P1 normal
Assignee: Ondrej Zary
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-24 00:40 UTC by Valerio Vanni
Modified: 2014-09-22 13:25 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.12.8
Subsystem:
Regression: No
Bisected commit-id:


Attachments
logs and configs (152.78 KB, text/plain)
2014-01-24 00:40 UTC, Valerio Vanni
Details

Description Valerio Vanni 2014-01-24 00:40:26 UTC
Created attachment 123231 [details]
logs and configs

[1.] One line summary of the problem:    

Kernel 3.12.8 gives a warning during resume from S3 sleep

[2.] Full description of the problem/report:

It happens also with 3.12.7, 3.12.6 and 3.13. It doesn't happen with 2.6.24.7.
OS is Debian Lenny, with vanilla kernel. It happens the same after upgrade to Squeeze.

I suspend the machine with s2ram and it goes off.
During the resume it writes that warning, then it seem to work normally, 
except for serial redirection of console.

I use redirection of console to serial port (with lilo directive: append="
console=ttyS0 console=tty0") and I check the messages in another machine.
This stops working as soon as I suspend. It begins to send mangled lines and 
it doesn't work again until the next full restart.
Only the serial redirection has this problem, the local console  works.

I put some log as attachment.
Comment 1 Lan Tianyu 2014-01-24 07:39:15 UTC
From the log, there are two warnings related with i915 and saa7134 drivers.


(In reply to Valerio Vanni from comment #0)
> I use redirection of console to serial port (with lilo directive: append="
> console=ttyS0 console=tty0") and I check the messages in another machine.
> This stops working as soon as I suspend. It begins to send mangled lines and 
> it doesn't work again until the next full restart.
> Only the serial redirection has this problem, the local console  works.

This also looks like a driver issue. I think you should apply bugs for these warning issues to related component separately.
Comment 2 Aaron Lu 2014-01-27 08:15:47 UTC
For the saa7134 warning, perhaps send an email to the maintainer and cc the list is a good idea:
$ ./scripts/get_maintainer.pl -f drivers/media/pci/saa7134/saa7134-core.c 
Mauro Carvalho Chehab <m.chehab@samsung.com> (odd fixer:SAA7134 VIDEO4LIN...,commit_signer:2/2=100%)
Hans Verkuil <hans.verkuil@cisco.com> (commit_signer:2/2=100%)
Ondrej Zary <linux@rainbow-software.org> (commit_signer:1/2=50%)
Michael Opdenacker <michael.opdenacker@free-electrons.com> (commit_signer:1/2=50%)
linux-media@vger.kernel.org (open list:SAA7134 VIDEO4LIN...)
linux-kernel@vger.kernel.org (open list)

For the i915 warning, please file a new bug to Drivers/Video-DRI(Intel).
Comment 3 Valerio Vanni 2014-01-27 16:22:33 UTC
For the saa7134: should I send an email with a referral to this bug or as a new thing?
Comment 4 Valerio Vanni 2014-01-27 16:54:13 UTC
I just saw that inside bugzilla.kernel.org there is a saa7134 section, can I open a bug there (ccing the mantainers) instead of sending an email?
Comment 5 Aaron Lu 2014-01-28 02:27:38 UTC
(In reply to Valerio Vanni from comment #3)
> For the saa7134: should I send an email with a referral to this bug or as a
> new thing?

As a new thing I think since we don't have made any progress except deciding this is a driver issue here.

And yes you can file a bug in the saa7134 section.

Note You need to log in before you can comment on or make changes to this bug.