From owner-freebsd-current@FreeBSD.ORG Mon May 19 14:50:44 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A9A6C37B401 for ; Mon, 19 May 2003 14:50:44 -0700 (PDT) Received: from grogged.dyndns.org (c-66-41-94-114.mn.client2.attbi.com [66.41.94.114]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4C7543F75 for ; Mon, 19 May 2003 14:50:43 -0700 (PDT) (envelope-from matt@grogged.dyndns.org) Received: by grogged.dyndns.org (Postfix, from userid 1001) id 2FF4916809; Mon, 19 May 2003 16:40:55 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by grogged.dyndns.org (Postfix) with ESMTP id 229CBD23C for ; Mon, 19 May 2003 16:40:55 -0500 (CDT) Date: Mon, 19 May 2003 16:40:54 -0500 (CDT) From: matt In-Reply-To: <3EC93331.7090004@isi.edu> Message-ID: <20030519162334.A82936-100000@grogged.dyndns.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: Interrupt latency problems X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 May 2003 21:50:45 -0000 I hate to even bring this one up but I'm seeing the same symptoms on a k6/2 400, which isn't an SMP box, and doesn't have acpi enabled. The problem is more or less as described earlier, any intense disk access more or less makes X unbearably unresponsive (mouse updates ever 3 seconds or so, same for keystroke echos on xterms). Back under 4.7-R I can remember downloading files from this box over 100Mbps e-net and saturating the line, with X remaining very usable, now it's more like 5MB/s with a semi-frozen X display, so I'm pretty sure the machine has enough muscle to do what I'm asking of it. Took some patience but I grabbed some output from top -S while I was downloading a file over ftp from the k6/2 400, as seen below. Oh, I guess I should mention that as soon as I kill a file transfer X instantly returns back to its normal, usable self. Other relevant (and not so relevant) information below: # dmesg Copyright (c) 1992-2003 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 5.1-BETA #2: Wed May 14 22:15:33 GMT 2003 matt@hopelessposh.dyndns.org:/usr/src/sys/i386/compile/POSH Preloaded elf kernel "/boot/kernel/kernel" at 0xc04d8000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400910367 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 201326592 (192 MB) avail memory = 190259200 (181 MB) K6-family MTRR support enabled (2 registers) npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 Using $PIR table, 6 entries at 0xc00fdb30 pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xe0000000-0xe3ffffff at device 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe03f,0xdc00-0xdc03,0xd800-0xd807,0xd400-0xd403,0xd000-0xd007 mem 0xed100000-0xed11ff ff irq 15 at device 8.0 on pci0 ata2: at 0xd000 on atapci0 ata3: at 0xd800 on atapci0 fxp0: port 0xe400-0xe43f mem 0xed000000-0xed0fffff,0xed120000-0xed120fff irq 11 at device 9.0 on pci0 fxp0: Ethernet address 00:04:ac:d3:7c:bb miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xe800-0xe8ff mem 0xed121000-0xed121fff irq 10 at device 10.0 on pci0 aic7880: Ultra Single Channel A, SCSI Id=7, 16/253 SCBs atapci1: port 0xf000-0xf00f at device 15.0 on pci0 ata0: at 0x1f0 irq 14 on atapci1 ata1: simplex device, DMA on primary only ata1: at 0x170 irq 15 on atapci1 orm0: