public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Stas Sergeev <stsp@aknet.ru>
Cc: ALSA devel <alsa-devel@alsa-project.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
Date: Sat, 21 Jun 2008 03:14:16 +0200	[thread overview]
Message-ID: <485C55E8.3090703@keyaccess.nl> (raw)
In-Reply-To: <485B2A92.4000801@aknet.ru>

On 20-06-08 05:57, Stas Sergeev wrote:

CCed onto linux-kernel to possibly help future googlers...

> Rene Herman wrote:

>> What's this? 2.6.26-rc6:
>> ===
>> input: PC Speaker as /class/input/input5
>> PCSP: Timer resolution is not sufficient (4000250nS)
>> PCSP: Make sure you have HPET and ACPI enabled.
>> PC-Speaker initialization failed.
>> pcspkr: probe of pcspkr failed with error -5
>> ===
>> A HPET I do not have, ACPI is enabled and the driver worked fine on a
>> previous -rc.
> 
> That means that the high-res timer > mode is not available. See
> cat /proc/timer_list
> It should contain the lines like
>   .resolution: 1 nsecs
> 1 nsecs means a high-res mode.
> Some large values (like 4000250)
> means low-res.
> Try adding the hrtimers people to
> CC if this is a problem.

In this case the problem was the ACPI PM-Timer (CONFIG_X86_PM_TIMER) got
disabled. Re-enabling it, snd-pcsp is working fine again.

It does seem a bit off that you needs something as (relatively) modern
as an ACPI timing source (or HPET, or ...) to drive something quite as
legacy as the PC speaker, but oh well.

Rene.



       reply	other threads:[~2008-06-21  1:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <485AB878.5080101@keyaccess.nl>
     [not found] ` <485B2A92.4000801@aknet.ru>
2008-06-21  1:14   ` Rene Herman [this message]
2008-06-21  7:00     ` 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient" Stas Sergeev

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=485C55E8.3090703@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stsp@aknet.ru \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox