From: Keith Owens <kaos@ocs.com.au>
To: Marc Schiffbauer <marc.schiffbauer@links2linux.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: new aic7xxx oopses with AHA2940
Date: Sun, 27 May 2001 12:32:20 +1000 [thread overview]
Message-ID: <27691.990930740@ocs3.ocs-net> (raw)
In-Reply-To: Your message of "Sun, 27 May 2001 04:21:30 +0200." <20010527042129.A12765@lisa.links2linux.home>
On Sun, 27 May 2001 04:21:30 +0200,
Marc Schiffbauer <marc.schiffbauer@links2linux.de> wrote:
>* Keith Owens schrieb am 27.05.01 um 03:07 Uhr:
>> Since you are failing during modprobe, creating /var/log/ksymoops is a
>> good idea, man insmod, see KSYMOOPS ASSISTANCE. Reproduce the
>> problem to get a clean oops trace then run it through ksymoops, using
>> the saved module data in /var/log/ksymoops.
>
>OK. Now I cut out the Oops out of my /var/log/messages, then did
>
>cat aic7xxx.oops | ksymoops -k /var/log/ksymoops/20010527040453.ksyms -l
>/var/log/ksymoops/20010527040453.modules > trace1
That one was no good. Because modprobe failed, the data in
/var/log/ksymoops did not get updated.
>and another run with default options:
>ksymoops 0.7c on i686 2.4.5. Options used
You should be running ksymoops 2.4.x with 2.4 kernels,from
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4
>>>EIP; e0a7b3a7 <[aic7xxx]ahc_match_scb+17/c0> <=====
>Trace; e0a7b79d <[aic7xxx]ahc_search_qinfifo+14d/6b0>
>Trace; e0a7c226 <[aic7xxx]ahc_abort_scbs+66/300>
That trace looks good, now it is up to the aic7xxx maintainer to fix
the problem.
next prev parent reply other threads:[~2001-05-27 2:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-26 16:05 new aic7xxx oopses with AHA2940 Marc Schiffbauer
2001-05-27 1:07 ` Keith Owens
2001-05-27 2:21 ` Marc Schiffbauer
2001-05-27 2:32 ` Keith Owens [this message]
2001-05-27 2:36 ` Jeff Garzik
2001-05-27 10:41 ` Marc Schiffbauer
2001-05-29 18:55 ` Justin T. Gibbs
2001-05-29 22:26 ` Marc Schiffbauer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=27691.990930740@ocs3.ocs-net \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.schiffbauer@links2linux.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.