From owner-freebsd-bugs  Fri Jul 31 01:57:03 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id BAA23594
          for freebsd-bugs-outgoing; Fri, 31 Jul 1998 01:57:03 -0700 (PDT)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23589;
          Fri, 31 Jul 1998 01:56:55 -0700 (PDT)
          (envelope-from phk@FreeBSD.org)
From: Poul-Henning Kamp <phk@FreeBSD.ORG>
Received: (from phk@localhost)
	by freefall.freebsd.org (8.8.8/8.8.5) id BAA06792;
	Fri, 31 Jul 1998 01:56:55 -0700 (PDT)
Date: Fri, 31 Jul 1998 01:56:55 -0700 (PDT)
Message-Id: <199807310856.BAA06792@freefall.freebsd.org>
To: SteveFriedrich@Hot-Shot.com, phk@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG
Subject: Re: kern/7431
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Synopsis: nca0(PAS16) can't mount -t cd9660 -r  /dev/cd0a /cdrom, previously worked

State-Changed-From-To: open-closed
State-Changed-By: phk
State-Changed-When: Fri Jul 31 01:52:53 PDT 1998
State-Changed-Why: 
Unfortunately we can't see from the above message what command failed,
only what the complaint was (that is a bit non-optimal for the case of
"ILLEGAL REQUEST" in particular), but if you poke around in the sys/scsi
source a bit I'm sure you can locate what causes this.  Since this is a CD,
you cannot hurt anything and if you boot -s and don't mount any of
your "real" filesystems, you don't even have to fsck if it panics.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message