Skip to contentSkip to conversation

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

DISCUSSION Rene Herman 2 participants 5 messages Jun 19, 2008 – Jun 21, 2008

lore
Share & tools
lore
#0 lore raw

Hi Stas.

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.

Rene.

#1 lore raw

Hi.

Quoted 10 lines · Rene Herman

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.

#2 lore raw

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

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

Quoted 13 lines
Quoted 10 lines · Rene Herman

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.

Quoted 9 lines

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.

#3 lore raw
In reply to Stas Sergeev

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

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

Quoted 13 lines
Quoted 10 lines · Rene Herman

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.

Quoted 9 lines

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.

#4 lore raw

Hello.

Quoted 2 lines · Rene Herman

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.

Note that this option is available
only if you enable CONFIG_EMBEDDED.
Most people will just never see it.