public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Shannon Hendrix <shannon@widomaker.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Adaptec aic7xxx driver problems?
Date: Sat, 7 Feb 2004 22:09:14 -0500	[thread overview]
Message-ID: <20040208030914.GE10344@widomaker.com> (raw)


Are there known issues with the Adaptec drivers on x86 systems?

Since upgrading to kernel 2.6.1, I get system lockups every few days to
a few weeks.

There are no messages, no warnings, not even debugging information.

The only thing I notice is that the SCSI bus appears to be hung, and the
system halts.  Sometimes the bus hangs before the system stops, but not
always.

Doesn't happen under any 2.4.x kernel, and I do not believe it happened
on the 2.6 betas I tried.

What would be the possible reasons for not getting any debug
information?  I do not have kernel debugging enabled, but do have SCSI
debugging in place.

If I enable kernel debugging, is that more likely to find something?

In the past when I had this problem, it was usually a kernel or driver
issue, and I rarely was able to get any debug information, but I'm open
to suggestions.

I cannot reproduce this problem on demand though.  It does happen when
there is moderate SCSI traffic, but doesn't seem to happen at the
highest SCSI bus loads.

I tried to cause the crash this week, but could not.  Thirty minutes
after I finally gave up, it happened.

Still have no information to go on, but I thought I would ask here in
case someone else is seeing trouble.


-- 
shannon "AT" widomaker.com -- [4649 5920 4320 204e 4452 5420 5348 5920 4820
2056 2054 434d 2048 4d54 2045 204e 5259 4820 444e 0a53]

                 reply	other threads:[~2004-02-08  3:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20040208030914.GE10344@widomaker.com \
    --to=shannon@widomaker.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox