linux-kernel - Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 21 Jun 2008 03:14:16 +0200
From:	Rene Herman <rene.herman@...access.nl>
To:	Stas Sergeev <stsp@...et.ru>
CC:	ALSA devel <alsa-devel@...a-project.org>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"

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.


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/