As far as I know kgdbwait still works fine with the 2.6.26 kernel. I
am reasonably certain that at certain points in the kgdb history it has
not worked for kgdboe. kgdbwait is definitely not deprecated, and is
fully supported with kgdboc, kgdboe and the kgdb8250 driver in the
kgdb-dev branch.
Jay Lan wrote:
Jason Wessel wrote:
Jay Lan wrote:
Hi Jason,
Please disregard the above comment. The kernel was hung in running init,
not during booting the kernel. I need to find what caused this problem
in this particular system setup.
Now, i put in kgdbwait
.
The following changes since commit c010b2f76c3032e48097a6eef291d8593d5d79a6:
Linus Torvalds (1):
Merge git://git.kernel.org/.../davem/net-2.6
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 (5
Remove HAVE_ARCH_KGDB_SHADOW_INFO because it does not
exist anywhere in the kernel mainline sources
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
lib/Kconfig.kgdb |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/lib/Kconfig.kgdb b/lib/Kconfig.kgdb
index a5d4b1d
specific kgdb implementation saves the previous state of the
debug hooks and restores them if you unconfigure the kgdb I/O driver.
Kgdb should have no impact on a kernel that has no kgdb I/O driver
configured.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
arch/powerpc/Kconfig
This patch adds the ARCH=arm specific a kgdb backend, originally
written by Deepak Saxena [EMAIL PROTECTED] and George Davis
[EMAIL PROTECTED]. Geoff Levand [EMAIL PROTECTED],
Nicolas Pitre, Manish Lachwani, and Jason Wessel have contributed
various fixups here as well.
The KGDB patch makes one
Add in console polling hooks for the cpm uart for use with kgdb and
kgdboc.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
---
drivers/serial/cpm_uart/cpm_uart_core.c | 95 ++-
1 files changed, 94 insertions(+), 1 deletions(-)
diff --git
There is no technical reason that the kgdb core requires frame
pointers. It is up to the end user of KGDB to decide if they need
them or not.
[ [EMAIL PROTECTED]: removed frame pointers on mips ]
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
Documentation/DocBook/kgdb.tmpl |8
Avi Cohen Stuart wrote:
Hi Jason,
Got me a 2.6.26 kernel, compiled and enabled kgdb. In the kernel config I
only find kgdboc. Does that mean I can only kgdb using a serial console or
can I use kgdboc with my normal console on my laptop?
It seems that kgdb8250 has disappeared...
Avi.
This is a cut and paste from the manual.
http://kernel.org/pub/linux/kernel/people/jwessel/kgdb/
If something is not clear, please help clear up the documentation.
--
NOTE: Kgdboc does not support interrupting the target via the gdb remote
protocol. You must manually send a sysrq-g unless
The BX and DX registers in the gdb serial register packet need to be
flipped for gdb to receive the correct data.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
include/asm-x86/kgdb.h |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/asm-x86/kgdb.h b/include
From: Atsuo Igarashi [EMAIL PROTECTED]
On the ARM architecture, kgdb will crash the kernel if the last byte
of valid memory is written due to a flush_icache_range flushing
beyond the memory boundary.
Signed-off-by: Atsuo Igarashi [EMAIL PROTECTED]
Signed-off-by: Jason Wessel [EMAIL PROTECTED
The tty_find_polling_driver() routine did not correctly check the base
part of the tty name. This can lead to kgdboc selecting an incorrect
driver, as well as accepting a completely invalid tty such as echo
0 /sys/module/kgdboc/parameters/kgdboc.
Signed-off-by: Jason Wessel [EMAIL PROTECTED
if it is single stepping. This
allows kgdb to correctly process an instruction steps if ptrace
happens to be requesting an instruction step over a system call.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
arch/arm/kernel/kgdb.c |2 --
arch/mips/kernel/kgdb.c|3 +--
arch/powerpc/kernel
per event: One time via
DIE_NMI_IPI notification, the second time on DIE_NMI. Removing the first
invocation cures the unhandled NMIs here.
Signed-off-by: Jan Kiszka [EMAIL PROTECTED]
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
arch/x86/kernel/kgdb.c |7 +--
1 files changed, 1
be touched when running
with CONFIG_BOOTPARAM_SOFTLOCKUP_PANIC_VALUE=1, else
the kernel executes a reboot if debugged for too long.
Short log follows:
---
Jan Kiszka (1):
kgdb, x86: Avoid invoking kgdb_nmicallback twice per NMI
Jason Wessel (1):
kgdb: call
The softlockup watchdog needs to be touched when resuming the from the
kgdb stopped state to avoid the printk that a CPU is stuck if the
debugger was active for longer than the softlockup threshold.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
kernel/kgdb.c |3 +++
1 files changed, 3
sonic zhang wrote:
In blackfin SMP architecture, different core has its own L1 SRAM and MMR
memory, which code running on the other core can't access. In current
kgdb
impelemntation, cpus are represented by thread with minus prefix.
If user run thread command in gdb to switch to the
not be safe to have an inline breakpoint
inside the kgdb I/O driver.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
include/linux/kgdb.h |1 +
kernel/kgdb.c| 26 ++
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/include/linux/kgdb.h b
://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git
for_linus
Short log follows:
---
Atsushi Nemoto (1):
kgdb: kgdboc console poll hooks for serial_txx9 uart
Jason Wessel (5):
kgdb: Add the ability to schedule a breakpoint via a tasklet
tty: Fix sparse static
The RX polling hook allows the debugger to hook character input so as
to allow entry to the kernel debugger with a control-c as an example.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
drivers/serial/8250.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
Documentation/DocBook/kgdb.tmpl | 49 ++
drivers/char/tty_io.c |7 +---
drivers/serial/kgdboc.c | 72 +-
drivers/serial/serial_core.c| 24
in tty_io.c to deal with the fact that
the inode and fpath.dentry were NULL with the generic flip structure.
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
drivers/char/tty_io.c | 96 +---
drivers/serial/kgdboc.c| 26
include/linux
to be reimplemented in
architecture specific kgdb.c. Update documentation and prototypes as
well.
Signed-off-by: Sonic Zhang [EMAIL PROTECTED]
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
include/linux/kgdb.h | 42 --
kernel/kgdb.c|6 +++---
2 files
Jason Wessel wrote:
A few minor changes were needed in tty_io.c to deal with the fact that
the inode and fpath.dentry were NULL with the generic flip structure.
After further testing and review one patch hunk has been eliminated.
Signed-off-by: Jason Wessel [EMAIL PROTECTED
From: Atsushi Nemoto [EMAIL PROTECTED]
Implement the serial polling hooks for the serial_txx9 uart for use
with kgdboc.
Signed-off-by: Atsushi Nemoto [EMAIL PROTECTED]
Signed-off-by: Jason Wessel [EMAIL PROTECTED]
---
drivers/serial/serial_txx9.c | 113
console poll hooks for serial_txx9 uart
Jason Wessel (5):
kgdb: Add the ability to schedule a breakpoint via a tasklet
tty: Fix sparse static warning for tty_driver_lookup_tty
kgdboc, tty: Add the rx polling call back capability
kgdboc, 8250: rx polling hook for the 8250
Alan Cox wrote:
On Tue, 21 Oct 2008 14:14:51 -0500
Jason Wessel [EMAIL PROTECTED] wrote:
+unlock_kernel();
+} else {
+tty = tty_driver_lookup_tty(driver, NULL, tty_line);
+if (!tty) {
+tty = tty_init_dev(driver, tty_line, 0);
+inc_tty
Alan Cox wrote:
tty: Fix sparse static warning for tty_driver_lookup_tty
kgdboc, tty: Add the rx polling call back capability
kgdboc, 8250: rx polling hook for the 8250 driver
kgdboc, amba-pl011: rx polling hook for the amba-pl011 driver
NAK.
The kgdb merge request
Bruce Beare (bbeare) wrote:
Jason,
I am interested in backporting KGDB (mips, PPC, x86) to my 2.6.24 kernel. I
have found your kgdb-next git tree and see that you have (at least some)
support in there for all of these architectures. I'd like to first get a
read-out on the status of KGDB
Caz Yokoyama wrote:
Hello,
I created a patch which has following modifications. I am glad if you
integrate the patch into kgdb.
* against gdb-6.8 instead of gdb-6.4.
* debug Linux 2.6.27.8 and kgdb modified 2.6.18.92.el5.
* Linux 2.6.27.8 should be kgdb and Magic SysRq activated.
*
Denis Joseph Barrow wrote:
Hi All,
ctrl-alt-sysrq G doesn't get me into kgdb anymore it doesn't appear as an
option in the sysrq menu.
I think it might be some kind of problem with the sysrq code.
I've done this
CONFIG_HAVE_ARCH_KGDB=y
CONFIG_KGDB=y
CONFIG_KGDB_SERIAL_CONSOLE=y
Frank Rowand wrote:
gdb command set remote debug 1 is not valid, change to correct command.
Signed-off-by: Frank Rowand frank.row...@am.sony.com
Thanks Frank,
I merged this change.
Cheers,
Jason.
--
Apps
It is prefered that you used the kgdb mailling list for question and
problem reports.
kgdb-bugreport@lists.sourceforge.net
You do not need to patch the kernel assuming you are ok with using kgdb
over console (see the instructions that come with the kernel).
The gdb mod patch is not applicable
srikanth krishnakar wrote:
The debug setup simply gives Time out error :
(gdb) set remotebaud 9600
(gdb) set debug remote 1
(gdb) target remote /dev/ttyS0
Remote debugging using /dev/ttyS0
Sending packet: $qSupported#37...Sending packet: $qSupported#37...Sending
packet:
Derek Atkins wrote:
srikanth krishnakar skrishna...@gmail.com writes:
On Tue, Apr 28, 2009 at 10:35 PM, Derek Atkins warl...@mit.edu wrote:
Jason,
I pulled down some of the patches and applied them to my F9 2.6.27
kernel SRC RPM but then the kernel wont boot. When I
Derek Atkins wrote:
Jason Wessel jason.wes...@windriver.com writes:
I think that yes, it probably is compiled with CONFIG_SMP=y. That never
used to be a problem before. Is it a problem now? Strangely I used
the same .config to manually build the 2.2.7 kgdb git snapshot I pulled
down
Jason Wessel wrote:
Derek Atkins wrote:
Jason Wessel jason.wes...@windriver.com writes:
I think that yes, it probably is compiled with CONFIG_SMP=y. That never
used to be a problem before. Is it a problem now? Strangely I used
the same .config to manually build the 2.2.7
Derek Atkins wrote:
Quoting Jason Wessel jason.wes...@windriver.com:
I'm currently booting with:
kgdb8250=ttyS0,115200 kgdbwait kgdbcon=ttyS0,115200
What am I missing to get the printk output to kgdb like I used to?
I had a 2.6.30-rc3 already built so I tried it out
srikanth krishnakar wrote:
Hi all,
Target : PowerPC, Virtex-440 Generic
Serial port : Xilinx 16550 Uart ( depends on OF_PLATFORM)
Further investigation of KGDBOC on PowerPC shows that kgdboc hangs at :
In file : arch/powerpc/include/asm/kgdb.h
*static inline void*
srikanth krishnakar wrote:
Hi Jason,
Re attempted with inserting a printk in kernel/kgdb.c kgdb_handle_exception()
function but seems the kgdb exception has never occurred !!
Does the PowerPC uses PowerPC64 hooks ??
I am not sure what you mean by this. The hook points for catching
This is a RFC patch. The work to possibly merge kdb and kgdb is being
evaluated and this patch is considered only a proof of concept or
prototype.
For kdb, the usb keyboard will become disabled if you use a sysrq
sequence to enter kdb. Using a tasklet solves the problem.
Signed-off-by: Jason
that are actually
known to work with the gdb monitor command will be available.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
include/linux/kgdb.h |3 ++-
kdb/kdb_io.c | 13 +
kernel/kgdb.c| 28 +---
3 files changed, 36 insertions
there is no character available. There are several other console
polling drivers which can be modified, but for the prototype only the
8250 and pl011 driver have been changed to make use of this.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/serial/8250.c |4 +-
drivers/serial/amba
at some
point down the road. :-)
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/char/kdb_keyboard.c | 199
drivers/hid/usbhid/hid-core.c | 26 +
drivers/hid/usbhid/usbkbd.c | 13 +++
drivers/serial/kgdboc.c | 12
for the original exception.
The kdb debugger wanted a chance to catch these sorts of exceptions
for analysis.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/arm/include/asm/kgdb.h |2 ++
arch/arm/kernel/kgdb.c |8
arch/arm/kernel/traps.c |5 +
3 files changed
are the ? and
qSupported query.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/arm/kernel/kgdb.c |5 +
arch/mips/kernel/kgdb.c|5 +
arch/powerpc/kernel/kgdb.c |5 +
arch/x86/kernel/kgdb.c |5 +
include/linux/kgdb.h |3 +
kernel/kgdb.c
not be safe to have an inline breakpoint
inside the kgdb I/O driver.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
include/linux/kgdb.h |1 +
kernel/kgdb.c| 26 ++
2 files changed, 27 insertions(+), 0 deletions(-)
diff --git a/include/linux/kgdb.h
this as
an alternative? The idea is that you want the calls to be always be
NOP's unless a kgdb I/O driver has been loaded.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/include/asm/kgdb.h |3 +++
arch/x86/kernel/kgdb.c | 22 +-
arch/x86/kernel/traps.c
Anupam Chomal wrote:
Hi,
I am sorry if I am posting to the wrong list...
I am trying to step through the native IPSec code in 2.6.28. I have
done the necessary steps:
1. Compiled the kernel on the development machine.
2. Copied the compiled kernel (Initrd, vmlinuz, and Systemmap) to the
that touches the sysrq change was already reviewed by the
owners of the code and includes the appropriate ack's.
Thanks,
Jason.
Short log follows:
Frank Rowand (1):
kgdb: gdb documentation fix
Jason Wessel (2):
sysrq, intel_fb: fix sysrq g collision
kgdb,i386: use address that SP
From: Frank Rowand frank.row...@am.sony.com
gdb command set remote debug 1 is not valid, change to correct command.
Signed-off-by: Frank Rowand frank.row...@am.sony.com
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
Documentation/DocBook/kgdb.tmpl |2 +-
1 files changed, 1
stack tracebacks from
working correctly in gdb.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/kernel/kgdb.c |3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
index eedfaeb..b1f4dff 100644
--- a/arch/x86
Linus Torvalds wrote:
Is this only ever used for kernel register state?
Because in the _general_ case, the code should likely be something like
if (user_mode_vm(regs)) {
gdb_regs[GDB_SS] = regs-ss;
gdb_regs[GDB_SP] = regs-sp;
} else {
Ingo Molnar wrote:
Just a first quick 30-seconds impression from skimming through the
patch:
- The cleanups are an absolute must before doing any in-depth
review. We only want to waste valuable review bandwidth on code
that at least _looks_ nice and tidy.
I think in depth review is
You are asking in the wrong forum.
Please direct your questions to:
KGDB Mailing List kgdb-bugreport@lists.sourceforge.net
http://git.kernel.org/?p=linux/kernel/git/jwessel/linux-2.6-kgdb.git
and
http://kernel.org/pub/linux/kernel/people/jwessel/branches
And I would not say that that kgdboe
Santosh Shukla wrote:
Hi All,
I am trying to add support for kgdb over serial (on arm1176 amba PL011
plateform) in linux-2.6.28 kernel.
I am not finding arm-lite patches of kgdb for ARM architecture, that uses
PL011 serial port.,
Has anybody tried this ?
The support for using
Santosh Shukla wrote:
Hi All,
Kernel Version : 2.6.30
Arch : x86
I have tried KGDBOE (kgdb over Ethernet) on v2.6.30 from linux-2.6-kgdb.git
jwessel tree. I found that, After hitting the breakpoint, and then saying
continue, console throws the message like Cannot remove breakpoints
Santosh Shukla wrote:
I have done same test on ubuntu gnu gdb 6.8-debian, and enabled set debug
remote 1 option..
Observed that, After saying continue command, Looks like while switching to
new thread, gdb unable to remove the breakpoints from current thread.
Test log:
Maxim Levitsky wrote:
On Thu, 2009-07-30 at 03:31 -0500, Jason Wessel wrote:
3) Develop a low level dedicated ethernet debug interface. If you have
more than one ethernet, or an ethernet device that has multiple hardware
queues, it is plausible to have a dedicated way to talk to a device
Nicholas Van Orton wrote:
What is the standard method used right now to add kgdb support to a
new platform such as Davinci ARM926? What are the arch specific calls
that I must change/make ?
In theory all you need is a console polling driver.
If this device is a multi cpu system you will
???(Nick Cheng) wrote:
Hi,
When I compile the kdgb-light on FC11, I got the error message as the
attached.
I use the default complier as GCC 4.4.0 20090506.
Could you tell me how to correct the error?
Thanks,
There was no attachment in your mail, the source force mailing list
Nicholas Van Orton wrote:
Ah! for a moment I thought this mailing list was a joke with almost
all spam originating from the oriental.
Thank you for the reply, I will proceed in that direction.
I took a look at the gnu mailman on the sf.net site, but I have not
figured out any way to black
Derek Atkins wrote:
Jason Wessel jason.wes...@windriver.com writes:
Nicholas Van Orton wrote:
Ah! for a moment I thought this mailing list was a joke with almost
all spam originating from the oriental.
Thank you for the reply, I will proceed in that direction.
I took
鄭守謙(Nick Cheng) wrote:
Hi Jason,
Sorry or late response.
The message is as following,
1: warnings being treated as errors
eval.c: In function ‘evaluate_subexp_standard’:
eval.c:1705: error: ‘subscript_array’ may be used uninitialized in this
function
eval.c:1644: note: ‘subscript_array’
Breno Leitao wrote:
Hi,
I was trying to use KGDB for the first time on PPC, and I set all the
*KGDB*=y on .config.
During the boot I got the following panic, and I'd like to know if someone
else hit this error before.
I had not seen that exact problem but it is crashing in the kgdb
The kdb_prototype9 is now available which will serve as the foundation
of the final consolidation work to post the kdb_prototype10 to the lkml.
The kdb_prototype9 will run the same demonstration that was shown at the
2009 Linux Plumbers Conference with the 2.6.32 development kernel. It
has a
From: Roel Kluin roel.kl...@gmail.com
Prevent write to put_buf[BUFMAX] in kgdb test suite.
If put_buf_cnt was BUFMAX - 1 at the earlier test,
`\0' is written to put_buf[BUFMAX].
Signed-off-by: Roel Kluin roel.kl...@gmail.com
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers
...@elte.hu
Acked-by: H. Peter Anvin h...@zytor.com
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/kernel/kgdb.c | 10 --
1 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
index f93d015..aefae46 100644
will work with the perf event
maintainers to repair the kgdb hw breakpoint support during the
2.6.33 cycle.
Thanks,
Jason.
Short log follows:
---
Geert Uytterhoeven (1):
kgdb: Replace strstr() by strchr() for single-character needles
Jason Wessel (6):
kgdb: Read buffer overflow
the
supported kgdb signal passing and execute a standard kgdb continue
operation.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
kernel/kgdb.c |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/kernel/kgdb.c b/kernel/kgdb.c
index ca21fe9..8584eac 100644
safety net in case a slave cpu is hung, the debug master
cpu will try 100 times before giving up and assuming control of the
slave cpus is no longer possible. It is more useful to be able to get
some information out of kgdb instead of spinning forever.
Signed-off-by: Jason Wessel jason.wes
doesn't have kgdb support).
Prevent this by explicitly calling strchr() instead.
Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/misc/kgdbts.c |8
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git
with out of line execution.
CC: Ingo Molnar mi...@elte.hu
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/kernel/kgdb.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/arch/x86/kernel/kgdb.c b/arch/x86/kernel/kgdb.c
index aefae46..dd74fe7 100644
--- a/arch
From: Roel Kluin roel.kl...@gmail.com
The for loop starts with a breakno of 0, and ends when it's 4. so
this test is always true.
CC: Ingo Molnar mi...@elte.hu
Signed-off-by: Roel Kluin roel.kl...@gmail.com
Signed-off-by: Andrew Morton a...@linux-foundation.org
Signed-off-by: Jason Wessel
Jiaqing Du wrote:
Hi List,
r...@linux:~# echo kgdbts=V1N6F100 /sys/module/kgdbts/parameters/kgdbts
Did you activate the nmi watch dog? It is required to run the nmi tests.
You can tell if it is running with:
cat /proc/sys/kernel/nmi_watchdog
If that returns zero, the nmi watchdog is
Jiaqing Du wrote:
2009/12/14 Jason Wessel jason.wes...@windriver.com:
Jiaqing Du wrote:
Hi List,
I am trying to use kgdb to debug some kernel modules (mainly for
oprofile and kvm). I had some weird problems. For example, break
points do not work and the target kernel hangs
Jiaqing Du wrote:
2009/12/14 Jason Wessel jason.wes...@windriver.com:
Jiaqing Du wrote:
2009/12/14 Jason Wessel jason.wes...@windriver.com:
Jiaqing Du wrote:
Hi List,
I am trying to use kgdb to debug some kernel modules (mainly for
oprofile and kvm). I had
for the available hw breakpoint slots.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/kernel/hw_breakpoint.c |5 +-
arch/x86/kernel/kgdb.c | 191 +++
kernel/kgdb.c |3 +
3 files changed, 139 insertions
resuming the system in
order to inspect arch specific cpu information.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
kernel/debug/debug_core.c | 158 +---
kernel/debug/debug_core.h |7 ++
2 files changed, 82 insertions(+), 83 deletions
branch 'drm-linus' of git://git.kernel.org/.../airlied/drm-2.6
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git
kdb_prototype10
Jason Wessel (33):
softlockup: add sched_clock_tick() to avoid kernel warning on kgdb resume
by introducing the
function touch_softlockup_watchdog_sync(), which allows kgdb to
request that the sched clock is updated when the watchdog thread runs
the first time after a resume from kgdb.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
Signed-off-by: Dongdong Deng dongdong.d
Move kgdb.c in preparation for to separate the gdbstub from the debug
core and exception handling.n
CC: Ingo Molnar mi...@elte.hu
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
kernel/Makefile |2 +-
kernel/debug/Makefile |5 +
kernel
distinguish between a single step trap and
a breakpoint trap generically.
CC: Paul Mundt let...@linux-sh.org
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/sh/kernel/kgdb.c | 14 +-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/arch/sh/kernel/kgdb.c b
at this point. Doing something like trying to set
breakpoints with the monitor command is going to cause nothing but
problems. Perhaps in the future only the commands that are actually
known to work with the gdb monitor command will be available.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
is
responsible for detecting are the ? and qSupported packets.
CC: Ingo Molnar mi...@elte.hu
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/arm/kernel/kgdb.c |5 ++
arch/mips/kernel/kgdb.c|5 ++
arch/powerpc/kernel/kgdb.c |5 ++
arch/x86/kernel/kgdb.c |5 ++
include
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/char/Makefile |1 +
drivers/char/kdb_keyboard.c | 207 +++
drivers/char/kdb_keyboard.h | 143 +
drivers/serial/kgdboc.c | 67 +--
include
who need it, it is added as a kernel .config
option called KGDB_LOW_LEVEL_TRAP.
CC: Ingo Molnar mi...@elte.hu
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/include/asm/kgdb.h |3 +++
arch/x86/kernel/kgdb.c | 22 +-
arch/x86/kernel/traps.c
Update the maintained files sections.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
MAINTAINERS |6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index d5244f1..98b2669 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -3177,15
Hooks for the kgdb core for registration of the drm layer to provide a
call backs so as to perform kernel mode switching, for use with kdb.
CC: Jesse Barnes jbar...@virtuousgeek.org
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/serial/kgdboc.c | 15
If kdb is open on a serial port that is not actually a console make
sure to call the poll routines to emit and receive characters.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/serial/kgdboc.c | 14 ++
include/linux/kgdb.h |3 +++
kernel/debug/kdb
From: Jesse Barnes jbar...@virtuousgeek.org
This allows callers to store the ops structure in a parent device structure.
Signed-off-by: Jesse Barnes jbar...@virtuousgeek.org
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/serial/kgdboc.c |4 ++--
include/linux/kgdb.h
not be safe to have an inline
breakpoint. This is true of some of the kgdb I/O drivers which share
code with kgdb and rest of the kernel users.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
include/linux/kgdb.h |1 +
kernel/debug/debug_core.c | 26
() is
called with correct parameters when catching an oops, because kdb
needs to know if the entry was an oops, single step, or breakpoint
exception.
CC: Benjamin Herrenschmidt b...@kernel.crashing.org
CC: Paul Mackerras pau...@samba.org
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch
It is highly desirable to trap into kdb on panic, and in order
to do so the notifier must be called before smp_send_stop(),
else the debug_core will not be able to correctly trap
all the CPUs.
CC: Ingo Molnar mi...@elte.hu
CC: Andrew Morton a...@linux-foundation.org
Signed-off-by: Jason Wessel
The sci_poll_get_char() needs to return immediately if there is no
input from the chip to process, and must return a value of
NO_POLL_CHAR.
This allows kgdboc to process multiple polled devices while kgdb is
active.
CC: Paul Mundt let...@linux-sh.org
Signed-off-by: Jason Wessel jason.wes
This allows kdb to debug a crash with in the kms code with a
single level recursive re-entry.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
kernel/debug/debug_core.c |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/kernel/debug/debug_core.c b/kernel
...@gmail.com
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
drivers/char/keyboard.c | 30 +-
drivers/input/input.c | 15 +++
drivers/serial/kgdboc.c |9 +
include/linux/input.h | 10 ++
4 files changed, 59 insertions
-by: Jason Wessel jason.wes...@windriver.com
---
arch/arm/include/asm/kgdb.h |2 ++
arch/arm/kernel/kgdb.c |8
arch/arm/kernel/traps.c |5 +
3 files changed, 15 insertions(+), 0 deletions(-)
diff --git a/arch/arm/include/asm/kgdb.h b/arch/arm/include/asm/kgdb.h
-ex_vector.
Signed-off-by: Jason Wessel jason.wes...@windriver.com
---
arch/x86/kernel/kgdb.c| 29 -
include/linux/kgdb.h | 14 --
kernel/debug/debug_core.c |8
3 files changed, 0 insertions(+), 51 deletions(-)
diff --git a/arch/x86
101 - 200 of 613 matches
Mail list logo
