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

[Luca A. <luc...@em...>]

Hi Tony,

[...] 
> >Does your machine crash even without using the RTC 
> Yes. I sent the first message at the end of the day after only running a
> couple of tests, but I then ran more tests the next day which showed the
> problem to occur even without the RTC. Sorry about the confusion - I
> thought the first email was lost but our mail server sent it out a day
> late!
Ok, so RTC is not the cause of the problem... Hence, since I am not able
to reproduce the crash I suspect that the problem is in a bad
interaction with the preemption patch.
 
> >Was the test performed with or without the kernel preemption patch?
> Yes, we have been using the kernel preemption patch.
I think this is the only difference between your configuration and my
one... I hope to be able to get an x86 test machine in the next week, so
that I can install the preemption patch and try to reproduce the
problem.

> I did plan to
> re-test without this patch but I've been busy with other work.
This would be very useful. Anyway, there is no hurry (I still have to
set up a test environment with a preemptive kernel).
 
> >If I understand well, the "HLS ERROR: Scheduler xxx posted a timer
> twice" is not the first error in your log... Is my understanding
> correct?
> 
> Yes, here is the log from when the hls_module was inserted:
Ok. So the timer was not the cause of the problem...

[...]
> Sep  9 09:36:31 wally kernel: [1938629664], 803 : sched 'PS' registered
> in slot 4
> Sep  9 09:36:31 wally kernel: [2011100543], 803 : sched 'RES' registered
> in slot 5
> Sep  9 09:36:31 wally kernel: already PRIVATE_DATA != NULL???
> Sep  9 09:36:31 wally kernel: already PRIVATE_DATA != NULL???
> Sep  9 09:36:36 wally kernel: hls_ctl: Moving to res1
> Sep  9 09:36:36 wally kernel:     ...and setting the parameters!
> Sep  9 09:36:52 wally kernel: HLS ERROR: Task 756 has rt_priority = 100
> and state = 1
> Sep  9 09:36:52 wally kernel: HLSUnblockThreadHook --- WAI = 5    [505]
> Sep  9 09:36:52 wally kernel: HLSUnblockThreadHook --- WAI = 5    [505]
It seems that about 15 seconds after moving a task to the res1
scheduler, the internal HLS status gets corrupted... I think the latest
two messages are just the log daemon that wakes up due the the "HLS
ERROR:" printk. Hence, the important message is "HLS ERROR: Task 756 has
rt_priority = 100 and state = 1". I'll have a look...

> >Is the HLS module failing when compiled with CLI=1 CREATE=1
> INT_SCHED=1 DEBUG=0 MULDIV=1?
> I've just tried this and it builds OK. My machine still froze - here's
> the output ... (I don't think that anything new was logged)
Looks like a similar output...

BTW, what does your program do? (how many reservations does it create,
how big are those reservations, and so on...). I think Paul tested both
the schedtest example and hourglass, and it worked...
Can you provide a simple program that causes this freeze?

			Thanks,
				Luca
-- 
_____________________________________________________________________________
Copy this in your signature, if you think it is important:
                               N O    W A R ! ! !



--
Email.it, the professional e-mail, gratis per te: http://www.email.it/f

Sponsor:
Se ami vivere all'aperto non puoi farne a meno...clicca e scopri cos'è
Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=1775&d=12-9