sparc64/140797: Panic on 8.0-RC3/sparc64 as an NFS server
Greg Lewis
glewis at FreeBSD.org
Sun Nov 22 22:50:01 UTC 2009
>Number: 140797
>Category: sparc64
>Synopsis: Panic on 8.0-RC3/sparc64 as an NFS server
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-sparc64
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Sun Nov 22 22:50:00 UTC 2009
>Closed-Date:
>Last-Modified:
>Originator: Greg Lewis
>Release: FreeBSD 8.0-RC3 sparc64
>Organization:
>Environment:
FreeBSD sol.eyesbeyond.com 8.0-RC3 FreeBSD 8.0-RC3 #0: Sun Nov 22 11:04:18
PST 2009 glewis at sol.eyesbeyond.com:/usr/src/sys/sparc64/compile/SOL
sparc64
>Description:
I have a sparc64 machine which I recently upgraded to 8.0-RC3. It
was previously running 6.3. I export the /home directory from it
(with -alldirs set) and mount a subdirectory on a FreeBSD 7.2/i386
client machine. Attempting to ls(1) the directory on the client
causes the sparc64 server to panic.
I have a core kgdb(1) doesn't appear to run under sparc64.
I enabled KDB and here is some output from it (unfortunately hand
copied since I don't have a serial console set up).
panic: trap: memory address not aligned
cpuid = 1
KDB: stack backtrace:
panic() at 0xc022a968 = panic+0x1c8
trap() at 0xc04fc230 = trap+0x4d0
-- memory address not aligned sfar=0xe6d7b424 sfsr=0x40029 %o7=0xc0402e4c --
fha_assign() at 0xc0402e60 = fha_assign+0x140
svc_run_internal at 0xc0427d5c = svc_run_internal+0x71c
svc_thread_start at 0xc04281a8 = svc_thread_start+0x8
fork_exit at 0xc01f82e0 = fork_exit+0x80
fork_trampoline at 0xc00711e8 = fork_trampoline+0x8
Note that this may affect other architectures which care about
memory alignment, but I'm putting it under sparc64 only for the
moment.
>How-To-Repeat:
/etc/exports on the sparc64 8.0-RC3 server:
/home -alldirs -maproot=0 -network 10.0.0.0 -mask 255.255.255.0
On the client machine:
> mount -t nfs sol:/home/glewis/sparc64 /home/glewis/sparc64
> ls ~glewis/sparc64
Note that I have the core.txt.0 and vmcore.0 from the the earlier
attempt at using kgdb if they would be helpful.
Since this is also easy to reproduce, I can provide additional data
from KDB if it would be helpful and/or try out patches.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-sparc64
mailing list