From owner-freebsd-stable Sat Jun 27 18:42:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03607 for freebsd-stable-outgoing; Sat, 27 Jun 1998 18:42:28 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from homer.supersex.com (homer.supersex.com [209.5.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03602; Sat, 27 Jun 1998 18:42:21 -0700 (PDT) (envelope-from leo@homer.supersex.com) Received: (from leo@localhost) by homer.supersex.com (8.8.8/8.8.5) id VAA13282; Sat, 27 Jun 1998 21:43:12 -0400 (EDT) Message-ID: <19980627214312.58671@supersex.com> Date: Sat, 27 Jun 1998 21:43:12 -0400 From: Leo Papandreou To: stable@FreeBSD.ORG Cc: stephan@FreeBSD.ORG Subject: NCR 875 and tagged queing. Broken? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 2.2-STABLE (cvsupped and built June 26) Twin channel NCR 875 adapter, Quantum Atlas III, FAILSAFE commented out in kernerl's configuration file. cp -RP dir1 dir2 (dir1 and dir2 on different partitions, same drive.) produces lots of these messages: Jun 26 17:42:47 abou /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Jun 26 17:42:48 abou /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f14a1800. I've seen recent reports of an identical problem. I'm not sure if its the hardware; the fact that these other reports are very recent makes me suspect the hard drive is not at fault. I wish I had a spare AHA around to test this suspicion but I do not. Also, although I realize older quantums cannot reliably do tagged queing, this is an 18.2 Gig Atlas III bought not 2 days ago. (Please let it not be the hardware.) This does not happen if the directories involved are small. This does not happen when FAILSAFE is present. The problem certainly has something to do with tagged queing as has already been pointed out in a previous msg. Without FAILSAFE, SCSI_NCR_DFLT_TAGS defaults to 4 but I've seen at least 1 msg on this list where someone had set SCSI_NCR_DFLT_TAGS=8. Can anyone confirm or deny that the problem is related to recent (Jun 2?) changes in the kernel? Jun 26 18:01:14 abou /kernel: FreeBSD 2.2.6-STABLE #0: Thu Jun 25 20:01:15 EDT 1998 Jun 26 18:01:14 abou /kernel: root@abou.adomainnamethatisharmfultochildren.com:/usr/src/sys/compile/ABOU Jun 26 18:01:14 abou /kernel: CPU: Pentium II (quarter-micron) (397.33-MHz 686-class CPU) Jun 26 18:01:14 abou /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 Jun 26 18:01:15 abou /kernel: Features=0x183fbff,,MMX,> Jun 26 18:01:15 abou /kernel: real memory = 134217728 (131072K bytes) Jun 26 18:01:15 abou /kernel: avail memory = 129908736 (126864K bytes) Jun 26 18:01:15 abou /kernel: Probing for devices on PCI bus 0: Jun 26 18:01:15 abou /kernel: chip0 rev 2 on pci0:0:0 Jun 26 18:01:15 abou /kernel: ncr0 rev 55 int a irq 5 on pci0:13:0 Jun 26 18:01:15 abou /kernel: ncr0 waiting for scsi devices to settle Jun 26 18:01:15 abou /kernel: (ncr0:6:0): "QUANTUM QM318000TD-SW N1B0" type 0 fixed SCSI 2 Jun 26 18:01:15 abou /kernel: sd0(ncr0:6:0): Direct-Access Jun 26 18:01:15 abou /kernel: sd0(ncr0:6:0): WIDE SCSI (16 bit) enabled Jun 26 18:01:15 abou /kernel: sd0(ncr0:6:0): 40.0 MB/s (50 ns, offset 16) Jun 26 18:01:15 abou /kernel: 17366MB (35566499 512 byte sectors) Jun 26 18:01:15 abou /kernel: ncr1 rev 55 int b irq 11 on pci0:13:1 Jun 26 18:01:15 abou /kernel: ncr1 waiting for scsi devices to settle Jun 26 18:01:15 abou /kernel: fxp0 rev 5 int a irq 11 on pci0:15:0 Jun 26 18:01:15 abou /kernel: fxp0: Ethernet address 00:a0:c9:ac:23:35 Jun 26 18:01:15 abou /kernel: chip1 rev 2 on pci0:18:0 Jun 26 18:01:15 abou /kernel: chip2 rev 1 on pci0:18:1 Jun 26 18:01:15 abou /kernel: chip3 rev 1 int d irq 11 on pci0:18:2 Jun 26 18:01:15 abou /kernel: chip4 rev 2 on pci0:18:3 Jun 26 18:01:15 abou /kernel: vga0 rev 35 on pci0:20:0 Jun 26 18:01:15 abou /kernel: Probing for devices on the ISA bus: Jun 26 18:01:15 abou /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Jun 26 18:01:15 abou /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Jun 26 18:01:15 abou /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Jun 26 18:01:15 abou /kernel: fdc0: FIFO enabled, 8 bytes threshold Jun 26 18:01:15 abou /kernel: fd0: 1.44MB 3.5in Jun 26 18:01:15 abou /kernel: npx0 flags 0x1 on motherboard Jun 26 18:01:15 abou /kernel: npx0: INT 16 interface Jun 26 18:01:15 abou /kernel: changing root device to sd0s1a Jun 26 18:01:25 abou login: ROOT LOGIN (root) ON ttyv0 Jun 26 18:08:43 abou /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Jun 26 18:08:44 abou /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f14a5c00. Jun 26 18:08:44 abou /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Jun 26 18:08:44 abou /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f14a5c00. Jun 26 18:08:44 abou /kernel: sd0(ncr0:6:0): COMMAND FAILED (4 28) @f14a1400. Jun 26 18:08:44 abou /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 Jun 26 18:08:44 abou /kernel: assertion "cp" failed: file "../../pci/ncr.c", line 6191 [ ... lots more of same ... ] Jun 26 18:21:44 abou reboot: rebooted by root Jun 26 18:21:44 abou syslogd: exiting on signal 15 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message