Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
The machines are dual PII 450's (N440BX) with 512MB RAM. We are also
using built in ethernet and SCSI
On Tue, 14 Sep 1999, Stevan Arychuk wrote:
Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
Here are the symptoms we are seeing:
1 machine
On Tue, 14 Sep 1999, Stevan Arychuk wrote:
Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
Are the kernel and user-land out of sync (kernel
Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
The machines are dual PII 450's (N440BX) with 512MB RAM. We are also
using built in ethernet and SCSI
On Tue, 14 Sep 1999, Stevan Arychuk wrote:
Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
Here are the symptoms we are seeing:
1 machine
On Tue, 14 Sep 1999, Stevan Arychuk wrote:
Greetings,
We are running 3.1-RELEASE with a kernel pulled on May 1, 1999 from the
RELENG_3 branch (used this to take advantage of the KVA modifications
that were rolled in after the release).
Are the kernel and user-land out of sync (kernel
Yes,
The KVA patches were introduced after the initial release of 3.1, so I
guess you could say we're running 3.1 1/2 - RELEASE.
We held off on upgrading to 3.2 as there was still a problem with GDB.
I'm testing 3.3-19990909-RC and I've been able to do a back trace on a
core dump from a
7 matches
Mail list logo
