Date: Sun, 10 Feb 2013 14:55:47 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Hans Ottevanger <hans@beastielabs.net> Cc: current@freebsd.org Subject: Re: Time to kill fdc ? Message-ID: <80625.1360508147@critter.freebsd.dk> In-Reply-To: <5117A0CD.6060904@beastielabs.net> References: <79955.1360494404@critter.freebsd.dk> <9EDF355D-07F7-4315-B00E-B181C674D763@gsoft.com.au> <80113.1360496675@critter.freebsd.dk> <AAE4A5DA-3565-446B-BF87-A136F18136F2@gsoft.com.au> <5117A0CD.6060904@beastielabs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Content-Type: text/plain; charset=ISO-8859-1 -------- In message <5117A0CD.6060904@beastielabs.net>, Hans Ottevanger writes: >On 02/10/13 12:46, Daniel O'Connor wrote: >But I just did an experiment on an old Pentium 4 system here, using the >fdc driver and 8.3-STABLE as of early December (r243900). I read several >diskettes using "dd /dev/fd0 /dev/null" and everything went flawlessly. Could you try: dd if=/dev/fd0 of=/dev/null bs=1048576 That consistently exploded 7.x and 8.x here yesterday... (I used recoverdisk, but that's not material) >Could it be that the drive that Poul-Henning is using is worn out a bit? No, that's not it. It's (amongst other things) ISA-DMA being børken (try something different that /dev null btw :-) and bounce buffers for same panicking the system. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?80625.1360508147>