From: David Harty <dwh@dharty.com>
To: DCRYPT@telefonica.net, stoth@kernellabs.com
Cc: linux-media@vger.kernel.org
Subject: Re: [BUG, workaround] HVR-2200/saa7164 problem with C7 power state
Date: Thu, 12 Feb 2015 15:38:46 -0800 [thread overview]
Message-ID: <54DD3986.3010707@dharty.com> (raw)
In-Reply-To: <8039614.312436.1422971964080.JavaMail.defaultUser@defaultHost>
On 02/03/2015 05:59 AM, DCRYPT@telefonica.net wrote:
>> ---- Mensaje original ----
>> De : stoth@kernellabs.com
>> Fecha : 02/02/2015 - 16:39 (GMT)
>> Para : DCRYPT@telefonica.net
>> CC : linux-media@vger.kernel.org
>> Asunto : Re: [BUG, workaround] HVR-2200/saa7164 problem with C7 power state
>>
>>>> Basically, it starts working but after a while I get an "Event timed out" message and several i2c errors and VDR shuts down (some hours after reboot). As the web page mentions, I tested downgrading the PCIe bandwith from GEN2 to GEN1 without success. But after playing with different BIOS options, what did the trick was limiting the power-saving C-states. If I select "C7" as the maximum C-state, the card fails as described. After limiting the maximum C-state to "C6", it has been working for a whole weekend.
>> Good feedback on the C7 vs C6 power state, thanks.
> You are welcome, Steve. Happy to be helpful.
>
> I will be at your disposal for testing purposes, if you need.
>
> BR
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Some additional input:
I made similar changes to the bios of my ASRock H87M Pro4. There were
multiple settings for CPU C state support. I set the C7 state to
disabled and forced selected C6 in the State support dropdown to further
force it to C6.
Within 3 hours the dmesg was filling up with the no free sequences errors.
I hadn't changed the PCI Express Configuration to Gen1 because per the
http://whirlpool.net.au/wiki/n54l_all_in_one page it didn't appear to
help reliably. I've made that change now. I'll report to see if that
improves anything, perhaps both changes have to be made in conjunction.
Regards,
David
next prev parent reply other threads:[~2015-02-12 23:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 15:04 DCRYPT
2015-02-02 15:33 ` [BUG, workaround] HVR-2200/saa7164 problem with C7 power state DCRYPT
2015-02-02 15:39 ` Steven Toth
2015-02-03 13:59 ` DCRYPT
2015-02-12 23:38 ` David Harty [this message]
2015-02-17 3:57 ` catchall
2015-02-17 12:47 ` dCrypt
2015-02-19 4:04 ` David Harty
2015-02-19 13:22 ` Steven Toth
2015-02-19 16:03 ` David Harty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54DD3986.3010707@dharty.com \
--to=dwh@dharty.com \
--cc=DCRYPT@telefonica.net \
--cc=linux-media@vger.kernel.org \
--cc=stoth@kernellabs.com \
--cc=v4l@dharty.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.