Welcome to the MacNN Forums.

goose · May 6, 2003, 02:03 PM

Hey all,

Been having this issue that just started yesterday. I get a kernel panic 31 minutes after logging in. I've already had four crashes today in roughly two hours (9:41 - 11:53).

I've read threads about USB and bad RAM, however, I've been with this set up for a while. The only "major" changes are two years ago I added a USB hub and one month ago I added a Bluetooth dongle. From the beginning (three and a half years ago), I changed to an Adesso keyboard and a Kensington trackball.

The only time I've had a kernel panic prior to the past two days is when I was running the public beta.

Okay, I do admit to running into a Bluetooth issue a day or two before I started getting these kernel panics, but I don't know if that's coincidental or not. When I first plugged in the Bluetooth dongle, everything was fine. I was able to sync without any problems and what not.

A few days ago, it stopped working and even after a couple reboots, it still didn't work. I turned off Bluetooth through the Bluetooth menu and when I did that, the menu widget things got (sound volume, iSync and the clock) hung up (spinning ball when the mouse went over them) as well as the Addressbook.

After rebooting and logging in, the Bluetooth menu stopped showing up and the rest of the menu widgets were hung as well as the Addressbook. I took the Addressbook out of my login items and after a reboot, the Bluetooth menu showed up. I was able to turn Bluetooth on again and iSync worked, but the Addressbook still got the spinning ball after launching. However, after several reboots, the systems was back ot "normal" (Addressbook working and all).

Everything was working for at least a day; my phone and my wife's phone had no problems syncing up. Then one day later, kernel panics. It's bad enough that I run a stop watch next to my keyboard so I can see when it's about 30 minutes so I can save all my work and close all the running apps, wait for the kernel panic and reboot.

Any thoughts?

MasonMcD · May 6, 2003, 03:35 PM

What do your console error messages say?

CheesePuff · May 6, 2003, 03:53 PM

Mac OS X 10.2.6 update (released today) says it fixes kernal panic problems that were very apparent in the OS X 10.2.5 version.

goose · May 6, 2003, 04:09 PM

Thanks for the help........

Where would I get older console.log files? The one that's /private/var/tmp/console.log only has info after the reboot. Here is my kernel panic log thing from the system profiler. Looks like some kinda USB thing, but I've been using all my USB devices for over a year and there have been no changes other than the Bluetooth dongle, but that was a month ago.

Hmmm 10.2.6, I will try to install that and hopefully, things will get back to normal.

BTW, I tried unplugging the Bluetooth dongle, but I still got the kernel panic.

Same kernel panic info for these times today

Tue May 6 09:48:27 2003
Tue May 6 10:38:55 2003
Tue May 6 11:12:35 2003
Tue May 6 11:48:44 2003
Tue May 6 12:22:36 2003
Tue May 6 12:58:44 2003

----------------------------------

Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000002c PC=0x1554a248
Latest crash info for cpu 0:
Exception state (sv=0x154F9C80)
PC=0x1554A248; MSR=0x00009030; DAR=0x0000002C; DSISR=0x40000000; LR=0x15540444; R1=0x0DA4BC80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000001 0x15540444 0x15A2E684 0x15A2F478 0x15A2F2E8 0x0003EED0 0x0003EDD8
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBHub(1.9.9f6)@0x15a29000
dependency: com.apple.iokit.IOUSBFamily(1.9.8)@0x1553d000
com.apple.iokit.IOUSBFamily(1.9.8)@0x1553d000
Proceeding back via exception chain:
Exception state (sv=0x154F9C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x154AFC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.5:
Mon Apr 7 17:05:38 PDT 2003; root:xnu/xnu-344.32.obj~1/RELEASE_PPC

panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00085C1C 0x0008604C 0x00028BB4 0x0008FAC8 0x00092BD8
Proceeding back via exception chain:
Exception state (sv=0x154F9C80)
PC=0x1554A248; MSR=0x00009030; DAR=0x0000002C; DSISR=0x40000000; LR=0x15540444; R1=0x0DA4BC80; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000001 0x15540444 0x15A2E684 0x15A2F478 0x15A2F2E8 0x0003EED0 0x0003EDD8
Kernel loadable modules in backtrace (with dependencies):
com.apple.driver.AppleUSBHub(1.9.9f6)@0x15a29000
dependency: com.apple.iokit.IOUSBFamily(1.9.8)@0x1553d000
com.apple.iokit.IOUSBFamily(1.9.8)@0x1553d000
Exception state (sv=0x154AFC80)
PC=0x00000000; MSR=0x0000D030; DAR=0x00000000; DSISR=0x00000000; LR=0x00000000; R1=0x00000000; XCP=0x00000000 (Unknown)

Kernel version:
Darwin Kernel Version 6.5:
Mon Apr 7 17:05:38 PDT 2003; root:xnu/xnu-344.32.obj~1/RELEASE_PPC

----------------------------------

pat++ · May 6, 2003, 05:10 PM

I bet 10.2.6 will fix your issue.

goose · May 6, 2003, 11:53 PM

Well, it seems that 10.2.6 addresses the kernel panics I was having. *crossing fingers* Funny how I just started having issue though. I guess that's Apple's way of insuring you update the system.