public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Francis Moreau <francis.moro@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: KGDB fails to pass selft tests on x86-64 (v2.6.26)
Date: Thu, 24 Jul 2008 09:55:32 -0500	[thread overview]
Message-ID: <488897E4.8070806@windriver.com> (raw)
In-Reply-To: <19f34abd0807240738h7ac5e716rcfa39d528b07870f@mail.gmail.com>

Vegard Nossum wrote:
> On Thu, Jul 24, 2008 at 4:30 PM, Jason Wessel
> <jason.wessel@windriver.com> wrote:
>   
>> Also, if you plan to use software breakpoints, please make sure to turn
>> off CONFIG_DEBUG_RODATA, else they will not work.   This is a regression
>> which will is on my list of things to take a look at, as time permits.
>>     
>
> I had a couple of kernels hang during single-stepping self-tests (I
> think), where it reached 500 and 900 tests respectively before it hung
> hard (NMI watchdog enabled, but not triggering). Is this related to
> the RODATA thing?
>
> This was with a recent (post-v2.6.26) kernel on a real P4.
>
>
>   

It is not likely that CONFIG_DEBUG_RODATA can have any impact because
the boot test occurs before the text sections are marked read-only.  A
hang in this section indicates a conflict where something is spinning
for a lock in the NMI handler, or the NMI handler re-entered and tried
to acquire another lock. 

In the 2.6.26 time frame I found and fixed at least one defect around
updating the clock while in the NMI which required that you not do it
from the NMI context.  It sounds as if there is yet another problem
along these lines, and of course it is a timing race...

Jason.

  reply	other threads:[~2008-07-24 14:56 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 13:24 KGDB fails to pass selft tests on x86-64 (v2.6.26) Francis Moreau
2008-07-24 14:08 ` Francis Moreau
2008-07-24 14:30   ` Jason Wessel
2008-07-24 14:38     ` Vegard Nossum
2008-07-24 14:55       ` Jason Wessel [this message]
2008-07-24 19:05         ` Vegard Nossum
2008-07-24 15:19     ` Francis Moreau

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=488897E4.8070806@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=francis.moro@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vegard.nossum@gmail.com \
    /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