Bug#390409: timers

[Václav Jůza <vaclavjuza@seznam.cz>]

Hi,

I am experiencing the same problem now (after disk crash, I reinstalled the 
system).
Before that, it used to work with kernel 2.6.16-1-k7 (I cannot find now the 
particular debian revision).
Now, I am using version 2.6.18-3 of linux-image-2.6.18-1-k7, and have tested 
2.6.16-2-k7 (2.6.16-18), with both the warning is displayed.

In that old working kernel 2.6.16-1-k7 there was in config:
# CONFIG_HZ_100 is not set
# CONFIG_HZ_250 is not set
CONFIG_HZ_1000=y
CONFIG_HZ=1000
while in the 2.6.16-2-k7 (2.6.16-18), there is:
# CONFIG_HZ_100 is not set
CONFIG_HZ_250=y
# CONFIG_HZ_1000 is not set
CONFIG_HZ=250

Mike O'Connor wrote:
>also,  can you show me the output of:
>cat /proc/asound/timers
>That will should definitively show whether your system timers are at 1khz or
>400hz
root@delfin(pts/1):~# cat /proc/asound/timers
G0: system timer : 4000.000us (10000000 ticks)
G1: RTC timer : 976.562us (100000000 ticks)
  Client sequencer queue 0 : stopped
P0-0-0: PCM playback 0-0-0 : SLAVE
P0-0-1: PCM capture 0-0-1 : SLAVE
P0-1-0: PCM playback 0-1-0 : SLAVE
P0-2-0: PCM playback 0-2-0 : SLAVE
P0-2-1: PCM capture 0-2-1 : SLAVE

>Have you tried the recommendations in the rosegarden FAQ?
1. When I selected the sequencer synchronization to rtc, the system freezed.
2,3. Most probably would work, but IMHO it is bug, if the recompilation of 
kernel 
is needed.
4. Even that way I did not get rid of the message (and it would not solve the 
actual problem anyway).

vj