From: Arjan van de Ven <arjan@infradead.org>
To: Olivier Galibert <galibert@pobox.com>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
SCSI Mailing List <linux-scsi@vger.kernel.org>,
"Hack inc." <linux-kernel@vger.kernel.org>
Subject: Re: Infinite interrupt loop, INTSTAT = 0
Date: Wed, 28 Sep 2005 19:24:08 +0200 [thread overview]
Message-ID: <1127928249.2893.39.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20050928171052.GA45082@dspnet.fr.eu.org>
On Wed, 2005-09-28 at 19:10 +0200, Olivier Galibert wrote:
> On Wed, Sep 28, 2005 at 11:24:46AM -0500, James Bottomley wrote:
> > On Wed, 2005-09-28 at 18:07 +0200, Olivier Galibert wrote:
> > > scsi1:0:0:0: Attempting to abort cmd ffff8101b1cdf880: 0x28 0x0 0x0
> > > 0xbc 0x0 0x3f 0x0 0x0 0x8 0x0
> >
> > Hmm, that message doesn't appear in the current kernel driver.
> >
> > Is this a non-standard kernel or non-standard aic79xx driver?
>
> Just reproduced the exact same message with a vanilla 2.6.13.2.
> Checking the just-untarred sources, it _is_ in aix79xx_osm.c, in
> ahd_linux_abort. You must have typoed "Attempting" in your grep :-)
>
> Want be to try to BUG() it or something to get a stack trace? The
> crash happens a handful of seconds after the card dumping, time enough
> for a well-placed dmesg in an xterm.
>
> Incidentally, how can one get a backtrace without crashing the kernel
> in the operation?
WARN_ON(1)
next prev parent reply other threads:[~2005-09-28 17:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 13:45 Infinite interrupt loop, INTSTAT = 0 Olivier Galibert
2005-09-28 15:05 ` James Bottomley
2005-09-28 16:07 ` Olivier Galibert
2005-09-28 16:24 ` James Bottomley
2005-09-28 16:42 ` Olivier Galibert
2005-09-28 17:10 ` Olivier Galibert
2005-09-28 17:13 ` Randy.Dunlap
2005-09-28 17:24 ` Arjan van de Ven [this message]
2005-09-28 17:51 ` James Bottomley
2005-09-28 18:33 ` Olivier Galibert
2005-10-01 14:03 ` James Bottomley
2005-10-03 13:42 ` Olivier Galibert
2005-10-03 16:15 ` James Bottomley
2005-10-04 8:45 ` Olivier Galibert
2005-10-04 13:23 ` James Bottomley
2005-10-04 14:55 ` Olivier Galibert
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=1127928249.2893.39.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=James.Bottomley@SteelEye.com \
--cc=galibert@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).