Welcome to the MacNN Forums.

Freeflyer · Mar 9, 2003, 11:31 PM

Hi,

My Tibook recently went back to apple to have a hinge replaced. In the week since it came back, there have been 3 occasions where after waking from sleep, there have been a few seconds pause and then the screen dims and a box with a message saying that I must restart the machine, which is in several languages, appears.

I reboot and all's well.

never seen this before, has anyone else? I didn't think they'd need to mess with the OS or something similar, but it seems a bit of a coincidence to see this message so often.

Below the message is a hex string of ff:ff:ff:ff:ff:ff. don't know if it's important. Anyone else able to shed some light here.

Cheers,

J.

motti · Mar 10, 2003, 03:49 AM

no exactly the same message but perhaps it is based on the same reason. after waking from sleep the monitor attached to my G4 flashes and i have to restart it. this is new since 10.2.4

rsh · Mar 10, 2003, 04:46 AM

The message you are seeing is a "kernal panic" which in most people's experience is rare in OS X. (Sound like it was rare in your experience too -- until recently)

Have you added any software recently, any unusual utility or screensaver? If so, try disabling or uninstalling it. If not, I'd definitely let Apple know about the issue. It shouldn't be happening.

Gul Banana · Mar 10, 2003, 05:51 AM

Originally posted by rsh:
The message you are seeing is a "kernal panic" which in most people's experience is rare in OS X. (Sound like it was rare in your experience too -- until recently)

No it isn't, it's a kernel panic. A log with useful debugging information will have been saved at /Library/Logs/panic.log - if you post the contents of that file here we might be able to help you figure out what's causing the problem.

ambush · Mar 10, 2003, 05:54 AM

Say it after me kids, k e r n e l p a n i c

Yeah I own an iBook and I have to restart it after it goes to sleep 1/2 of the time for no reason. (I wake it up from sleep and I get a nice black screen)

Apple sux, it's like that.

Gul Banana · Mar 10, 2003, 05:58 AM

Ever thought of trying to fix it/get it fixed? I wouldn't just accept that level of suckiness if I were you.. especially not since I put my iBook in and out of sleep several times a day

Freeflyer · Mar 10, 2003, 01:41 PM

Originally posted by Gul Banana:
No it isn't, it's a kernel panic. A log with useful debugging information will have been saved at /Library/Logs/panic.log - if you post the contents of that file here we might be able to help you figure out what's causing the problem.

there's not panic.log file anywhere on the machine. could it be under any other name. There are some crash logs from various apps, but nothing that's named panic.

I haven't installed anything new since getting the Tibook back from it's repair.

Thanks for the help so far, at least I know other people have been seeing this. I'd be grateful for any further advice.

Phoning apple isn't going to be so easy, as I'm currently on holiday in New Zealand, and haven't been able to find a number for apple down here. Nearest I can find is australia.

Cheers,

J.

Freeflyer · Mar 12, 2003, 12:48 PM

Well the machine threw another kernal panic yesterday, just after waking from sleep. Same display screen, same hex address at the bottom.

Still no panic log anywhere that I can find. Might have to wait until I get back to the us in a couple of months to talk to apple unless someone here has a better guess of what I can do next.

Cheers for the help so far,

J.

Angus_D · Mar 12, 2003, 12:50 PM

Originally posted by Freeflyer:
kernal panic

Why are people so obsessed with spelling kernel incorrectly?

Freeflyer · Mar 12, 2003, 11:44 PM

Originally posted by Angus_D:
Why are people so obsessed with spelling kernel incorrectly?

Not obsessed, just crap typing

pete · Mar 15, 2003, 01:14 PM

I've had the same thing happen to me for past month or so.Get a kernel panic when I wake it up from sleep. Not always just sometimes. Annoying problem though. I have a 800mhz tibook/40/512ram. here are the logs, hope somebody can help!! Thanks.

Just realized that it hasn't logged all the panics I've had over the past few weeks. Hmmm...

Date/Time: 2003-01-15 10:50:34 -0500
OS Version: 10.2.3 (Build 6G30)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf00807f0 r2: 0x42000284 r3: 0x00000088
r4: 0x00000000 r5: 0x00000000 r6: 0xf00807d0 r7: 0x00000000
r8: 0xa0007124 r9: 0x00000000 r10: 0x000ad0e0 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000001
r20: 0xa2be8198 r21: 0xf0080d10 r22: 0xa2bd8198 r23: 0xa2ba8198
r24: 0x00000000 r25: 0xf0080d50 r26: 0x00000f03 r27: 0xbffffab0
r28: 0xf0080980 r29: 0x00000088 r30: 0x00000000 r31: 0x9005ceb0

**********

Date/Time: 2003-01-30 22:16:04 -0500
OS Version: 10.2.3 (Build 6G30)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf0305aa0 r2: 0x24004282 r3: 0x00000ac0
r4: 0x00000000 r5: 0x00000000 r6: 0xf0305a80 r7: 0x00000000
r8: 0xa000715c r9: 0x00000000 r10: 0x07007180 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xf0305e00 r27: 0xf0305cfc
r28: 0x17292100 r29: 0x00000ac0 r30: 0x00000000 r31: 0x9005ceb0

**********

Date/Time: 2003-01-30 22:32:54 -0500
OS Version: 10.2.3 (Build 6G30)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf0284aa0 r2: 0x24004282 r3: 0x00002d4d
r4: 0x00000000 r5: 0x00000000 r6: 0xf0284a80 r7: 0x00000000
r8: 0xa000714c r9: 0x00000000 r10: 0x02d59d90 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xf0284e00 r27: 0xf0284cfc
r28: 0x02d86c20 r29: 0x00002d4d r30: 0x00000000 r31: 0x9005ceb0

**********

Date/Time: 2003-01-30 22:34:42 -0500
OS Version: 10.2.3 (Build 6G30)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf0284aa0 r2: 0x24004282 r3: 0x00002d57
r4: 0x00000000 r5: 0x00000000 r6: 0xf0284a80 r7: 0x00000000
r8: 0xa000714c r9: 0x00000000 r10: 0x02a94f20 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xf0284e00 r27: 0xf0284cfc
r28: 0x03b856a0 r29: 0x00002d57 r30: 0x00000000 r31: 0x9005ceb0

**********

Date/Time: 2003-01-31 18:14:38 -0500
OS Version: 10.2.3 (Build 6G30)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0000f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf0284aa0 r2: 0x24004282 r3: 0x00003080
r4: 0x00000000 r5: 0x00000000 r6: 0xf0284a80 r7: 0x00000000
r8: 0xa0007154 r9: 0x00000000 r10: 0x01583ac0 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0x00000000 r22: 0x00000000 r23: 0x00000000
r24: 0x00000000 r25: 0x00000000 r26: 0xf0284e00 r27: 0xf0284cfc
r28: 0x02a8c400 r29: 0x00003080 r30: 0x00000000 r31: 0x9005ceb0

**********

Date/Time: 2003-02-26 12:30:50 -0500
OS Version: 10.2.4 (Build 6I32)
Host: Computer.local.

Command: Unknown
PID: Unknown

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
(null)
PPC Thread State:
srr0: 0x9005cf18 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x9005cf14 ctr: 0x9001b520 mq: 0x00000000
r0: 0x00000025 r1: 0xf01018a0 r2: 0x42000284 r3: 0x00000089
r4: 0x00000000 r5: 0x00000000 r6: 0xf0101880 r7: 0x00000000
r8: 0xa0007124 r9: 0x00000000 r10: 0x000b2e60 r11: 0xa00045d4
r12: 0x9001b520 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000001
r20: 0xa2be8180 r21: 0xf0101d10 r22: 0xa2bd8180 r23: 0xa2ba8180
r24: 0x00000000 r25: 0x00001103 r26: 0x00000002 r27: 0xbffffab0
r28: 0xf0101a30 r29: 0x00000089 r30: 0x00000000 r31: 0x9005ceb0