[OpenAFS-port-darwin] Re: Many crashes on OS X 10.3 - MP problem?

Nicholas Riley njriley@uiuc.edu
Sun, 15 Feb 2004 13:37:59 -0600


On Fri, Feb 13, 2004 at 11:06:37PM +0100, Ragnar Sundblad wrote:
> Could it be an MP problem? What do everyone else on this list
> say, what machines have you typically used?

iMac G4/800, G4/400 desktop, dual G5/2 GHz.  All of these are public
lab machines, for users with their home directories in AFS.  I used to
see panics on my G4/800 PowerBook and dual G4/533 desktop before I
took OpenAFS off them.

We have a dual G4/867 which is still running 10.2.8, but is primarily
used by users with non-AFS home directories; it hasn't seen an
AFS-related panic since September 2003.

*********

Thu Sep 25 22:04:03 2003


panic(cpu 0): read volumeinfo
Latest stack backtrace for cpu 0:
      Backtrace:
         0x000857F4 0x00085C24 0x000287B4 0x25B4F12C 0x25B302F4
	 0x25B3100C 0x25B31C18 0x25B31554 
         0x25B24664 0x25B276D4 0x25B5EE64 0x000B13B0 0x000B0D84
	 0x000B91EC 0x0020FF8C 0x00092950 
         0xFF518CC4 
      Kernel loadable modules in backtrace (with dependencies):
         org.openafs.filesystems.afs(1.2.9fc1)@0x25af6000
Proceeding back via exception chain:
   Exception state (sv=0x19661A00)
      PC=0x9000FD6C; MSR=0x0000F030; DAR=0x1700C000; DSISR=0x40000000;
      LR=0x9022961C; R1=0xF0178E80; XCP=0x00000030 (0xC00 - System call)

Kernel version:
Darwin Kernel Version 6.8:
Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC


> Are these problem entirely new with 10.3, or have they
> just intensified, or what is the history here?

They have just intensified.  The iMac formerly ran 10.2.8, and it
panicked about once a day in that configuration.  The 10.3 panics are
much more frequent, once an hour or more.  The way OpenAFS panics on
10.3 when you're doing a lot of file operations, even if the
operations do not involve AFS space, seems new.  Opening LaunchBar
with your home directory on AFS is a sure-fire recipe for a panic
under 10.3.

We've also had another problem which came up recently; we get lots of
error messages about not being able to access the current directory
when running command-line programs like vim and cvs.  It seems to be a
specific filesystem operation, as I can do a Subversion checkout but
not a CVS checkout in the same directory.  Carbon apps report error
-35 (no such volume).

Between this problem and the crashes, it's making our Macs pretty much
unusable.

-- 
=Nicholas Riley <njriley@uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>