From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: more 3ware issues
Date: Sat, 12 May 2001 21:54:28 -0700 [thread overview]
Message-ID: <200105130454.VAA17842@bitmover.com> (raw)
I have a few more data points on the 3ware 6410 card in case anyone else
is looking at this. As I said before, this is a nicely designed card,
I like it, kudos to the 3ware folks.
Combinations which work for me:
ASUS A7V and K7V motherboards, K7@1Ghz, 3c905, 1GB - 1.5GB ram. Works
like a champ under 2.2.19, not so great under 2.2.15 (Mandrake 7.1) nor
under 2.4.4.
Combination which does not work under 2.2.15, 2.2.19, or 2.4.4:
Abit KT7 motherboard, K7@1Ghz, 3c905, 1GB. I strongly suspect the Abit
motherboard being the cause of the problem. What I see is as soon as
I start a disk scrubber on all 4 drives, is stuff like
3w-xxxx: tw_post_command_packet(): Unexpected bits.
3w-xxxx: tw_check_bits(): Found unexpected bits (0x572076c0).
3w-xxxx: tw_check_bits(): Found unexpected bits (0x57206a60).
3w-xxxx: tw_post_command_packet(): Unexpected bits.
3w-xxxx: tw_interrupt(): Bad response, status = 0xc7, flags = 0x1b, unit = 0x0.
3w-xxxx: tw_check_bits(): Found unexpected bits (0x572079a0).
3w-xxxx: tw_interrupt(): Unexpected bits.
3w-xxxx: tw_interrupt(): Bad response, status = 0xc7, flags = 0x1b, unit = 0x0.
3w-xxxx: tw_check_bits(): Found unexpected bits (0x572079c0).
3w-xxxx: tw_interrupt(): Unexpected bits.
3w-xxxx: tw_scsi_eh_abort(): Abort failed for unknown Scsi_Cmnd 0xfbf4ac00, resetting card 0.
3w-xxxx: tw_scsi_eh_reset(): Reset succeeded for card 0.
3w-xxxx: tw_post_command_packet(): Unexpected bits.
3w-xxxx: tw_check_bits(): Found unexpected bits (0x57226a60).
3w-xxxx: tw_post_command_packet(): Unexpected bits.
3w-xxxx: tw_check_bits(): Found unexpected bits (0x57226a60).
3w-xxxx: tw_post_command_packet(): Unexpected bits.
3w-xxxx: tw_scsi_eh_abort(): Abort failed for unknown Scsi_Cmnd 0xfbf49e00, resetting card 0.
Those are cut and pasted from several different OS versions, so they don't
all go together. The bottom line was that with the Abit the system was
just completely unstable and unusable. When the problems occurred, it
would stall all I/O for quite a while (a minute or more) and then reset
the card, unwedge, and repeat.
Again, I don't want people to take this as a slam on the 3ware cards, I
like them a lot, in fact after getting the first one to work last week
I ordered more of them, which resulted in the Abit problems. I don't
think it's the card at all. Everyone I know who has them likes them.
It's just that some combinations work and some don't (yet) so it's
useful information for people to know which is which.
If Adam or anyone wants to try and debug this, I'll happliy put the machine
with the Abit and a card up on the net, you can ssh in and do whatever
you want to it, let me know.
--lm
next reply other threads:[~2001-05-13 4:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 4:54 Larry McVoy [this message]
2001-05-13 5:35 ` Jeff V. Merkey
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=200105130454.VAA17842@bitmover.com \
--to=lm@bitmover.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
all inboxes | Powered by JetHome®