Date: Tue, 08 May 2001 12:53:45 +0000 From: lists@mediumgreen.com To: freebsd-scsi@freebsd.org Subject: Tekram DC-390U2W problems Message-ID: <20010508165428.5F09837B422@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
Hi. I've gone through and read the archives for the list from last year regarding the Tekram 390U2W, but am unclear exactly what the outcome was - it sounded like the sym driver was updated already. I'm seeing some problems on my machine with one of these cards - and occasional panics (which I'm not sure are related). Here are some recent messages logs: kumquat.hlcca.org: 34 > grep sym /var/log/messages May 2 17:30:09 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. May 2 17:30:09 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 3 12:36:04 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. May 3 12:36:06 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 3 15:19:38 kumquat /kernel: sym0:0: message d sent on bad reselection. May 3 15:20:38 kumquat /kernel: sym0:0:control msgout: 80 20 73 d. May 3 15:20:38 kumquat /kernel: sym0:0: message d sent on bad reselection. May 5 02:59:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 5 02:59:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 5 02:59:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 5 02:59:19 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 5 02:59:19 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 5 02:59:19 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): WRITE(10). CDB: 2a 0 0 d7 0 ef 0 0 10 0 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): ABORTED COMMAND asc:4e,0 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): Overlapped commands attempted field replaceable unit: 1 May 5 20:08:47 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 5 20:08:47 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 5 20:08:47 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 5 20:08:47 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 5 20:08:47 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 5 20:08:47 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 7 12:58:47 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 7 12:58:47 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 7 12:58:48 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 7 12:58:48 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 7 12:58:48 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 7 12:58:48 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 8 09:52:52 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 8 09:52:52 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 8 09:52:52 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 8 09:52:52 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 8 09:52:52 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 8 09:52:52 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 8 12:38:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 8 12:38:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 8 12:38:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 8 12:38:19 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 8 12:38:19 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 8 12:38:19 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 I'm worried about the errors from May 3 & 5. I'm kinda hoping that fixing this problem will also fix the problem of machine panic's. What can I do next to determine what the cause of those errors is? Thank you -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010508165428.5F09837B422>