[OpenAFS] Panic under MacOS 10.3.6 with OpenAFS-1.2.13
Garance A Drosihn
drosih@rpi.edu
Thu, 18 Nov 2004 19:31:08 -0500
On my machine, OpenAFS has suddenly gone from pretty reliable to very
problematic. Several things have been happening, so I am not quite
sure which are the most significant.
You may remember that our cell (rpi.edu) was having some problems
with the fileservers hanging. The new version of OpenAFS has been
installed on some of our servers, but I am not sure if it has been
installed on all of them.
As it was getting installed on various file servers, I started
noticing that *some* references into AFS space from my Mac would
hang for 56 seconds. Once I got past one hang, any accesses would
work fine for awhile. Then, sometime later on, I would get another
56-second hang. At about the same time, I decided to apply about a
month's worth of recent updates from Apple, including the update to
10.3.6. This is on a dual 2-GHz G5 from Apple.
I am not certain which version of OpenAFS I had been running, but I
believe it was 1.2.11. So, I figured I might as well upgrade my Mac
to 1.2.13. Now, I seem to get panics when I save a file which I
am editing in the XCode 1.5 application. I may be able to change
and save any given file some small number of times, but after one-
too-many saves, the machine will panic. I have only noticed this
with XCode, but then that is the way I usually modify files.
Once the machine comes back from the panic, the original file will
be gone, but there's a temp backup file still around. E.g., if I am
editting 'printjob.c', then 'printjob.c' will be missing, but there
is an extra 'printjob~.c' file sitting in the same directory. That
file will not have the changes that I just saved, and I think it is
also missing the *previous* set of changes that I had saved.
I suspect this is something XCode is doing oddly. Before all of
these recent changes, I would sometimes get into a situation where
XCode would claim it could not save a file. When it did that, the
original file would be missing, and that blah~.c file would be there.
However, I could always get out of that situation without triggering
any panic, so it wasn't quite as annoying as this is.
In any case, here is some information from the panic log. What else
should I do to help with this?
*********
Thu Nov 18 17:05:36 2004
Unresolved kernel trap(cpu 0): 0x300 - Data access
DAR=0x00000000DEADD1F5 PC=0x000000000022BC30
Latest crash info for cpu 0:
Exception state (sv=0x2DD43780)
PC=0x0022BC30; MSR=0x00009030; DAR=0xDEADD1F5;
DSISR=0x40000000; LR=0x000C0FC0; R1=0x1746BCD0; XCP=0x0000000C (0x300
- Data access)
Backtrace:
0x000C1B04 0x000C9724 0x002463C4 0x00094200 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB4E0
Proceeding back via exception chain:
Exception state (sv=0x2DD43780)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2E3E9C80)
PC=0x9002E08C; MSR=0x0200D030; DAR=0xBFFFAE80;
DSISR=0x0A000000; LR=0x90323EC4; R1=0xBFFFB4E0; XCP=0x00000030 (0xC00
- System call)
Kernel version:
Darwin Kernel Version 7.6.0:
Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC
panic(cpu 0): 0x300 - Data access
Latest stack backtrace for cpu 0:
Backtrace:
0x000836E4 0x00083BC8 0x0001EDA4 0x00090C60 0x0009406C
Proceeding back via exception chain:
Exception state (sv=0x2DD43780)
PC=0x0022BC30; MSR=0x00009030; DAR=0xDEADD1F5;
DSISR=0x40000000; LR=0x000C0FC0; R1=0x1746BCD0; XCP=0x0000000C (0x300
- Data access)
Backtrace:
0x000C1B04 0x000C9724 0x002463C4 0x00094200 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB4E0
Exception state (sv=0x2E3E9C80)
PC=0x9002E08C; MSR=0x0200D030; DAR=0xBFFFAE80;
DSISR=0x0A000000; LR=0x90323EC4; R1=0xBFFFB4E0; XCP=0x00000030 (0xC00
- System call)
Kernel version:
Darwin Kernel Version 7.6.0:
Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC
*********
Thu Nov 18 18:35:15 2004
Unresolved kernel trap(cpu 1): 0x300 - Data access
DAR=0x00000000DEADD1F5 PC=0x000000000022BC30
Latest crash info for cpu 1:
Exception state (sv=0x2DCBC000)
PC=0x0022BC30; MSR=0x00009030; DAR=0xDEADD1F5;
DSISR=0x40000000; LR=0x000C0FC0; R1=0x17783CD0; XCP=0x0000000C (0x300
- Data access)
Backtrace:
0x000C1B04 0x000C9724 0x002463C4 0x00094200 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB4E0
Proceeding back via exception chain:
Exception state (sv=0x2DCBC000)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x2D588500)
PC=0x9002E08C; MSR=0x0200F030; DAR=0x00B5F3D8;
DSISR=0x40000000; LR=0x90323EC4; R1=0xBFFFB4E0; XCP=0x00000030 (0xC00
- System call)
Kernel version:
Darwin Kernel Version 7.6.0:
Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC
panic(cpu 1): 0x300 - Data access
Latest stack backtrace for cpu 1:
Backtrace:
0x000836E4 0x00083BC8 0x0001EDA4 0x00090C60 0x0009406C
Proceeding back via exception chain:
Exception state (sv=0x2DCBC000)
PC=0x0022BC30; MSR=0x00009030; DAR=0xDEADD1F5;
DSISR=0x40000000; LR=0x000C0FC0; R1=0x17783CD0; XCP=0x0000000C (0x300
- Data access)
Backtrace:
0x000C1B04 0x000C9724 0x002463C4 0x00094200 0x00000000
backtrace terminated - frame not mapped or invalid: 0xBFFFB4E0
Exception state (sv=0x2D588500)
PC=0x9002E08C; MSR=0x0200F030; DAR=0x00B5F3D8;
DSISR=0x40000000; LR=0x90323EC4; R1=0xBFFFB4E0; XCP=0x00000030 (0xC00
- System call)
Kernel version:
Darwin Kernel Version 7.6.0:
Sun Oct 10 12:05:27 PDT 2004; root:xnu/xnu-517.9.4.obj~1/RELEASE_PPC
*********
--
Garance Alistair Drosehn = gad@gilead.netel.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu