From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Jason Wessel" <jason.wessel@windriver.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 16:38:23 +0200 [thread overview]
Message-ID: <19f34abd0807240738h7ac5e716rcfa39d528b07870f@mail.gmail.com> (raw)
In-Reply-To: <488891F2.9020509@windriver.com>
On Thu, Jul 24, 2008 at 4:30 PM, Jason Wessel
<jason.wessel@windriver.com> wrote:
> Francis Moreau wrote:
>> On Thu, Jul 24, 2008 at 3:24 PM, Francis Moreau <francis.moro@gmail.com> wrote:
>>> So the first thing I did is to enable kgdb support and also the
>>> kgdb self tests:
>>>
>>> CONFIG_HAVE_ARCH_KGDB=y
>>> CONFIG_KGDB=y
>>> CONFIG_KGDB_SERIAL_CONSOLE=y
>>> CONFIG_KGDB_TESTS=y
>>> # CONFIG_KGDB_TESTS_ON_BOOT is not set
>>>
>>> Once compiled I booted this kernel through qemu and got the following:
>>>
>> and unfortunately it seems this issue is related to qemu: if I did boot the
>> kernel without qemu and the self tests passed...
>>
>>
>>
>
> It is because the qemu you are using does not support hardware
> breakpoints. The tests will warn, but the kernel will continue to boot
> and tell you that hw breakpoint support doesn't work on your simulated
> hardware.
>
> 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.
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-07-24 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 13:24 Francis Moreau
2008-07-24 14:08 ` Francis Moreau
2008-07-24 14:30 ` Jason Wessel
2008-07-24 14:38 ` Vegard Nossum [this message]
2008-07-24 14:55 ` Jason Wessel
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=19f34abd0807240738h7ac5e716rcfa39d528b07870f@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=francis.moro@gmail.com \
--cc=jason.wessel@windriver.com \
--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
all inboxes | Powered by JetHome®