From owner-freebsd-stable Mon Jul 30 13: 7:41 2001 Delivered-To: freebsd-stable@freebsd.org Received: from zibbi.icomtek.csir.co.za (zibbi.icomtek.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id 07ACD37B403 for ; Mon, 30 Jul 2001 13:07:32 -0700 (PDT) (envelope-from jhay@zibbi.icomtek.csir.co.za) Received: (from jhay@localhost) by zibbi.icomtek.csir.co.za (8.11.1/8.11.1) id f6UK78K54426; Mon, 30 Jul 2001 22:07:08 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <200107302007.f6UK78K54426@zibbi.icomtek.csir.co.za> Subject: Re: ata timeouts after debug commits In-Reply-To: <20010730152647.A68471@neutrino.bsdhome.com> from Brian Dean at "Jul 30, 2001 03:26:47 pm" To: bsd@bsdhome.com (Brian Dean) Date: Mon, 30 Jul 2001 22:07:08 +0200 (SAT) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > ######### > > 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. Maybe it isn't the code itself but just that things moved? I tried the snaps on internat and the ones before July 13 worked, but Jul 13 and later didn't work. Even a fairly stripped down kernel with later sources didn't work until I backed out those 3 files. > > 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. I'll do that as soon as I can get hold of the notebook again. It isn't mine, I just borrowed it to get the Lucent/Orinoco/Dell mini-pci wireless card going. The kernel doesn't hang though. It just don't see the disk and then does not have anywhere to boot from. John -- John Hay -- John.Hay@icomtek.csir.co.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message