Re: help needed debugging SCSI bus problem
* Igor Pokrovsky [EMAIL PROTECTED] [20031012 05:40]: On Sat, Oct 11, 2003 at 05:28:24PM +0200, Joan Picanyol wrote: This isn't that useful, unfortunately :( How do I setup my system to save the console messages? Since it freezes absolutely I have no way of accurate error reporting. You can always edit your /etc/syslog.conf to redirect console messages wherever you want. Also don't forget about /var/log/messages. Anything written to disk get's lost (I have to press the reset button). In fact I don't believe I could write anything to disk, since it looks like the SCSI bus freezes. tks -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help needed debugging SCSI bus problem
hi, i'm using 4.8-release[1] and experienced a similar problem last week using the same scsi-adapter[2] and the same drive[3]: my system froze during boottime just like yours. it stopped after detecting the dnes-309170w. i've successfully tested the controller, the cable and the termination with another scsi-drive[4]. desperate as i was i decided to low-level format the broken drive via the controllers buildin scsi-tools ... the drive got detected afterwards and is up and running since then. - worldi [1] %uname -srm FreeBSD 4.8-RELEASE-p13 i386 [2] ahc0: Adaptec 2940 Ultra2 SCSI adapter port 0xa800-0xa8ff mem 0xed001000-0xed001fff irq 11 at device 9.0 on pci0 [3] da0 at ahc0 bus 0 target 0 lun 0 da0: IBM DNES-309170W SAH0 Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 30, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) [4] da1 at ahc0 bus 0 target 1 lun 0 da1: IBM DDRS-39130W S97B Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (1785 512 byte sectors: 255H 63S/T C) -- Look what has become of your world... [not subscribed to -scsi, if OT for stable please keep me in Mail-Followup-To:] Hi, I can hang my system at will reading from my SCSI CD-RW. My hardware is(excerpt from dmesg): ahc0: Adaptec 2940 Ultra2 SCSI adapter port 0x1000-0x10ff mem 0xd002-0xd00 20fff irq 11 at device 14.0 on pci0 aic7890/91: Ultra2 Wide Channel A, SCSI Id=7, 32/253 SCBs [...] cd0 at ahc0 bus 0 target 2 lun 0 cd0: YAMAHA CRW2100S 1.0G Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 7) [...] da0 at ahc0 bus 0 target 0 lun 0 da0: SEAGATE ST318438LW 0003 Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 19001MB (38914049 512 byte sectors: 255H 63S/T 2422C)[...] da1 at ahc0 bus 0 target 6 lun 0 da1: IBM DNES-309170W SA30 Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) I can't paste the error messages, but I see a Dumping Card Ends. The first error is an SCB timeout (0x25) on 0:6:0 (the IBM drive). I also see other SCB timeout on 0:0:0 (the Seagate drive). I can break into the debugger, but that's not much use (I'm always on the keyboard interrupt handling routine) and I wouldn't know where to go from there anyway. Would a panic be helpful (I'd would be painful to setup but I would if needed)? Oh, I'm running -stable from last week: (12:26:50 ~) 0 $ uname -v FreeBSD 4.9-RC #1: Fri Oct 3 21:02:09 CEST 2003 [EMAIL PROTECTED]:/fs/ tmp/mount/tmp/build/obj/fs/bulk/mount/FreeBSD/src/sys/GRUMMITD I really don't know how to go on, any hints on what to do to help debugging or what the source of the problem might be are most welcomed. tks -- pica ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help needed debugging SCSI bus problem
Joan Picanyol [EMAIL PROTECTED] writes: ahc0: Adaptec 2940 Ultra2 SCSI adapter port 0x1000-0x10ff mem cd0: YAMAHA CRW2100S 1.0G Removable CD-ROM SCSI-2 device Nothing more needs to be said. I have bad experience with both Adaptec SCSI adaptors (1542CF, 2842VL and 2940UW Pro) and with YAMAHA CD-writers (CD-R 200T, CRW 4416S). I've never had issues with AMD-based Tekram DC-390. I've had minor issues with wide drive on narrow SYM53C875 configuration (see NetBSD PR kern/6849 for the full round-up -- and some FreeBSD versions, same problem) that seem to be solved in recent -STABLE versions. I do look after two Linux machines with a solid 2940UW setup (the adaptors are from 1998, one is driving a Fujitsu U320 10,025/min drive) though, so not all are bad. My Adaptec 2940UW Pro would lock up every other week. (I wonder if it would lock with Windows and who'd take the blame, but I'm digressing.) My Yamaha 200T would go faulty early, it can no longer write disks, but is fine reading. The Yamaha 4260S and 4416S had an awful firmware, Yamaha has never been able to deliver a robust firmware, there's always something that could lock the driver in a state that might block the whole bus. Don't mount these into servers. I wonder if the 2100S fares much better. I've now replaced the adaptor by a used Tekram DC-390F (15 EUR) and a new Plextor PX-W4824TA (hum, 119 EUR last winter). There are Plextor SCSI CD writers available (IIRC the fastest is the PX-W4012TS) if you want one, but they're around twice as expensive as their flagship ATAPI CD writer. I'm sure there are other good alternatives for either component (SCSI HA and CD writer), but I can only talk about those I know first-hand. -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: help needed debugging SCSI bus problem
On Sat, Oct 11, 2003 at 05:28:24PM +0200, Joan Picanyol wrote: * Doug White [EMAIL PROTECTED] [20031011 05:12]: On Fri, 10 Oct 2003, Joan Picanyol wrote: I can't paste the error messages, but I see a Dumping Card Ends. The first error is an SCB timeout (0x25) on 0:6:0 (the IBM drive). I also see other SCB timeout on 0:0:0 (the Seagate drive). This isn't that useful, unfortunately :( I know, but I though the subject was explicit enough. How do I setup my system to save the console messages? Since it freezes absolutely I have no way of accurate error reporting. You can always edit your /etc/syslog.conf to redirect console messages wherever you want. Also don't forget about /var/log/messages. -ip -- Ask not for whom the telephone bell tolls ... if thou art in the bathtub, it tolls for thee. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
