From owner-freebsd-stable Fri Aug 2 23:22:54 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 4490337B400 for ; Fri, 2 Aug 2002 23:22:51 -0700 (PDT) Received: from arutam.inch.com (ns.inch.com [216.223.192.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9DD6F43E65 for ; Fri, 2 Aug 2002 23:22:50 -0700 (PDT) (envelope-from spork@inch.com) Received: from inch.com (inch.com [216.223.192.20]) by arutam.inch.com (8.12.2/8.12.2/UTIL-INCH-3.0.6) with ESMTP id g736Mhuh018778; Sat, 3 Aug 2002 02:22:43 -0400 (EDT) Date: Sat, 3 Aug 2002 02:22:43 -0400 (EDT) From: Charles Sprickman To: Soeren Schmidt Cc: Martin Blapp , Subject: Re: After upgrade: panic with ad0 device In-Reply-To: <200208021535.g72FZcKC041719@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE 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 Hi, Sounds like he's got the same chipset as I do. Same symptoms, see: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D40003 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: ----- (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", par= am =3D 0x0, driver =3D 0x0, flags =3D 0, mode =3D 0, cmd =3D 0, result =3D 0x0} ad_attach() is trying to dereference atadev->param, which is NULL. ----- I'm still set up with remote gdb ready to go if you need any other info. I also used to get the "falling back to PIO" delays/resets, regardless of whether I turn off dma in loader.conf. Thanks, Charles -- Charles Sprickman spork@inch.com On Fri, 2 Aug 2002, Soeren Schmidt wrote: > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message