Messages in this thread | | | Date | Sat, 18 Sep 1999 23:31:42 -0400 (EDT) | From | Didier Contis <> | Subject | Re: Oops not catched by klogd |
| |
On Sat, 18 Sep 1999, Keith Owens wrote:
> On Thu, 16 Sep 1999 19:24:43 -0400, > Didier CONTIS <didier@ece.gatech.edu> wrote: > >Right now, this machine won't stay up more than 3 days. I get on > >the console an oops, but it does no appear in > >my /var/adm/messages. > > > >This is really bad because I cannot track what is happening. > > > >Both syslog and klog are running : > > Does klogd die after the oops? There is a bug in klogd that makes it > SEGV itself when trying to decode an oops. I always run "klogd -x", no > klogd decode. >
Well, I cannot answer this question since after the oops I am unable to access the console. I can still switch from one console to another (alt + fx) but cannot login.
Thanks for the tip regarding the "-x" switch.
Regards, Didier.
----------------------------------------------------------------------- Research Engineer I Georgia Institute of Technology School of Electrical Engineering, Atlanta, GA 30332-0250 E-MAIL: didier@ee.gatech.edu PHONE: (404) 894-3872
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |