capture kernel panic / hardware problem?

From: Johnson, Shaunn (SJohnson6_at_bcbsm.com)
Date: 05/25/04

  • Next message: Vivek Kumar: "Re: BIND issues with rndc" 
    To: "'General Red Hat Linux discussi on list'" <redhat-list@redhat.com>
Date: Tue, 25 May 2004 16:30:44 -0400

    Howdy list:

    Running RHEL v.3.0 rel. 2. (new install)

    I have been having a problem with what I -think- is
    the kernel, but not sure. Every time I do something like
    extract data (via cpio -idmv) or copy something to
    or from directories, I get a kernel panic. I thought
    it may have something to do with the filesystem,
    so I went to kernel.org and compiled 2.4.26 and see
    if it really was the options in the initial install.

    I'll have to figure out how to post the result of
    the panic. I thought I modified the /etc/syslog.conf
    to capture the errors, but nothing ever gets put into
    the messages file.

    Questions:

    1) how can I capture kernel panic messages and put
    it into a file when this happens?

    [my /etc/syslog.conf modification looks like so:

    kern.* /var/log/kern.log
    ...
    ]

    2) I can't help but to think that this is a problem with
    the IDE drive, but there are no hardware error regarding
    /dev/hdb or the like in the messages file. I'm going to
    switch out the drive, but why would cpio or cp cause
    the kernel to freak out if not hardware?

    Note: I didn't run up2date on this server - I will try that
    tonight as well.

    Suggestions?

    Thanks!

    -X 

    


    -- 
redhat-list mailing list
unsubscribe mailto:redhat-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/redhat-list
  • Next message: Vivek Kumar: "Re: BIND issues with rndc"

    Relevant Pages

    • Re: [PATCH] sata_sil: greatly improve DMA handling
      ... >>>To make it easy for others to test, since there are merge conflicts, ... as you can see from the messages file the kernel is capable of writing logging ... as the kernel was fully started... ...
      (Linux-Kernel)
    • Re: [SLE] hw tcp v4 cvsum failed
      ... In the messages file I found entries like: ... hw tcp v4 cvsum failed ... Kernel 2.4 has known problems with Intel's e100. ... Would it be a faster and safer fix to change to D-Link DFE-530 ??? ...
      (SuSE)
    • Re: [SLE] hw tcp v4 cvsum failed
      ... In the messages file I found entries like: ... hw tcp v4 cvsum failed ... Kernel 2.4 has known problems with Intel's e100. ...
      (SuSE)
    • Re: [SLE] hw tcp v4 cvsum failed
      ... In the messages file I found entries like: ... hw tcp v4 cvsum failed ... what kernel version are you running ...
      (SuSE)
    • Firewall enabling confusion.
      ... rebuilding my kernel with the following options turned on: ... I rebooted, for unrelated reasons, and now see in the messages file that ... I haven't yet rebuilt my kernel, so I don't understand why this kicked ... If it is a module, how do I enable logging, as adding ...
      (freebsd-questions)