Date: Mon, 6 Apr 1998 15:03:38 +0400 From: "Eugene Radchenko" <genie@qsar.chem.msu.su> To: "Alex" <garbanzo@hooked.net>, <ache@nagual.pp.ru> Cc: <scsi@FreeBSD.ORG>, <current@FreeBSD.ORG> Subject: Re: SCSI errors with latest -current Message-ID: <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su>
next in thread | raw e-mail | index | archive | help
Hi! -----Original Message----- From: Alex <garbanzo@hooked.net> Date: Sunday, April 05, 1998 12:43 AM Subject: Re: SCSI errors with latest -current On Sat, 4 Apr 1998, Andrey Chernov wrote: > With latest -current I start to get this sort of errors for my several > SCSI drives. Since they started at once for several drives, I suppose it > is not hardware problem. Any ideas? I find that if your disk system is pushed hard enough, that you will get errors like that with SCB paging and/or TAGGED_QUEUING enabled even before PHKs commits. This is one of the things the CAM code (dunno if it's stable enough to use) fixes. In essence it's a combination hardware and software problem... I think. As I tried to shout all over the SCSI list recently (to no avail), this is not limited to -current or 2.2.5. I had something like this even in 2.1 (though not as drastic -- just dump died and not the whole system). I have the feeling that 2.1 had not done tagged queueing yet. I hope now that one of the core team was bitten, this problem will be solved sooner ;-) BTW this definitely would classify as bug fix and as such, should be put in -stable, yes? I think many people are somewhat disappointed to obtain a release CD just to begin patching the system right after installation... Cheers Genie --- ######################################################### Eugene V. Radchenko Research associate, Computer Chemistry E-mail: genie@qsar.chem.msu.su http://org.chem.msu.su/~genie =================================================== "There are now new criminals out there that don't have guns. They have computers and many have other weapons of mass destruction." -- Janet Reno, Attorney General of the United States To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005f01bd614b$b01d65c0$6330fa9e>