From nobody  Wed Jul 29 11:48:32 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id LAA29277;
          Wed, 29 Jul 1998 11:48:32 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199807291848.LAA29277@hub.freebsd.org>
Date: Wed, 29 Jul 1998 11:48:32 -0700 (PDT)
From: SteveFriedrich@Hot-Shot.com
To: freebsd-gnats-submit@freebsd.org
Subject: nca0(PAS16) can't mount -t cd9660 -r  /dev/cd0a /cdrom, previously worked
X-Send-Pr-Version: www-1.0

>Number:         7431
>Category:       kern
>Synopsis:       nca0(PAS16) can't mount -t cd9660 -r  /dev/cd0a /cdrom, previously worked
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Jul 29 11:50:00 PDT 1998
>Closed-Date:    Fri Jul 31 01:52:53 PDT 1998
>Last-Modified:  Fri Jul 31 01:56:55 PDT 1998
>Originator:     Steve Friedrich
>Release:        2.2.7-RELEASE #0
>Organization:
>Environment:
FreeBSD 486DX66.StevenFriedrich.org 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0: Wed Jul 29 11:09:00 EDT 1998     root@486DX66.StevenFriedrich.org:/usr/src/sys/compile/AMD486  i386
>Description:
I recently upgraded from FreeBSD 2.1.5 to 2.2.7 (I'm new to FreeBSD, but
I have a fairly extensive hardware background and some UNIX admin, etc.)

Just days ago, while running 2.1.5, I could mount the CD with:
mount -r -t cd9660 /dev/cd0a /cdrom

Under 2.2.7, I can't.  I get:
cd0(nca0:6:0): ILLEGAL REQUEST csi:30,20,0,0 asc:20,0 Invalid command operation code

And here's my dmesg:
avail memory = 14708736 (14364K bytes)
Probing for devices on the ISA bus:
vt0 at 0x60-0x6f irq 1 on motherboard
vt0: et4000, 80/132 col, color, 8 scr, mf2-kbd, [R3.20-b24]
sio0 at 0x3f8-0x3ff irq 4 on isa
sio0: type 16550A
sio1 at 0x2f8-0x2ff irq 3 on isa
sio1: type 16550A
sio2 at 0x3e8-0x3ef irq 11 on isa
sio2: type 16550A
sio3 at 0x2e8-0x2ef irq 12 on isa
sio3: type 16550A
lpt0 at 0x378-0x37f irq 7 on isa
lpt0: Interrupt-driven port
lp0: TCP/IP capable interface
fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa
fd0: 1.44MB 3.5in
fd1: 1.2MB 5.25in
wdc0 at 0x1f0-0x1f7 irq 14 on isa
wdc0: unit 0 (wd0): <WDC AC31000H>
wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S
wdc0: unit 1 (wd1): <WDC AC31200F>
wd1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S
wdc1 not found at 0x170
nca0 at 0x1f88-0x1f8b irq 9 on isa
nca0: type ProAudioSpectrum-16
nca0 waiting for scsi devices to settle
(nca0:6:0): "NEC CD-ROM DRIVE:84 1.0" type 5 removable SCSI 1
cd0(nca0:6:0): CD-ROM cd present [268501 x 2048 byte records]
1 3C5x9 board(s) on ISA found at 0x300
ep0 at 0x300-0x30f irq 10 on isa
ep0: aui/utp/bnc[*BNC*] address 00:a0:24:8f:cc:62
npx0 flags 0x1 on motherboard
npx0: INT 16 interface
cd0(nca0:6:0): ILLEGAL REQUEST csi:30,20,0,0 asc:20,0 Invalid command operation code

>How-To-Repeat:
After booting FreeBSD 2.2.7, mount the FreeBSD 2.1.5 CD 1 with:
mount -r -t cd9660 /dev/cd0a /cdrom

I just recently upgraded from 2.1.5 to 2.2.7.  This mount command
worked under 2.1.5 (just a few days ago). I don't know which release
actually broke it, or if it's caused by a new config requirement that
I'm unaware of.
>Fix:

>Release-Note:
>Audit-Trail:

From: "Steve Friedrich" <SteveFriedrich@Hot-Shot.com>
To: "freebsd-gnats-submit@freebsd.org" <freebsd-gnats-submit@freebsd.org>
Cc:  Subject: Re: kern/7431: nca0(PAS16) can't mount -t cd9660 -r  /dev/cd0a /cdrom, previously worked
Date: Thu, 30 Jul 1998 00:15:08 -0500

 Accept my apology... I assumed the CD didn't mount... in fact, in does.  If someone could analyze the error message and 
 ascertain if it is indicative of a deeper problem, I'd appreciate it.  At this point, it appears to be cosmetic... Viva la FreeBSD 
 (and you and me...)
 
 
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. 

>Unformatted:
