RE: [Linux-hls-devel] Processes freezing up

[Tony L. <tl...@au...>]

Hi Luca,

We've had problems with our mail server, so this email is a re-post of
the one I sent yesterday with some added comments....

I applied the patch you sent and also uncommented the __DO_CLI__ macros
from hls_timers.c (Note, I had to add "unsigned long flags;" to
hls_timers.c to get the code to build with the macro enabled).

I then ran my program a few times (~10) with and without the rtc.

The machine froze independently of running my program with the rtc. On
one occasion, the machine froze when I ran "init 6" to reboot it (when I
couldn't kill off my program).

I suspected that the amount of logging to /var/log/messages was the
cause of the freeze, so I rebuilt the HLS scheduler with DEBUG=3D0, but
then the module wouldn't install and locked up my machine! I then
rebuilt the HLS scheduler with CLI=3D1 CREATE=3D1 INT_SCHED=3D1 =
DEBUG=3D1
MULDIV=3D1 (ie normal build) and stopped syslogd.

I then tested my program with no syslogd and with the rtc - which froze
my program and also the machine, so there does seem to be a problem with
the rtc and hls. During all of the rtc tests, I only saw the debug
statement from your last patch once, eg:

Sep  9 09:38:42 wally kernel: HLS ERROR: Task 635 has rt_priority =3D =
100
and state =3D 1
Sep  9 09:38:42 wally last message repeated 34 times
Sep  9 09:39:38 wally kernel: hls_ctl: Moving to res1
Sep  9 09:39:38 wally kernel:     ...and setting the parameters!
Sep  9 09:39:47 wally kernel: HLS ERROR: Scheduler res1 posted a timer
twice!!! WAI =3D 0
Sep  9 09:40:04 wally last message repeated 2 times
Sep  9 09:40:05 wally kernel: HLS ERROR: Task 1130 has rt_priority =3D =
100
and state =3D 1
Sep  9 09:40:05 wally kernel: HLSUnblockThreadHook --- WAI =3D 5    =
[505]

I then tested with no syslogd and no rtc. My program froze after running
for a few minutes, but the machine did not lock up, so I was able to
stop my program by removing the HLS module. This produces the following
errors, but I'm able to access the machine OK after removing the module:
(task 861 is my program)

Removing task 861 from HLS

../hls/hls_hooks.c:329: failed HLS assertion: "current_task() =3D=3D
Thread".      =20
../hls/hls_hooks.c:329: failed HLS assertion: "current_task() =3D=3D
Thread".      =20
HLS ERROR: not panicing, but continuing...

HLS ERROR: not panicing, but continuing... =20

During both rtc/non-rtc tests, either nothing was logged before the
program froze, or messages similar to the following appeared in the
messages file while the program was frozen (a lot of them!):

Sep  9 10:26:46 wally kernel: HLSUnblockThreadHook --- WAI =3D 5    =
[503]
Sep  9 10:26:46 wally kernel: HLS ERROR: Task 754 has rt_priority =3D =
100
and state =3D 1
Sep  9 10:26:46 wally kernel: HLS ERROR!!! Task state changed during the
hook??? 0 !=3D 1!!! Correcting...

Hope this was helpful.

Thanks,
Tony