Re: kern/39774: (not really) dirhash kernel panic

[David Holland <dholland-bugs%netbsd.org@localhost>]

On Wed, Oct 22, 2008 at 06:40:03PM +0000, Hauke Fath wrote:
 > cpu_Debugger(0xf0275310, 0xf0101870, 0xf65757f4, 0xf0291000, 0x100,
 > 0xf02c5400) at netbsd:mem_access_fault4m+0x204
 > mem_access_fault4m(0x9, 0x5336, 0xf65757f4, 0xf53f6a78, 0x0, 0x34bc) at
 > 0xf0006254
 > 0xf0006254(0x0, 0x17f0, 0x6, 0x200, 0x0, 0x78000) at netbsd:ufs_lookup+0x204
 > ufs_lookup(0x5d7e0, 0x3fff, 0x2, 0xf53f6e74, 0x0, 0x200) at
 > netbsd:VOP_LOOKUP+0x24
 > VOP_LOOKUP(0xf7717c68, 0xf53f6e60, 0xf53f6e74, 0x0, 0xf7717c68, 0xf4e0b802)
 > at netbsd:lookup+0x2a8

Am I right in thinking this means it croaked in whatever function is
at 0xf0006254 (inside a module?), which was called from offset 0x204
into ufs_lookup?

I don't see anything in ufs_lookup, or at least anything near enough
to the top to be at offset 0x204, that ought to be a call into a
module, so I'm not sure what to make of this.

Anyone with sparc knowledge want to comment?

-- 
David A. Holland
dholland%netbsd.org@localhost