|
FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below. |
|
Thread Tools | Display Modes |
|
|||
Anyone with AMD64 random panics on i386?
I'm using FreeBSD/i386 7.1 on AMD Dual Core system, and it's randomly crashing with trap 12.
Last crash was on CPU 0, virtual addr 0x18, supervisor read page not present, current process (ls!!!) Maybe I need some RAM testing, but Win/Linux seem stable. |
|
|||
Seems that disabling ACPI solves my problem... ACPI still a problem on FreeBSD 7.X? Experiences with ACPI anyone?
Thank you very much. |
|
|||
I think the kernel is crashing with trap 12 not signal 12 -- the crash is in kernel mode, specifically a page fault occuring in KM.
Last edited by indiocolifa; 22nd March 2009 at 02:55 AM. |
|
|||
I'm not trying to hijack the thread, but I'm seeing something similar with a very, very old computer (an early dual Athlon) with i386. Does loading with ACPI turned off eliminate all that code? If it does, then I have something else going on.
|
|
||||
That system is likely to have a very buggy ACPI. You would probably be best turning off the ACPI in the BIOS and in FreeBSD.
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
||||
ACPI is still a problem on every operating system. Windows just hides some problems and breaks some time later. So most of the time it would be better to address your problems toward the manufacturer of your motherboard/laptop/bios.
__________________
use UNIX or die :-) |
|
||||
I just noticed that I was looking at a linux signum.h file, not a BSD one.
SIGBUS (bus error) is 10 on FreeBSD, an 12 is SIGSYS (non-existent system call invoked).
__________________
The only dumb question is a question not asked. The only dumb answer is an answer not given. |
|
|||
See thre FreeBSD FAQ: http://www.freebsd.org/doc/en_US.ISO...#TRAP-12-PANIC
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
Turning off ACPI seems to solve to problem, the strange thing is that under a VMWare Virtual Machine (Win32), FreeBSD 7 crashes with the same errors. Is VMWare using some of my platform chipset hardware or it completely virtualizes all, excepting the CPU?
Thanks. |
|
|||
Why are you running x86 software on x64 cpu's?
X86 is soooooooo 2008. Take a step into 2009 and drop all of that old x86 code..You purchased a computer with x64/Cpu's. Why would you want to run old x86 software? |
|
|||
The nVidia driver, wine, acroread, the old vmware, flash, ...
Only if you need to address more than 3Gb of RAM is there any reason to use AMD64. |
|
|||
Quote:
What about your math? Linpac/lapac etc..? |
|
|||
If it takes more than 3GB of memory, then use AMD64. Otherwise, forget it.
|
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
HDD formatted UFS under AMD64 experiences weirdness under I386 | Gemini | FreeBSD General | 4 | 9th December 2008 05:27 AM |
Allow i386 and amd64 to boot from extended DOS partitions | lvlamb | OpenBSD General | 4 | 16th July 2008 03:24 PM |
i386 drivers on amd64 | kienjakenobi | FreeBSD Ports and Packages | 5 | 25th June 2008 05:37 PM |
i386 6.x binaries not working on AMD64 7.x (with compat) | lesmando24 | FreeBSD General | 5 | 29th May 2008 05:39 AM |
Revert from AMD64 to i386 | chavez243 | FreeBSD General | 6 | 6th May 2008 12:24 PM |