Brief freezes with -current as of early last week

Nik Clayton nik at
Mon Sep 20 03:00:48 PDT 2004

After updating from -current built on 2004/04/27 to -current built on
2004/09/13, I'm seeing some annoying 'freezes'.  I'd not seen these with
the earlier -current.

To complicate matters, right around the time I did the update I also
switched from a configuration with two SCSI disks and an IDE disk, to a
configuration with two IDE disks (each SCSI disk, bought at the same
time, from the same supplier, died within 4 days of each other --

So, I guess what I might be seeing is plain old I/O contention --
although I'm surprised that it freezes the box.  According to
'atacontrol mode 0', both IDE devices are using UDMA100, which is the
maximum the motherboard (dual 1GHz PIII) supports).

The symptoms typically manifest themselves right after kicking off a
portupgrade command.  The system will (sort-of) freeze.  If I'm in X,
the mouse cursor stops responding, there's no response to the keyboard.
However, if I happen to have top(1) running in an xterm, the top(1)
display keeps updating.  This lasts (wall-clock) 10 to 15 seconds, and
then the system becomes responsive again.

I'm running a kernel built with SCHED_4BSD.  INVARIANTS,
I don't have an /etc/malloc.conf symlink, so I'm using whatever the
-current defaults are (as a side note, where are those defaults

Any thoughts, or recommendations to help tracking this down greatly

FreeBSD: The Power to Serve               (__)
FreeBSD Documentation Project    \\\'',)
                                                                      \/  \ ^
   --- 15B8 3FFC DDB4 34B0 AA5F  94B7 93A8 0764 2C37 E375 ---         .\._/_)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url :

More information about the freebsd-current mailing list