Date: Mon, 19 Dec 2005 18:40:45 -0800 From: "Vinod Kashyap" <vkashyap@amcc.com> To: "Mike Andrews" <mandrews@bit0.com>, <freebsd-stable@freebsd.org> Subject: RE: "Request Requeued/Retrying Command" with twa card on FreeBSD 6.0 Message-ID: <2B3B2AA816369A4E87D7BE63EC9D2F2601224B37@SDCEXCHANGE01.ad.amcc.com>
next in thread | raw e-mail | index | archive | help
> -----Original Message----- > From: owner-freebsd-stable@freebsd.org=20 > [mailto:owner-freebsd-stable@freebsd.org] On Behalf Of Mike Andrews > Sent: Monday, December 19, 2005 6:10 PM > To: freebsd-stable@freebsd.org > Subject: "Request Requeued/Retrying Command" with twa card on=20 > FreeBSD 6.0 >=20 > I've got a weird but apparently minor issue with a 3Ware=20 > 9500S-4LP in a FreeBSD 6.0-RELEASE system... >=20 > When the system is run with boot.verbose=3D"YES" in=20 > /boot/loader.conf, I get these messages on the console: >=20 > (da0:twa0:0:0:0): Request Requeued > (da0:twa0:0:0:0): Retrying Command > (da0:twa0:0:0:0): Request Requeued > (da0:twa0:0:0:0): Retrying Command > (repeat a few dozen times each time) >=20 > ...during some heavy disk activity, like, for example,=20 > qpopper rewriting a 50 MB mailbox. (I know qpopper's a bit=20 > of a slug.) Not all heavy disk IO triggers it, though; I can=20 > do something like "dd if=3D/dev/zero of=3D/tmp/testfile=20 > bs=3D10485760 count=3D128" followed by "dd if=3D/tmp/testfile=20 > of=3D/dev/null bs=3D10485760" and have it complete without a=20 > single SCSI timeout message. >=20 > Turn boot.verbose=3D"NO" off and the messages go away, but IO=20 > still lags badly. >=20 > "camcontrol tags" says it has 254 tag openings, which seems=20 > like a bit much. Dropping down to 16 seems to make the=20 > messages go away. >=20 > Do the twa cards even do TCQ between the card and the OS? =20 > From what I understand, they won't do NCQ between the card=20 > and the SATA disks, even if you have something like=20 > Barracudas that support it -- you need the new 3Ware 9550=20 > card for that. >=20 > If they don't, why does it advertise 254 tags, and if it=20 > does, why does it seem to choke on the default setting of 254? >=20 Although the driver can handle 254 simultaneous requests, if the I/O's, are big, there's the possibility that the firmware cannot accept new requests even if 254 has not been hit. In that case, the driver will have to ask CAM to requeue the requests. > Other than laggy IO (shell prompts hang, MP3's skip for 5 -=20 > 30 seconds) there aren't any actual IO errors or anything=20 > else wrong, which for this particular system is just minor=20 > annoyance instead of serious problem.=20 > 5.4-RELEASE did the same thing. I have an apparent=20 > workaround, I'm just trying to sanity-check it and its necessity. >=20 > This is an Asus P4C800-E Deluxe board, so I'm running the twa=20 > card in a 32-bit slot. The system is otherwise totally idle=20 > when this happens, no interrupt storms, USB and Firewire=20 > disabled in the BIOS so we don't have IRQs shared with=20 > Giant-locked drivers... >=20 > dmesg, vmstat -i, other stuff available on request if needed.=20 > Kernel config is the stock 'SMP' one. >=20 >=20 >=20 > Mike Andrews * mandrews@bit0.com * http://www.bit0.com > It's not news, it's Fark.com. Carpe cavy! >=20 > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to=20 > "freebsd-stable-unsubscribe@freebsd.org" > -------------------------------------------------------- CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, = is for the sole use of the intended recipient(s) and contains = information that is confidential and proprietary to Applied Micro = Circuits Corporation or its subsidiaries. It is to be used solely for = the purpose of furthering the parties' business relationship. All = unauthorized review, use, disclosure or distribution is prohibited. If = you are not the intended recipient, please contact the sender by reply = e-mail and destroy all copies of the original message.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2B3B2AA816369A4E87D7BE63EC9D2F2601224B37>