* 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
@ 2008-06-19 19:50 Rene Herman
2008-06-20 3:57 ` Stas Sergeev
0 siblings, 1 reply; 5+ messages in thread
From: Rene Herman @ 2008-06-19 19:50 UTC (permalink / raw)
To: Stas Sergeev; +Cc: ALSA devel
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
2008-06-19 19:50 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient" Rene Herman
@ 2008-06-20 3:57 ` Stas Sergeev
2008-06-21 1:00 ` Rene Herman
2008-06-21 1:14 ` Rene Herman
0 siblings, 2 replies; 5+ messages in thread
From: Stas Sergeev @ 2008-06-20 3:57 UTC (permalink / raw)
To: Rene Herman; +Cc: ALSA devel
Hi.
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
2008-06-20 3:57 ` Stas Sergeev
@ 2008-06-21 1:00 ` Rene Herman
2008-06-21 1:14 ` Rene Herman
1 sibling, 0 replies; 5+ messages in thread
From: Rene Herman @ 2008-06-21 1:00 UTC (permalink / raw)
To: Stas Sergeev; +Cc: ALSA devel
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
2008-06-20 3:57 ` Stas Sergeev
2008-06-21 1:00 ` Rene Herman
@ 2008-06-21 1:14 ` Rene Herman
2008-06-21 7:00 ` Stas Sergeev
1 sibling, 1 reply; 5+ messages in thread
From: Rene Herman @ 2008-06-21 1:14 UTC (permalink / raw)
To: Stas Sergeev; +Cc: ALSA devel, Linux Kernel
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient"
2008-06-21 1:14 ` Rene Herman
@ 2008-06-21 7:00 ` Stas Sergeev
0 siblings, 0 replies; 5+ messages in thread
From: Stas Sergeev @ 2008-06-21 7:00 UTC (permalink / raw)
To: Rene Herman; +Cc: ALSA devel, Linux Kernel
Hello.
Rene Herman wrote:
> 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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-06-21 7:00 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-06-19 19:50 2.6.26-rc6 snd-pcsp: "Timer resolution is not sufficient" Rene Herman
2008-06-20 3:57 ` Stas Sergeev
2008-06-21 1:00 ` Rene Herman
2008-06-21 1:14 ` Rene Herman
2008-06-21 7:00 ` Stas Sergeev
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.