Forums
New posts
Articles
Product Reviews
Policies
FAQ
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Menu
Log in
Register
Install the app
Install
Forums
Apple Computing Products:
macOS - Operating System
Omg, I just had a kernal panic.
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="mathogre" data-source="post: 402481" data-attributes="member: 25890"><p>Netty,</p><p></p><p>Your kernel may have panicked, but I wouldn't if I were you. OS X crashes once in a while, and I've had two or three panics since coming to Mac. For that matter, I've crashed Linux in the past, locking it sometimes, getting a kernel panic others. "Linux doesn't crash." Yeah, right.</p><p></p><p>What you should do is note what you were running at the time. In my experience, two or more applications are vying for the same resource, memory addresses for instance. The OS *should* be protecting resources from contention from multiple applications, but holes occasionally exist. When applications encounter such holes, the OS goes belly-up.</p><p></p><p>For now you should run Disk Utility (Applications> Utilities> Disk Utility), highlight your hard drive, and do a "Verify". If you get any errors, post about it here. My guess is you're probably okay.</p><p></p><p>What to do if it happens again?</p><p></p><p>1. Note what time your machine crashed.</p><p></p><p>2. Note what apps you were running.</p><p></p><p>3. Boot your machine.</p><p></p><p>4. Run Disk Utility and verify your hard drive.</p><p></p><p>If you're sufficently geek proficient...</p><p></p><p>5. Open Terminal.</p><p></p><p>6. Type:</p><p></p><p>less /var/log/system.log</p><p></p><p>You'll get a view of some of the things happening in your machine. To go to the end of the file, type</p><p></p><p>G</p><p></p><p>To move through the file, scroll up and down with the arrow keys. What you're looking for is anything that happened around the time of your system crash.</p><p></p><p>To get out of "less" (the program you're running), type</p><p></p><p>q</p><p></p><p>and it will end. Close the terminal as needed.</p><p></p><p>In closing, you want to discover what caused the crash. With luck it won't happen again. Should it do so, you want to see if you can find the cause. If and when you do, then you can potentially upgrade whatever seems to be broken. When panics are rare, it's tough to find the problems.</p><p></p><p>Good luck!</p></blockquote><p></p>
[QUOTE="mathogre, post: 402481, member: 25890"] Netty, Your kernel may have panicked, but I wouldn't if I were you. OS X crashes once in a while, and I've had two or three panics since coming to Mac. For that matter, I've crashed Linux in the past, locking it sometimes, getting a kernel panic others. "Linux doesn't crash." Yeah, right. What you should do is note what you were running at the time. In my experience, two or more applications are vying for the same resource, memory addresses for instance. The OS *should* be protecting resources from contention from multiple applications, but holes occasionally exist. When applications encounter such holes, the OS goes belly-up. For now you should run Disk Utility (Applications> Utilities> Disk Utility), highlight your hard drive, and do a "Verify". If you get any errors, post about it here. My guess is you're probably okay. What to do if it happens again? 1. Note what time your machine crashed. 2. Note what apps you were running. 3. Boot your machine. 4. Run Disk Utility and verify your hard drive. If you're sufficently geek proficient... 5. Open Terminal. 6. Type: less /var/log/system.log You'll get a view of some of the things happening in your machine. To go to the end of the file, type G To move through the file, scroll up and down with the arrow keys. What you're looking for is anything that happened around the time of your system crash. To get out of "less" (the program you're running), type q and it will end. Close the terminal as needed. In closing, you want to discover what caused the crash. With luck it won't happen again. Should it do so, you want to see if you can find the cause. If and when you do, then you can potentially upgrade whatever seems to be broken. When panics are rare, it's tough to find the problems. Good luck! [/QUOTE]
Verification
Post reply
Forums
Apple Computing Products:
macOS - Operating System
Omg, I just had a kernal panic.
Top