[mikellanes]

As you may remember I have been having daily kernel panics for several months, I thought everything was fine for a couple days but it has continued... here are the three latest:

*********

Fri Feb 28 08:07:01 2003


panic(cpu 0): thread_invoke: preemption_level -1

Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x000336EC 0x00033CD0 0x0009235C 0x0061006D
Proceeding back via exception chain:
Exception state (sv=0x1EAF3C80)
PC=0x90073C48; MSR=0x0000F030; DAR=0x02177000; DSISR=0x42000000; LR=0x90005F90; R1=0xBFFFEA90; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

Fri Feb 28 18:33:44 2003


panic(cpu 0): thread_invoke: preemption_level -1

Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x000336EC 0x00033CD0 0x0001EA14 0x00024078 0x00024FC0
0x00092318 0x00410041
Proceeding back via exception chain:
Exception state (sv=0x1EBD3A00)
PC=0x90000E08; MSR=0x0200F030; DAR=0x000F5A60; DSISR=0x0A000000; LR=0x90006164; R1=0xBFFF7650; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

Fri Feb 28 23:24:56 2003


panic(cpu 1): thread_invoke: preemption_level -1

Latest stack backtrace for cpu 1:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x000336EC 0x00033CD0 0x0022D584 0x0022D430
Proceeding back via exception chain:
Exception state (sv=0x2820AA00)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********


I have brought 2 seperate 512MB ram modules (2 different vendors) and these crashes occur on both and 4 older modules i have been using, I have re-installed the OS (10.2.4) twice and still have these problems

I am at a loss, i have removed every piece if extra hardware and my computer is almost useless because im afraid to add anything to it or use it for more than 5 seconds without a crash.

any suggestions other than dumping it in the trash?

[wadesworld]

Do you have an Apple Pro Mouse? I've seen lots of reports of these going bad and causing panics.

If so, replace it with another mouse and see if the panics continue.

If they do, you'll need to find some kind Darwin developer that can translate the backtrace for you and give you a better idea of where they may be coming from.

Additionally, I believe you can startup with the Shift-key held down and that will prevent non-Apple kernel extensions from loading. That'd be something worth trying.

Wade

[JB72]

What kind of hardware is this happening on?

[Gul Banana]

The problem is caused by some sort of threading error, occuring in IOWorkLoop::disableAllInterrupts()
This, along with what you've said, suggests unfortunately that there's something fundamentally screwed with your hardware - possibly at the motherboard level. Try disabling one CPU (the CHUD tools can do it) and see if you keep getting the panics.

[bleuvixen]

are the CHUD tools on the Developer Tools CD?

I had an apple pro mouse but switched to a logitech wi the same results.

Also, could this be my 3rd part CD-RW Drive, for some reason I get several panics in a row when burning a CD & surfing online.

Thanks a lot

[JB72]

Oh man this is scaring me. I have an MDD w/ KPs and I can't seem to track the source. My worst fear is bad hardware.

[mikellanes]

I have now given up, i'm parting out the computer and just got a new one... thanks for all the help

I am/have sold the case and most everythign else online, and the motherboard and processor card to a local mac dealer who wanted to buy them for testing.

Keeping my CDRW and Video card to pop in the new system tonight, i hope its not the CDRW or Video Card!! hahaha

Ill let you know, thanks for all the help thus-far.

[someone_else]

Originally posted by Gul Banana:
The problem is caused by some sort of threading error, occuring in IOWorkLoop::disableAllInterrupts()
This, along with what you've said, suggests unfortunately that there's something fundamentally screwed with your hardware - possibly at the motherboard level. Try disabling one CPU (the CHUD tools can do it) and see if you keep getting the panics.

Yep. In particular, this panic will occur in one of two cases. The thread is holding a spinlock (a non-blocking lock) and tries to aquire a mutux, semaphore or some other blocking lock. Or, the thread tries to aquire one of the latter while interrupts are disabled (this looks to be the case here). Only spinlocks can be aquired while interrupts are disabled.

So, this problem could be bad hardware or a mis-behaving driver. These kinds of lock problems will show up much more frequently on a dual-CPU system so driver vendors should always test on a dualie.

[mikellanes]

new system is up and running fine, so i will see how it goes for the next few weeks!

[JB72]

It looks like we got some good kp log decoding going on here. I'm going to have to dig mine up and post them, hoping for an interpretation.

I can't afford to get another machine. So if it comes down to it I'll have to lock horns with Apple on this one. It's just not acceptable, obviously.

[Gul Banana]

Originally posted by JB72:
It looks like we got some good kp log decoding going on here. I'm going to have to dig mine up and post them, hoping for an interpretation.

Feel free to do so - and if you want, download kpdecode, my utility which can produce a more human-readable stack backtrace from a kernel panic log.

[Visnaut]

Gul, that is such a cool little utility! You should wrap an Applescript Studio app around it and post it on VT under a friendlier name such as "Kernel Panic Decoder" and call it a day. I think a lot of people would be interested in a utility such as this.

In any case, i guess i'll toss in my KP backtraces which i still couldn't decipher. If anyone could shed any further light into them that would be great.

Code:
Thu Feb  6 22:55:56 2003:
        Backtrace 1:
                0x00024968: _mach_msg_overwrite_trap
                0x000257fc: _mach_msg_trap
                0x00092a38: .L_syscall_got_args
                0x006b0065: _rld_env
        Backtrace 2:
                0x000856cc: _print_backtrace
                0x00085afc: _Debugger
                0x000287a8: _panic
                0x0008f588: _trap
                0x00092698: .L_call_trap
        Backtrace 3:
                0x00024968: _mach_msg_overwrite_trap
                0x000257fc: _mach_msg_trap
                0x00092a38: .L_syscall_got_args
                0x006b0065: _rld_env

Code:
Fri Feb  7 00:10:25 2003:
        Backtrace 1:
                0x90334000: CreateShutdownCTXCall
                0x0005f5c0: _vm_fault
                0x0008f884: _trap
                0x00092698: .L_call_trap
        Backtrace 2:
                0x000856cc: _print_backtrace
                0x00085afc: _Debugger
                0x000287a8: _panic
                0x0008f588: _trap
                0x00092698: .L_call_trap
        Backtrace 3:
                0x90334000: CreateShutdownCTXCall
                0x0005f5c0: _vm_fault
                0x0008f884: _trap
                0x00092698: .L_call_trap

And hey! This is my 100th post! Sweet

[JB72]

Thanx Gul.

Here's a couple of my most recent (since my last complete reformat/reinstall .)

Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x38302d32 PC=0x1d680be0
Latest crash info for cpu 1:
Exception state (sv=0x1D619780)
PC=0x1D680BE0; MSR=0x00009030; DAR=0x38302D32; DSISR=0x40000000; LR=0x0003E2C4; R1=0x1606BDD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000407D4 0x0003E2C4 0x0003E1CC
Proceeding back via exception chain:
Exception state (sv=0x1D619780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x271C1C80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

panic(cpu 1): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1D619780)
PC=0x1D680BE0; MSR=0x00009030; DAR=0x38302D32; DSISR=0x40000000; LR=0x0003E2C4; R1=0x1606BDD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000407D4 0x0003E2C4 0x0003E1CC
Exception state (sv=0x271C1C80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

[smeger]

Originally posted by Gul Banana:
Feel free to do so - and if you want, download kpdecode, my utility which can produce a more human-readable stack backtrace from a kernel panic log.

Gul, that's a really cool little utility. If you don't mind me asking, how are you mapping addresses to symbols?

[Gul Banana]

Originally posted by Visnaut:
Gul, that is such a cool little utility! You should wrap an Applescript Studio app around it and post it on VT under a friendlier name such as "Kernel Panic Decoder" and call it a day. I think a lot of people would be interested in a utility such as this.

See below for why I haven't done this yet; thanks for the encouragement, though!

Originally posted by Visnaut:
In any case, i guess i'll toss in my KP backtraces which i still couldn't decipher. If anyone could shed any further light into them that would be great.

Code:
Thu Feb  6 22:55:56 2003:
        Backtrace 1:
                0x00024968: _mach_msg_overwrite_trap
                0x000257fc: _mach_msg_trap
                0x00092a38: .L_syscall_got_args
                0x006b0065: _rld_env
        Backtrace 2:
                0x000856cc: _print_backtrace
                0x00085afc: _Debugger
                0x000287a8: _panic
                0x0008f588: _trap
                0x00092698: .L_call_trap
        Backtrace 3:
                0x00024968: _mach_msg_overwrite_trap
                0x000257fc: _mach_msg_trap
                0x00092a38: .L_syscall_got_args
                0x006b0065: _rld_env

Urg. That one's the hardest kind.. a generic "something went wrong". It happened somewhere that the kernel doesn't have direct access to.. all I can say is that it's probably not a driver, and the most likely thing is a bug in some application. Possibly.

Originally posted by Visnaut:

Code:
Fri Feb  7 00:10:25 2003:
        Backtrace 1:
                0x90334000: CreateShutdownCTXCall
                0x0005f5c0: _vm_fault
                0x0008f884: _trap
                0x00092698: .L_call_trap
        Backtrace 2:
                0x000856cc: _print_backtrace
                0x00085afc: _Debugger
                0x000287a8: _panic
                0x0008f588: _trap
                0x00092698: .L_call_trap
        Backtrace 3:
                0x90334000: CreateShutdownCTXCall
                0x0005f5c0: _vm_fault
                0x0008f884: _trap
                0x00092698: .L_call_trap

And hey! This is my 100th post! Sweet

Sounds like bad RAM (the vm_fault() calls) though hopefully that's not the case. Do try swapping out RAM if you can, though, and see if it keeps happening. Also, how much hard drive space do you have free?

Originally posted by JB72:
Thanx Gul.

Here's a couple of my most recent (since my last complete reformat/reinstall .)

Unfortunately, I need the full log to be able to help you - without knowing, for example, what kernel version you're using, kpdecode won't work and doing it manually may not either.

Originally posted by smeger:
Gul, that's a really cool little utility. If you don't mind me asking, how are you mapping addresses to symbols?

In a really hackish way This is the primary reason kpdecode is still in alpha - it calls nm on mach_kernel and any loadable modules in the backtrace, runs the output through c++filt and grep, sorts the symbols by address, and finds the location of each tracepoint by taking the first symbol _before_ the tracepoint's address, since it must have been in that function. Due to this,
a) It's very slow
b) It won't work unless you have both the BSD subsystem (for grep) and the developer tools (for nm and c++filt) installed.
But, it works.

[JB72]

OK here's the "director's cut" kp log:

Fri Feb 28 17:39:58 2003




Unresolved kernel trap(cpu 1): 0x300 - Data access DAR=0x38302d32 PC=0x1d680be0
Latest crash info for cpu 1:
Exception state (sv=0x1D619780)
PC=0x1D680BE0; MSR=0x00009030; DAR=0x38302D32; DSISR=0x40000000; LR=0x0003E2C4; R1=0x1606BDD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000407D4 0x0003E2C4 0x0003E1CC
Proceeding back via exception chain:
Exception state (sv=0x1D619780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x271C1C80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 1): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1D619780)
PC=0x1D680BE0; MSR=0x00009030; DAR=0x38302D32; DSISR=0x40000000; LR=0x0003E2C4; R1=0x1606BDD0; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x000407D4 0x0003E2C4 0x0003E1CC
Exception state (sv=0x271C1C80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

Sat Mar 1 08:54:19 2003




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000010 PC=0x00076058
Latest crash info for cpu 0:
Exception state (sv=0x271B3780)
PC=0x00076058; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x0007602C; R1=0x1617BB80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0007602C 0x00076920 0x0006E5E4 0x0006DFA0 0x00065C60 0x00065EB4 0x0003857C 0x001DB0F0
0x001DAF84 0x0020E59C 0x00092110 0x6572636F
Proceeding back via exception chain:
Exception state (sv=0x271B3780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x27CF6280)
PC=0x900058CC; MSR=0x0000D030; DAR=0x018544A8; DSISR=0x40000000; LR=0x000039C8; R1=0xBFFFFE30; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x0008EE68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x271B3780)
PC=0x00076058; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x0007602C; R1=0x1617BB80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0007602C 0x00076920 0x0006E5E4 0x0006DFA0 0x00065C60 0x00065EB4 0x0003857C 0x001DB0F0
0x001DAF84 0x0020E59C 0x00092110 0x6572636F
Exception state (sv=0x27CF6280)
PC=0x900058CC; MSR=0x0000D030; DAR=0x018544A8; DSISR=0x40000000; LR=0x000039C8; R1=0xBFFFFE30; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

TIA.

[JB72]

Oh joy I got a new one!

Tue Mar 4 16:26:46 2003




Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000010 PC=0x00076058
Latest crash info for cpu 0:
Exception state (sv=0x271E8280)
PC=0x00076058; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x0007602C; R1=0x16143B20; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x0007602C 0x00076920 0x0006E5E4 0x0006DFA0 0x00065C60 0x00065EB4 0x000548BC 0x0002A28C
0x00024C00 0x00024FFC 0x00092318 0xA1B1C1D3
Proceeding back via exception chain:
Exception state (sv=0x271E8280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1D607280)
PC=0x90073C28; MSR=0x0200F030; DAR=0x00AD7000; DSISR=0x40000000; LR=0x90005F70; R1=0xBFFEF360; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC


panic(cpu 1): simple lock deadlock detection - l=0031E10C, cpu=1, ret=03672EF4
Latest stack backtrace for cpu 1:
Backtrace:
0x00084FAC 0x000853DC 0x00027FA8 0x00076150 0x0005EB94 0x0008ED68 0x00091F78
Proceeding back via exception chain:
Exception state (sv=0x1DAABA00)
PC=0x00092F1C; MSR=0x00009030; DAR=0xE0147000; DSISR=0x42000000; LR=0x00091DA4; R1=0x1612BC30; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x00067C14 0x0001DA44 0x0001DC30 0x00023F4C 0x000240C4 0x0001E760
Exception state (sv=0x1D698C80)
PC=0x90073C28; MSR=0x0000F030; DAR=0x1612BB98; DSISR=0x40000000; LR=0x90005F70; R1=0xBFFFF7B0; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.4:
Wed Jan 29 18:50:42 PST 2003; root:xnu/xnu-344.26.obj~1/RELEASE_PPC



*********

! !

OK now my 1024 MB Corsair XMS is out and a fresh 512 MB Crucial was popped in.

*fingers crossed*