On Thursday 25 August 2005 20:10, Jack F Vogel wrote:
> 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?
>

I will.

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

Yes, that was what I was working in yesterday when I got distracted with some 
other stuff.  I will track down a UP Opteron as well and see what happens 
there.

> Anything I can do to help let me know.
>
> Jack

-- 
Ray Bryant
AMD Performance Labs                   Austin, Tx
512-602-0038 (o)                 512-507-7807 (c)

---------------------------
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.

Reply via email to