Re: Temporary random kernel hang

2006-12-15 Thread seven
Peter Zijlstra wrote: > > 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 subscrib

Re: Temporary random kernel hang

2006-12-15 Thread Peter Zijlstra
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

Re: Temporary random kernel hang

2006-12-14 Thread seven
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 that this is the cause of the direct mail. Andrew Morton wrote:

Re: Temporary random kernel hang

2006-12-14 Thread Andrew Morton
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

Re: Temporary random kernel hang

2006-12-11 Thread seven
> 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 /var/lib/oprofile > opcontrol --vmlinux=/boot/vmlinux-$(uname -r) > opcontrol --