Subject: Re: [linux-audio-user] system freezes
From: Josh Green (jgreen_AT_users.sourceforge.net)
Date: Thu Oct 25 2001 - 01:52:14 EEST
I've found one of the best ways to find out what is going on with a
kernel freeze is to hook up another computer via a serial cable and
configure it as another console (use minicom or something at 9600 baud
on other machine). See Documentation/serial-console.txt for more
information. The kernel will often times spit out OOPs information or
other debugging that you can't normally see because user space never
gets control again. When (and if) you get the oops info save it on the
other machine and then run ksymoops on the text output once you get your
primary machine booted again, which will often give you the address and
module that caused the crash. You'll probably need to re-compile your
kernel to get console on a serial port. I think you can also do this
with a network card, but I've never tried it.
--
Josh Green
Smurf Sound Font Editor (http://smurf.sourceforge.net)
On Tue, 2001-10-23 at 07:30, yeeking_AT_no-future.com wrote:
> nah - tried all that. tried logging in from another machine as well. the
> machine completely freezes. like you say, it must be a kernel problem.
> maybe its the lines i put in modules.conf - i didn't really kmow what i
> was doing and i copied what looked like the relevant bits for my
> soundcard from the alsa INSTALL file in the kmod section. must have put
> something dumb in there. don;t have access to my audio linux machine at
> the moment but:
>
> has anyone got an example modules.conf for alsa 0.9 and a single
> ens1370 card?
>
> cheers
>
> matthew
>
> > Why don't you try ctrl-alt-backspace instead. Most the time when things
> > freeze up it is not the entire system. It is usually the xserver. If
> > you
> > have kernel hacking configured in then that gives an even deeper level
> > to...
>
This archive was generated by hypermail 2b28 : Thu Oct 25 2001 - 01:42:48 EEST