Re: Adaptec AHD U320 operating as only U160

On Feb 17, 2008 3:36 PM, Justin T. Gibbs <gibbs@xxxxxxxxxxx> wrote:
Niki Denev wrote:

With aic79xx_osm.c 1.30 all of my U320 drives are detected as such. Thanks!
I'm only wondering why with the latest version
"cpi->transport_version" is set to 2, and
then set to 4 on the next line? Probably you left it there for readability?

It was an oversight. It seems that this section of code came from the
aic7xxx driver where, depending on controller model, the protocol version
must be reported differently. I missed some of the duplication when trying
to remove it in my last checkin. :-( Should be fixed now.

Nope, no SES enclosure, just plain 68pin scsi drives.
I have now put version 1.30 of aic79xx_osm.c on two machines,
One of them is running the Dtrace snapshot of 8.0-current
with dual channel PCI-X Adaptec U320 controller (on a plain
32bit/33mhz pci slot) :

ahd0@pci0:4:1:0: class=0x010000 card=0x00429005 chip=0x80129005

The error only occurs on rev B. controllers (0x10 reported in the PCI
revision register). The machine not reporting the error has an A4
part.

Then there are several messages like this one too :
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0

Invalid command opcode. CAM will usually report the command that failed.
You don't see any other output?

--
Justin



Sorry, I must have missed the full output :

Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass0:ahd0:0:0:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 ec 0
(pass0:ahd0:0:0:0): CAM Status: SCSI Status Error
(pass0:ahd0:0:0:0): SCSI Status: Check Condition
(pass0:ahd0:0:0:0): ILLEGAL REQUEST asc:20,0
(pass0:ahd0:0:0:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass0:ahd0:0:0:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 a1 0
(pass0:ahd0:0:0:0): CAM Status: SCSI Status Error
(pass0:ahd0:0:0:0): SCSI Status: Check Condition
(pass0:ahd0:0:0:0): ILLEGAL REQUEST asc:20,0
(pass0:ahd0:0:0:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass1:ahd0:0:1:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 ec 0
(pass1:ahd0:0:1:0): CAM Status: SCSI Status Error
(pass1:ahd0:0:1:0): SCSI Status: Check Condition
(pass1:ahd0:0:1:0): ILLEGAL REQUEST asc:20,0
(pass1:ahd0:0:1:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass1:ahd0:0:1:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 a1 0
(pass1:ahd0:0:1:0): CAM Status: SCSI Status Error
(pass1:ahd0:0:1:0): SCSI Status: Check Condition
(pass1:ahd0:0:1:0): ILLEGAL REQUEST asc:20,0
(pass1:ahd0:0:1:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass2:ahd0:0:2:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 ec 0
(pass2:ahd0:0:2:0): CAM Status: SCSI Status Error
(pass2:ahd0:0:2:0): SCSI Status: Check Condition
(pass2:ahd0:0:2:0): ILLEGAL REQUEST asc:20,0
(pass2:ahd0:0:2:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass2:ahd0:0:2:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 a1 0
(pass2:ahd0:0:2:0): CAM Status: SCSI Status Error
(pass2:ahd0:0:2:0): SCSI Status: Check Condition
(pass2:ahd0:0:2:0): ILLEGAL REQUEST asc:20,0
(pass2:ahd0:0:2:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass3:ahd0:0:3:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 ec 0
(pass3:ahd0:0:3:0): CAM Status: SCSI Status Error
(pass3:ahd0:0:3:0): SCSI Status: Check Condition
(pass3:ahd0:0:3:0): ILLEGAL REQUEST asc:20,0
(pass3:ahd0:0:3:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid
Copied 18 bytes of sense data offset 12: 0x70 0x0 0x5 0x0 0x0 0x0 0x0
0xa 0x0 0x0 0x0 0x0 0x20 0x0 0x2 0xcf 0x0 0x0
(pass3:ahd0:0:3:0): Vendor Specific Command. CDB: 85 8 e 0 0 0 1 0 0 0
0 0 0 0 a1 0
(pass3:ahd0:0:3:0): CAM Status: SCSI Status Error
(pass3:ahd0:0:3:0): SCSI Status: Check Condition
(pass3:ahd0:0:3:0): ILLEGAL REQUEST asc:20,0
(pass3:ahd0:0:3:0): Invalid command operation code field replaceable
unit: 2: Command byte 0 bit 7 is invalid


This is printed right after smartd (from smartmontools) is started,
and I think it's what it causes these messages.
I guess they are harmless too?

--Niki
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • [opensuse] k3b unable to burn Boot DVDs: SUSE10.2 x86_64
    ... Can some one help me with this or suggest a command line way to do it ... QGDict::hashKeyString: Invalid null key ... klauncher said: Unknown protocol ''. ... growisofs: 6.1 ...
    (SuSE)
  • Re: Steven L Umbanch.
    ... > Semicolon wont even let me complete command successfully. ... > gives error and says invalid date specified. ... > able to log in at 5:05 on system clock. ...
    (microsoft.public.win2000.group_policy)
  • Re: New Mainframe Blog Site -- mainframeblogger.com
    ... Have you followed the instructions for "first time" use of WSA - as documented ... get me COMMAND FILEXFER NOT FOUND. ... INVALID DATA SET NAME, C::dload:fred.txt ...
    (comp.lang.cobol)
  • Nope Jerry net user /times
    ... Semicolon wont even let me complete command successfully. ... gives error and says invalid date specified. ... net user user /times:monday-sunday;8am-5pm ...
    (microsoft.public.win2000.group_policy)
  • Re: ndd on x86
    ... >etc. by sparc architekture. ... >i try to use this command on a x86 machine but will not work. ... >operation failed: Invalid argument ...
    (comp.unix.solaris)