Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > macOS > Kernel panic readers, please come

Kernel panic readers, please come
Thread Tools
Xeo
Moderator Emeritus
Join Date: Mar 2001
Location: Austin, MN, USA
Status: Offline
Reply With Quote
Mar 17, 2005, 02:37 AM
 
I've gotten 3 kernel panics recently. They bother me. Twice has been in the middle of a video game. Once was when I wasn't at the computer at all. I suspect it is my firewire enclosure but don't know how to tell from these. Anyone help? I will just keep my firewire enclosure unplugged when I don't need it if that's the cause.

[edit] Just noticed, they all happened near midnight.

The decoded panics:
Code:
Fri Mar 11 21:28:27 2005: Backtrace 1: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler Backtrace 2: 0x000835f8: _print_backtrace 0x00083adc: _Debugger 0x0001eda4: _panic 0x00090bd8: _trap 0x00093fcc: _thandler Backtrace 3: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler Mon Mar 14 21:52:48 2005: Backtrace 1: 0x002341cc: _soisdisconnected 0x0011ee74: _tcp_close 0x0012009c: _tcp_timers 0x0011ffa4: _tcp_slowtimo 0x0022d298: _pfslowtimo 0x000355ac: _call_thread_unblock 0x0003548c: _call_thread_unblock Backtrace 2: 0x000835f8: _print_backtrace 0x00083adc: _Debugger 0x0001eda4: _panic 0x00090bd8: _trap 0x00093fcc: _thandler Backtrace 3: 0x002341cc: _soisdisconnected 0x0011ee74: _tcp_close 0x0012009c: _tcp_timers 0x0011ffa4: _tcp_slowtimo 0x0022d298: _pfslowtimo 0x000355ac: _call_thread_unblock 0x0003548c: _call_thread_unblock Thu Mar 17 00:19:04 2005: Backtrace 1: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler 0x5e6766e9: _libsa_builder Backtrace 2: 0x000835f8: _print_backtrace 0x00083adc: _Debugger 0x0001eda4: _panic 0x00090bd8: _trap 0x00093fcc: _thandler Backtrace 3: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler 0x5e6766e9: _libsa_builder
From:
Code:
Fri Mar 11 21:28:27 2005 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FADEDFAD PC=0x0000000000236E50 Latest crash info for cpu 0: Exception state (sv=0x25ED6A00) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x122F3D90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x00000000 Proceeding back via exception chain: Exception state (sv=0x25ED6A00) previously dumped as "Latest" state. skipping... Exception state (sv=0x25301780) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE07B2000; DSISR=0x42000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC panic(cpu 0): copyin/out has no recovery point Latest stack backtrace for cpu 0: Backtrace: 0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC Proceeding back via exception chain: Exception state (sv=0x25ED6A00) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x122F3D90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x00000000 Exception state (sv=0x25301780) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE07B2000; DSISR=0x42000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC ********* Mon Mar 14 21:52:48 2005 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000008AECE90A PC=0x000000000098EFA0 Latest crash info for cpu 0: Exception state (sv=0x25277280) PC=0x0098EFA0; MSR=0x00009030; DAR=0x8AECE90A; DSISR=0x42000000; LR=0x002341CC; R1=0x120FBC20; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00000000 0x002341CC 0x0011EE74 0x0012009C 0x0011FFA4 0x0022D298 0x000355AC 0x0003548C Proceeding back via exception chain: Exception state (sv=0x25277280) previously dumped as "Latest" state. skipping... Exception state (sv=0x25170280) PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC panic(cpu 0): 0x300 - Data access Latest stack backtrace for cpu 0: Backtrace: 0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC Proceeding back via exception chain: Exception state (sv=0x25277280) PC=0x0098EFA0; MSR=0x00009030; DAR=0x8AECE90A; DSISR=0x42000000; LR=0x002341CC; R1=0x120FBC20; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00000000 0x002341CC 0x0011EE74 0x0012009C 0x0011FFA4 0x0022D298 0x000355AC 0x0003548C Exception state (sv=0x25170280) PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC ********* Thu Mar 17 00:19:04 2005 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FADEDFAD PC=0x0000000000236E50 Latest crash info for cpu 0: Exception state (sv=0x255BC000) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x121CBD90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x5E6766E9 Proceeding back via exception chain: Exception state (sv=0x255BC000) previously dumped as "Latest" state. skipping... Exception state (sv=0x256D1A00) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE078E9C0; DSISR=0x42000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC panic(cpu 0): copyin/out has no recovery point Latest stack backtrace for cpu 0: Backtrace: 0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC Proceeding back via exception chain: Exception state (sv=0x255BC000) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x121CBD90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x5E6766E9 Exception state (sv=0x256D1A00) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE078E9C0; DSISR=0x42000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC
     
forkies
Mac Elite
Join Date: Apr 2001
Location: Frickersville
Status: Offline
Reply With Quote
Mar 17, 2005, 07:50 AM
 
looks like you're lettin your silters run free. close the door to keep em inside. that might fix the problem

Mystical, magical, amazing! | Part 2 | The spread of Christianity is our goal. -Railroader
     
Xeo  (op)
Moderator Emeritus
Join Date: Mar 2001
Location: Austin, MN, USA
Status: Offline
Reply With Quote
Mar 18, 2005, 04:06 AM
 
Same thing. This one and the other two that look just like it are all while playing Starcraft. I also had my FW enclosure plugged in during all these. I need to keep it unplugged now to see if I get this one again without it.
Code:
Fri Mar 18 02:02:29 2005: Backtrace 1: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler 0x2fe634f2: _libsa_builder Backtrace 2: 0x000835f8: _print_backtrace 0x00083adc: _Debugger 0x0001eda4: _panic 0x00090bd8: _trap 0x00093fcc: _thandler Backtrace 3: 0x00236d6c: _sendmsg 0x0023734c: _recvmsg 0x002463e4: _unix_syscall 0x00094160: _shandler 0x2fe634f2: _libsa_builder
And from here:
Code:
Fri Mar 18 02:02:29 2005 Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FADEDFAD PC=0x0000000000236E50 Latest crash info for cpu 0: Exception state (sv=0x258F7280) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x121A3D90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x2FE634F2 Proceeding back via exception chain: Exception state (sv=0x258F7280) previously dumped as "Latest" state. skipping... Exception state (sv=0x33832280) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE078E9C0; DSISR=0x40000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC panic(cpu 0): copyin/out has no recovery point Latest stack backtrace for cpu 0: Backtrace: 0x000835F8 0x00083ADC 0x0001EDA4 0x00090BD8 0x00093FCC Proceeding back via exception chain: Exception state (sv=0x258F7280) PC=0x00236E50; MSR=0x00009030; DAR=0xFADEDFAD; DSISR=0x40000000; LR=0x00236D6C; R1=0x121A3D90; XCP=0x0000000C (0x300 - Data access) Backtrace: 0x00236D6C 0x0023734C 0x002463E4 0x00094160 0x2FE634F2 Exception state (sv=0x33832280) PC=0x9000A8CC; MSR=0x0000D030; DAR=0xE078E9C0; DSISR=0x40000000; LR=0x906142F0; R1=0xF078E880; XCP=0x00000030 (0xC00 - System call) Kernel version: Darwin Kernel Version 7.8.0: Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC
     
Detrius
Professional Poster
Join Date: Apr 2001
Location: Asheville, NC
Status: Offline
Reply With Quote
Mar 19, 2005, 11:28 AM
 
I would start by suspecting bad RAM. Run the Apple Hardware Test. If it doesn't tell you anything, pull out the RAM modules one at a time (replacing them as you pull out a different one) and see if you can get the machine to stop crashing this way.

If the FireWire hard drive were related, you would likely see a reference to FireWire in the panic.log.

If you haven't already read it, now would be a good time to check this out: http://forums.macnn.com/showthread.p...hreadid=248286
ACSA 10.4/10.3, ACTC 10.3, ACHDS 10.3
     
Xeo  (op)
Moderator Emeritus
Join Date: Mar 2001
Location: Austin, MN, USA
Status: Offline
Reply With Quote
Mar 19, 2005, 11:54 PM
 
I doubt it's the RAM. I have an iBook and have a 512 MB chip. This RAM is accessed all the time since OS X itself can easily take up the initial 256. Other apps, including PS, use this RAM all the time. I would surely see a more consistent occurrence of this if that was the case.

The game in question is StarCraft. Is there any way an individual piece of software can bring down OS X? I thought it is more protected than that. That is why I suspected FW. But I was also surprised that there is no mention of FW in the log.
     
theolein
Addicted to MacNN
Join Date: Feb 2001
Location: zurich, switzerland
Status: Offline
Reply With Quote
Mar 20, 2005, 12:20 AM
 
Those logs don't really say much. The only thing i can make out is specific registers and memory addresses. I also think it might be RAM.
weird wabbit
     
Detrius
Professional Poster
Join Date: Apr 2001
Location: Asheville, NC
Status: Offline
Reply With Quote
Mar 20, 2005, 01:09 AM
 
Originally posted by Xeo:
The game in question is StarCraft. Is there any way an individual piece of software can bring down OS X? I thought it is more protected than that. That is why I suspected FW. But I was also surprised that there is no mention of FW in the log.
Only the kernel and kernel extensions can bring down the OS. Technically, some firewire device probably could bring down the OS, but it would be possible to write the drivers to avoid this (recognizing a faulty device and either turning off the bus, or ignoring the device).

An application like StarCraft cannot bring down the system, as there are no kernel extensions associated with StarCraft. However, this is likely stressing the system differently than PS.

Do random applications quit on you on a semi-regular basis?
ACSA 10.4/10.3, ACTC 10.3, ACHDS 10.3
     
Cadaver
Addicted to MacNN
Join Date: Jan 2003
Location: ~/
Status: Offline
Reply With Quote
Mar 20, 2005, 01:23 PM
 
If its just games, could it be the video drivers or Core Audio libraries (which are kernel extensions, I believe) are screwed?
     
Detrius
Professional Poster
Join Date: Apr 2001
Location: Asheville, NC
Status: Offline
Reply With Quote
Mar 20, 2005, 05:28 PM
 
Originally posted by Cadaver:
If its just games, could it be the video drivers or Core Audio libraries (which are kernel extensions, I believe) are screwed?
The only issue with this theory is that it should show up in the panic.log to have been at least caused by that driver.
ACSA 10.4/10.3, ACTC 10.3, ACHDS 10.3
     
paul w
Mac Elite
Join Date: Feb 2005
Location: Vente: Achat
Status: Offline
Reply With Quote
Mar 22, 2005, 09:01 AM
 
I'll try this thread before starting my own.

Out of nowhere I started getting kp's, except there weren't any logs of them. This was very similar to the big GUI freeze problem a while back, except I'd get the text on the left side of the display and a frozen system. No elegant "You need to restart.." message. Until today. I'd appreciate ANY help.

Tue Mar 22 13:53:50 2005


panic(cpu 0): Uncorrectable machine check: pc = 000000000008C084, msr = 0000000000141000, dsisr = 42000000, dar = 000000000809B000
AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000
L2FIR = 0000000000000000, BusFir = 0000000000000000

Latest stack backtrace for cpu 0:
Backtrace:
0x000835F8 0x00083ADC 0x0001EDA4 0x000915AC 0x00090898 0x00093FCC
Proceeding back via exception chain:
Exception state (sv=0x32F1D780)
PC=0x0008C084; MSR=0x00141000; DAR=0x0809B000; DSISR=0x42000000; LR=0x00089E80; R1=0x11E7BC80; XCP=0x00000008 (0x200 - Machine check)
Backtrace:
0x0002B310 0x00086590 0x00073310 0x0006D0C0 0x0006DD1C 0x0006DCF8
Exception state (sv=0x00970000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 7.8.0:
Wed Dec 22 14:26:17 PST 2004; root:xnu/xnu-517.11.1.obj~1/RELEASE_PPC

Now I know the drill, the steps to take and so on. I've been here before, sadly. But I was hoping someone could shed some light into what the panic actually MEANS.

Thanks,

Paul
     
Detrius
Professional Poster
Join Date: Apr 2001
Location: Asheville, NC
Status: Offline
Reply With Quote
Mar 22, 2005, 12:10 PM
 
Originally posted by paul w:
I'll try this thread before starting my own.

Out of nowhere I started getting kp's, except there weren't any logs of them. This was very similar to the big GUI freeze problem a while back, except I'd get the text on the left side of the display and a frozen system. No elegant "You need to restart.." message. Until today. I'd appreciate ANY help.

...

Now I know the drill, the steps to take and so on. I've been here before, sadly. But I was hoping someone could shed some light into what the panic actually MEANS.

Thanks,

Paul
In general, it's a really bad sign if the panic.log doesn't get written. I'm leaning towards logic board/processor on this one, due to the "Uncorrectable machine check." Sometimes, the IDE bus or hard drive just flat out dies on you, but that would have been aparent from the log--which it isn't in this case.
ACSA 10.4/10.3, ACTC 10.3, ACHDS 10.3
     
paul w
Mac Elite
Join Date: Feb 2005
Location: Vente: Achat
Status: Offline
Reply With Quote
Mar 22, 2005, 12:33 PM
 
that's what I was afraid of/suspecting. Well, I'll go through the basics, backup my hd and give Apple a call.
     
   
Thread Tools
 
Forum Links
Forum 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
Top
Privacy Policy
All times are GMT -4. The time now is 07:45 AM.
All contents of these forums © 1995-2017 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.8 © 2000-2017, Jelsoft Enterprises Ltd.,