Date: Fri, 21 Jan 2005 23:51:20 +0100 From: =?ISO-8859-1?Q?S=F8ren_Schmidt?= <sos@DeepCore.dk> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@FreeBSD.org Subject: Re: panic: Duplicate free of item 0xc433e420 from zone 0xc1045c00(g_bio) Message-ID: <41F18768.4050809@DeepCore.dk> In-Reply-To: <p06200730be172d908fe6@[128.113.24.47]> References: <p06200730be172d908fe6@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41F18768.4050809>