Date: Wed, 29 Mar 2000 16:59:03 -0500 From: Lee Cremeans <lcremeans@erols.com> To: Jason Garman <jgarman@wedgie.org> Cc: hometeam <hometeam@techpower.net>, Gawel <gawel@sim.com.pl>, Eric Jacoboni <jaco@titine.fr.eu.org>, Grigoriy Strokin <grg@philol.msu.ru>, freebsd-stable@FreeBSD.ORG Subject: Re: New kernel with its ATA drivers damages the filesystem Message-ID: <20000329165903.B7857@lcremeans.erols.com> In-Reply-To: <20000329161649.A15367@got.wedgie.org>; from jgarman@wedgie.org on Wed, Mar 29, 2000 at 04:16:49PM -0500 References: <38E1D32B.F946EEB8@sim.com.pl> <Pine.BSF.4.21.0003290849210.3533-100000@techpower.net> <20000329161649.A15367@got.wedgie.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 29, 2000 at 04:16:49PM -0500, Jason Garman wrote:
> On Wed, Mar 29, 2000 at 08:53:38AM -0500, hometeam wrote:
> >
> > I agree this really should be fix ...I notcied this straight away and sent
> > mail to the group...Now it is damaging file Systems after the fact and
> > wiping out file systems... I mean change the
> > hardware ??? Why not fix the driver ?
> >
> Because in my experience at least it is a hardware problem, not unlike the
> old cmd640 and rz1000 bugs. Granted there should be an easy way to
> disable dma in the kernel config (so that you can disable it early on,
> before bootup and also during installation)
Some things I've noticed about all this:
1) My machine is running FreeBSD 3.4-STABLE (soon to be 4.0-STABLE) on a
Soyo SY-5EHM board (using an ETEQ chipset, really a relabelled VIA MVP3)
board, and in the time I've had it (over a year now), I've not seen any
serious problems or filesystem corruption in DMA mode, and I've done
stressful things like make buildworld on it many times without trouble. Just
FYI, I have a Seagate Medalist Pro 9.1GB, a Toshiba 32x CDROM and an LS-120
drive hooked up (HD's on the primary channel, CD-ROM and floppy on the
second).
2) Here's the weird bit...I cut an ISO of 4.0-RELEASE...uh, last Friday I
think? and I decided to play with it on an Intel SE440BX2 board. (Celeron
300A processor, I think). I was noticing all sorts of weird
filesystem-corruption problems while it was installing ("panic: dup alloc"
was one of them), and it also had trouble seeing the hard drive I had hooked
up (an old (1997) JTS Champion 3.2GB). Changing out the memory, of all
things, seemed to make it work. THis drive also worked without a problem
once I connected it to my machine (to check out 4.0 without having to pull
the trigger on my main disk).
PS: IDE unfortunately still sucks when you have two devices on the same
channel (the LS-120 lags the CD-ROM horribly when I try to use both at
once), but that's not a FreeBSD problem, that's a "I need a SCSI LS-120"
problem (they're hard to find, but they're out there). :)
-lee
--
+--------------------------------------------------------------------+
| Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) |
| lcremeans@erols.com | http://wakky.dyndns.org/~lee |
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000329165903.B7857>