:It currently has no swap started at all, which is one reason I was rather
:puzzled to see this panic:
:
:192.168.50.1:/cboss/devel/nfsroot/crash2.cboss.tislabs.com / nfs ro 0
: 0
:proc/proc procfs rw 0 0
:/dev/ad0s1e /mntufs rw 0
On Sun, 28 Apr 2002, Matthew Dillon wrote:
>
> :(Matt gets CC'd because he's just unlucky :-)
> :
> :This system is (as always) a pxeboot'd nfsroot'd dual processor box. This
> :time, however, it's running straight GENERIC from the main tree instead of
> :the MAC branch. The box network boots,
On Sun, 28 Apr 2002, Hiten Pandya wrote:
> Talking about doing something twice, it reminds me, that there is the same
> type of issue with the md devices, which when they are destroyed twice or
> thrice, they panic the kernel.
Re.v.108 of kern_conf.c fixes similar bugs.
Bruce
To Unsubscribe:
--- Matthew Dillon <[EMAIL PROTECTED]> wrote:
> No idea, but the last time someone had a weird swap issue it
> turned out that they had swapon'd the same swap partition twice.
> The system's checks are not sufficient if you swapon the same device
> from different mounts. So check
:(Matt gets CC'd because he's just unlucky :-)
:
:This system is (as always) a pxeboot'd nfsroot'd dual processor box. This
:time, however, it's running straight GENERIC from the main tree instead of
:the MAC branch. The box network boots, does a buildkernel -j 8, and then
:reboots. It current
(Matt gets CC'd because he's just unlucky :-)
This system is (as always) a pxeboot'd nfsroot'd dual processor box. This
time, however, it's running straight GENERIC from the main tree instead of
the MAC branch. The box network boots, does a buildkernel -j 8, and then
reboots. It currently has
This is from -CURRENT a few days ago with the TrustedBSD MAC patches.
Unfortunately, I don't know what time the panic occurred, so I can't say
what the machine was doing. Either it was largely idle, or it was working
on a make -j 8 buildworld. It's a pxeboot'd machine, with most
filesystems out
