--dc+cDN39EJAMEtIO
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Mar 28, 2004 at 10:00:28PM +0200, Hauke Fath wrote:
> Hi,
>=20
> early during a build-sh build on a -current mac68k (tried with a
> 2004-03-18 1.6ZK kernel and a 1.6ZL kernel from today's sources), I have =
repeatedly run into an nfs related kernel panic:

[snip]

> panic: MMU fault
> Stopped in pid 383.1 (mount_nfs) at     netbsd:cpu_Debugger+0x6:        u=
nlk a6
> db> t                            =20
> cpu_Debugger(2000,8,43fac78,43fac64,114746) + 6
> panic(13c0bc,10002,50c,23,43d9668) + f8
> trap(8,505,ffffffd4) + 254
> vn_lock(30bc,10002) + 82
> vget(30bc,2) + 92

30bc doesn't look like a good vnode address. Something somewhere's=20
confused.

I bet one of the nfs ops caches got corrupted.

> nqnfs_clientd(111e800,111df80,43faea4,100,ffffc4f8,86ec00) + 272
> sys_nfssvc(86ec00,43faf44,43faf3c) + 4e2
> syscall_plain(9b,86ec00,43fafb4,100,ffffc73a) + 82
> syscall(9b) + 4c
> trap0() + e
> db> ps
[snip]
> db>=20
>=20
> Is this "known"? Or should I send-pr?

I'd say send-pr. I'm not familiar enough with the NFS client to know=20
what's up.

Take care,

Bill

--dc+cDN39EJAMEtIO
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)

iD8DBQFAbamNWz+3JHUci9cRAsuqAJwO5w4wNUXKDNaYtuCsljDKAbTl1gCfRYe4
XPzUzwmQp2e3XYjrfKTvUmg=
=66Ib
-----END PGP SIGNATURE-----

--dc+cDN39EJAMEtIO--