[2518] in linux-scsi channel archive

home help back first fref pref prev next nref lref last post

New MB breaks fdomain module?

daemon@ATHENA.MIT.EDU (Judah Milgram)
Mon Sep 22 17:29:21 1997

From: Judah Milgram <milgram@eng.umd.edu>
Date: 	Mon, 22 Sep 1997 15:50:56 -0400 (EDT)
To: linux-scsi@vger.rutgers.edu

Hi,

Am  baffled by a problem I've been having with the fdomain module after
a motherboard/CPU upgrade. Would be grateful if anyone could  point me
in the right direction.

A description of the problem is below.

thanks for any tips,

Judah Milgram
milgram@eng.umd.edu

----------------------------------------------------------------
Summary: upgraded MB/CPU, fdomain module broke (?).

Old System: DX2/66 ISA MB running kernel 2.0.29 w/ fdomain as module
            Future Domain TMC-1680 ISA card, 0x140/IRQ11
            Wangdat 3100 DAT tape drive, SCSI-2 on internal connector
            HP Scanjet 4p scanner on external mini-50 pin connector
            scanner worked,  tape worked.
New System: AMD K6-233 on Epox P55-TX (Intel TX chipset)
            same old system - didn't reinstall.
            Kernel 2.0.29, recompiled for Pentium
            Future Domain, Wangdat, HP as above.
            Now, the Future Domain BIOS finds both Wangdat and Scanner
            on boot, but when I try to modprobe fdomain, I get sense
            errors and timeouts. See below for actual messages. Seems
            to be related to Wangdat; scanner still functional.

Already tried: kernel 2.1.56, same result
               different SCSI cable
               reserving F-Domain's memory in the MB BIOS
               removed all other cards (except video)
               disconnected scanner, no change
               disconnected scanner and tape - fdomain loads w/o error!
               disconnected tape, left scanner on - loads w/o error!
               verified IRQ11 available to "legacy" ISA card 
               booted with tape in drive   no change
               booted DOS, can use tape backup utility, ergo probably not
                 broken tape drive or cable.

Here's the actual error messages: (written to syslog)

After modprobe'ing fdomain:
Sep 22 15:42:06 localhost kernel: scsi2 <fdomain>: BIOS version 3.5 at 0xca000 using scsi id 7
Sep 22 15:42:06 localhost kernel: scsi2 <fdomain>: TMC-18C30 chip at 0x140 irq 11
Sep 22 15:42:06 localhost kernel: scsi2 : Future Domain TMC-16x0 SCSI driver, version 5.44
Sep 22 15:42:06 localhost kernel: scsi : 1 host.
Sep 22 15:42:07 localhost kernel: scsi2 : channel 0 target 0 lun 0 request sense failed, performing reset.
Sep 22 15:42:07 localhost kernel: SCSI bus is being reset for host 2 channel 0.
Sep 22 15:42:07 localhost kernel: fdomain: SCSI Bus Reset
Sep 22 15:42:07 localhost kernel: Future Domain TMC-16x0 SCSI driver, version 5.44
Sep 22 15:42:07 localhost kernel: scsi2 <fdomain>: BIOS version 3.5 at 0xca000 using scsi id 7
Sep 22 15:42:07 localhost kernel: scsi2 <fdomain>: TMC-18C30 chip at 0x140 irq 11
Sep 22 15:42:07 localhost kernel: other (8), target = 0 cmnd = 0x03 pieces = 0 size = 16
Sep 22 15:42:07 localhost kernel: sent_command = 12, have_data_in = 0, timeout = 50
Sep 22 15:42:07 localhost kernel: in_interrupt_flag = 1
Sep 22 15:42:07 localhost kernel: IMR = 0x0840 (masked), IRR = 0x0800, ISR = 0x0000
Sep 22 15:42:07 localhost kernel: SCSI Status      = 0x00
Sep 22 15:42:07 localhost kernel: TMC Status       = 0x40 (interrupt)
Sep 22 15:42:07 localhost kernel: Interrupt Status = 0x00
Sep 22 15:42:07 localhost kernel: FIFO Status      = 0x08
Sep 22 15:42:07 localhost kernel: Int. Condition   = 0x00
Sep 22 15:42:07 localhost kernel: Configuration 1  = 0x86
Sep 22 15:42:07 localhost kernel: Configuration 2  = 0x07
Sep 22 15:42:09 localhost kernel:   Vendor: WangDAT   Model: Model 3100        Rev: 03.0
Sep 22 15:42:09 localhost kernel:   Type:   Sequential-Access                  ANSI SCSI revision: 02
Sep 22 15:42:11 localhost kernel:   Vendor: HP        Model: C1130A            Rev: 3540
Sep 22 15:42:11 localhost kernel:   Type:   Processor                          ANSI SCSI revision: 02


"modprobe st" results in:   (in /var/log/messages)

Sep 22 15:43:58 localhost kernel: Detected scsi tape st0 at scsi2, channel 0, id 0, lun 0

Then, after (for example) mt-st -f /dev/st0 status

tcraft:ROOT:~$ mt-st -f /dev/st0 status
/dev/st0: I/O error

and in the syslog:

Sep 22 15:45:56 localhost kernel: scsi2 : channel 0 target 0 lun 0 request sense failed, performing reset.
Sep 22 15:45:56 localhost kernel: SCSI bus is being reset for host 2 channel 0.
Sep 22 15:45:56 localhost kernel: fdomain: SCSI Bus Reset
Sep 22 15:45:56 localhost kernel: Future Domain TMC-16x0 SCSI driver, version 5.44
Sep 22 15:45:56 localhost kernel: scsi2 <fdomain>: BIOS version 3.5 at 0xca000 using scsi id 7
Sep 22 15:45:56 localhost kernel: scsi2 <fdomain>: TMC-18C30 chip at 0x140 irq 11
Sep 22 15:45:56 localhost kernel: other (8), target = 0 cmnd = 0x03 pieces = 0 size = 16
Sep 22 15:45:56 localhost kernel: sent_command = 12, have_data_in = 0, timeout = 50
Sep 22 15:45:56 localhost kernel: in_interrupt_flag = 1
Sep 22 15:45:56 localhost kernel: IMR = 0x0840 (masked), IRR = 0x0800, ISR = 0x0000
Sep 22 15:45:56 localhost kernel: SCSI Status      = 0x00
Sep 22 15:45:56 localhost kernel: TMC Status       = 0x40 (interrupt)
Sep 22 15:45:56 localhost kernel: Interrupt Status = 0x00
Sep 22 15:45:56 localhost kernel: FIFO Status      = 0x08
Sep 22 15:45:56 localhost kernel: Int. Condition   = 0x00
Sep 22 15:45:56 localhost kernel: Configuration 1  = 0x86
Sep 22 15:45:56 localhost kernel: Configuration 2  = 0x07
Sep 22 15:45:57 localhost kernel: st0: Error with sense data: extra data not valid Current error st09:00: sense key Unit Attention
Sep 22 15:45:57 localhost kernel: Additional sense indicates Power on, reset, or bus device reset occurred


[end]


home help back first fref pref prev next nref lref last post