[mikellanes]

Hey all,

I have been having a lot of kernel panics latley, haven't added anything new or any new software, here is the KP text

------
panic(cpu 0): thread_invoke: preemption_level -1

Latest stack backtrace for cpu 0:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x00033EEC 0x000345BC 0x00024F58 0x000257FC 0x00092A38
0x00000000
Proceeding back via exception chain:
Exception state (sv=0x27049780)
PC=0x90073C48; MSR=0x0000F030; DAR=0x025D1B73; DSISR=0x00002017; LR=0x90005F90; R1=0xBFFFAA50; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC
-----

anything you can make out of that?

any help would be appreciated as this once usable machine is now very unstable

[mikellanes]

I used the CLI program "kpdecode"

and this is what it says...

Tue Jan 14 20:16:37 2003:
Backtrace 1:
0x000856cc: Symbol not found!
0x00085afc: Symbol not found!
0x000287a8: Symbol not found!
0x00033eec: Symbol not found!
0x000345bc: Symbol not found!
0x00024f58: Symbol not found!
0x000257fc: Symbol not found!
0x00092a38: Symbol not found!


can anyone decipher that?!? LOL

[Hash]

After I had same experience and wrote about that, immediately some popped up and declared that they had troublefree mac os x for 2 years without single use of utilities and claimed i'm a troll

[mikellanes]

that sucks

how did you do, are you currently having problems? or did you get it worked out?

I don't know what to try next, the panics seem so random that i cant re-create them with the same steps...

[MacGorilla]

Same here: here is my back trace for the two I had today:

ue Jan 14 09:25:28 2003:
Backtrace 1:
0x02881650: _rld_env
0x0022e744: IOInterruptEventSource::enable()
0x0022e8b8: IOInterruptEventSource::checkForWork()
0x0022d744: IOWorkLoop::threadMain()
0x0022d6b0: IOWorkLoop::disableAllInterrupts() const
Backtrace 2:
0x000856cc: _print_backtrace
0x00085afc: _Debugger
0x000287a8: _panic
0x0008f588: _trap
0x00092698: .L_call_trap
Backtrace 3:
0x02881650: _rld_env
0x0022e744: IOInterruptEventSource::enable()
0x0022e8b8: IOInterruptEventSource::checkForWork()
0x0022d744: IOWorkLoop::threadMain()
0x0022d6b0: IOWorkLoop::disableAllInterrupts() const
Tue Jan 14 17:12:13 2003:
Backtrace 1:
0x001e5ac0: __sleep_continue
0x001e5a88: _hashinit
Backtrace 2:
0x000856cc: _print_backtrace
0x00085afc: _Debugger
0x000287a8: _panic
0x0008f588: _trap
0x00092698: .L_call_trap
Backtrace 3:
0x001e5ac0: __sleep_continue
0x001e5a88: _hashinit

[Hash]

As for kpdecode, its creator, Gul Banana from MacNN, said me that you must have developer tools installed but he working on non-developer tools version as well.

I really appreciate his feedback and his efforts to help to help fellow mac users. Its so unlike some apologetists like some useless piece of sh*t called edddef*ck.

[Gul Banana]

mikellanes, Hash is correct, currently for kpdecode to work you must have the Developer Tools installed. I copied your log and ran it for you, but unfortunately the results are not too helpful:

0x000856cc: _print_backtrace
0x00085afc: _Debugger
0x000287a8: _panic
0x00033eec: _thread_invoke
0x000345bc: _thread_run
0x00024f58: _mach_msg_overwrite_trap
0x000257fc: _mach_msg_trap
0x00092a38: .L_syscall_got_args

MacGorilla's problem is a device driver, but the only thing I can tell about yours is that it has something to do with threading - a guess: have you been renicing anything lately? Something appears to be trying to run at a priority level that doesn't exist.

[moki]

The majority of kernel panics are the result of faulty RAM -- I'd suggest swapping your RAM modules out, and seeing if that doesn't solve it.

The next most likely thing is if you installed a third-party kernel extension that isn't functioning properly.

I'd place my bets on the bad RAM, though.

[Gul Banana]

In mikellanes' case it's definitely not a malfunctioning kernel extension; the entirety of the backtrace is within mach itself. There's nothing to suggest that it isn't bad RAM, though, which is just as common a cause as moki says it is. Mind you, there's nothing to suggest it IS; I'd expect to see at least a few _pmap_whatevers in there.
Hypothesis: Bad RAM causes random data to exist where it's expecting the thread priority; this data happens to be an invalid priority and kernel goes BOOM.

[mikellanes]

Hmm, I checked for any installed extras and the only thing I have installed was USB overdrive, which I don't really need, so that is removed, everthing else is stock.
(Edit: I now see you said it WASN'T a ktext, thanks

This machine was always runing Mac OS 9, with the same RAM for almost a year (I believe)
Very infrequent crashes, and the ram is all from crucial.com...

I ram DIMM First Aid in OS 9 and it all checks out OK.

Any way to force-check the RAM in OSX?
or would Tech Tool Pro's RAM check reveal anything?

I guess what im asking is how can I know if its the RAM? beside swapping out 1 of the 3 and so on... since these panics aren't super-frequent it would take a while

[Avon]

Originally posted by mikellanes:
Hmm, I checked for any installed extras and the only thing I have installed was USB overdrive, which I don't really need, so that is removed, everthing else is stock.
(Edit: I now see you said it WASN'T a ktext, thanks

The second most comon cause of Kernel panics is USB. Unplug all your usb devices and make sure your keyboard is on a diffrent bus as your modem. Use the ASP to make sure.

If it stops crashing, plug usb devices in one by one and find the culprit.

Also, get rid of that 3rd party usb stuff...

[mikellanes]

Hmm, does anyone else think the USB is the culprit?

I recently got a Kensington Studio Mouse Wireless and Re-Arranged ALL my USB stuff, as of now here is how its layed out.

BUS 0>Modem
Studio Mouse
Hub (Cinema Display)
>Keyboard
>SoundSticks
BUS 1>EPSON USB Printer

im going to rearrange now...

[mikellanes]

alright got it straightened out, with use of a USB hub the modem & keyboard are once again separated, and the rest is evened out on a bandwith/power/usage basis

I will run like this and see how it goes

thanks everyone for their help! and I appreciate all the work just for lil old me

[p.s. would it be wise to get a USB card (2.0?) since I seem to have a lot of USB devices, and spare PCI slots...]

[BTP]

I recently solved serious kernel panics when I replaced the RAM. Problem solved.

[moki]

Originally posted by mikellanes:
This machine was always runing Mac OS 9, with the same RAM for almost a year (I believe)
Very infrequent crashes, and the ram is all from crucial.com...

I ram DIMM First Aid in OS 9 and it all checks out OK.

Right, i had the same problem on my machine. It worked Ok with OS 9, but that's because OS 9 is much, much less stressful on RAM.

My machine would randomly kernel panic for no apparent reason, on a clean OS install. It turned out to be a DIMM that wasn't up to snuff. Once it was removed, it was clear sailing.

Just because it worked okay under OS 9 doesn't mean you don't have a defective DIMM.

[Hash]

Moki, didnt you write yesterday that in 2 years you never had crashes in OS X?

[mikellanes]

Ah another day, another KP

here is the one from this morning:

-----
Wed Jan 15 07:01:27 2003


panic(cpu 0): simple lock deadlock detection - l=002E6794, cpu=0, ret=5A2F39D2
Latest stack backtrace for cpu 0:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x0003E59C 0x1E6B0A34 0x1E6B30E8 0x1E6B2EB8 0x00247474
0x00092A38 0xA3A6B195
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.3.1)@0x1e6a5000
Proceeding back via exception chain:
Exception state (sv=0x1E977000)
PC=0x90497608; MSR=0x0200F030; DAR=0x170BBB48; DSISR=0x40000000; LR=0x94D83C94; R1=0xF0182A60; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC

-----

looks a little different than the previous ones...
perhaps because I unplugged & re-plugged my soundsticks in to a different port?

I have re-booted and ill leave this running today and see what happens next..

Gul Banana, Thanks for all your help

Moki, I will start popping RAM modules once im sure it wasn't the USB acting up. (or me for being stupid with the USB modules) Thanks!

[edddeduck]

Have you tried Apple's Hardware Test Disk (If you got one) This has a fairly thorough RAM Checker in it.

Dunno if this helps.

Cheers Edwin

[Gul Banana]

Originally posted by mikellanes:
Ah another day, another KP

here is the one from this morning:

-----
Wed Jan 15 07:01:27 2003


panic(cpu 0): simple lock deadlock detection - l=002E6794, cpu=0, ret=5A2F39D2
Latest stack backtrace for cpu 0:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x0003E59C 0x1E6B0A34 0x1E6B30E8 0x1E6B2EB8 0x00247474
0x00092A38 0xA3A6B195
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOAudioFamily(1.3.1)@0x1e6a5000
Proceeding back via exception chain:
Exception state (sv=0x1E977000)
PC=0x90497608; MSR=0x0200F030; DAR=0x170BBB48; DSISR=0x40000000; LR=0x94D83C94; R1=0xF0182A60; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC

-----

looks a little different than the previous ones...
perhaps because I unplugged & re-plugged my soundsticks in to a different port?

I have re-booted and ill leave this running today and see what happens next..

Gul Banana, Thanks for all your help

Moki, I will start popping RAM modules once im sure it wasn't the USB acting up. (or me for being stupid with the USB modules) Thanks!

This one is very definitely the soundsticks.

Wed Jan 15 07:01:27 2003 :
Backtrace 1:
0x000856cc: _print_backtrace
0x00085afc: _Debugger
0x000287a8: _panic
0x0003e59c: _thread_call_enter1_delayed
0x1e6b0a34: IOAudioEngineUserClient::initWithAudioEngine(IOAud ioEngine*, task*, void*, unsigned long)
0x1e6b30e8: IOAudioLevelControl::_RESERVEDIOAudioLevelControl9 ()
0x1e6b2eb8: IOAudioLevelControl::IOAudioLevelControl[in-charge]()
0x00247474: _iokit_user_client_trap
0x00092a38: .L_syscall_got_args

As you can see, the panic occurred when trying to set the volume of aforesaid speakers... I guess the only solution is "Don't switch them between ports"

[mikellanes]

Gul Banana,

hmm, must have been when my screensaver came on? (it does have sound) because it was fine when i went to bed :-)

Ok at least that clears that up, ill see if anyothers happen...

Ill try running the Apple hardware test CD tonight.
Ive since pulled all but 1 DIMM of Ram im fairly sure was good.

If its still runing when I get home at least ill know that chip is OK.


Thanks again

[mikellanes]

Have had 3 panics all the same

------
Sat Jan 18 11:28:38 2003


panic(cpu 0): simple lock deadlock detection - l=002E6794, cpu=0, ret=00000001
Latest stack backtrace for cpu 0:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x0003E1D0 0x1E8676C0 0x1E867648 0x0022EF58 0x1E867620
0x1E870AF8 0x1E85E6A8 0x1E85844C 0x1E71FBB8 0x1E71FA24 0x2802B650 0x28093930 0x280935F0
0x28094898 0x28094A48 0x0022E888 0x0022D744 0x0022D6B0
Kernel loadable modules in backtrace (with dependencies):
com.apple.iokit.IOUSBHIDDriver(1.9.5)@0x1e71d000
dependency: com.apple.iokit.IOUSBFamily(1.9.5)@0x28029000
dependency: com.apple.iokit.IOHIDFamily(1.2.1)@0x1e854000
com.apple.driver.AppleUSBOHCI(1.9.4)@0x28090000
dependency: com.apple.iokit.IOPCIFamily(1.2)@0x1e701000
dependency: com.apple.iokit.IOUSBFamily(1.9.5)@0x28029000
com.apple.iokit.IOUSBFamily(1.9.5)@0x28029000
com.apple.iokit.IOHIDFamily(1.2.1)@0x1e854000
Proceeding back via exception chain:
Exception state (sv=0x02015000)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC
------

Damn USB

Would getting a USB PCI Card help with some of the problems im seeing? or is it a bad USB port?

I think the problem is the modem, seems to be panicking when im online, luckily Cable access will be avilable in a few weeks so i can pull that damn modem

[Jerommeke]

I'm having kernel panic regurly when mounting/searching/connecting/etc. to the SMB Winodws machines on my network. I am fully sure that is the cause, because:
1. it happens only then
2. this situation is new, before I was in another environment without SMB drives, and I had no kp's at all.
3. there are some words in the panic.log which let me think it has something to do with it.

But I submitted it to Apple HQ

[Gul Banana]

mikellanes: I don't suppose you use any force feedback devices, do you?

[mikellanes]

no, only: Soundsticks, Mouse & USB printer

[mikellanes]

And a new unrelated one this morning

*********

Sun Jan 19 09:35:55 2003


panic(cpu 1): thread_invoke: preemption_level -1

Latest stack backtrace for cpu 1:
Backtrace:
0x000856CC 0x00085AFC 0x000287A8 0x00033EEC 0x000344D0 0x00027954 0x000277EC 0x00092A38
0x003E000A
Proceeding back via exception chain:
Exception state (sv=0x1EAAEC80)
PC=0x90006AE8; MSR=0x0000F030; DAR=0xE0147000; DSISR=0x42000000; LR=0x900067EC; R1=0xF008F410; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.3:
Sat Dec 14 03:11:25 PST 2002; root:xnu/xnu-344.23.obj~4/RELEASE_PPC



*********

[Cipher13]

I call bad RAM.