Tyan k8sr lockups
gmulder at infotechfl.com
Fri Apr 1 07:42:54 PST 2005
Thanks for testing. It is not SMP causing the problem, as I can cause
the hang with the GENERIC amd64 uniproccesor kernel as well.
Any idea how we can get more diagnostics on what in FreeBSD is causing
the crash? I suppose I can truss the dd and copy the truss output off
the remote terminal session after is hangs...
Is there a way to force a crash dump? I heard mention of a key combo on
the console to force a crash dump, but I suspect the console keyboard is
totally hung as well.
Does anyone have a doc on how to run the kernel under gdb or something
and log what is happening to a serial console?
Sven Willenberger wrote:
> Confirmed the hang with a dual opteron system (248's) with 8GB of ram
> using the dd command above. System hung within seconds of issuing said
> command using an SMP-enabled kernel.
> FreeBSD 5.4-PRERELEASE #0: Thu Mar 17 22:41:53 EST 2005
> Timecounter "i8254" frequency 1193182 Hz quality 0
> CPU: AMD Opteron(tm) Processor 248 (2190.55-MHz K8-class CPU)
> Origin = "AuthenticAMD" Id = 0xf5a Stepping = 10
> AMD Features=0xe0500800<SYSCALL,NX,MMX+,LM,3DNow+,3DNow>
> real memory = 8589934592 (8192 MB)
> avail memory = 8250437632 (7868 MB)
> ACPI APIC Table: <A M I OEMAPIC >
> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
> cpu0 (BSP): APIC ID: 0
> cpu1 (AP): APIC ID: 1
> MADT: Forcing active-low polarity and level trigger for SCI
> ioapic0 <Version 1.1> irqs 0-23 on motherboard
> ioapic1 <Version 1.1> irqs 24-27 on motherboard
> ioapic2 <Version 1.1> irqs 28-31 on motherboard
> acpi0: <A M I OEMRSDT> on motherboard
> acpi0: Power Button (fixed)
> Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
> acpi_timer0: <24-bit timer at 3.579545MHz> port 0x5008-0x500b on acpi0
> cpu0: <ACPI CPU> on acpi0
> acpi_throttle0: <ACPI CPU Throttling> on cpu0
> cpu1: <ACPI CPU> on acpi0
More information about the freebsd-amd64