Messages in this thread | | | Date | Thu, 24 Jul 2008 16:38:23 +0200 | From | "Vegard Nossum" <> | Subject | Re: KGDB fails to pass selft tests on x86-64 (v2.6.26) |
| |
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
| |