that it does not.
I will use gmail with 'Reply to all' from now on in order to post messages.
Sorry for any inconveniences.
Regards,
Horia
--
View this message in context:
http://www.nabble.com/Temporary-random-kernel-hang-tf2779860.html#a7890237
Sent from the linux-kernel mailing list archive
On Thu, 2006-12-14 at 15:07 -0800, seven wrote:
>
> Andrew Morton wrote:
> >
> > No, I wasn't ignoring you for four days. Please, always do reply-to-all.
> >
>
> I am using nabble's interface to post messages ( www.nabble.com ) and I am
> not subscribed to the mailing list, so it's possible th
m calls.
>
> The next step would be to try to catch one of these eposides with strace.
>
I will try. Thank you.
Regards,
Horia
--
View this message in context:
http://www.nabble.com/Temporary-random-kernel-hang-tf2779860.html#a7883193
Sent from the linux-kernel mailing list archive a
On Mon, 11 Dec 2006 10:46:25 -0800 (PST)
seven <[EMAIL PROTECTED]> wrote:
>
>
>
> > A kernel profile will tell us were the kernel is burning CPU. Something
> > like this (run as root):
> >
> > #!/bin/sh
> > while true
> > do
> > opcontrol --stop
> > opcontrol --shutdown
> > rm -rf
y relation between the CPU temp. and system freezes (only one
match could be just a coincidence).
Is is possible that this kernel behavior could be related to temp. control
events?
Regards and thank you again,
Horia
--
View this message in context:
http://www.nabble.com/Temporary-random-ker
N = 9
PATCHLEVEL = 3
-
Can you give me some pointers about where to start debugging this issue?
Regards,
Horia
--
View this message in context:
http://www.nabble.com/Temporary-random-kernel-hang-tf2779860.html#a7755634
Sent f
6 matches
Mail list logo