Bob Bernstein wrote:

> On Fri, Apr 11, 2003 at 08:55:45PM -0400, Steven M. Bellovin wrote:
> 
>> Out of curiousity, what day's 1.6Q?  I'm running 1.6Q from 31 March
>> with no problems.
> 
> I have a build of 1.6Q (i386) from cvs source dated April 5th. It's
> been running continuously since then, with a couple of reboots thrown
> in just to see how they would go. (This release is available here:
> http://www.ruptured-duck.com/NetBSD/i386/ if anyone thinks it might be
> of use.)

NetBSD 1.6Q (GENERIC) #1: Tue Apr  8 12:30:48 CDT 2003

The first three times I booted this on one machine, I ran into the
described problems.  After the third time of running fsck and
rebooting, the problem went away. Didn't have the problem on a very
similar machine. Main difference I can see is a different drive /
DMA mode 4 vs mode 5 - a Seagate ATA IV (problem occurred with
this) vs an older Quantum fireball:

wd0 at pciide0 channel 1 drive 0: <ST340016A>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 38166 MB, 16383 cyl, 16 head, 63 sec, 512 bytes/sect x 78165360 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 5 (Ultra/100)

wd0 at pciide0 channel 1 drive 0: <QUANTUM FIREBALL CR6.4A>
wd0: drive supports 16-sector PIO transfers, LBA addressing
wd0: 6149 MB, 13328 cyl, 15 head, 63 sec, 512 bytes/sect x 12594960 sectors
wd0: 32-bit data port
wd0: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 4 (Ultra/66)
wd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 4 (Ultra/66) (using DMA data
transfers)