From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 27 10:20:03 2009 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A1C741065672 for ; Tue, 27 Jan 2009 10:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 905E78FC08 for ; Tue, 27 Jan 2009 10:20:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n0RAK3qv012592 for ; Tue, 27 Jan 2009 10:20:03 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n0RAK3st012591; Tue, 27 Jan 2009 10:20:03 GMT (envelope-from gnats) Date: Tue, 27 Jan 2009 10:20:03 GMT Message-Id: <200901271020.n0RAK3st012591@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Dominic Fandrey Cc: Subject: Re: kern/131032: hald causing panic in atapicam X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominic Fandrey List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Jan 2009 10:20:03 -0000 The following reply was made to PR kern/131032; it has been noted by GNATS. From: Dominic Fandrey To: Thomas Quinot Cc: bug-followup@FreeBSD.org Subject: Re: kern/131032: hald causing panic in atapicam Date: Tue, 27 Jan 2009 11:15:12 +0100 Thomas Quinot wrote: > * Dominic Fandrey, 2009-01-27 : > >>> Number: 131032 >>> Category: kern >>> Synopsis: hald causing panic in atapicam > > Can you clarify why you think this panic is related to ATAPI/CAM at all? > The backtrace you show does not give any indication that ATAPI/CAM is > involved, which is expected since you are using USB devices, not ATA. > > Thomas. > 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 As you said atapicam shouldn't be involved at all, so why is an atapicam funtion doing a giant-locked read?