Opened 9 years ago
Closed 9 years ago
#14085 closed defect (worksforme)
Panic on OSX on recent Intel CPUs (SMAP)
| Reported by: | Fane | Owned by: | |
|---|---|---|---|
| Component: | VM control | Version: | VirtualBox 4.3.26 |
| Keywords: | SMAP | Cc: | |
| Guest type: | Linux | Host type: | Mac OS X |
Description
Hi,
i've been redirected from https://www.virtualbox.org/ticket/9897#comment:56 to post a new ticket.
Attaching crash report.
Thanks for Your time :)
Attachments (4)
Change History (16)
by , 9 years ago
comment:1 by , 9 years ago
Thanks. Do you also have the corresponding VBox.log file available? And please attach the output of 'sudo dmesg'.
comment:2 by , 9 years ago
Sorry dmesg does not give much information or i'am using it wrong.
The VBox.log was overwritten, because i destroyed the vagrant machine.
I didnt know it was necessary, next time i back it up...
by , 9 years ago
| Attachment: | cfprefsd_2015-05-05-111318_MacBook-Pro-Thomas.crash added |
|---|
by , 9 years ago
comment:3 by , 9 years ago
I got it again. After the crash i cat the dmesg to a file, and got the newest crash report.
This crash happend while starting vagrant manager, but all my machines are on VitualBox.
by , 9 years ago
comment:5 by , 9 years ago
But that VBox.log was not modified when the error occured. I Think this might be not realted to VB. Or dou You see something unusual in the logs?
comment:6 by , 9 years ago
Nothing unusual there but we still need this log file to be able to decode the crash dump. The VBox.log file contains the load addresses of certain VBox libraries.
comment:7 by , 9 years ago
Actually it turns out that the latest crash was not a host crash but a crash from /usr/sbin/cfprefsd. This process is not related to VirtualBox. Are you sure this is the correct crash report? Did really your host crash or a single process?
comment:8 by , 9 years ago
Im not sure thats the problem.
I noted the time when the system crashed and search logs for that time. Only that came up.
I did a reasearch, and i have to reinstall the system.
After that i will post more info if it still happens. Sorry for your lost time...
comment:9 by , 9 years ago
It turned out that i've had a hardware issue. Ram problem. I will test the case after the laptop is fixed and report back here.
comment:11 by , 9 years ago
I am testing it for over a week now, no problems at all. It was the damaged ram.
I apologize for taking Your time.
comment:12 by , 9 years ago
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
Glad to hear that your problem is solved. Thank you for the feedback!
Crash report