All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: James Bourne <jbourne@mtroyal.ab.ca>
Cc: linux-kernel@vger.kernel.org, gibbs@plutotech.com
Subject: Re: 2.4.18 AIC7XXX hard lockup
Date: Fri, 07 Jun 2002 15:26:49 -0700	[thread overview]
Message-ID: <3D013329.E872EAE2@zip.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0206070726060.27407-102000@skuld.mtroyal.ab.ca>

James Bourne wrote:
> 
> Hi,
> We are currently running 2.4.18 (Marcelo) on a Dell PE4400 with
> Perc3/DC and 2 on board adaptec controllers (two 7899 channels and one
> 7880).
> 
> On the first 7899 channel we have attached 2 Quantum DLT 7000 drives and a
> BHTi Quad 7 changer, on the second there are another 2 Quantum DLT
> 7000 drives and a BHTi Q2 changer as well as the internal CDROM.
> 
> Now, what is happening is when we are initializing the JBs, the host
> system will abruptly hang.  Turning on aic7xxx=verbose on the kernel
> command line has given additional output, but still nothing solid as far
> as trouble shooting information.  The only information I have been
> able to get out of it has been:
> 
> scsi1:0:6:0: Attempting to queue an ABORT message
> 
> This is the stock 6.2.4 adaptec driver in 2.4.18 and with the 6.2.5 driver
> under 2.4.18 (I've patched and tested this one today).  Attached are
> kernel log segments of the information from boot to hang for 6.2.4 and
> 6.2.5 driver revisions...
> 

It does that for me in 2.5 as well, very occasionally.

Try booting with the `nmi_watchdog=1' kernel boot option,
and see if that catches a backtrace.

-

      parent reply	other threads:[~2002-06-07 22:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 21:29 2.4.18 AIC7XXX hard lockup James Bourne
2002-06-07 22:19 ` Justin T. Gibbs
2002-06-13  3:47   ` James Bourne
2002-06-07 22:26 ` Andrew Morton [this message]

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=3D013329.E872EAE2@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=gibbs@plutotech.com \
    --cc=jbourne@mtroyal.ab.ca \
    --cc=linux-kernel@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 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.