Craig Boston wrote:
> Well, I haven't had much luck tracking down the exact cause. For some
> reason I haven't been able to figure out, all of my crash dumps jump
> directly from vn_open_cred (line 185 of vfs_vnops.c) to calltrap(). The
> namei call doesn't show up in the stack at all, almost lik
Lars Eggert wrote:
> Terry Lambert wrote:
> > Debug:
> >
> [excellent kernel-debugging recipe snipped]
>
> Here's a backtrace of a crashdump that should be more helpful:
[ ... ]
> (kgdb) up 12
> #12 0xc02098a4 in namei (ndp=0x9e) at /usr/src/sys/kern/vfs_lookup.c:158
> 158 FILEDESC_
On Wed, 2003-02-19 at 16:44, Lars Eggert wrote:
> #11 0xc0302ff8 in calltrap () at {standard input}:97
> #12 0xc02098a4 in namei (ndp=0x9e) at /usr/src/sys/kern/vfs_lookup.c:158
> #13 0xc021bcfc in vn_open_cred (ndp=0xeb3b1a44, flagp=0xeb3b1a0c, cmode=0,
> cred=0xc2195e80) at /usr/src/sys/kern
Terry Lambert wrote:
Debug:
>
[excellent kernel-debugging recipe snipped]
Here's a backtrace of a crashdump that should be more helpful:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual address = 0x34
fault code = supervisor read, page n
Lars Eggert wrote:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; lapic.id =
> fault virtual address = 0x34
> fault code = supervisor read, page not present
> instruction pointer = 0x8:0xc01b28a6
[ ... ]
> kernel: type 12
Craig Boston wrote:
FWIW, this looks nearly identical to the panic I reported last night in
the thread "VFS panic (possibly NFS locking related?)".
I missed your message, just read it: yes, that sounds similar.
I didn't manage
to catch the ddb trace and had to work postmortem with a crash dum
FWIW, this looks nearly identical to the panic I reported last night in
the thread "VFS panic (possibly NFS locking related?)". I didn't manage
to catch the ddb trace and had to work postmortem with a crash dump and
gdb. But it looked just like here.
Lars: Do you by any chance have your home dir
Hi,
on today's -current, I get the following panic when starting gnome from
xdm; a kernel from 2/10 works with today's world, so it must be
something in the kernel that changed over the last week:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; lapic.id =
fault virtual addres
