From owner-freebsd-current@FreeBSD.ORG Sat Nov 1 13:04:56 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 92E0616A4CE for ; Sat, 1 Nov 2003 13:04:56 -0800 (PST) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id E9AB243F75 for ; Sat, 1 Nov 2003 13:04:54 -0800 (PST) (envelope-from sos@spider.deepcore.dk) Received: from spider.deepcore.dk (localhost [127.0.0.1]) by spider.deepcore.dk (8.12.10/8.12.10) with ESMTP id hA1L5EVv024534; Sat, 1 Nov 2003 22:05:14 +0100 (CET) (envelope-from sos@spider.deepcore.dk) Received: (from sos@localhost) by spider.deepcore.dk (8.12.10/8.12.10/Submit) id hA1L5EvC024533; Sat, 1 Nov 2003 22:05:14 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200311012105.hA1L5EvC024533@spider.deepcore.dk> In-Reply-To: <20031101204827.GA8407@gosling.home.xbsd.net> To: Sven Esbjerg Date: Sat, 1 Nov 2003 22:05:14 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL99f (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 X-mail-scanned: by DeepCore Virus & Spam killer v1.3 cc: freebsd-current@FreeBSD.ORG Subject: Re: ata and mfs 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: Sat, 01 Nov 2003 21:04:56 -0000 It seems Sven Esbjerg wrote: > On my Fujitsu-Siemens S-4572 I get random hangs when doing recursive copying > to af mfs device. I suspect it has something to do with the fact the I still > get a lot of spurious interrupst on the ata controller. Those spurious interrupts are because ata1 share irq15 with USB. Most HW was not designed for this. If its a problem that they get printed dont bot verbose or comment out the prints in ata-lowlevel.c There is a problem in the kernel that makes the console lockup if there is too much printed too fast from inside the kernel.. -Søren