From: Duncan Gibb <duncangibb@uk.dmgworldmedia.com>
To: "Justin T. Gibbs" <gibbs@scsiguy.com>
Cc: "Cress, Andrew R" <andrew.r.cress@intel.com>,
Rohit Gupta <rohit@davsys.com>,
linux-scsi@vger.kernel.org
Subject: RE: aic79xx U320 + e1000 Intel hangs on Idual Xeon 7505
Date: 10 Apr 2003 22:00:51 +0100 [thread overview]
Message-ID: <1050008453.23304.52.camel@astrognat> (raw)
In-Reply-To: <530360000.1049993706@aslan.btc.adaptec.com>
On Thu, 2003-04-10 at 17:55, Justin T. Gibbs wrote:
JG> Do you have the nmi_watchdog enabled?
Not normally. I tried booting with "nmi_watchdog=1" and it made no
difference. Note that in my case (unlike Rohit Gupta's), it's not a
complete kernel lockup - the system is fine apart from one dead SCSI
channel. Processes which try to touch devices on ChB hang apparently
indefinitely.
JG> What bus speed are you running for the aic7902 and the gig-E card?
The BIOS says "AUTO"; /proc/pci says 66MHz.
JG> Are the on the same physical PCI/PCI-X bus?
No. SuperMicro built the board such that PCI-X slots 1 and 2 and the
SCSI controller are on one bus, and PCI-X slot 3 and the Ethernet
interface are on another. All the slots are empty.
DG> the driver has negotiated "Max Tagged Openings 0" with
DG> all the devices on this bus.
JG> That seems really wierd - like you disabled disconnection.
I don't know how I would do that with this hardware. SCSIselect doesn't
have that as an option (and has everything defaulted except ChB
termination), and none of my hardware can be jumpered that way AFAIK.
DG> /proc/scsi/aic79xx/1 {..} controller as Channel B,
DG> but all the device info says Channel A.
JG> The two channels are actually two independent, single channel,
JG> controllers. The user doesn't know that
The user has been misled by the marketing info and the motherboard
manual ;-)
JG> I'll review the code to see if I can make it less confusing
JG> (perhaps just omit the channel identifier).
Presumably channel identifiers are useful in some cases, so IMHO the
most logical option would be to make them match what's reported by
/proc/scsi/scsi. There the channels are all called "00".
JG> send me privately {..} the output of "cat /proc/scsi/aic79xx/*"
JG> and "cat /proc/scsi/scsi" as well as a dmesg from the system.
JG> {..} If you compile the driver with debugging enabled and a
JG> debug mask of 8, I can also see the content of the serial
JG> eeprom to see if the settings are strange.
OK. I noticed you released new source today, so I will download that
and play 'make' again.
Duncan
next prev parent reply other threads:[~2003-04-10 20:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-09 19:26 aic79xx U320 + e1000 Intel hangs on Idual Xeon 7505 Cress, Andrew R
2003-04-09 20:23 ` Duncan Gibb
2003-04-09 20:27 ` Justin T. Gibbs
2003-04-09 22:01 ` Duncan Gibb
2003-04-10 16:55 ` Justin T. Gibbs
2003-04-10 21:00 ` Duncan Gibb [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-09 15:47 Duncan Gibb
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=1050008453.23304.52.camel@astrognat \
--to=duncangibb@uk.dmgworldmedia.com \
--cc=andrew.r.cress@intel.com \
--cc=gibbs@scsiguy.com \
--cc=linux-scsi@vger.kernel.org \
--cc=rohit@davsys.com \
/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