From owner-freebsd-current Wed Dec 9 11:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19095 for freebsd-current-outgoing; Wed, 9 Dec 1998 11:49:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19090 for ; Wed, 9 Dec 1998 11:49:18 -0800 (PST) (envelope-from mike@sentex.net) Received: from marble.sentex.ca (marble.sentex.ca [199.212.134.2]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id OAA16436 for ; Wed, 9 Dec 1998 14:48:59 -0500 (EST) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by marble.sentex.ca (8.8.8/8.8.8) with SMTP id OAA03043 for ; Wed, 9 Dec 1998 14:48:58 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981209145124.00927bb0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 09 Dec 1998 14:51:24 -0500 To: current@FreeBSD.ORG From: Mike Tancsa Subject: Strange pausing problem with Current... Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have started to experiment with current these past few weeks and have run into a strange problem.... I am assuming its hardware related, but I can quite pin it down where or why. I have 2 machines, one a Dual PII 450 with 512M RAM FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 ahc0: rev 0x00 int a irq 18 on pci0.10.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs The other is a CPU: Pentium II (quarter-micron) (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 134217728 (131072K bytes) wdc0 at 0x1f0-0x1f7 irq 14 flags 0xff8004 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-4 wd0: 4104MB (8406720 sectors), 8896 cyls, 15 heads, 63 S/T, 512 B/S But I have also tried machine B with da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4149MB (8498506 512 byte sectors: 255H 63S/T 529C) Both are running FreeBSD current cvsup'd as of yesterday with sysctl -w vfs.ffs.doreallocblks=0 set. Now the problem... On machine B when there is some moderate disk acitivity, the machine gets quite sluggish and unresponsive. e.g. if I telnet to it, the login prompt takes quite a while to come up. Similarly, just typing 'w' from the prompt has about a 1 to 2 second delay. Machine A), although far more 'beefy' does not exhibt this behaviour, even in the middle of a make -j 32 world, or running a few copies of bonnie. Is it a hardware problem ? BIOS settings ? Any clues/suggestions as to what it may be ? Thanks, ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator (), noc@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message