From owner-freebsd-bugs Mon May 20 13: 0:32 2002 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id E79A937B406 for ; Mon, 20 May 2002 13:00:08 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.11.6/8.11.6) id g4KK08k67608; Mon, 20 May 2002 13:00:08 -0700 (PDT) (envelope-from gnats) Date: Mon, 20 May 2002 13:00:08 -0700 (PDT) Message-Id: <200205202000.g4KK08k67608@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Andrew Gallatin Subject: Re: kern/37060 Reply-To: Andrew Gallatin Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The following reply was made to PR kern/37060; it has been noted by GNATS. From: Andrew Gallatin To: Matthias Andree Cc: matthias.andree@web.de, freebsd-gnats-submit@freebsd.org, sos@freebsd.org Subject: Re: kern/37060 Date: Mon, 20 May 2002 15:53:15 -0400 (EDT) Matthias Andree writes: > On Mon, 20 May 2002, Andrew Gallatin wrote: > > > >It would be helpful to know which pointer was null. There > > >are many of them on line 710 of ata-disk.c > > Ok, it looks as though bad things happen when the non-existant primary > slave is probed. I used boot -dg, set a breakpoint at ad_service and > after successfully detecting the first drive, I got some info. > > The most important lines from below, consistent with the trap > (ATA_DEV(ATA_SLAVE) == 1): > > (kgdb) print ((struct ad_softc *)(adp->device->channel->device[1].driver)) > $9 = (struct ad_softc *) 0x0 > > So the problem happens probably at line #713 when dereferencing > ->flags. What if you protect those access with a check for a non-null driver? Also, what happens if you comment out the call to the ata_raiddisk_attach() in ad_attach() ? Drew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message