Jacques A. Vidrine
cc current@
I have an ASUS P2L97-DS ACPI BIOS Revision 1008 Dual cpu box
FreeBSD 5.0-DP2 #0: Wed Dec 4 00:26:02 CET 2002
CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x650 Stepping = 0
On Mon, Dec 09, 2002 at 10:47:24PM +0100, Julian H. Stacey wrote:
I dropped back to a generic single CPU kernel.
( Which cancelled main reason I moved to 5.0-DP2:
to get ATA bus working with dual, see my Nov. 22
Subject: 5.0-DP2: SMP+ATA OK. But 4.7 stable boot panic with ASUS
Hello All,
I finally managed to put some time aside to redo my main
development/desktop machine to run FreeBSD 5.0. (I've been running
5.x on my laptop for some months.) I had to retreat back to 4.7
because I could not get through some simple tasks without the system
hanging. The system is a
Jacques A. Vidrine wrote:
Hello All,
I finally managed to put some time aside to redo my main
development/desktop machine to run FreeBSD 5.0. (I've been running
5.x on my laptop for some months.) I had to retreat back to 4.7
because I could not get through some simple tasks without the system
cc -O -pipe -mcpu=pentiumpro -DLIBC_SCCS -I/dell/imp/p4/newcard/src/lib/libkvm -c
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c -o kvm_proc.o
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c: In function `kvm_proclist':
/dell/imp/p4/newcard/src/lib/libkvm/kvm_proc.c:327: `KI_MTXBLOCK' undeclared
I know this is not a -current problem, but if it was fixed by someone they
are likely to be reading here, and not in -stable..
We have a hybrid (4.11+patches) kernel that sometimes crashes.
The crash always has teh same symptoms and I'm hoping that
they look familiar to someone
On 24-Jul-01 Julian Elischer wrote:
In a VFS operation, %ecx get's corrupted (maybe from an interrupt?)
betweeen the instruction where it's loaded with a constant,
and the instruction where it's used... It'always the same instruction,
though often in DIFFERENT VFS instructions (fsync,
I know this is not a -current problem, but if it was fixed by someone they
are likely to be reading here, and not in -stable..
We have a hybrid (4.11+patches) kernel that sometimes crashes.
The crash always has teh same symptoms and I'm hoping that
they look familiar to someone