From owner-freebsd-stable Tue Aug 6 18: 1:17 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B623237B400 for ; Tue, 6 Aug 2002 18:01:07 -0700 (PDT) Received: from mx1.freebsdsystems.com (mx1.freebsdsystems.com [216.126.94.33]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7CA4F43E70 for ; Tue, 6 Aug 2002 18:01:06 -0700 (PDT) (envelope-from lnb@cybertouch.org) Received: (qmail 89464 invoked from network); 7 Aug 2002 01:01:05 -0000 Received: from unknown (HELO panda.FreeBSDsystems.com) (216.126.94.34) by panda.freebsdsystems.com with SMTP; 7 Aug 2002 01:01:05 -0000 Subject: Re: After upgrade: panic with ad0 device From: Lanny Baron To: Charles Sprickman Cc: Soeren Schmidt , Martin Blapp , stable@freebsd.org In-Reply-To: References: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailer: Ximian Evolution 1.0.8 Date: 06 Aug 2002 21:01:04 -0400 Message-Id: <1028682065.96438.166.camel@panda.FreeBSDsystems.COM> Mime-Version: 1.0 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 The problem below seems to be more with a particular brand of hard drives. Lanny On Sat, 2002-08-03 at 02:22, Charles Sprickman wrote: > Hi, >=20 > Sounds like he's got the same chipset as I do. Same symptoms, see: >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D40003 >=20 > It took me a while but I got a trace with Julian and DES's help, it's > attached to the pr now. In one of the past threads on this, there's this > response: >=20 > ----- > (kgdb) p adp > $2 =3D (struct ad_softc *) 0x68c040 > (kgdb) p atadev > $3 =3D (struct ata_device *) 0xc075b650 > (kgdb) p *adp > Cannot access memory at address 0x68c040. > (kgdb) p *atadev > $4 =3D {channel =3D 0xc075b600, unit =3D 16, name =3D 0xc04503b0 "ad1", p= aram =3D 0x0, > driver =3D 0x0, flags =3D 0, mode =3D 0, cmd =3D 0, result =3D 0x0} >=20 > ad_attach() is trying to dereference atadev->param, which is NULL. > ----- >=20 > I'm still set up with remote gdb ready to go if you need any other info. >=20 > I also used to get the "falling back to PIO" delays/resets, regardless of > whether I turn off dma in loader.conf. >=20 > Thanks, >=20 > Charles >=20 > -- > Charles Sprickman > spork@inch.com >=20 >=20 > On Fri, 2 Aug 2002, Soeren Schmidt wrote: >=20 > > It seems Martin Blapp wrote: > > > We get repeatable panics on a old machine, where a ATA > > > disk seems to have problems. > > > > > > It works fine on 4.4 (beside some timeout messages), > > > panics reproducable at startup every time at the same > > > place. > > > > > > With 4.4 we got: > > > > > > ad0: READ command timeout tag=3D0 serv=3D0 - resetting > > > ata0: resetting devices .. done > > > ad0: READ command timeout tag=3D0 serv=3D0 - resetting > > > ata0: resetting devices .. done > > > ad0: READ command timeout tag=3D0 serv=3D0 - resetting > > > ata0: resetting devices .. done > > > ad0: READ command timeout tag=3D0 serv=3D0 - resetting > > > ad0: trying fallback to PIO mode > > > ata0: resetting devices .. done > > > > > > Everything worked. Now, after a upgrade to 4.6 STABLE > > > we get a panic after "ad0: trying fallback to PIO mode". > > > > dmesg ? !?! > > > > > Set the device in BIOS to PIO mode doesn't help too. > > > > That changes nothing at all.. > > > > Maybe you could disable DMA from the loader, does it work then ? > > > > -S=F8ren > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > >=20 >=20 > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message