PowerPC Kernel Panic upon installation

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install MacFUSE
2. Reboot
3. Behold the wonder that is the Kernel Panic

What is the expected output? What do you see instead?
Expected: It boots up
What I see: a panic

What version of the product are you using? On what operating system?
1.7 on Mac OS X 10.4.11 PowerPC G4

Please provide any additional information below.
I would install MacFUSE, reboot as directed, and it would boot fine into the 
loginwindow.app. 
Once it reached the preliminary blue-screen for login, it would take some 30 or 
40 seconds, and 
then it would panic.

Host Name:      ???
Date/Time:      2008-10-25 22:01:08.951 -0500
OS Version:     10.4.11 (Build 8S165)
Report Version: 4

Command: loginwindow
Path:    /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
Parent:  WindowServer [90]

Version:        4.7 (4.7)
Build Version:  1
Project Name:   loginwindow
Source Version: 11700500

PID:    1172
Thread: 2

Exception:  EXC_BAD_ACCESS (0x0001)
Codes:      KERN_PROTECTION_FAILURE (0x0002) at 0x00000006

I would attach the log, if it were useful. Coming from an only slight 
programming background, 
that of barely being on XNU, I'd have to guess the loginwindow is trying to 
read from your nifty 
little system. I guess because KERN_PROTECTION_FAILURE is pretty vague.

Original issue reported on code.google.com by fra...@gmail.com on 26 Oct 2008 at 4:53

[GoogleCodeExporter]

"Behold the wonder that is the Kernel Panic" is pretty poetic.

I've explained numerous times here that MacFUSE isn't something that runs by 
itself. It's essentially a library that kicks 
in only when you actually run a program that's written on top of MacFUSE. When 
you boot up your system, NOTHING 
MacFUSE-related happens. The MacFUSE kernel extension doesn't load 
automatically--it's loaded on demand when you 
run a program that is written on top of MacFUSE.

"loginwindow is trying to read from your nifty little system" doesn't make any 
sense whatsoever. Which "nifty little 
system"? If you mean MacFUSE, that is nifty, but not little by any means. If 
you mean Mac OS X, that's neither nifty nor 
little.

Your kernel panic occurring after you installed MacFUSE sounds circumstantial. 
Did you actually install some MacFUSE-
based program (say, ntfs-3g) that runs upon boot-up or upon login?

Yes, do attach the log, so I might be able to tell you more.

Original comment by si...@gmail.com on 26 Oct 2008 at 5:21

[GoogleCodeExporter]

Well, I can say that I have tested this 5 times on this machine, in which 
loginwindow.app would fail to startup 
correctly only after MacFUSE was installed. I have no other MacFUSE based 
program on this machine. I'm a patient 
"do A; goto B; arrive at C; repeat; kind of person.

Original comment by fra...@gmail.com on 26 Oct 2008 at 2:19

Attachments:

• crashlog.rtf

[GoogleCodeExporter]

First off, what you're seeing is an application crash, not a kernel panic. 
There is substantial difference between the two. 
The term "KERN_PROTECTION_FAILURE" means that the process tried to do something 
(say, write) to a piece of memory 
that it was not permitted to (say, the memory was read-only). The crash is 
occurring in Core Foundation, one of the 
built-in Mac OS X libraries.

It could be occurring because of one or more of many things: ranging from bad 
hardware (memory, process, or disk) to 
bad software (corrupted file system).

Circumstantial evidence notwithstanding, the mere act of installing MacFUSE and 
rebooting is not causing the 
loginwindow application to crash.

If you believe you can fix this by uninstalling MacFUSE (how were you 
uninstalling anyway when you did your testing 5 
times?), do that and see if your crash returns in the next few days or weeks.

Original comment by si...@gmail.com on 26 Oct 2008 at 8:12

• Changed state: Invalid