From owner-freebsd-bugs Mon May 20 11:59:54 2002 Delivered-To: freebsd-bugs@freebsd.org Received: from freebsd.dk (cpe.atm2-0-56339.0x50c6aa0a.abnxx2.customer.tele.dk [80.198.170.10]) by hub.freebsd.org (Postfix) with ESMTP id 0B4F737B444 for ; Mon, 20 May 2002 11:59:47 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.12.2/8.12.2) id g4KIxkmX077493; Mon, 20 May 2002 20:59:46 +0200 (CEST) (envelope-from sos) From: Søren Schmidt Message-Id: <200205201859.g4KIxkmX077493@freebsd.dk> Subject: Re: kern/37060 In-Reply-To: <200205201850.g4KIo7o56401@freefall.freebsd.org> To: Matthias Andree Date: Mon, 20 May 2002 20:59:43 +0200 (CEST) Cc: freebsd-bugs@FreeBSD.ORG Reply-To: sos@freebsd.dk X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=ISO-8859-1 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 It seems Matthias Andree wrote: > > Ack, this is a boot problem, so a crashdump is going to be hard. > > Can you print out adp->device->channel->devices and > > device[ATA_DEV(ATA_SLAVE)].drive and > > ((struct ad_softc *)(adp->device->channel->device[ATA_DEV(ATA_SLAVE)].driver))->flags > > in ad_service, prior to the line which causes the panic? > > So the driver for that drive is NULL. Find the rest above. Hmm, something is wrong here that codepath in ad_service is only called for devices that has tags supported, and the Maxtor on ad0 doesnt do tags, so this codepath should not be reached at all... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message