From owner-freebsd-current@FreeBSD.ORG Tue Sep 16 16:53:31 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CC8216A521 for ; Tue, 16 Sep 2003 16:53:29 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id E598444284 for ; Tue, 16 Sep 2003 16:31:38 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 10302 invoked by uid 1000); 16 Sep 2003 23:31:40 -0000 Date: Tue, 16 Sep 2003 16:31:40 -0700 (PDT) From: Nate Lawson To: Soren Schmidt In-Reply-To: <200309081753.h88HrNwQ047003@spider.deepcore.dk> Message-ID: <20030916161748.T10282@root.org> References: <200309081753.h88HrNwQ047003@spider.deepcore.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@FreeBSD.ORG Subject: Re: ATAng panic: ATAFD re-using freed memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 23:53:32 -0000 On Mon, 8 Sep 2003, Soren Schmidt wrote: > It seems Nate Lawson wrote: > > With a fresh checkout of last night's -current, I cannot boot my laptop. > > ATAFD panics the box by reusing freed memory. I do not have a floppy > > drive in the laptop and when I do, it's a legacy floppy, not atapi. Here > > are the messages: > > > > [normal ad0/acd0 probe message] > > afd0: timeout waiting for ATAPI ready > > afd0: timeout waiting for ATAPI ready > > afd0: timeout waiting for ATAPI ready > > afd0: timeout waiting for ATAPI ready > > afd0: timeout waiting for ATAPI ready > > panic: Memory modified after free: 0xc33ed400 (252) > > Most recently used by AFD driver > > > > A working dmesg: > > http://www.root.org/~nate/acpi/ibm.dmesg > > >From the above I can tell whats going on, please upgrade to the latest > -current as I've fixed a couble of things in the probe code there. > > If it still panic's please include a verbose boot from a atapicam-less > kernel... This has been fixed. However, ATAng is still not usable for the reasons in my next email message: Message-ID: <20030913164950.S3069@root.org> -Nate