From owner-freebsd-stable Mon Jul 30 12:28:19 2001 Delivered-To: freebsd-stable@freebsd.org Received: from saturn.bsdhome.com (unknown [24.25.2.193]) by hub.freebsd.org (Postfix) with ESMTP id 1901637B403 for ; Mon, 30 Jul 2001 12:28:05 -0700 (PDT) (envelope-from bsd@bsdhome.com) Received: from neutrino.bsdhome.com (jupiter [192.168.220.13]) by saturn.bsdhome.com (8.11.4/8.11.4) with ESMTP id f6UJRwq15505; Mon, 30 Jul 2001 15:27:59 -0400 (EDT) Received: (from bsd@localhost) by neutrino.bsdhome.com (8.11.4/8.11.4) id f6UJRpf68759; Mon, 30 Jul 2001 15:27:51 -0400 (EDT) (envelope-from bsd) Date: Mon, 30 Jul 2001 15:26:47 -0400 From: Brian Dean To: John Hay Cc: freebsd-stable@FreeBSD.ORG Subject: Re: ata timeouts after debug commits Message-ID: <20010730152647.A68471@neutrino.bsdhome.com> References: <200107300718.f6U7Ipq34846@zibbi.icomtek.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200107300718.f6U7Ipq34846@zibbi.icomtek.csir.co.za>; from jhay@icomtek.csir.co.za on Mon, Jul 30, 2001 at 09:18:51AM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Jul 30, 2001 at 09:18:51AM +0200, John Hay wrote: > ######### > atapci0: port 0xbfa0-0xbfaf at device 31.1 on pci > 0 > ata0: at 0x1f0 irq 14 on atapci0 > ... > ata0-master: ata_command: timeout waiting for intr > ata0-master: identify failed > ######### > > At the end I tracked it down to these commits: > > src/sys/i386/i386/db_trace.c,v 1.35.2.1 2001/07/12 02:57:11 bsd > src/sys/i386/i386/support.s,v 1.67.2.4 2001/07/12 02:57:11 bsd > src/sys/i386/include/cpufunc.h,v 1.96.2.2 2001/07/12 02:57:11 bsd > > If I back those commits out, the machine boots and see the disk with no > problems. > > Anybody have any ideas about it? Hmmm ..., I guess I'm more confused than anything. The changes you refer to above affect only accessing the debug registers while in the DDB kernel debugger. None of the code from the above commit should be in the code path during startup, or anywhere else, actually, except from withing ddb. Do you have DDB enabled in your config? If not, try adding that to your kernel and then boot and try breaking to the debugger (CTL-ALT-ESC) when the system is hung and see if you can determine where the system is hung. While I'm not dismissing your problem, I can't think of how the above commit could cause this problem you are describing. -Brian -- Brian Dean bsd@FreeBSD.org bsd@bsdhome.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message