Date: Thu, 17 Jul 2003 22:20:53 +0200 From: Thomas Quinot <thomas@FreeBSD.ORG> To: Daniel Lang <dl@leo.org> Cc: Thomas Quinot <thomas@FreeBSD.ORG> Subject: Re: atapicam hangs system Message-ID: <20030717202053.GA52407@melusine.cuivre.fr.eu.org> In-Reply-To: <20030717150759.GA811@atrbg11.informatik.tu-muenchen.de> References: <20030704094935.GA335@atrbg11.informatik.tu-muenchen.de> <20030704130345.GA348@atrbg11.informatik.tu-muenchen.de> <20030708184838.GB26342@melusine.cuivre.fr.eu.org> <20030715142556.GA380@atrbg11.informatik.tu-muenchen.de> <20030717150759.GA811@atrbg11.informatik.tu-muenchen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 2003-07-17, Daniel Lang écrivait :
> I found out, that the hangs do not appear (or way less likely),
> if the writing speed used is <= 12. But they seem to occur
> very likely if the (attempted) writing speed is like 48.
Hum, nasty, nasty. Looks like the amount of interrupts caused by
high-speed burning might trigger a race condition between two
instances of camisr(). camisr() does splcam(), but maybe this is not
sufficient to correctly prevent concurrent execution when interrupts
from the ATA driver occur. Maybe the freebsd-scsi people will have a
clearer idea of what is going on here.
Thomas.
--
Thomas.Quinot@Cuivre.FR.EU.ORG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030717202053.GA52407>