From: John Jasen <jjasen@datafoundation.com>
To: <linux-kernel@vger.kernel.org>
Cc: <gibbs@freebsd.org>, <dima@datafoundation.com>
Subject: problems with aic7xxx driver 6.1.11 (fwd)
Date: Fri, 29 Jun 2001 12:37:26 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.30.0106291237030.9716-100000@flash.datafoundation.com> (raw)
---------- Forwarded message ----------
Date: Mon, 25 Jun 2001 11:31:32 -0400 (EDT)
From: John Jasen <jjasen@datafoundation.com>
To: gibbs@freebsd.org
Cc: Dima Meschaninov <dima@datafoundation.com>
Subject: problems with aic7xxx driver 6.1.11
#1) It seems that the new aic7xxx drivers do not detect raid controllers,
et al on the bus, as we have an nStor NexStor 8le that is completely
invisible to your driver.
#2) There seem to be a few problems with the new driver, where it can
easily get confused into a reset loop. (see below for a rough
description)
---------- Forwarded message ----------
Date: Mon, 25 Jun 2001 11:20:08 -0400
From: Dmitry Meshchaninov <dima@datafoundation.com>
To: John Jasen <jjasen@datafoundation.com>
Subject: Description of SCSI situation on zathras
Looks like we have had power down at night. Afterwards, the scsi tray was
in a strange state - the system BIOS didn't find anything on the bus, and
naturally the linux driver didn't either.
After we power cycled scsi tray and rebooted the system, the system BIOS
detected all the scsi devices but the linux driver still was blind.
It said something about timeouts during lun probing and marked all the
devicess offline, and we tried it via reboot/powercycle of the system at
least 2-3 times.
After we setup the old driver everything went fine.
reply other threads:[~2001-06-29 16:37 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=Pine.LNX.4.30.0106291237030.9716-100000@flash.datafoundation.com \
--to=jjasen@datafoundation.com \
--cc=dima@datafoundation.com \
--cc=gibbs@freebsd.org \
--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
all inboxes | Powered by JetHome®