From owner-freebsd-current@FreeBSD.ORG Fri Jan 21 22:51:27 2005 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 E59C916A4CE for ; Fri, 21 Jan 2005 22:51:27 +0000 (GMT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2183D43D31 for ; Fri, 21 Jan 2005 22:51:27 +0000 (GMT) (envelope-from sos@DeepCore.dk) Received: from [194.192.25.143] (laptop.deepcore.dk [194.192.25.143]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id j0LMpKAg088560; Fri, 21 Jan 2005 23:51:22 +0100 (CET) (envelope-from sos@DeepCore.dk) Message-ID: <41F18768.4050809@DeepCore.dk> Date: Fri, 21 Jan 2005 23:51:20 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= User-Agent: Mozilla Thunderbird 1.0 (X11/20050116) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Garance A Drosihn References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-mail-scanned: by DeepCore Virus & Spam killer v1.6 cc: Ian Dowse cc: freebsd-current@FreeBSD.org Subject: Re: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) 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: Fri, 21 Jan 2005 22:51:28 -0000 Garance A Drosihn wrote: > I got another panic. This time I got a clean core-dump, and I also > have a kernel with all the debugging symbols if that would help. > Here is some of the info. The system had been up about 18 hours > before the panic. The system was basically idle at the time of the > panic. This is a snapshot of current which I started to build at > about 2pm EST on January 20th. The duplicate free on failed ATA retry is known. I have a fix here=20 locally but it doesnt apply to whats in -current.. However, -current has severe problems that provokes those timeouts for=20 no good reason and in all my cases locks up hard. I just vasted last=20 nights sleep hunting for what I thought was a bug in my WIP. I had=20 PREEMPTION turned of etc, but it sitll failed in odd ways. Going back to Jan 10 00:00 UTC sources make things "just work" with=20 PREEMPTION and all. My testbox has now moved around some 800 GB's of=20 data with no problems with above backstep, on -current it fails within=20 the first few Mbytes.. > Note that I have no idea when those WRITE_DMA messages came out, so > I do not know if they are related to the panic, or if those messages > were written hours earlier. >=20 > Let me know if anyone wants to pursue this further. >=20 > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D42098457 > ad4: TIMEOUT - WRITE_DMA retrying (2 retries left) LBA=3D42098457 > ad4: FAILURE - WRITE_DMA timed out --=20 -S=F8ren