>
> 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: <Intel PIIX4 ATA33 controller> 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 <BCD E520C> 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 -
--
[EMAIL PROTECTED] Work: (919) 676-0847
Get your mainframe programming tools at http://www.dignus.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
