Date: Sat, 24 Mar 2007 11:26:19 -0600 From: Scott Long <scottl@samsco.org> To: KillFill <pneumann@gmail.com> Cc: scottl@freebsd.org, erich@areca.com.tw, FreeBSD Stable <freebsd-stable@freebsd.org>, Nikolas Britton <nikolas.britton@gmail.com> Subject: Re: Amd64 Unstable Areca Message-ID: <46055F3B.8070101@samsco.org> In-Reply-To: <1174757792.881.3.camel@localhost> References: <460292F9.3050802@gmail.com> <ef10de9a0703231901p461d1e27x8a9893a9c63827a@mail.gmail.com> <1174757792.881.3.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
KillFill wrote: > El vie, 23-03-2007 a las 21:01 -0500, Nikolas Britton escribió: >> A newer version of the driver has been release to fix this problem (I >> think): >> http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/arcmsr/ >> >> If that doesn't work move back down to 1.20.00.12: >> http://www.nbritton.org/uploads/areca/ >> >> Added erich and scott to the cc list. >> > > Well, you may notice im using RELENG_6 > > im using the latest versions for releng_6: > > * $FreeBSD: src/sys/dev/arcmsr/arcmsr.c,v 1.8.2.3 > * $FreeBSD: src/sys/dev/arcmsr/arcmsr.h,v 1.1.4.2 > > unfortunatly cannot move the box to -CURRENT to test arcmsr.c 1.20 and > arcmsr.h 1.4 > > thanks. It's possible that I might have botched the merge from -CURRENT. Your panics definitely point to data corruption, which implicates the driver. I'll take a look. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46055F3B.8070101>