Date: Sat, 10 Feb 2001 09:18:14 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= <groudier@club-internet.fr> To: klh@alum.mit.edu Cc: Darren Joy <darrenj@uk.uu.net>, klh@panix.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Continuing Problems with DC390W and 4.2 Release Message-ID: <Pine.LNX.4.10.10102100824010.1037-100000@linux.local> In-Reply-To: <CMM.0.90.4.981784772.klh@panix2.panix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 10 Feb 2001, Ken Harrenstien wrote: > Hi, >=20 > Was searching through the archives to see if anyone else has had > problems similar to mine, and found yours. I was wondering if there > had been any further resolution since the last round of messages > circa 7-Jan-2001? >=20 > If not, perhaps my info will add some data for Gerard or others. >=20 > My story is that I just now began trying to move from 3.3 to 4.2 > (because only 4.x can understand large ATA drives, sigh) and ran into > some odd error messages that look like this: >=20 > =09sym0:0: message d sent on bad reselection. > =09sym0:0:control msgout: 80 20 35 d. As seen from the driver this is a SCSI protocol violation from the device. The device wanted to reselect for the tag 0x35 and the corresponding nexus= =20 didn't exist (as seen by the driver). > I have a Tekram DC390-U2W and this problem is happening with a Conner > CFP1080S (Conner again... hmmm). Tagged Queueing is enabled. It This hardware and and its firmware=3Dsoftware are probably no more supported. We know by experience that any software has still bugs even after years of maintainance. In my opinion, trying to make work something that is not supported/maintained is full time lost. I have had a CFP1080S years ago and was using it with 8 tags max on a=20 P90/24MB/NCR53C825 system. It worked reliably for me. Newer systems are a lot much faster and may trigger device bugs that didnt bite us with slower systems. Btw, I donnot use such antic drive anymore. This drive is probably wasting a lot your SCSI BUS bandwidth and nobody will give more than half an euro for it, in my opinion. > isn't frequent, but I haven't tried much yet. Happened once during > shutdown for a reboot (which wedged things and required a fsck after > resetting the CPU), again upon logging in after a night of running > idle. There are currently two other devices on the SCSI chain but > they should be completely unused (nothing is mounted from them). If you really like this drive, I would recommend you to disable tagged command queuing for it. Given the actual drive performance, this will not make significant difference and will avoid the offending bad reselection issue. > I would have used the NCR driver, except I couldn't figure out how to > coerce the new 4.2 /usr/sbin/config to accept the setting of > SCSI_NCR_DFLT_SYNC=3D6 which is required in order to use LVD drives at > full 80Mb/s speed. Grumble. Different topic. Was hoping SYM would work > without this fussing, but until I understand what's going on with "bad > reselection" I'm not going to put my LVD drives on this system. If you plan to keep with the Conner thing on your SCSI BUS, the BUS bandwidth wastage due to the Conner thing will be a significant penalty=20 for your system, in my opinion. > Here's the dmesg since it always seems to be asked for. Apologies if > it turns out to be unnecessary! I would recommend you the following: 1) Disable TCQ for the Conner (or disable the drive definitely as I did=20 years ago with mine :-) ) 2) In case of you still like a lot this drive, put it on the SE part=20 of the BUS (behind the LVD-SE converter). 3) Install your LVD drives on the LVD part of the SCSI BUS. Use any driver you want and send problem reports if any. Now some explanations and questions: > sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking Means that your 895 is operating in SE =3D Single Ended SCSI mode. > (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. This one should be harmless but it is strange, since the driver does=20 waits 100 ms to ensure SCSI BUS mode is stable after a reset. OTOH, the driver message that tells that the SCSI BUS has been reset is missing. You may have configured you BIOS for this RESET not to be performed at start up. If it is the case, could you please change this BIOS setting for the driver to reset the BUS prior to any IO. Are you playing with multi-initiator SCSI BUS ? Regards, G=E9rard. > --Ken > =09=09-------------- >=20 > ghost:~> dmesg > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD 4.2-RELEASE #0: Fri Feb 9 01:52:53 PST 2001 > klh@ghost:/usr/src/sys/compile/PCKLH-300 > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 300683344 Hz > CPU: Pentium II/Pentium II Xeon/Celeron (300.68-MHz 686-class CPU) > Origin =3D "GenuineIntel" Id =3D 0x660 Stepping =3D 0 > Features=3D0x183f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MC= A,CMOV,PAT,PSE36,MMX,FXSR> > real memory =3D 268419072 (262128K bytes) > avail memory =3D 257679360 (251640K bytes) > Preloaded elf kernel "kernel" at 0xc039f000. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: <math processor> on motherboard > npx0: INT 16 interface > pcib0: <Intel 82443BX (440 BX) host to PCI bridge> on motherboard > pci0: <PCI bus> on pcib0 > pcib1: <Intel 82443BX (440 BX) PCI-PCI (AGP) bridge> at device 1.0 on pci= 0 > pci1: <PCI bus> on pcib1 > isab0: <Intel 82371AB PCI to ISA bridge> at device 4.0 on pci0 > isa0: <ISA bus> on isab0 > atapci0: <Intel PIIX4 ATA33 controller> port 0xd800-0xd80f at device 4.1 = on pci0 > ata0: at 0x1f0 irq 14 on atapci0 > pci0: <Intel 82371AB/EB (PIIX4) USB controller> at 4.2 > chip1: <Intel 82371AB Power management controller> port 0xe800-0xe80f at = device 4.3 on pci0 > sym0: <895> port 0xd000-0xd0ff mem 0xe0800000-0xe0800fff,0xe1000000-0xe10= 000ff irq 11 at device 10.0 on pci0 > sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking > pci0: <Cirrus Logic GD5446 SVGA controller> at 12.0 > dc0: <82c169 PNIC 10/100BaseTX> port 0xb800-0xb8ff mem 0xe0000000-0xe0000= 0ff irq 10 at device 13.0 on pci0 > dc0: Ethernet address: 00:c0:f0:2d:89:bc > miibus0: <MII bus> on dc0 > ukphy0: <Generic IEEE 802.3u media interface> on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0 > atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0 > kbd0 at atkbd0 > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > psm0: model IntelliMouse, device ID 3 > vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: <System console> at flags 0x100 on isa0 > sc0: VGA <16 virtual consoles, flags=3D0x300> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 > ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode > ppc0: FIFO with 16/16/9 bytes threshold > plip0: <PLIP network interface> on ppbus0 > lpt0: <Printer> on ppbus0 > lpt0: Interrupt-driven port > ppi0: <Parallel I/O> on ppbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding en= abled, default to deny, logging limited to 1000 packets/entry by default > ad0: 43979MB <IBM-DTLA-307045> [89355/16/63] at ata0-master UDMA33 > Waiting 5 seconds for SCSI devices to settle > (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. > Mounting root from ufs:/dev/da0s1a > cd0 at sym0 bus 0 target 5 lun 0 > cd0: <TOSHIBA XM-4101TASUNSLCD 1084> Removable CD-ROM SCSI-2 device=20 > cd0: 4.237MB/s transfers (4.237MHz, offset 15) > cd0: cd present [1304908 x 512 byte records] > da0 at sym0 bus 0 target 0 lun 0 > da0: <CONNER CFP1080S 3939> Fixed Direct Access SCSI-2 device=20 > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 1030MB (2110812 512 byte sectors: 255H 63S/T 131C) > da1 at sym0 bus 0 target 1 lun 0 > da1: <IBM DORS32160SUN2.1G WA7A> Fixed Direct Access SCSI-2 device=20 > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing = Enabled > da1: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) > sym0:0: message d sent on bad reselection. > sym0:0:control msgout: 80 20 35 d. > ghost:~>=20 >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message >=20 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?Pine.LNX.4.10.10102100824010.1037-100000>