Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Apr 2002 19:27:13 -0700 (PDT)
From:      Mikko Tyolajarvi <mikko@dynas.se>
To:        cyouse@geekbean.com
Cc:        questions@freebsd.org
Subject:   Re: Advansys PCI SCSI
Message-ID:  <200204240227.g3O2RDe32991@mikko.rsa.com>
References:  <20020423074401.I67361-100000@wind.geekbean.com>

next in thread | previous in thread | raw e-mail | index | archive | help
No solutions, just a bit of information:

In local.freebsd.questions you write:

>I've recently installed a PCI SCSI controller in my box solely for
>controlling an old HP T4 tape drive for some backups.  This is a stable
>box, last updated Apr 22 as you can see.

>The controller itself is not Advansys (it's some el-cheapo PCI controller)
>but the chipset is so I can only imagine it's a rebranded item:

I've got The Real Thing (solely for controlling an old scanner :)

>FreeBSD 4.5-STABLE #2: Mon Apr 22 16:11:42 EDT 2002

>adv0: <AdvanSys ASC3030/50 SCSI controller> port 0xe800-0xe8ff mem 0xec001000-0xec0010ff irq 10 at device 13.0 on pci0
>adv0: Warning EEPROM Checksum mismatch. Using default device parameters
>adv0: AdvanSys SCSI Host Adapter, SCSI ID 7, queue depth 16

>sa0 at adv0 bus 0 target 0 lun 0
>sa0: <HP T4000s 1.08> Removable Sequential Access SCSI-2 device
>sa0: 3.300MB/s transfers

>The problem that I'm having is that any accesses to the tape drive leave
>the process that initiated the I/O stuck in the D state (looking at top).
>So, a couple of questions:

>1. What's the EEPROM checksum mismatch about?  Anything to worry about?
>The controller seems to work properly (to a point) as it can probe the
>tape drive.  The driver source seems to indicate that it's not much of a
>problem (it just sets the defaults).

I get the same error:

atlas% dmesg | grep -i adv
adv0: <AdvanSys ASC3030/50 SCSI controller> port 0x1000-0x10ff mem 0xf0000000-0xf00000ff irq 11 at device 13.0 on pci0
adv0: Warning EEPROM Checksum mismatch. Using default device parameters
adv0: AdvanSys SCSI Host Adapter, SCSI ID 7, queue depth 16
pass0 at adv0 bus 0 target 1 lun 0

Scanner works.  No problems.

>2. Once a process has hung, how can I see where in the kernel it's
>hanging?  This might help me to track down the problem.

>3. Any ideas why this stuff doesn't work?  Has anyone seen this before?

You may have better luck on the -scsi list.

  $.02,
  /Mikko
-- 
 Mikko Työläjärvi_______________________________________mikko@rsasecurity.com
 RSA Security

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200204240227.g3O2RDe32991>