From owner-freebsd-current Fri Jul 2 0:21:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 172CF14D19 for ; Fri, 2 Jul 1999 00:21:29 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id JAA71793; Fri, 2 Jul 1999 09:21:02 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199907020721.JAA71793@freebsd.dk> Subject: Re: Something weird happening w/ SMP -current In-Reply-To: <199907020654.XAA53043@apollo.backplane.com> from Matthew Dillon at "Jul 1, 1999 11:54:28 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Fri, 2 Jul 1999 09:21:02 +0200 (CEST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Matthew Dillon wrote: > > Here's some more info. If the dd is stuck and systat -vm 1 is showing > no interrupts occuring on, for example, ahc2 (irq17), and I then do > something that causes an interrupt to occur on mux (irq19), which I > guess is ahc1, ahc2 then starts working... until it gets stuck again, > that is. I can also get ahc2 going again by issuing another dd on ahc2. > > For example: > > dd if=/dev/rda1d bs=32k of=/dev/null > ... let this one run ... > ... it gets stuck ... > dd if=/dev/rda1d bs=32k of=/dev/null count=1 > ... this unsticks the first dd ... > ... the first dd runs again ... > ... the first dd gets stuck again ... > repeat... > > All I can think of is that something is causing the system to lose an > occassional interrupt. There's a race condition somewhere. Ahhh, I see this too, on an ATA only box that is, I loose my network from time to time, especially if there is lots of interrups on another source, it endeeed looks like we are loosing interrupts somewhere. Guess we have to study some of the latest changes more carefully and see went wrong, I'll try to experiment a bit with it.... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message