On 2011-12-08 08:55, Aragon Gouveia<ara...@phat.za.net> wrote: > On 12/07/11 23:00, Soren Kristensen wrote: >> I don't have the knowledge to find out where and why FreeBSD stops, but >> if some FreeBSD hacker can go down and tell me why, I will do what I can >> do fix it if the BIOS need a little adjustment.... > > Considering all the ACPI error messages, I guess it's a problem there > somewhere. The freebsd-acpi@ mailing list is a good place to seek ACPI > wizards. :)
If I try to boot FreeBSD 9.0-RC2 in verbose mode with amd64 and i386 and compare the boot messages side-by-side, there are as many error messages about ACPI with the (successful) i386 boot than with the (failed) amd64 boot. The amd64 boot ends with the following lines: > panic: No usable event timer found! > cpuid = 0 > KDB: stack backtrace: > #0 0xffffffff80867e4e at kdb_backtrace+0x5e > #1 0xffffffff80832ab7 at panic+0x187 > #2 0xffffffff80b5250b at cpu_initclocks_bsp+0x3cb > #3 0xffffffff807e9ec0 at initclocks+0x20 > #4 0xffffffff807e7507 at mi_startup+0x77 > #5 0xffffffff8029f6ec at btext+0x2c > Uptime: 1s > Automatic reboot in 15 seconds - press a key on the console to abort Whereas the i386 boot goes on at this same spot with: > lapic: Divisor 2, Frequency 50001280 Hz > Timecounters tick every 1.000 msec Somehow, the "LAPIC" timer is reported with the i386 boot thus: > MPTable: <Soekris net6501 > > Event timer "LAPIC" quality 400 > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 HTT threads > cpu0 (BSP): APIC ID: 0 > cpu1 (AP/HT): APIC ID: 1 but not on the amd64 boot. Also, the i386 reports early on: > MP Configuration Table version 1.4 found at 0xc00fe110 and *not* the amd64 boot. Anyway, just some preliminary information in case it triggers an Ah-ha! with some of the list members. Cheers, Denis F. _______________________________________________ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
