DaemonForums  

Go Back   DaemonForums > FreeBSD > FreeBSD General

FreeBSD General Other questions regarding FreeBSD which do not fit in any of the categories below.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 21st March 2009
indiocolifa indiocolifa is offline
Real Name: Hernán Di Pietro
UnixUser
 
Join Date: Mar 2009
Location: La Plata
Posts: 17
Thanked 0 Times in 0 Posts
Default 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.
Reply With Quote
  #2   (View Single Post)  
Old 22nd March 2009
indiocolifa indiocolifa is offline
Real Name: Hernán Di Pietro
UnixUser
 
Join Date: Mar 2009
Location: La Plata
Posts: 17
Thanked 0 Times in 0 Posts
Default

Seems that disabling ACPI solves my problem... ACPI still a problem on FreeBSD 7.X? Experiences with ACPI anyone?

Thank you very much.
Reply With Quote
  #3   (View Single Post)  
Old 22nd March 2009
robbak's Avatar
robbak robbak is offline
Real Name: Robert Backhaus
VPN Cryptographer
 
Join Date: May 2008
Location: North Queensland, Australia
Posts: 366
Thanked 40 Times in 39 Posts
Default

Hardware with bad miss-implementations of ACPI are very common. Thankfully, most of their problems have been detected and coded around, and manufacturers have got a little better, but we cannot say that we have got every one of them.
Search for other problem reports and posts from other users with your hardware.

By the way, are you sure they are crashing with signal 12? Signal 12 is SIGUSR2, which is a generic number that is redefined by the process for any purpose it desires.
More common signals are 11 (SIGSEGV, Segmentation violation, similar to GPFs and Page Faults in the windows world - generally, bad ram, cache or other hardware), 6 (SIGABRT, general aborts, usually called when, for instance, a C++ exception is unhandled, or any other reason the program may want to kill itself abnormally) and 4 (SIGILL, illegal instruction - where you have compiled a program for the wrong processor). 7 (SIGBUS, buss error) also crops up occasionally.
__________________
The only dumb question is a question not asked.
The only dumb answer is an answer not given.
Reply With Quote
  #4   (View Single Post)  
Old 22nd March 2009
indiocolifa indiocolifa is offline
Real Name: Hernán Di Pietro
UnixUser
 
Join Date: Mar 2009
Location: La Plata
Posts: 17
Thanked 0 Times in 0 Posts
Default

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.
Reply With Quote
  #5   (View Single Post)  
Old 22nd March 2009
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

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.
Reply With Quote
  #6   (View Single Post)  
Old 22nd March 2009
robbak's Avatar
robbak robbak is offline
Real Name: Robert Backhaus
VPN Cryptographer
 
Join Date: May 2008
Location: North Queensland, Australia
Posts: 366
Thanked 40 Times in 39 Posts
Default

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.
Reply With Quote
  #7   (View Single Post)  
Old 22nd March 2009
Oliver_H's Avatar
Oliver_H Oliver_H is offline
Real Name: Oliver Herold
UNIX lover
 
Join Date: May 2008
Location: Germany
Posts: 429
Thanked 26 Times in 22 Posts
Default

Quote:
Originally Posted by indiocolifa View Post
Seems that disabling ACPI solves my problem... ACPI still a problem on FreeBSD 7.X? Experiences with ACPI anyone?

Thank you very much.
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 :-)
Reply With Quote
  #8   (View Single Post)  
Old 22nd March 2009
robbak's Avatar
robbak robbak is offline
Real Name: Robert Backhaus
VPN Cryptographer
 
Join Date: May 2008
Location: North Queensland, Australia
Posts: 366
Thanked 40 Times in 39 Posts
Default

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.
Reply With Quote
  #9   (View Single Post)  
Old 22nd March 2009
J65nko J65nko is offline
Administrator
 
Join Date: May 2008
Location: Budel - the Netherlands
Posts: 3,148
Thanked 182 Times in 149 Posts
Default

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
Reply With Quote
Old 23rd March 2009
indiocolifa indiocolifa is offline
Real Name: Hernán Di Pietro
UnixUser
 
Join Date: Mar 2009
Location: La Plata
Posts: 17
Thanked 0 Times in 0 Posts
Default

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.
Reply With Quote
Old 24th March 2009
MetalHead MetalHead is offline
Port Guard
 
Join Date: Sep 2008
Posts: 24
Thanked 2 Times in 1 Post
Default

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?
Reply With Quote
Old 24th March 2009
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

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.
Reply With Quote
Old 24th March 2009
MetalHead MetalHead is offline
Port Guard
 
Join Date: Sep 2008
Posts: 24
Thanked 2 Times in 1 Post
Default

Quote:
Originally Posted by DrJ View Post
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.
You Think?

What about your math? Linpac/lapac etc..?
Reply With Quote
Old 24th March 2009
DrJ DrJ is offline
ISO Quartermaster
 
Join Date: Apr 2008
Location: Gold Country, CA
Posts: 506
Thanked 39 Times in 39 Posts
Default

If it takes more than 3GB of memory, then use AMD64. Otherwise, forget it.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

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


All times are GMT. The time now is 02:11 PM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick