Re: [Kgdb-bugreport] Posted kdb doc, and a question about unused env variables

On 06/29/2011 07:30 PM, Tim Bird wrote: Hi all, I'm new to KDB, but I've been looking at the code and trying to document a few things. I couldn't find any documentation on a few kdb features (initialization commands, defcmd, supported environment vars, etc.) I wrote some up at:

[Kgdb-bugreport] [PATCH] sparc, kgdbts: fix compile regression with kgdb test suite

pointer on the Sparc architecture. Signed-off-by: Jason Wessel jason.wes...@windriver.com Acked-by: Mike Frysinger vap...@gentoo.org Acked-by: David S. Miller da...@davemloft.net --- arch/sparc/include/asm/ptrace.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/arch/sparc

[Kgdb-bugreport] [GIT PULL] kgdb compile fix for 3.0 rc7

3a5c3743f15f27237ab025736a981e2d0c9fdfed: Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-2.6 (2011-07-18 13:29:26 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus Jason Wessel (1): sparc,kgdbts: fix compile regression

[Kgdb-bugreport] [PATCH 1/4] kdb: cleanup unused variables missed in the original kdb merge

The BTARGS and BTSYMARG variables do not have any function in the mainline version of kdb. Reported-by: Tim Bird tim.b...@am.sony.com Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_bt.c |5 ++--- kernel/debug/kdb/kdb_cmds |4 kernel/debug/kdb

[Kgdb-bugreport] [GIT PULL] kgdb/kdb updates for 3.1

: Linux 3.0 (2011-07-21 19:17:23 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus Jason Wessel (4): kdb: cleanup unused variables missed in the original kdb merge kdb,kgdb: Implement switch and pass

[Kgdb-bugreport] [PATCH 2/4] kdb, kgdb: Implement switch and pass buffer from kdb - gdb

was zero'ing out the character buffer and this could lead to gdb failing to connect at all, or a lengthy pause could occur on the initial connect. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/gdbstub.c | 22 +++--- kernel/debug/kdb/kdb_debugger.c | 17

[Kgdb-bugreport] [PATCH 4/4] kdb, kgdb: Allow arbitrary kgdb magic knock sequences

$D#44+ Example 2 cold start test: echo g /proc/sysrq-trigger $3#33 The second one should re-enter kdb's shell right away and is purely a test. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_io.c | 28 1 files changed, 20 insertions

[Kgdb-bugreport] [PATCH 3/4] kdb: Remove all references to DOING_KGDB2

The DOING_KGDB2 was originally a state variable for one of the two ways to automatically transition from kdb to kgdb. Purge all these variables and just use one single state for the transition. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_debugger.c |4

Re: [Kgdb-bugreport] Question on monitor command over serial connection

On 08/02/2011 03:05 PM, Francois wrote: Hi, I'm using a 3.0 Kernel on x86 platform. I'm debugging over a (virtual) serial port. Here is the way I'm usually doing it - gdb is running on the host, and I attach to the Linux kernel running on the guest with target remote /dev/pts/.. - on the

Re: [Kgdb-bugreport] patch for kgdb.tmpl (for make pdfdocs)

On 12/13/2011 10:30 AM, Rajaneesh Acharya wrote: From 66937ca9088ebce297d78719a1487d7b07fdd6e9 Mon Sep 17 00:00:00 2001 From: Rajaneesh Acharya rajaneesh.acha...@yahoo.com Date: Tue, 13 Dec 2011 10:46:08 -0500 Subject: [PATCH] The following are the enhancements that removed the errors while

Re: [Kgdb-bugreport] Anyone used KDB single-stepping on ARM

On 10/12/2011 12:41 PM, Tim Bird wrote: I've tried to use single-stepping ('ss' command) on ARM from KDB, without success. Has anyone done this - is it currently supported on ARM? It is only supported via patches that are not in the mainline kernel the same is also true of the MIPS

Re: [Kgdb-bugreport] [PATCH] KDB: Fix usability issues relating to the 'enter' key.

On 02/17/2012 05:52 PM, Andrei Warkentin wrote: This fixes the following problems: 1) Typematic-repeat of 'enter' gives warning message. 2) Use of 'keypad enter' gives warning message. 3) Lag on the order of seconds between break and make when expecting the enter break code. Seen under

Re: [Kgdb-bugreport] [PATCH] KDB: Fix usability issues relating to the 'enter' key.

On 02/26/2012 07:10 AM, Jason Wessel wrote: On 02/17/2012 05:52 PM, Andrei Warkentin wrote: This fixes the following problems: 1) Typematic-repeat of 'enter' gives warning message. 2) Use of 'keypad enter' gives warning message. 3) Lag on the order of seconds between break and make when

Re: [Kgdb-bugreport] [PATCH] KDB: Fix usability issues relating to the 'enter' key.

On 02/26/2012 07:04 PM, Andrei Warkentin wrote: Hi, - Original Message - From: Jason Wessel jason.wes...@windriver.com To: Andrei Warkentin andr...@vmware.com Cc: kgdb-bugreport@lists.sourceforge.net, linux-ker...@vger.kernel.org Sent: Sunday, February 26, 2012 8:58:37 AM Subject

Re: [Kgdb-bugreport] [PATCHv3 1/3] NETPOLL: Extend rx_hook support.

On 02/26/2012 09:30 PM, Andrei Warkentin wrote: From: Andrei Warkentin andr...@vmware.com Pass down source information to rx_hook, useful for accepting connections from unspecified clients. Cc: kgdb-bugreport@lists.sourceforge.net Cc: Jason Wessel jason.wes...@windriver.com Cc: Matt

Re: [Kgdb-bugreport] [PATCH] KDB: Fix usability issues relating to the 'enter' key.

On 02/27/2012 05:18 PM, Andrei Warkentin wrote: Hi, - Original Message - From: Jason Wessel jason.wes...@windriver.com To: Andrei Warkentin awarken...@vmware.com Cc: kgdb-bugreport@lists.sourceforge.net, linux-ker...@vger.kernel.org, Andrei Warkentin andr...@vmware.com Sent

Re: [Kgdb-bugreport] [PATCH] KDB: Fix usability issues relating to the 'enter' key.

I think we are a lot closer this time. I attached a new patch based on your prior version. On 02/27/2012 10:26 PM, Andrei Warkentin wrote: This fixes the following problems: 1) Typematic-repeat of 'enter' gives warning message and leaks make/break if KDB exits. Repeats look something like

Re: [Kgdb-bugreport] [PATCHv3 1/3] NETPOLL: Extend rx_hook support.

On 02/27/2012 05:33 PM, Andrei Warkentin wrote: From: Jason Wessel jason.wes...@windriver.com To: Andrei Warkentin andrey.warken...@gmail.com Cc: net...@vger.kernel.org, linux-ker...@vger.kernel.org, Andrei Warkentin andr...@vmware.com, kgdb-bugreport@lists.sourceforge.net, Matt Mackall m

Re: [Kgdb-bugreport] [PATCHv3 1/3] NETPOLL: Extend rx_hook support.

On 03/01/2012 03:04 PM, Andrei Warkentin wrote: - Original Message - From: Andrei Warkentin awarken...@vmware.com To: Jason Wessel jason.wes...@windriver.com Cc: net...@vger.kernel.org, linux-ker...@vger.kernel.org, Andrei Warkentin andr...@vmware.com, kgdb-bugreport

Re: [Kgdb-bugreport] [PATCH 3/4] kgdb: Respect that flush op is optional

On 03/16/2012 07:17 AM, Jan Kiszka wrote: Not all kgdb I/O drivers implement a flush operation. Adjust gdbstub_exit accordingly. The flush is certainly optional. The reason we never saw this bug is because it was only used by some code not in the mainline, where it is in fact patched. The

Re: [Kgdb-bugreport] [PATCH 4/4] kgdb: x86: Detach gdb if machine shuts down or reboots

On 03/16/2012 07:17 AM, Jan Kiszka wrote: Hook into machine restart/power-off/halt handlers and call gdbstub_exit so that a attached gdb frontend is properly informed. If kgdb is disabled or no frontend attached, gdbstub_exit will do nothing. We have long had an out of tree patch which

Re: [Kgdb-bugreport] [PATCH 1/4] kgdb: x86: Return all segment registers also in 64-bit mode

On 03/16/2012 07:17 AM, Jan Kiszka wrote: Even if the content is always 0, gdb expects us to return also ds, es, fs, and gs while in x86-64 mode. Do this to avoid ugly errors on info registers. Signed-off-by: Jan Kiszka jan.kis...@siemens.com --- arch/x86/include/asm/kgdb.h |6 +-

Re: [Kgdb-bugreport] [PATCH 2/4] kgdb: Make gdbstub_exit a nop unless gdb is attached

On 03/16/2012 07:17 AM, Jan Kiszka wrote: This allows to call gdbstub_exit without worrying if - CONFIG_KGDB is enabled - if an kgdb I/O driver is loaded - if a gdb frontend is currently attached If you took a look at the alternate patch I sent in the 4 of 4 response, I made a modification

Re: [Kgdb-bugreport] [PATCH 3/4] kgdb: Respect that flush op is optional

On 03/16/2012 07:53 AM, Jan Kiszka wrote: On 2012-03-16 13:46, Jason Wessel wrote: On 03/16/2012 07:17 AM, Jan Kiszka wrote: Not all kgdb I/O drivers implement a flush operation. Adjust gdbstub_exit accordingly. The flush is certainly optional. The reason we never saw this bug is because

Re: [Kgdb-bugreport] [PATCH 1/4] kgdb: x86: Return all segment registers also in 64-bit mode

On 03/19/2012 08:52 AM, Jan Kiszka wrote: On 2012-03-16 16:57, Jason Wessel wrote: The rest should be fine. I can test this and add it to the merge queue with the NUMREGBYTES change, unless you disagree. I don't disagree. :) Sounds fine. I added this to the merge queue for the 3.4 kernel

Re: [Kgdb-bugreport] [PATCH 4/4] kgdb: x86: Detach gdb if machine shuts down or reboots

On 03/19/2012 08:49 AM, Jan Kiszka wrote: An arch-independent hook has its advantages, no question. Maybe we should just start this way and then evolved on top as needed. Sounds good to me. I added the reboot notifier patch into the merge queue for kgdb/kdb. I was wondering why those

[Kgdb-bugreport] KGDB / KDB Merge queue for 3.4

. Jan Kiszka (2): kgdb: x86: Return all segment registers also in 64-bit mode kgdb: Respect that flush op is optional Jason Wessel (2): kgdb,debug-core,gdbstub: Hook the reboot notifier for debugger detach kgdb,debug_core: add the ability to control the reboot notifier

[Kgdb-bugreport] [PATCH 2/5] kgdb: Respect that flush op is optional

From: Jan Kiszka jan.kis...@siemens.com Not all kgdb I/O drivers implement a flush operation. Adjust gdbstub_exit accordingly. Signed-off-by: Jan Kiszka jan.kis...@siemens.com Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/gdbstub.c |3 ++- 1 files changed, 2

[Kgdb-bugreport] [PATCH 3/5] kgdb, debug-core, gdbstub: Hook the reboot notifier for debugger detach

, SYS_REBOOT, etc... Reported-by: Jan Kiszka jan.kis...@siemens.com Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/debug_core.c | 17 + kernel/debug/gdbstub.c|7 +++ 2 files changed, 24 insertions(+), 0 deletions(-) diff --git a/kernel/debug

[Kgdb-bugreport] [PATCH 5/5] kgdb, debug_core: add the ability to control the reboot notifier

Signed-off-by: Jason Wessel jason.wes...@windriver.com --- Documentation/DocBook/kgdb.tmpl | 17 + kernel/debug/debug_core.c | 16 2 files changed, 33 insertions(+), 0 deletions(-) diff --git a/Documentation/DocBook/kgdb.tmpl b/Documentation/DocBook/kgdb.tmpl

[Kgdb-bugreport] [PATCH 4/5] KDB: Fix usability issues relating to the 'enter' key.

executed anytime the kdb_main loop exits. Tested on QEMU. Set a bp on atkbd.c to verify no scan code was leaked. Cc: Andrei Warkentin andr...@vmware.com [jason.wes...@windriver.com: move cleanup calls to kdb_main.c] Signed-off-by: Andrei Warkentin andrey.warken...@gmail.com Signed-off-by: Jason

Re: [Kgdb-bugreport] [PATCH 4/4] kgdb: x86: Detach gdb if machine shuts down or reboots

On 03/20/2012 06:18 AM, Sergei Shtylyov wrote: Hello. On 20-03-2012 5:00, Jason Wessel wrote: An arch-independent hook has its advantages, no question. Maybe we should just start this way and then evolved on top as needed. Sounds good to me. I added the reboot notifier patch into the merge

Re: [Kgdb-bugreport] Fwd: [PATCH] kdb: Avoid using dbg_io_ops until it is initialized

On 03/20/2012 11:34 AM, Tim Bird wrote: Jason, This patch has apparently fallen through the cracks. Can you please apply? This fixes a kernel panic for a use case where I'm setting a breakpoint from kdb_cmds on kernel startup. In this case, without this patch dbg_io_ops is used before it

Re: [Kgdb-bugreport] [PATCH] kdb: Add message about CONFIG_DEBUG_RODATA on failure to install breakpoint

suggestions about how to use the debugger. Reported-by: Tim Bird tim.b...@am.sony.com Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_bp.c |7 +++ 1 files changed, 7 insertions(+), 0 deletions(-) diff --git a/kernel/debug/kdb/kdb_bp.c b/kernel/debug/kdb/kdb_bp.c

Re: [Kgdb-bugreport] [PATCH] kdb: Avoid using dbg_io_ops until it is initialized

On 09/21/2011 03:19 PM, Tim Bird wrote: This fixes a bug with setting a breakpoint during kdb initialization (from kdb_cmds). Any call to kdb_printf() before the initialization of the kgdboc serial console driver (which happens much later during bootup than kdb_init), results in kernel panic

[Kgdb-bugreport] [PATCH 0/2] Fix KGDB to work with CONFIG_DEBUG_RODATA using kprobe API

compiled with CONFIG_DEBUG_RODATA. Comments are welcome of course. Thanks, Jason. --- Jason Wessel (2): kgdb,debug_core: pass the breakpoint struct instead of address and memory kgdb,debug_core,kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints drivers/misc/kgdbts.c

[Kgdb-bugreport] [PATCH 2/2] kgdb, debug_core, kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints

attempt to use the traditional probe_kernel_write(), and next try using a kprobe breakpoint. The kgdb test suite was updated to run all the software breakpoint tests when using a kernel with built with CONFIG_DEBUG_RODATA. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- drivers/misc/kgdbts.c

[Kgdb-bugreport] [PATCH 1/2] kgdb, debug_core: pass the breakpoint struct instead of address and memory

() and kgdb_arch_remove_breakpoint(). A future commit adds the logic for the kprobe breakpoint type. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- include/linux/kgdb.h |4 +- kernel/debug/debug_core.c | 53 2 files changed, 26 insertions(+), 31 deletions

Re: [Kgdb-bugreport] [PATCH 2/2] kgdb, debug_core, kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints

On 03/21/2012 09:53 PM, Masami Hiramatsu wrote: (2012/03/22 2:55), Jason Wessel wrote: There has long been a limitation using software breakpoints with a kernel compiled with CONFIG_DEBUG_RODATA. The kprobe breakpoint code has its own text_poke() function which accommodates writing

Re: [Kgdb-bugreport] kdb: Avoid using dbg_io_ops until it is initialized

On 03/22/2012 01:30 AM, Dan Carpenter wrote: Hello Tim Bird, This is a semi-automatic email about new static checker warnings. The patch 3492c71d374c: kdb: Avoid using dbg_io_ops until it is initialized from Sep 21, 2011, leads to the following Smatch complaint:

Re: [Kgdb-bugreport] [PATCH 2/2] kgdb, debug_core, kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints

On 03/23/2012 09:08 AM, Masami Hiramatsu wrote: (2012/03/22 20:57), Jason Wessel wrote: I will use the arch specific provision to override the kgdb_arch_set_breakpoint() and use the text_poke() directly. Thanks! that's what I meant. You can use __weak attribute. I created and tested

[Kgdb-bugreport] [GIT PULL] KGDB/KDB updates for the 3.4 merge window

breakpoints Andrei Warkentin (1): KDB: Fix usability issues relating to the 'enter' key. Jan Kiszka (2): kgdb: x86: Return all segment registers also in 64-bit mode kgdb: Respect that flush op is optional Jason

Re: [Kgdb-bugreport] kdb: Avoid using dbg_io_ops until it is initialized

On 03/23/2012 11:39 AM, Tim Bird wrote: On 03/22/2012 05:06 AM, Jason Wessel wrote: On 03/22/2012 01:30 AM, Dan Carpenter wrote: Hello Tim Bird, This is a semi-automatic email about new static checker warnings. The patch 3492c71d374c: kdb: Avoid using dbg_io_ops until it is initialized

Re: [Kgdb-bugreport] [PATCH 2/2] kgdb, debug_core, kgdbts: End DEBUG_RODATA limitation using kprobe breakpoints

On 03/26/2012 04:46 AM, Masami Hiramatsu wrote: (2012/03/23 23:38), Jason Wessel wrote: On 03/23/2012 09:08 AM, Masami Hiramatsu wrote: (2012/03/22 20:57), Jason Wessel wrote: I will use the arch specific provision to override the kgdb_arch_set_breakpoint() and use the text_poke() directly

Re: [Kgdb-bugreport] KGDB error in kernel 2.6.32

On 03/28/2012 07:01 AM, Rahul Viradiya wrote: I am using kernel version 2.6.32.5.. gdbstub.c is not present in path kernel/debug. Is there anything I need to install? I have compiled the kernel with kgdb support. Applied patch for kdb from

[Kgdb-bugreport] [PATCH 0/6] KGDB/KDB/KGDBTS various regression fixes for 2.6.x - 3.4

that they work. :-) Cheers, Jason. --- Jason Wessel (6): kdb: Fix smatch warning on dbg_io_ops-is_console kgdbts: Fix kernel oops with CONFIG_DEBUG_RODATA kgdbts: (1 of 2) fix single step awareness to work correctly with SMP kgdbts: (2 of 2) fix single step awareness

[Kgdb-bugreport] [PATCH 2/6] kgdbts: Fix kernel oops with CONFIG_DEBUG_RODATA

...] This commit re-orders the running of the tests and puts the RODATA check into its own function so as to correctly avoid the kernel oops by detecting and using the hw breakpoints. Cc: sta...@vger.kernel.org # = 2.6.26 Signed-off-by: Jason Wessel jason.wes...@windriver.com --- drivers/misc/kgdbts.c | 52

[Kgdb-bugreport] [PATCH 5/6] kgdb, debug_core: pass the breakpoint struct instead of address and memory

-by: Jason Wessel jason.wes...@windriver.com --- include/linux/kgdb.h |4 ++-- kernel/debug/debug_core.c | 53 - 2 files changed, 26 insertions(+), 31 deletions(-) diff --git a/include/linux/kgdb.h b/include/linux/kgdb.h index fa39183..e5d689c

[Kgdb-bugreport] [PATCH 4/6] kgdbts: (2 of 2) fix single step awareness to work correctly with SMP

concurrently on different CPUs. This also means we wait at least one second before unplumbing the debugger connection at the very end, so as respond to any debug threads waiting to be serviced. Cc: sta...@vger.kernel.org # = 3.0 Signed-off-by: Jason Wessel jason.wes...@windriver.com

[Kgdb-bugreport] [PATCH 3/6] kgdbts: (1 of 2) fix single step awareness to work correctly with SMP

: sta...@vger.kernel.org # = 2.6.26 Signed-off-by: Jason Wessel jason.wes...@windriver.com --- drivers/misc/kgdbts.c | 54 +++-- 1 file changed, 43 insertions(+), 11 deletions(-) diff --git a/drivers/misc/kgdbts.c b/drivers/misc/kgdbts.c index 997e94d

[Kgdb-bugreport] [PATCH 1/6] kdb: Fix smatch warning on dbg_io_ops-is_console

get set when kdb is fully active and initialized. If we ever encounter changes or defects in the KDB_PAGER state we do not want to crash the kernel in a kdb_printf/printk. CC: Tim Bird tim.b...@am.sony.com Reported-by: Dan Carpenter dan.carpen...@oracle.com Signed-off-by: Jason Wessel jason.wes

[Kgdb-bugreport] [PATCH 6/6] x86, kgdb: Fix DEBUG_RODATA limitation using text_poke()

Inspried-by: Masami Hiramatsu masami.hiramatsu...@hitachi.com Signed-off-by: Jason Wessel jason.wes...@windriver.com --- arch/x86/kernel/kgdb.c | 60 include/linux/kgdb.h |3 ++- 2 files changed, 62 insertions(+), 1 deletion(-) diff --git a/arch

Re: [Kgdb-bugreport] Kgdb Gdb on a serial link

On 03/28/2012 02:01 AM, Gilles Allard wrote: On Wednesday 22 February 2012 10:32:43 Gilles Allard wrote: To debug a driver, I try to use Kgdb along with Gdb on a serial link between an host machine and the target one running the buggy driver. - Up to now, everything seems to be as

[Kgdb-bugreport] [GIT PULL] KGDB/KDB regression fixes for 3.4-rc2

for all archs with HW single stepping Jason Wessel (6): kdb: Fix smatch warning on dbg_io_ops-is_console kgdbts: Fix kernel oops with CONFIG_DEBUG_RODATA kgdbts: (1 of 2) fix single step awareness to work correctly

Re: [Kgdb-bugreport] Trouble setting software breakpoints

On 04/07/2012 12:11 PM, Ward, David - 0663 - MITLL wrote: Nevermind -- I added the commits tagged 'for_linus-3.4-rc2' onto my kernel and I can set software breakpoints now. Glad to see it is working for you now. I had already sent the patch series to the -stable/-longterm trees, and they are

[Kgdb-bugreport] [PATCH 1/3] kdb: Remove unused KDB_FLAG_ONLY_DO_DUMP

This code cleanup was missed in the original kdb merge, and this code is simply not used at all. The code that was previously used to set the KDB_FLAG_ONLY_DO_DUMP was removed prior to the initial kdb merge. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- include/linux/kdb.h

[Kgdb-bugreport] [PATCH 0/3] patches for the 3.5 merge window.

This is just a simple series for the 3.5 merge window, and I'll send the pull request after the next linux-next cycle unless anyone pipes up. Cheers, Jason. -- Live Security Virtual Conference Exclusive live event will

[Kgdb-bugreport] [PATCH 3/3] kernel/debug: Make use of KGDB_REASON_NMI

for the master CPU. Signed-off-by: Anton Vorontsov anton.voront...@linaro.org Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_debugger.c |4 1 file changed, 4 insertions(+) diff --git a/kernel/debug/kdb/kdb_debugger.c b/kernel/debug/kdb/kdb_debugger.c index 8b68ce7

[Kgdb-bugreport] [PATCH 2/3] kdb: Remove cpu from the more prompt

Having the CPU in the more prompt is completely redundent vs the standard kdb prompt, and it also wastes 32 bytes on the stack. Signed-off-by: Jason Wessel jason.wes...@windriver.com --- kernel/debug/kdb/kdb_io.c | 11 --- 1 file changed, 11 deletions(-) diff --git a/kernel/debug/kdb

Re: [Kgdb-bugreport] [PATCH 01/11] kernel/debug: Make use of KGDB_REASON_NMI

On 07/30/2012 06:58 AM, Anton Vorontsov wrote: Currently kernel never set KGDB_REASON_NMI. We do now, when we enter KGDB/KDB from an NMI. This is not to be confused with kgdb_nmicallback(), NMI callback is an entry for the slave CPUs during CPUs roundup, but REASON_NMI is the entry for the

[Kgdb-bugreport] [GIT PULL] KGDB/KDB/dbgp fixes for 3.6-rc1

Anton Vorontsov (1): kernel/debug: Make use of KGDB_REASON_NMI Colin Ian King (1): USB: echi-dbgp: increase the controller wait time to come out of halt. Jason Wessel (2): kdb: Remove unused KDB_FLAG_ONLY_DO_DUMP kdb: Remove cpu from the more prompt

[Kgdb-bugreport] [PATCH 4/4] kgdboc: Accept either kbd or kdb to activate the vga + keyboard kdb shell

abbreviation for keyboard). With this change kgdboc will now accept either to mean the same thing: kgdboc=kbd kgdboc=kdb Signed-off-by: Jason Wessel jason.wes...@windriver.com --- drivers/tty/serial/kgdboc.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/tty

[Kgdb-bugreport] [PATCH 2/4] pmac_zilog, kdb: Fix console poll hook to return instead of loop

a...@linux.intel.com Cc: Greg Kroah-Hartman gre...@linuxfoundation.org Signed-off-by: Jason Wessel jason.wes...@windriver.com --- drivers/tty/serial/pmac_zilog.c | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/drivers/tty/serial/pmac_zilog.c b/drivers/tty/serial/pmac_zilog.c

[Kgdb-bugreport] [PATCH 1/4] mips, kgdb: fix recursive page fault with CONFIG_KPROBES

. Miller da...@davemloft.net Signed-off-by: Jason Wessel jason.wes...@windriver.com --- arch/mips/kernel/kgdb.c |9 + 1 file changed, 9 insertions(+) diff --git a/arch/mips/kernel/kgdb.c b/arch/mips/kernel/kgdb.c index f4546e9..23817a6 100644 --- a/arch/mips/kernel/kgdb.c +++ b/arch

Re: [Kgdb-bugreport] [PATCH 02/11] kdb: Implement disable_nmi command

On 09/13/2012 10:03 AM, Anton Vorontsov wrote: This command disables NMI-entry. If NMI source has been previously shared with a serial console (debug port), this effectively releases the port from KDB exclusive use, and makes the console available for normal use. Of course, NMI can be

Re: [Kgdb-bugreport] [PATCH 07/11] tty/serial: Add kgdb_nmi driver

On 09/13/2012 10:03 AM, Anton Vorontsov wrote: This special driver makes it possible to temporary use NMI debugger port as a normal console by issuing 'nmi_console' command (assuming that the port is attached to KGDB). Unlike KDB's disable_nmi command, with this driver you are always able

Re: [Kgdb-bugreport] [PATCH] kdb: Remove unhandled ssb command

On 02/12/2013 04:34 AM, Vincent wrote: The 'ssb' command can only be handled when we have a disassembler, to check for branches, so remove the 'ssb' command for now. Wow, that was fast. This looks fine too. I'll add it to the merge queue. Thanks! Jason. Signed-off-by: Vincent Stehlé

[Kgdb-bugreport] [GIT PULL] KGDB/KDB fixes for 3.9

ppc64 support for kgdbts Add missing kconfig option from original kdb port for dealing with catastrophic kernel crashes such that you can reboot automatically on continue from kdb Jason Wessel (4): kdb: Fix

Re: [Kgdb-bugreport] [PATCH] Fixed dead ifdef block by adding missing Kconfig option.

'5d5314d6795f3c1c0f415348ff8c51f7de042b77' by Jason Wessel. This patchset (kdb: core for kgdb back end (1 of 2)) added platform independent part of kdb to the linux kernel. The Kernel option however, even though it had the same options and behaviour on all supported architectures, was part of the x86 and ia64 patchset of KDB

Re: [Kgdb-bugreport] [PATCH 03/15] KDB: up the default LINES value

On 03/25/2013 01:50 PM, Mike Travis wrote: Currently the default for the # of lines displayed by the KDB pager is 24. This does not allow all of the lines for the entry messages, reg dump and process trace. Increase it to something more reasonable. Unfortunately this is something that

Re: [Kgdb-bugreport] [PATCH 01/15] KDB: fix the interrupt of the KDB btc command

On 03/25/2013 01:50 PM, Mike Travis wrote: The KDB 'btc' (backtrace cpus) command ignores the 'quit' reply to the 'more' prompt. This is quite annoying when you have a large number of processors and thousands of lines are being printed. This fixes that problem. Merged to kgdb-next and

Re: [Kgdb-bugreport] kdb: kgdb: CONFIG_DEBUG_RODATA setting?

On 04/09/2013 08:06 AM, Sedat Dilek wrote: config DEBUG_RODATA bool Write protect kernel read-only data structures - default y depends on DEBUG_KERNEL + default n if KGDB + default y ---help--- Mark the kernel read-only data as write-protected in the

Re: [Kgdb-bugreport] kgdb_mips64_watchpoint

On 07/24/2014 03:23 AM, skunlin wrote: Recently, when doing kgdb on my cpu which arch is mips_64, I encounter some problems. arch : mips_64-octeon kernel-version: linux 2.6.32 when setting watchpoints on the kernel , it logs that (gdb) watch jiffies Sending packet:

Re: [Kgdb-bugreport] Some KGDB conceptual questions

On 10/09/2014 11:17 AM, joaoandrefe...@sapo.pt wrote: Hello all, I'm trying to use KGDB for some days now, and since I'm still getting some errors that need to be fixed (working on it), I think that for now it's better to ask here if what I'm trying to achieve is theoretically

Re: [Kgdb-bugreport] [PATCH] kdmx fails when 0xff is read from serial port

On 10/22/2014 02:12 AM, Frank Rowand wrote: From: Frank Rowand frank.row...@sonymobile.com kdmx incorrectly detects a 0xff character read from the serial port as a read error. The false read error results in kdmx terminating. Signed-off-by: Frank Rowand frank.row...@sonymobile.com Thanks!

Re: [Kgdb-bugreport] Instrument KGDB locally on target: is it possible?

On 11/06/2014 05:41 PM, Pete Delaney wrote: I'm wondering how complex (or possible) would be to instrument locally KGDB on the target machine, i. e., somehow remove the serial connection (and the host machine, GDB) from the setup, since on this new scenario the host (GDB) and the target

Re: [Kgdb-bugreport] Getting Linux kernel symbols to resolve in kgdb

On 01/05/2015 03:19 PM, Jake Oshins wrote: Please forgive my ignorant question. I'm very new to this. I've built a Linux kernel from a source tree cloned from Linus's tree with a tag of v3.18.1 , which was from the middle of last month. I've installed it by building a Deb package and

Re: [Kgdb-bugreport] kgdb-next not pushed to Linus for 3.19

On 01/06/2015 03:21 PM, Andrew Morton wrote: On Tue, 06 Jan 2015 10:57:42 -0800 Joe Perches j...@perches.com wrote: On Tue, 2015-01-06 at 18:54 +, Daniel Thompson wrote: Hi Jason I'm trying to figure out what to do with my long-outstanding kgdb/kdb patches in preparation for the 3.20

Re: [Kgdb-bugreport] [PATCH] kgdb: fix potential out-of-bounds access

On 01/12/2015 01:45 PM, Brian Norris wrote: CPU arrays (e.g., kgdb_info[]) are indexed from 0 (inclusive) to NR_CPUS (exclusive). Pointed out by Coverity, CID 1262269 Signed-off-by: Brian Norris computersforpe...@gmail.com Cc: Jason Wessel jason.wes...@windriver.com --- Untested kernel

[Kgdb-bugreport] [GIT PULL] KGDB/KDB fixes for 3.19-rc4

Linus, Please pull the kgdb tree bug fixes. These have been around since 3.17 and in kgdb-next for the last 9 weeks and some will go back to -stable. Summary of changes: KGDB/KDB fixes and cleanups Cleanups kdb: Remove unused command flags, repeat flags and KDB_REPEAT_NONE Fixes

Re: [Kgdb-bugreport] [PATCH] kdb: Fix handling of kallsyms_symbol_next() return value

On 03/02/2015 08:13 AM, Daniel Thompson wrote: kallsyms_symbol_next() returns a boolean (true on success). Currently kdb_read() tests the return value with an inequality that unconditionally evaluates to true. This is fixed in the obvious way and, since the conditional branch is supposed to

Re: [Kgdb-bugreport] using sysrq-trigger to start kgdb

On 07/29/2015 08:45 AM, נעמה ממן wrote: Hello, cross compiled raspberry pi kernel using an Ubuntu virtual machine. Using this configurations: CONFIG_DEBUG_INFO=y CONFIG_MAGIC_SYSRQ=y CONFIG_FRAME_POINTER=y CONFIG_KGDB=y CONFIG_KGDB_SERIAL_CONSOLE=y CONFIG_KGDB_KDB=y

Re: [Kgdb-bugreport] [PATCH 4/4] drivers/misc: make kgdbts.c slightly more explicitly non-modular

. :-) Acked-by: Jason Wessel jason.wes...@windriver.com -- ___ Kgdb-bugreport mailing list Kgdb-bugreport@lists.sourceforge.net https://lists.sourceforge.net/lists

Re: [Kgdb-bugreport] [PATCH -repost] kgdb: depends on VT

:(.text+0x7b5d5): undefined reference to `vc_cons' > > kgdboc.o is built when KGDB_SERIAL_CONSOLE is set. So make > KGDB_SERIAL_CONSOLE depend on HW_CONSOLE which includes those symbols. Acked-by: Jason Wessel <jason.wes...@windriver.com> I'll put this in the kgdb-next branch and sub

Re: [Kgdb-bugreport] [RESEND PATCH] arm64: kgdb: fix single stepping

On 04/20/2015 08:13 PM, AKASHI Takahiro wrote: > Jason, > > Could you please review my patch below? > See also arm64 maintainer's comment: > http://lists.infradead.org/pipermail/linux-arm-kernel/2015-January/313712.html > > Thanks, > -Takahiro AKASHI > > I tried to verify kgdb in vanilla kernel on

Re: [Kgdb-bugreport] [RESEND PATCH] arm64: kgdb: fix single stepping

On 09/15/2016 05:41 AM, Daniel Thompson wrote: > On 15/09/16 08:56, AKASHI Takahiro wrote: >> On Wed, Sep 14, 2016 at 03:58:51PM +0100, Will Deacon wrote: >>> Hi Akashi, >>> >>> On Tue, Apr 21, 2015 at 02:13:13AM +0100, AKASHI Takahiro wrote: Could you please review my patch below? See

Re: [Kgdb-bugreport] [RESEND PATCH] arm64: kgdb: fix single stepping

On 09/15/2016 11:32 PM, AKASHI Takahiro wrote: > @@ -176,18 +183,14 @@ int kgdb_arch_handle_exception(int exception_vector, > int signo, >>> * over and over again. >>> */ >>> kgdb_arch_update_addr(linux_regs, remcom_in_buffer); >>> -

Re: [Kgdb-bugreport] [RESEND PATCH] arm64: kgdb: fix single stepping

On 09/16/2016 02:45 AM, Will Deacon wrote: > On Fri, Sep 16, 2016 at 01:32:19PM +0900, AKASHI Takahiro wrote: >> On Thu, Sep 15, 2016 at 08:04:57AM -0500, Jason Wessel wrote: >>> I added the patch to kgdb-next after fixing up the context since it no >>> longer applied

Re: [Kgdb-bugreport] [PATCH] MAINTAINERS: kgdb: Replace Jason with Daniel

On 12/05/2017 08:09 AM, Lee Jones wrote: On Tue, 05 Dec 2017, Daniel Thompson wrote: ... with many, many thanks for Jason for all his hard work. Cc: Jason Wessel <jason.wes...@windriver.com> Signed-off-by: Daniel Thompson <daniel.thomp...@linaro.org> --- Notes: Over the yea

Re: [Kgdb-bugreport] [PATCH] misc: kgdbts: Display progress of asynchronous tests

On 12/12/2017 06:10 AM, Daniel Thompson wrote: kgdbts includes a couple of different "thrashing" style tests that may have long runtimes (especially on simulated platforms) and which run asynchronously. This is uncomfortable for interactive use and makes setting timeouts tricky for automatic

Re: [Kgdb-bugreport] [PATCH 2/3] kdb: drop newline in unknown command output

...@infradead.org> Cc: Daniel Thompson <daniel.thomp...@linaro.org> Cc: Jason Wessel <jason.wes...@windriver.com> Cc: kgdb-bugreport@lists.sourceforge.net --- kernel/debug/kdb/kdb_main.c | 11 +++ 1 file changed, 11 insertions(+) --- lnx-415-rc1.orig/kernel/debug/kdb

Re: [Kgdb-bugreport] [PATCH 2/2] kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson

On 12/06/2017 06:52 PM, Randy Dunlap wrote: On 12/06/2017 02:33 PM, Jason Wessel wrote: L:kgdb-bugreport@lists.sourceforge.net T:git git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/kgdb.git I would urge you to move to a different mailing list server. No argument here

[Kgdb-bugreport] [GIT PULL] KGDB/KDB fixes for 4.15-rc2

Daniel Thompson (1): kdb: Fix handling of kallsyms_symbol_next() return value Jason Wessel (1): kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson MAINTAINERS | 1 + kernel/debug/kdb/kdb_io.c | 2 +- 2 files changed

[Kgdb-bugreport] [PATCH 1/2] kdb: Fix handling of kallsyms_symbol_next() return value

pposed to be unreachable, we also add a WARN_ON(). Reported-by: Dan Carpenter <dan.carpen...@oracle.com> Signed-off-by: Daniel Thompson <daniel.thomp...@linaro.org> Cc: linux-stable <sta...@vger.kernel.org> Signed-off-by: Jason Wessel <jason.wes...@windriver.com> --- kernel/deb

[Kgdb-bugreport] [PATCH 2/2] kgdb/kdb/debug_core: Add co-maintainer Daniel Thompson

Signed-off-by: Jason Wessel <jason.wes...@windriver.com> --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 2811a21..74be63b 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -7659,6 +7659,7 @@ F:security/keys/ KGDB / KDB /debug_c

Re: [Kgdb-bugreport] [PATCH] kdb: use __ktime_get_real_seconds instead of __current_kernel_time

On 10/13/2017 03:26 AM, Daniel Thompson wrote: On 12/10/17 23:40, Andrew Morton wrote: On Thu, 12 Oct 2017 16:06:11 +0200 Arnd Bergmann wrote: kdb is the only user of the __current_kernel_time() interface, which is not y2038 safe and should be removed at some point. The kdb

Re: [Kgdb-bugreport] [PATCH] kdb: use __ktime_get_real_seconds instead of __current_kernel_time

ded a comment about the __ktime_get_real_seconds() not taking the lock because it was done that way in other places in the header file. === extern time64_t ktime_get_real_seconds(void); +/* does not take xtime_lock */ +extern time64_t __ktime_get_real_seconds(void); === Acked-by: Jason Wes

Re: [Kgdb-bugreport] [PATCH] MAINTAINERS: kgdb: Replace Jason with Daniel

On 12/05/2017 10:42 AM, Randy Dunlap wrote: On 12/05/2017 06:55 AM, Daniel Thompson wrote: On 05/12/17 14:37, Jason Wessel wrote: I have a series of 50+ patches for kgdb/kdb/usb which have never been published.  I am not saying that we actually need any of those patches, but it would be nice

Re: [Kgdb-bugreport] [PATCH] MAINTAINERS: kgdb: Replace Jason with Daniel

On 12/05/2017 08:55 AM, Daniel Thompson wrote: On 05/12/17 14:37, Jason Wessel wrote: On 12/05/2017 08:09 AM, Lee Jones wrote: On Tue, 05 Dec 2017, Daniel Thompson wrote: ... with many, many thanks for Jason for all his hard work. Cc: Jason Wessel <jason.wes...@windriver.com> Sign

Re: [Kgdb-bugreport] [PATCH] MAINTAINERS: kgdb: Replace Jason with Daniel

On 12/05/2017 09:14 AM, Lee Jones wrote: Will you also be drafting a MAINTAINERS patch to identify Daniel as co-maintainer? If you're busy, either myself or I'm sure Daniel will be happy to author one. I'll take care of it and get it pushed to the tree. I'd like to get a signed tag

<    1   2   3   4   5   6   7   >