Re: Adaptec AHD U320 operating as only U160 (was: Crash when issueing shutdown -r now)

From: Gelsema, P \(Patrick\) <"Gelsema,>
Date: Mon, 11 Feb 2008 22:55:34 +0100 (CET)
On Mon, February 11, 2008 19:44, David O'Brien wrote:
> On Thu, Apr 19, 2007 at 02:13:46PM +0200, Gelsema, P (Patrick) wrote:
>> I do have an Adaptec SCSI Controller, and yes I use it. I boot from it.
>>
>> ahd0: <Adaptec 39320D Ultra320 SCSI adapter> port
>> 0xe800-0xe8ff,0xe400-0xe4ff mem 0xdd7fe000-0xdd7fffff irq 16 at devuce
>> 10.0 on pci1
>>
>> da0 at ahd0 bus 0 target 4 lun 0
>> da0: <SEAGATE ST336753LW HPS2> Fixed Direct Access SCSI-3 device
>> da0: 160.000MB/s transfers (80.000MHz DT, offset 63, 16 bit)
>> da0: Command Queueing Enabled
>> da0: 34732MB (71132960 512 byte sectors: 255H 63S/T 4427C)
>>
>> Please note that the transferspeed is 160.00MB/s. In Freebsd 6.2 it's
>> recognised as 320MB.
>
> Gelsema & Joćo,
>
> Do you still have your U320 disks running as U160 disks with an Adaptec
> U320 controller in 7.0 or 8-CURRENT?  I also have this problem and I've
> traced it down to the CAM "NEW TRAN" code.
>     ----------------------------
>     revision 1.166
>     date: 2006/11/02 00:54:33;  author: mjacob;  state: Exp;  lines: +0
> -333
>     2nd and final commit that moves us to CAM_NEW_TRAN_CODE as the
> default.
>     ----------------------------
>
> Given that we're not seeing tons of reports of this issue, I wonder if
> its related to either revision of the ASIC or firmware.  For comparison
> here is my information from a verbose boot.
>
> ahd0: <Adaptec 39320 Ultra320 SCSI adapter> port
> 0xb000-0xb0ff,0xa800-0xa8ff mem 0xfa8f8000-0xfa8f9fff irq 29 at device 6.0
> on pci4
> ahd0: Defaulting to MEMIO on
> ahd0: Reserved 0x2000 bytes for rid 0x14 type 3 at 0xfa8f8000
> ahd0: Reading VPD from SEEPROM...ahd0: VPD parsing successful
> ahd0: Reading SEEPROM...done.
> ahd0: STPWLEVEL is on
> ahd0: Manual Secondary Termination
> ahd0: Primary High byte termination Enabled
> ahd0: Primary Low byte termination Enabled
> ahd0: Secondary High byte termination Disabled
> ahd0: Secondary Low byte termination Disabled
> ahd0: Downloading Sequencer Program... 752 instructions downloaded
> ahd0: Features 0x101, Bugs 0x8ffe3f, Flags 0x43f1
> ahd0: [MPSAFE]
> ahd0: [ITHREAD]
> aic7902: Ultra320 Wide Channel A, SCSI Id=7, PCI 33 or 66Mhz, 512 SCBs

Hi David,

I am still running at 160MB/s in 7.0-RC2.

hulk# camcontrol inquiry da1
pass1: <SEAGATE ST336753LW HPS3> Fixed Direct Access SCSI-3 device
pass1: Serial Number 3HX35KPH000075191ZRW
pass1: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Command
Queueing Enabled

pciconf -lv shows

ahd0_at_pci0:1:10:0:       class=0x010000 card=0x00419005 chip=0x80119005
rev=0x03 hdr=0x00
    vendor     = 'Adaptec Inc'
    device     = 'ASC-39320D Ultra320 SCSI Controller'
    class      = mass storage
    subclass   = SCSI
ahd1_at_pci0:1:10:1:       class=0x010000 card=0x00419005 chip=0x80119005
rev=0x03 hdr=0x00
    vendor     = 'Adaptec Inc'
    device     = 'ASC-39320D Ultra320 SCSI Controller'
    class      = mass storage
    subclass   = SCSI

See below some results from a verbose boot. It's from last July but still
the same box/hardware. If you require a more fresh verbose boot I will be
able to supply tomorrow evening.

Jul 13 21:47:48 hulk kernel: ahd0: <Adaptec 39320D Ultra320 SCSI adapter>
port 0xe800-0xe8ff,0xe400-0xe4ff mem 0xdd5fe000-0xdd5fffff irq 17 at
device 10.0 on pci1
Jul 13 21:47:48 hulk kernel: ahd0: Defaulting to MEMIO on
Jul 13 21:47:48 hulk kernel: ahd0: Reserved 0x2000 bytes for rid 0x14 type
3 at 0xdd5fe000
Jul 13 21:47:48 hulk kernel: ahd0: Enabling 39Bit Addressing
Jul 13 21:47:48 hulk kernel: ahd0: Reading VPD from SEEPROM...ahd0: VPD
parsing successful
Jul 13 21:47:48 hulk kernel: ahd0: Reading SEEPROM...done.
Jul 13 21:47:48 hulk kernel: ahd0: STPWLEVEL is on
Jul 13 21:47:48 hulk kernel: ahd0: Manual Primary Termination
Jul 13 21:47:48 hulk kernel: ahd0: Manual Secondary Termination
Jul 13 21:47:48 hulk kernel: ahd0: Primary High byte termination Enabled
Jul 13 21:47:48 hulk kernel: ahd0: Primary Low byte termination Enabled
Jul 13 21:47:48 hulk kernel: ahd0: Secondary High byte termination Disabled
Jul 13 21:47:48 hulk kernel: ahd0: Secondary Low byte termination Disabled
Jul 13 21:47:48 hulk kernel: ahd0: Downloading Sequencer Program... 753
instructions downloaded
Jul 13 21:47:48 hulk kernel: ahd0: Features 0x101, Bugs 0x8ffe3f, Flags
0x143f1
Jul 13 21:47:48 hulk kernel: ioapic0: routing intpin 17 (PCI IRQ 17) to
vector 52
Jul 13 21:47:48 hulk kernel: ahd0: [MPSAFE]
Jul 13 21:47:48 hulk kernel: ahd0: [ITHREAD]
Jul 13 21:47:48 hulk kernel: aic7902: Ultra320 Wide Channel A, SCSI Id=7,
PCI 33 or 66Mhz, 512 SCBs
Jul 13 21:47:48 hulk kernel: ahd1: <Adaptec 39320D Ultra320 SCSI adapter>
port 0xe000-0xe0ff,0xd800-0xd8ff mem 0xdd5fc000-0xdd5fdfff irq 18 at
device 10.1 on pci1
Jul 13 21:47:48 hulk kernel: ahd1: Defaulting to MEMIO on
Jul 13 21:47:48 hulk kernel: ahd1: Reserved 0x2000 bytes for rid 0x14 type
3 at 0xdd5fc000
Jul 13 21:47:48 hulk kernel: ahd1: Enabling 39Bit Addressing
Jul 13 21:47:48 hulk kernel: ahd1: Reading VPD from SEEPROM...ahd1: VPD
parsing successful
Jul 13 21:47:48 hulk kernel: ahd1: Reading SEEPROM...done.
Jul 13 21:47:48 hulk kernel: ahd1: STPWLEVEL is on
Jul 13 21:47:48 hulk kernel: ahd1: Manual Secondary Termination
Jul 13 21:47:48 hulk kernel: ahd1: Primary High byte termination Enabled
Jul 13 21:47:48 hulk kernel: ahd1: Primary Low byte termination Enabled
Jul 13 21:47:48 hulk kernel: ahd1: Secondary High byte termination Disabled
Jul 13 21:47:48 hulk kernel: ahd1: Secondary Low byte termination Disabled
Jul 13 21:47:48 hulk kernel: ahd1: Downloading Sequencer Program... 753
instructions downloaded
Jul 13 21:47:48 hulk kernel: ahd1: Features 0x101, Bugs 0x8ffe3f, Flags
0x143f0
Jul 13 21:47:48 hulk kernel: ioapic0: routing intpin 18 (PCI IRQ 18) to
vector 53
Jul 13 21:47:48 hulk kernel: ahd1: [MPSAFE]
Jul 13 21:47:48 hulk kernel: ahd1: [ITHREAD]

If you require more info just let me know. Glad to provide.

Rgds,

Patrick

>
> --
> -- David  (obrien_at_FreeBSD.org)
> Q: Because it reverses the logical flow of conversation.
> A: Why is top-posting (putting a reply at the top of the message) frowned
> upon?
> Let's not play "Jeopardy-style quoting"
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
Received on Mon Feb 11 2008 - 20:56:03 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:27 UTC