From owner-freebsd-current@FreeBSD.ORG Mon Jan 24 03:03:36 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 6B15816A4CE for ; Mon, 24 Jan 2005 03:03:36 +0000 (GMT) Received: from smtp2.server.rpi.edu (smtp2.server.rpi.edu [128.113.2.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9EC2943D3F for ; Mon, 24 Jan 2005 03:03:35 +0000 (GMT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.netel.rpi.edu [128.113.24.47]) by smtp2.server.rpi.edu (8.13.0/8.13.0) with ESMTP id j0O33Ow8004225; Sun, 23 Jan 2005 22:03:26 -0500 Mime-Version: 1.0 Message-Id: In-Reply-To: <41F18768.4050809@DeepCore.dk> References: <41F18768.4050809@DeepCore.dk> Date: Sun, 23 Jan 2005 22:03:23 -0500 To: =?iso-8859-1?Q?S=F8ren_Schmidt?= From: Garance A Drosihn Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable X-CanItPRO-Stream: default X-RPI-SA-Score: undef - spam-scanning disabled X-Scanned-By: CanIt (www . canit . ca) 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: Mon, 24 Jan 2005 03:03:36 -0000 At 11:51 PM +0100 1/21/05, S=F8ren Schmidt wrote: >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 >locally but it doesnt apply to whats in -current.. It'd be nice if that could get fixed in -current. Right now my main system goes about 12 to 18 hours before it panics due to this. >However, -current has severe problems that provokes those timeouts >for no good reason and in all my cases locks up hard. I have been seeing these timeout messages for as long as I've been running FreeBSD on this sata-based box. Not more than two or three times a day, and my machine usually does not lock up when I do get them. But they've always been there, and now they cause panics at an annoying rate. The panics also seem to always happen when the machine is pretty idle. Usually when I'm not in my office, which of course means the machine has crashed when I later go to ssh into it from home... -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu