kdb
[Top] [All Lists]

Re: kdb patch for 2.6.11 and x86_64

To: Ray Bryant <raybry@xxxxxxxxxxxxxxxxx>
Subject: Re: kdb patch for 2.6.11 and x86_64
From: Jack F Vogel <jfv@xxxxxxxxxxxx>
Date: Thu, 25 Aug 2005 18:10:27 -0700
Cc: kdb@xxxxxxxxxxx
In-reply-to: <200508251433.57534.raybry@mpdtxmail.amd.com>
References: <200508242015.55653.raybry@mpdtxmail.amd.com> <200508251051.15223.raybry@mpdtxmail.amd.com> <20050825170423.GA9391@trane.bluesong.net> <200508251433.57534.raybry@mpdtxmail.amd.com>
Reply-to: jfv@xxxxxxxxxxxx
Sender: kdb-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.6i
On Thu, Aug 25, 2005 at 02:33:57PM -0500, Ray Bryant wrote:
> 
> I applied Jim's patch.  The good news is that it applies cleanly.  The bad 
> news is that it doesn't fix my problem.
> 
> I does appear that there is a bogus value in the notifier die_chain.   I put 
> a 
> dump_stack() in notifier_call_chain() and that is getting invoked from 
> do_page_fault() so I am working under the assumption at the present time that 
> I took an unhandled kernel page fault and the bogus value in the die_chain 
> was causing the triple fault.   Why the first of these happened is still a 
> mystery.  (2.6.11 without the kdb patches boots fine.)
> 
> At the moment I'm trying to track down where the bogus value in the die_chain 
> is coming from.

I got a kernel with the new patch just posted installed on 
an Athlon64 machine, it boots ok, drops to kdb after its up.
I quickly checked the usual commands and everything worked ok.

Unfortunately this system is uniproc, and I do not have access to
other boxes right now (I hope this is a temporary situation
to be correctted in a couple weeks). Anyone willing to give the
new patch a quick check on SMP?

Maybe some debug printk in the notify_die registration code? I still
think that is where something is going wrong.

Anything I can do to help let me know.

Jack


---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
<Prev in Thread] Current Thread [Next in Thread>