From owner-freebsd-current Sun Dec 12 23:36:17 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 7F21A14D50 for ; Sun, 12 Dec 1999 23:36:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA27323; Mon, 13 Dec 1999 08:35:53 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130735.IAA27323@freebsd.dk> Subject: Re: ATA problem In-Reply-To: <14418.33865.945738.983367@grasshopper.cs.duke.edu> from Andrew Gallatin at "Dec 11, 1999 12:15:59 pm" To: gallatin@cs.duke.edu (Andrew Gallatin) Date: Mon, 13 Dec 1999 08:35:53 +0100 (CET) Cc: gchil0@pop.uky.edu (Greg Childers), freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Andrew Gallatin wrote: > > Greg Childers writes: > > Hello, > > > > Seems now is the time to raise problems with ATA, so here goes. I have used the ATA driver > > since its introduction into -current without problem until recently. A kernel from October > > 5 worked fine. Now, it no longer works using ATA, but works fine using the old WD drivers. > > The console freezes after the dmesg and the keyboard is unresponsive. The ata info in > > I'm having similar problems, however mine are spurrious. They happen > maybe 1 in 15 or so reboots. I'm seeing them on two kinds of > machines, both alpha & i386. All the machines I'm seeing this on > have serial consoles, but since about 95% of the machines I take care > of do, they might not mean anything. I haven't seen it on a SCSI > machine, but I'm not sure if that means anything either, since nearly > all our machines boot from IDE disks. > > When they happen, the machine is unresponsive. It will ignore > attempts to break into ddb. I'd have tried to debug it already, but > its pretty damned hard to catch. Usually it only seems to happen when > I reboot a machine from home & cannot walk up & hit the reset button. > :-( Hmm, damn that I can reproduce that error here, I have a machine on constant reboot now, and hope to eventually catch this... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message