From: Adam Radford <aradford@3WARE.com>
To: "'Manish Lachwani'" <manish@Zambeel.com>, linux-kernel@vger.kernel.org
Subject: RE: Hangs seen with the 3ware controller and the 2.4.17 kernel .. .
Date: Tue, 12 Nov 2002 10:47:28 -0800 [thread overview]
Message-ID: <A1964EDB64C8094DA12D2271C04B812672C85A@tabby> (raw)
You're using an old driver before the conversion to
documentation/DMA-mapping. This
will cause raw io to 'not work'. If you upgrade to the latest driver
1.02.00.031
driver, you should be fine.
-Adam
-----Original Message-----
From: Manish Lachwani [mailto:manish@Zambeel.com]
Sent: Monday, November 11, 2002 11:54 PM
To: linux-kernel@vger.kernel.org
Cc: Manish Lachwani
Subject: Hangs seen with the 3ware controller and the 2.4.17 kernel ...
Hello,
I am using a 2.4.17 SMP kernel and .018 version of the 3ware driver. This
happens when we have two controllers (8-port and 4-port), IO is going on
with both the controllers and on one controller (4-port in my experiment),
there is command timeout and the reset sequence fails. This is a hard
kernel hang. The last message on the window is "reset sequence failed"
kdb for the eh_1 shows:
scsi_error_handler -> scsi_unjam_host -> scsi_try_host_reset -> schedule
I do know that the scsi_try_host_reset(..) calls scsi_sleep for 10*HZ.
Anyway, another scenario that causes a hang:
scsi_error_handler -> scsi_unjam_host -> scsi_try_to_abort_command ->
schedule
Also, This hang seems to occur when there are two controllers only. When I
tried with
one controller numerous times, I could not reproduce this problem. Is it
possible that scsi_unjam_host is getting confused with two devices and when
reset fails on one host?
Any help is appreciated ...
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
reply other threads:[~2002-11-12 18:38 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=A1964EDB64C8094DA12D2271C04B812672C85A@tabby \
--to=aradford@3ware.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manish@Zambeel.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
all inboxes | Powered by JetHome®