From owner-freebsd-stable Fri May 11 11:10:21 2001 Delivered-To: freebsd-stable@freebsd.org Received: from fjord.dignus.com (sdsl-66-80-58-206.dsl.lax.megapath.net [66.80.58.206]) by hub.freebsd.org (Postfix) with ESMTP id E703037B423 for ; Fri, 11 May 2001 11:10:13 -0700 (PDT) (envelope-from rivers@dignus.com) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by fjord.dignus.com (8.11.1/8.11.1) with ESMTP id f4BIAJf08841; Fri, 11 May 2001 14:10:19 -0400 (EDT) (envelope-from rivers@dignus.com) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id OAA11089; Fri, 11 May 2001 14:13:07 -0400 (EDT) Date: Fri, 11 May 2001 14:13:07 -0400 (EDT) From: Thomas David Rivers Message-Id: <200105111813.OAA11089@lakes.dignus.com> To: barney@tp.databus.com, eugen@grosbein.pp.ru Subject: Re: 4.3-STABLE panics while mounting CD-R Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <20010511135459.A24957@tp.databus.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is it an audio cd? I've experienced the instant panic when mistakenly > trying to mount such as a cd9660 fs. Of course it shouldn't panic, > but the workaround is not to do that. I get similar situations when mounting the 4.2-RELEASE 3rd CD for reading packages... This is with a 4.2-RELEASE system... From the boot messages: atapci0: port 0xd8 00-0xd80f at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 acd0: CDROM at ata1-master using PIO4 And here's an example: May 3 09:13:18 fjord /kernel: cd9660: RockRidge Extension May 3 09:14:02 fjord /kernel: acd0: READ_BIG - NO SENSE asc=00 ascq=00 error=00 May 3 09:14:12 fjord /kernel: acd0: READ_BIG - NO SENSE asc=00 ascq=00 error=00 May 3 09:15:00 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:15:00 fjord /kernel: ata1: resetting devices .. done May 3 09:15:30 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:15:30 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:15:30 fjord /kernel: done May 3 09:15:56 fjord su: rivers to root on /dev/ttyp1 May 3 09:16:00 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:16:00 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:16:00 fjord /kernel: done May 3 09:16:30 fjord /kernel: acd0: READ_BIG command timeout - resetting May 3 09:16:30 fjord /kernel: ata1: resetting devices .. ata1-master: timeout w aiting for command=ef s=00 e=50 May 3 09:16:30 fjord /kernel: done At which point the cdrom was hung and a reboot was needed... I can reproduce this when I NFS mount the CDROM with the 4.2-RELEASE Disk #2 in the drive. - Dave Rivers - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe programming tools at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message