Kernel Panic on OSX 10.2

[Thomas Jordan]

I do have /Libray/Logs/panic.log.

Where can I find the kernel module to do the checking that you describe? If
this is a file what is the path?

The panics seem to happen when using the finder to access files in AFS
space. In other words, using the finder to  "click" on or select a file in
AFS space. There may be some variability in how "deep" the file is.
Selecting files closer to the top of the cell may not cause the panic. This
is unclear just now. Aaron described the same panic (and cause - he selected
an AFS file) a bit ago in a similar thread.

I came back from a meeting once yesterday to a panicked machine. Arla had
been running and I left the machine alone for ~ 2 hours.

Let me know what we can do to help find the error. It may be the change you
mentioned in your next post. But we can provide evidence to support or
refute that so you have less to look for in the solution.

I will install current on an "clean from arla" machine to see if that helps.

    t.

On 9/5/02 18:58, "Magnus Ahltorp" <ahltorp at nada.kth.se> wrote:

>> I have experienced several kernel panics on four different machines running
>> OSX 10.2 and arla 0.35.10pre2 built from snap.
> 
> I have seen one of these, but I have been running arla current on my
> laptop with 10.2 for some months, and never seen a crash. There may be
> a difference between 0.35.x and current.
> 
> Have you any idea in which situations the panics occur?
> 
>> I don't see anything obvious in the system log(s) of the panicked machines.
>> Is there some logging that I can turn on on my end so that I can provide
>> clues back to the list about the source of the panics? What data do you
>> need?
> 
> On my computer, /Library/Logs/panic.log contains panic information.
> Some people have reported that it doesn't happen on their computers,
> but according to AppleCare documents, it should be recorded there.
> 
> The binary kernel module is also needed, since the information in the
> panic.log is only relevant when used with the correct kernel module.
> It must be exactly the same file that was used during the crash.
> 
> You can choose to send me the panic.log file and the kernel module, or
> look at it yourself with gdb. I should probably put together a
> document describing how to do that.
> 
> It basically boils down to that you take each address of the backtrace
> (and the PC) and look if it seems to be in a kernel module or not (the
> load addresses of the kernel modules in the backtrace are listed).
> 
> If an address is not in a kernel module, you can use "gdb
> /mach_kernel" and "x/i <address>" or "disas <address>" to get
> information about the address.
> 
> If it is in a kernel module, you can load the kernel module in gdb
> (with "gdb <module>") and subtract the load address from the address
> you want to inspect. Note that you have to subtract another 0x1000
> from the address, don't ask me why.
> 
> /Magnus

-- 
Thomas Jordan
Fermi National Accelerator Laboratory
Kirk and Pine Streets
PO Box 500
MS 226 WH15W
Batavia, Illinois
60510
voice: 630.840.4035
fax : 630.840.8248