Re: rt20 patch question

[Steven Rostedt <rostedt@goodmis.org>]

On Fri, 12 May 2006, Mark Hounschell wrote:

>
> They stops can be anywhere up to even a few minutes depending how
> patient I want to be. I was just playing with it to possibly get another
> log. The machine froze. Did the log thing while frozen. Then I attempted
> to ssh into it from another machine. It let me in and the machine
> unfroze at that same time. But only to stop again in a few seconds. The
> new shell was also frozen. I sshd to it again, same thing.

This is a good indictation of a missed wake up.  Now the question is, what
is sleeping and why didn't it wake up.

>
> While the machine was unfrozen I was able to halt the cpu process
> basically taking it out of its execution loop and putting into a delay
> loop of 1 ms via
>
> while(clock_nanosleep(CLOCK_REALTIME, TIMER_ABSTIME, &tim, NULL) &&
> errno == EINTR);

Hmm, do you have high res timers turned on?

>
> As long as the CPU process is halted and in this loop the machine acts
> normal. As soon as the CPU process goes back into his execution loop we
> are back to the "stops".
>

Could you hook up a serial, and on the machine do a

  # cat /dev/ttyS0 &

Just to open the serial for reading.  And then on the machine on the other
end of the serial cable, bring up minicom, do a ctrl-a f t

ctl-a f sends a break,

the t will do a task dump.  Do this when the machine is stopped and see
what is running.  Hopefuly the sysrq works from serial (I've had boxes
where the keyboard sysrq didn't work but serial did).

Oh, and send me the output too.

Thanks,

-- Steve

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/