From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Keith Owens <kaos@sgi.com>
Cc: kdb@oss.sgi.com, linux-kernel@vger.kernel.org,
linux-ia64@vger.kernel.org
Subject: Re: Announce: kdb v4.4 is available for kernel 2.6.15
Date: Wed, 04 Jan 2006 08:04:46 -0700 [thread overview]
Message-ID: <43BBE40E.5040600@wolfmountaingroup.com> (raw)
In-Reply-To: <13550.1136365849@kao2.melbourne.sgi.com>
Keith,
I noticed that during page faults, the OOPS handler is not getting
called when the kernel crashes in
filp_open() -- the notifier chain does not return for some reason. I
also noticed that when this happens, if you the section in
/arch/i386/kernel/traps.c in function die() prior to the busting of
spinlocks, it will work (sortof work). To reproduce this error, call
filp_open with a text string complied in the kernel. I can reproduce on
2.6.10 and 2.6.11 Fedora Kernels. Also noticed that when Kprobes is
enabled, the debugger page faults during a page fault exeception.
Seems related to the notifier chain.
If you fixed this already, disregard this notice.
Jeff
prev parent reply other threads:[~2006-01-04 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-04 9:10 Announce: kdb v4.4 is available for kernel 2.6.15 Keith Owens
2006-01-04 15:04 ` Jeff V. Merkey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43BBE40E.5040600@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=kaos@sgi.com \
--cc=kdb@oss.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox