From owner-freebsd-current@FreeBSD.ORG Fri Sep 12 21:10:34 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A8A3216A4BF for ; Fri, 12 Sep 2003 21:10:34 -0700 (PDT) Received: from remt28.cluster1.charter.net (remt28.cluster1.charter.net [209.225.8.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id B306E43F3F for ; Fri, 12 Sep 2003 21:10:33 -0700 (PDT) (envelope-from glennpj@charter.net) Received: from [24.158.214.251] (HELO gforce.johnson.home) by remt28.cluster1.charter.net (CommuniGate Pro SMTP 4.0.6) with ESMTP id 151384867; Sat, 13 Sep 2003 00:10:32 -0400 Received: from gforce.johnson.home (localhost [127.0.0.1]) by gforce.johnson.home (8.12.9/8.12.9) with ESMTP id h8D4AV1b043947; Fri, 12 Sep 2003 23:10:31 -0500 (CDT) (envelope-from glenn@gforce.johnson.home) Received: (from glenn@localhost) by gforce.johnson.home (8.12.9/8.12.9/Submit) id h8D4AUxs043830; Fri, 12 Sep 2003 23:10:30 -0500 (CDT) (envelope-from glenn) From: Glenn Johnson Date: Fri, 12 Sep 2003 23:10:30 -0500 To: Kevin Oberman Message-ID: <20030913041030.GA32168@gforce.johnson.home> Mail-Followup-To: Kevin Oberman , current@freebsd.org References: <20030912155722.E7CA05D04@ptavv.es.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030912155722.E7CA05D04@ptavv.es.net> User-Agent: Mutt/1.5.4i cc: current@freebsd.org Subject: Re: scsi_cd or atapicam crash in current. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Sep 2003 04:10:34 -0000 On Fri, Sep 12, 2003 at 08:57:22AM -0700, Kevin Oberman wrote: > I am seeing a peculiar, possibly timing sensitive, crash that looks > like if is probably in either atapicam or scsi_cd. The system is > CURRENT as of yesterday morning. > > The crash happens frequently when nautilus starts up. It does not > always crash, but does so fairly frequently and leaves my laptop > locked in X with no access to the console. If nautilus starts, the > system continues without problems until X is terminated and restarted. Check your cdrom entry in /etc/fstab. If you have an entry for /dev/cd0, try changing that to /dev/acd0, or whatever the appropriate ATAPI device is for your system. I was having the same problem you describe and that "fixed" it. -- Glenn Johnson glennpj@charter.net