Phil Homewood wrote:
> Attached is a copy of my dmesg and kernel config.
Well, it would have been, if I hadn't been distracted by... ooh, shiny...
Um, yeah. Here it is.
(Also another point: UFS_DIRHASH appears to make no difference.)
Copyright (c) 1992-2002 The FreeBSD Project.
Copy
A system recently upgraded from a 6 month old 4.3-STABLE image
appears to be suddenly experiencing massive FS corruption (or
fsck is very confused when checking a readonly-mounted FS.)
I've been following what seem to be a lot of dead-ends on this,
but seem to have tracked it down to the followin
Mike C. Muir wrote:
> Sound card is:
>
> sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5
>on isa0
Unsure if it's related or not, but I had a spurious reboot
immediately after playing a .wav file a few days ago.
version:
FreeBSD 4.0-STABLE #10: Tue May 2 12:08:10 EST 2000
dme
The last two days have seen two lockups on one of our firewall
machines. Box is pingable, accepts TCP connections but does
nothing more. syslog shows it logging "MARK" every five minutes
even when unresponsive.
First thought: DoS attack. After cvsupping and recompiling
kernel and world yesterday
Brad Knowles wrote:
> Am I missing something here? Should I not be using "make update"
> at all, but instead be calling the appropriate cvsup commands with
> the appropriate supfiles directly? If so, then why does "make
> update" exist at all?
% grep SUP /etc/make.conf
# CVSup update f
