Date: Wed, 24 Apr 2002 18:11:44 +0100 From: Jean-Mark Dupoux <jmdupoux@lineone.net> To: mikko@rsasecurity.com Cc: questions@freebsd.org Subject: Re: Advansys PCI SCSI Message-ID: <3CC6E750.1CBEEA6A@lineone.net>
next in thread | raw e-mail | index | archive | help
hello Mikko, I have several Advansys-based cards at home and im prettythe warning line is not "normal" - it never shows up in my boots, and in any case it looks as if it's affecting the potential transfer speed to your tape drive got a couple of general tips that might help you though, assuming cables etc are not the likely issue 1. If you have any doubts about the card, download the flash-rom file and installer from advansys's site - it means booting into DOS somehow, but the software is very intelligent in that it will detect the exact card model, the type of ROM chip (if it is really flashable), and the firmware version you currently have, as well as checking the flash file before you try to use it 2. if I ever have problems with a card and a particular combination of hardware, I've found one thing which usually gets things running is to make a settings change in the Advansys BIOS (press ctrl-A at the banner) - select SCSI configuration, go down to BIOS Target Control and change that to "disabled" for all the SCSI ID's except the card's own (The major drawback of doing this is if you're dual-booting and you needed to boot off a BIOS control drive attached to the card for the other OS, because with the option disabled it will be completely invisible until a driver gets loaded) jean-mark jmdupoux_@_lineone.net > 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 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?3CC6E750.1CBEEA6A>