Date: Tue, 27 Jan 2009 10:50:02 GMT From: Dominic Fandrey <kamikaze@bsdforen.de> To: freebsd-scsi@FreeBSD.org Subject: Re: kern/131032: hald causing panic in atapicam Message-ID: <200901271050.n0RAo2wf035690@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/131032; it has been noted by GNATS. From: Dominic Fandrey <kamikaze@bsdforen.de> To: Thomas Quinot <thomas@FreeBSD.ORG> Cc: bug-followup@FreeBSD.org, scottl@freebsd.org Subject: Re: kern/131032: hald causing panic in atapicam Date: Tue, 27 Jan 2009 11:31:49 +0100 Thomas Quinot wrote: > * Dominic Fandrey, 2009-01-27 : > >> It's that line. I don't think it's supposed to be there: >> at /usr/src/sys/modules/cam/../../cam/scsi/scsi_sg.c:798 > > This module is part of the generic CAM layer, which sits *above* the > various SCSI transport modules (e.g. ATAPI/CAM and umass). It is *not* > part of ATAPI/CAM, and it is fully expected that this generic code is > involved when using umass devices. > >> As you said atapicam shouldn't be involved at all, so why >> is an atapicam funtion doing a giant-locked read? > > This is *not* an ATAPI/CAM function. > > Thomas. > OK, so thanks for clarifying that. It doesn't get me rid of the panic, though. So I assume I should CC someone involved with SCSI. Regards
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200901271050.n0RAo2wf035690>