I've concluded now that SMP support is a goner in the current
4.8-stable.
I did an install of 4.8-release, made a SMP kernel, verified
it works (mptable, top, boot sequence).
Then I did a complete cvsup (from cvsup10), then the following
chflags -R noschg /usr/obj/usr
rm -rf /usr/obj/usr
cd
I've concluded now that SMP support is a goner in the current
4.8-stable.
Anyone else either have SMP working on 4.8-stable
and/or knows that it doesn't?
I did a cvsup this morning and it builds and runs fine on an SMP
system here. Compaq Proliant - twin 550MHz PIII's. No problems, just
On Mon, Jun 23, 2003, Marc G. Fournier wrote:
Not sure what all to do, but doing a 'gdb -k kernel.debug /dev/mem', a
backtrack on one of the processes shows ... server has been up 12 days
now, and running a June 8th kernel ...
#0 0x20f4f0 in ?? ()
(kgdb) proc 67258
(kgdb) bt
#0
Can't this time, since we had to reboot (else alot of pissed off
postgresql.org users *grin*) ... but will add that to my debugging for
next time through ... the fun part is catching the system while its only
one of the VMs that is stuck and not the whole server :(
On Mon, 23 Jun 2003, David
On Sun, Jun 22, 2003 at 04:43:03AM -0700, Kris Kennaway wrote:
The client also needs to run lockd/statd. Be aware that rpc.lockd in
4.x and earlier is a null implementation that does not actually
perform NFS file locking with the server, it just returns success to
the client. A working lockd
I've concluded now that SMP support is a goner in the current
4.8-stable.
Zounds! I just booted the same machine/OS and saw this:
SMP: AP CPU #1 Launched!
which made me think I must have booted off the backup 4.8-release
disk... but No, it's the 4.8-stable that I've been complaining about.
I have a Supermicro SuperServer 6013P-8 system which features a X5DPR-8G2
motherboard with embedded Adaptec AIC-7902 dual-Ultra320 SCSI controller.
Said system boots and runs fine with 4.8-RELEASE (with a slight cosmetic
problem during boot that can be cured by building a kernel without eisa
On Saturday 21 June 2003 17:19, Yousif Hassan wrote:
KMail, which comes with the KDE desktop environment, is a good
GUI-based client. KDE 3.x has been ported to FreeBSD.
I use kmail daily, from 3 different machines, to access my IMAP server
out on the net. It is, so far, the best IMAP client
--On Monday, June 23, 2003 14:02:21 -0700 Wes Peters [EMAIL PROTECTED]
wrote:
On Saturday 21 June 2003 17:19, Yousif Hassan wrote:
KMail, which comes with the KDE desktop environment, is a good
GUI-based client. KDE 3.x has been ported to FreeBSD.
I use kmail daily, from 3 different machines,
Today my system coredumped (4.8-STABLE from Saturday), I believe it's somehow
X11 related:
X11 crashed first (signal 11). I was running it as root (I know I shouldn't).
I didn't think about it and restarted X11. While it was starting, I had a look
at the console, there was a bright white
Date: Mon, 23 Jun 2003 10:12:50 -0700 (PDT)
From: Mark Kent [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: SMP goes away after installworld (4.8-STABLE)
I've concluded now that SMP support is a goner in the current
4.8-stable.
Anyone else either have SMP working on 4.8-stable
and/or
On Mon, 23 Jun 2003, Mark Kent wrote:
Anyone else either have SMP working on 4.8-stable
and/or knows that it doesn't?
I upgraded two boxes this weekend to -STABLE ... no problems here ...
___
[EMAIL PROTECTED] mailing list
From: Jeffrey [EMAIL PROTECTED]
Got a pretty stupid question... My kernel is now 4.8 Stable#1 but when
does the number change when i do makeworld and the other things? or where
can i see that?
The #1 only changes when you re-compile the kernel using the same sources.
If you use cvsup/cvs
I believe that I'm having some problems with a Zip 100 drive and the
new (not really so new anymore) ATA driver. I added a Zip and a new
CD-R device to a system over the weekend. The BIOS identifies all of
the new devices just fine, but when I boot FreeBSD (the only OS on the
system), I get to the
14 matches
Mail list logo
