05-15-2005, 09:58 AM

Hi

I just using upgrade from 10.3.9 to OSX Tiger 10.4 on my Cube G4. I did verified and repair permissions before selecting upgrade. Every time I shut down, It said like "Warning - Please hold down power button for seconds or hold down restart button....usual kernal error. I know it not the hard drive problem as it is OSX problem.

Using 10.3.9 I have never have problem shutting down which goes perfectly. I have more than one accounts. I didn't have any problems installing OSX Tiger on Bue & White G3 and shutdown is fine.

So why it doing that with kernal error comes up every shutdown errors.? Usually I had to restart and wait for that login and then shutdown ok sometimes.

There no track of Norton firewall or other products and no Virex products on G4 Cube hard drive. It not the memory issues and it been perfectly normal with 10.2 up to 10.3.9.

Any suggestions?

Regards

AussieDownUnder

05-15-2005, 11:37 AM

Since you are telling us that it worked fine on 10.3, it's probably not a memory issue, which is mainly the cause to kernel panics. However, I notice you did an upgrade to OS X.4, and it may be because I've used Windows for the majority of my life(not anymore), but I still really hate anything but Fresh installs.

Just my 2 Cents!

05-16-2005, 09:35 AM

Did you repair permission are the upgrade to 10.4?

05-16-2005, 10:27 AM

Originally Posted by rman

Did you repair permission are the upgrade to 10.4?

Hi

Yes I verified and repair permission before upgrading to OSX 10.4. The installation went without hiccups. And everything seems okay like applications. Only minor application unexpectedly quitting. The memory in Apple cube G4 is genuine apple memory. The memory I have is 768mb.

Whether might be worth waiting for that 10.4.1 update might solve that but who knows!!

AussieDownUnder

05-16-2005, 10:30 AM

Same Thing Happened To Me
I Installed Tiger On My Powerbook And G5 And That Happened Like The First 4 Or 5 Times I Shut Down But Now It Works Fine
Seems Like It Worked Out The Problkem On Its Own

05-16-2005, 10:30 AM

repair the permmissions now... after the install of 10.4.... that might do the trick.

05-19-2005, 08:50 AM

Originally Posted by adamxj2

Same Thing Happened To Me
I Installed Tiger On My Powerbook And G5 And That Happened Like The First 4 Or 5 Times I Shut Down But Now It Works Fine
Seems Like It Worked Out The Problkem On Its Own

Jo

Hi Jo

Did that happened to you with kernal panic but how come you said it worked fine?? I'm puzzled?

AussieDownUnder

05-19-2005, 08:52 AM

Originally Posted by xthisisRomancex

repair the permmissions now... after the install of 10.4.... that might do the trick.

Hi Romancex

I done that many times every installation!! But nothing solved that Kernal panic in shutdowns and also it occurs in restart! No matter who account that been login and shut down it happened every accounts.

I cleaned the preferences, etc. But I tested the memory but it does not make any difference.

05-19-2005, 08:53 AM

Here is the copy of the panic log:

panic.log:

Description: Panic (system crashes) log
Size: 15.41 KB
Last Modified: 19/05/05 10:27 PM
Location: /Library/Logs/panic.log
Recent Contents: ...
Backtrace:
0x00F9A01C 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x00EC7280
Exception state (sv=0x1971D500)
PC=0x9000514C; MSR=0x0200F030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
*********

Thu May 19 22:09:17 2005


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000040 PC=0x00000000000F8D00
Latest crash info for cpu 0:
Exception state (sv=0x192DB280)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x078C3B90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x00000000
Proceeding back via exception chain:
Exception state (sv=0x192DB280)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x24E11780)
PC=0x9000514C; MSR=0x0000D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x192DB280)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x078C3B90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00000000 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x00000000
Exception state (sv=0x24E11780)
PC=0x9000514C; MSR=0x0000D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
*********

Thu May 19 22:12:07 2005


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000040 PC=0x00000000000F8D00
Latest crash info for cpu 0:
Exception state (sv=0x199ED780)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x0790BB90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00F82600 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x010E3DA0
Proceeding back via exception chain:
Exception state (sv=0x199ED780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2525EC80)
PC=0x9000514C; MSR=0x0200D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x199ED780)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x0790BB90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00F82600 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x010E3DA0
Exception state (sv=0x2525EC80)
PC=0x9000514C; MSR=0x0200D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
*********

Thu May 19 22:27:45 2005


Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000040 PC=0x00000000000F8D00
Latest crash info for cpu 0:
Exception state (sv=0x192DE000)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x07903B90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00F88D00 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x0112FE40
Proceeding back via exception chain:
Exception state (sv=0x192DE000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x1923B780)
PC=0x9000514C; MSR=0x0200D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x00095564 0x00095A7C 0x0002683C 0x000A819C 0x000ABB00
Proceeding back via exception chain:
Exception state (sv=0x192DE000)
PC=0x000F8D00; MSR=0x00009030; DAR=0x00000040; DSISR=0x40000000; LR=0x000F9C14; R1=0x07903B90; XCP=0x0000000C (0x300 - Data access)
Backtrace:
0x00F88D00 0x000F4CB0 0x0025B090 0x002A8604 0x000ABCB0 0x0112FE40
Exception state (sv=0x1923B780)
PC=0x9000514C; MSR=0x0200D030; DAR=0xE0020628; DSISR=0x40000000; LR=0x00019138; R1=0xBFFFFA80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 8.1.0: Tue May 10 18:16:08 PDT 2005; root:xnu-792.1.5.obj~4/RELEASE_PPC
*********

05-19-2005, 10:14 AM

Hmmm.

I had a customer in today with that exact same problem... I gave him a copy of the latest updates to install, to see if that'll fix the problem.

Have you updated to 10.4.1?