Hey everyone,
I've written about this before, but I've specific questions now ;-)
I'm running stock 2.4.16, self compiled, on a Beige G3/266, with KDE as my
window manager. I get random crashes with any 2.4.x kernel. I would like to
use xmon to figure out what's wrong so that I can get it fixe
Hello!
>>> Russell Hires <[EMAIL PROTECTED]> 04.12.2001 14.30 Uhr >>>
> I want to record this xmon info to a file, which I tried, but it didn't save.
Maybe the program sends ist output to stderr? Have you tried "xmon foo bar 2>&1
> myfile"?
--benny.
"Benny Siegert" <[EMAIL PROTECTED]> writes:
> Maybe the program sends ist output to stderr? Have you tried "xmon
> foo bar 2>&1 > myfile"?
That would be rather difficult since xmon is a in-kernel debugger...
ttyl,
--
Josh Huber | [EMAIL PROTECTED] |
On Tue, 2001-12-04 at 14:30, Russell Hires wrote:
> I'm running stock 2.4.16, self compiled, on a Beige G3/266, with KDE as my
> window manager. I get random crashes with any 2.4.x kernel. I would like to
> use xmon to figure out what's wrong so that I can get it fixed, but I can't
> see the te
> That machine has a Mach64 chip, right?
I forgot to include an important detail: I'm actually running with a Voodoo3
card.
> if before
> running X, you set the VT X runs on to the same depth (using fbset) you
> have configured in X. You'll have to find out yourself.
I guess I've got more readi
On Thu, 2001-12-06 at 01:00, Russell Hires wrote:
>
> > If that was the only problem... when you're in xmon, bad things have
> > happened and everything is interrupted. Only when you exit xmon (by
> > entering 'x') does the system continue to run. So there is no filesystem
> > access in xmon.
> Ty
Okay, accepting for the moment that when the kernel dies, I can't read the
console to find out what went wrong, what else can I do to figure out what's
wrong? Which kernel or other system logs would tell me?
I do know that for some reason, heavy disk activity kills the kernel. I run
anacron, a
On Mon, 2001-12-10 at 15:34, Russell Hires wrote:
> Okay, accepting for the moment that when the kernel dies, I can't read the
> console to find out what went wrong, what else can I do to figure out what's
> wrong? Which kernel or other system logs would tell me?
/var/log/kern.log, but as it se
8 matches
Mail list logo