Date: Fri, 15 Mar 1996 20:10:32 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: tricotek!henry@uunet.uu.net (Henry Hojnacki) Cc: questions@freebsd.org Subject: Re: NCR 53C810 problems Message-ID: <199603151910.AA10642@Sisyphos> In-Reply-To: tricotek!henry@uunet.uu.net (Henry Hojnacki) "NCR 53C810 problems" (Mar 14, 14:58)
next in thread | raw e-mail | index | archive | help
On Mar 14, 14:58, Henry Hojnacki wrote: } Subject: NCR 53C810 problems } Greetings! Hi! } It seems I have a problem booting up. Also about 50% of the time, the boot } procedure fails, with the error message: } } NCR RESET: COMMAND FAILED . . . Please give the exact message text. } If I reset the machine, (hard reset) It sometimes works, and sometimes not, } again about 50% of the time. I have a 100MHz Pentium, and am running a SCSI } only system, no IDE drives aside from the floppy. My question is, do I have } a problem with my SCSI adapter, or is this a software issue? I want to be as } smart as I can before I go back to my vendor. Also I want to avoid all the } hardware and software people standing in a circle and pointing to the right.:-) } } Specific areas that I do not understand are as follows: } (refer to the below listing for line numbers) } } In line 27 from the boot procedure, what does it mean "not supported"? There is no driver for a PCI device. But none is required, since the chip is part of the CPU chip set, and all initialization has been done by the BIOS ... } In line 28, what is the meaning of "not bound"? Well, first it tells that you are running an obsolete version of FreeBSD :) You did not assign an IRQ to the slot the NCR card resides in, and it is used in a polled mode, which significantly reduces disk throughput ... } In line 30, how can I map the interrupt? Depends on your BIOS. Most have a PCI setup screen, where you can choose an IRQ for each PCI slot. } In line 46, what is the meaning of this, it happens on every boot? The driver tries to negotiate sync. SCSI transfers, and the CDROM replies in a way that had not been expected. } As verified by the listing, I am running v2.0, from the Walnut Creek CDROM. } I have obtained 2.0.5 from Walnut Creek, however the install procedure locks } up. I am sure it is related to this issue, since if I remove the SCSI adapter, } the install procedure does not lock up. Of course having no SCSI adapter means } having no SCSI disks, and the install procedure is somewhat silly then. :-) Well, 2.1R is out, and a 2.2-SNAP has been announced. Best if you tried a more recent version than 2.0.5 ... } Below is some output from the ncrcontrol command, it may be of some use to you. } ---------------- } [/users/henry/temp] 124) ncrcontrol -i -v -dcdhmn } T:L Vendor Device Rev Speed Max Wide Tags } 0:0 FUJITSU M1606S-512 6226 10.0 10.0 8 4 } 2:0 TANDBERG TDC 3800 =05: asyn 10.0 8 - } 3:0 NEC CD-ROM DRIVE:501 2.3 asyn 10.0 8 - There was nothing special, so I deleted the driver state information ... } below is the boot output listing: } 1} kernel: FreeBSD 2.0-RELEASE #0: Sat Oct 28 16:05:09 EDT 1995 } 2} kernel: root@teknocat:/sys/compile/HEH } 3} kernel: CPU: Pentium (Pentium-class CPU) 99 MHz Id = 0x525 Origin = "GenuineIntel" } 4} kernel: real memory = 33161216 (8096 pages) } 5} kernel: avail memory = 31113216 (7596 pages) } 26} kernel: pci0: scanning device 0..31, mechanism=1. } 27} kernel: pci0:0: INTEL CORPORATION, device=0x122d, class=bridge [not supported] } 28} kernel: ncr0 <ncr 53c810 scsi> int a (config) not bound on pci0:6 } 29} kernel: reg20: virtual=0xf507a000 physical=0xc0000000 } 30} kernel: pci_map_int failed: no int line set. } 31} kernel: interruptless mode: reduced performance. } 32} kernel: ncr0: restart (scsi reset). } 33} kernel: ncr0 scanning for targets 0..6 (1.12) } 34} kernel: ncr0 waiting for scsi devices to settle } 35} kernel: ncr0 targ 0 lun 0: type 0(direct) fixed SCSI2 } 36} kernel: ncr0 targ 0 lun 0: <FUJITSU M1606S-512 6226> } 37} kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } 38} kernel: sd0: 1041MB (2131992 total sec), 3457 cyl, 6 head, 102 sec, bytes/sec 512 } 39} kernel: ncr0 targ 2 lun 0: type 1(sequential) removable SCSI2 } 40} kernel: ncr0 targ 2 lun 0: <TANDBERG TDC 3800 =05:> } 41} kernel: st0(ncr0:2:0): asynchronous. } 42} kernel: st0(ncr0:2:0): asynchronous. } 43} kernel: st0: density code 0x0, drive empty } 44} kernel: ncr0 targ 3 lun 0: type 5(readonly) removable SCSI2 } 45} kernel: ncr0 targ 3 lun 0: <NEC CD-ROM DRIVE:5012.3 > } 46} kernel: assertion "cp == np->header.cp" failed: file "../../i386/pci/ncr.c", line 5171 } 47} kernel: cd0(ncr0:3:0): phase change 6-7 6@2523c0 resid=4. } 48} kernel: cd0(ncr0:3:0): asynchronous. } 49} kernel: cd0(ncr0:3:0): M_REJECT received (3:8). } 50} kernel: cd0: cd present.[285196 x 2048 byte records] } 51} kernel: pci0:7: INTEL CORPORATION, device=0x122e, class=bridge [not supported] } 52} kernel: graphics0 <display device> int a irq 10 on pci0:9 } 53} kernel: pci uses physical addresses from 0xc0000000 to 0xc0001000 } 54} lpd[66]: restarted Looks fine, except for the assertion failed resulting from the attempt to negotiate sync. transfers with the CDROM. Please give the 2.1R or 2.2-SNAP boot floppy a try, and tell me if you find there are still problems ... Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199603151910.AA10642>