xfs
[Top] [All Lists]

Re: kernel panic using xfs as modules and gcc-2.96

To: Juha Saarinen <juha@xxxxxxxxxxxx>
Subject: Re: kernel panic using xfs as modules and gcc-2.96
From: "Marcelo E. Magallon" <marcelo.magallon@xxxxxxxxxxx>
Date: Sun, 17 Jun 2001 03:11:17 +0200
Cc: xfs ML <linux-xfs@xxxxxxxxxxx>
In-reply-to: <Pine.LNX.4.33.0106171108540.5399-100000@xxxxxxxxxxxxxxxxxxxxx>
Mail-followup-to: Juha Saarinen <juha@xxxxxxxxxxxx>, xfs ML <linux-xfs@xxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.3.18i
>> Juha Saarinen <juha@xxxxxxxxxxxx> writes:

 > I don't mind giving the latest CVS a go and compiling it with 2.96.
 > Could someone give me short instructions on how to use ksymoops etc?

 Create a directory /var/log/ksymoops/, owned by root, mode 0644 or
 0600, then reproduce the oops.  On that directory you'll find several
 files named like:

 20010602.log
 20010602135630.ksyms
 20010602135630.modules

 you are interested in the last two.  As you might have guessed, the
 name of the file is a timestamp (YYYYMMDDHHMMSS).

 Once you have your oops, save it to a file, say xfs.oops and do
 something like this:

 $ ksymoops -v /boot/the-kernel-that-oopsed \
   -k /var/log/closesttimebeforetheoops.ksyms \
   -l /var/log/closesttimebeforetheoops.modules \
   -m /boot/System.map-correspondingtothekernel \
   xfs.oops

 I have kernels called vmlinuz-2.4.6-pre3 with a System.map called
 System.map-2.4.6-pre3, so this would be:

 $ ksymoops -v /boot/vmlinuz-2.4.6-pre3 \
   -k /var/log/20010602135630.ksyms \
   -l /var/log/20010602135630.modules \
   -m /boot/System.map-2.4.6-pre3 \
   xfs.oops

 You probably want to run insmod_ksymoops_clean on a dayly cronjob,
 otherwise you'll collect a lot of logs in /var/log/ksymoops.

 HTH,

-- 
Marcelo

<Prev in Thread] Current Thread [Next in Thread>