* kgdb doesn't respond to Ctrl+C
@ 2004-03-23 6:32 Amit S. Kale
2004-03-23 15:25 ` Tom Rini
0 siblings, 1 reply; 3+ messages in thread
From: Amit S. Kale @ 2004-03-23 6:32 UTC (permalink / raw)
To: Linux Kernel, KGDB bugreports, Tom Rini
I guess something's gone wrong with serial port interrupts.
Tom, any ideas?
--
Amit Kale
EmSysSoft (http://www.emsyssoft.com)
KGDB: Linux Kernel Source Level Debugger (http://kgdb.sourceforge.net)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kgdb doesn't respond to Ctrl+C
2004-03-23 6:32 kgdb doesn't respond to Ctrl+C Amit S. Kale
@ 2004-03-23 15:25 ` Tom Rini
2004-03-29 12:05 ` Amit S. Kale
0 siblings, 1 reply; 3+ messages in thread
From: Tom Rini @ 2004-03-23 15:25 UTC (permalink / raw)
To: Amit S. Kale; +Cc: Linux Kernel, KGDB bugreports
On Tue, Mar 23, 2004 at 12:02:30PM +0530, Amit S. Kale wrote:
> I guess something's gone wrong with serial port interrupts.
>
> Tom, any ideas?
Current CVS works for me. Relevant .config section:
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_DEBUG_HIGHMEM is not set
CONFIG_DEBUG_INFO=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
CONFIG_KGDB=y
CONFIG_KGDB_8250=y
# CONFIG_PPC_SIMPLE_SERIAL is not set
CONFIG_KGDB_SIMPLE_SERIAL=y
CONFIG_KGDB_9600BAUD=y
# CONFIG_KGDB_19200BAUD is not set
# CONFIG_KGDB_38400BAUD is not set
# CONFIG_KGDB_57600BAUD is not set
# CONFIG_KGDB_115200BAUD is not set
CONFIG_KGDB_TTYS0=y
# CONFIG_KGDB_TTYS1 is not set
# CONFIG_KGDB_TTYS2 is not set
# CONFIG_KGDB_TTYS3 is not set
CONFIG_FRAME_POINTER=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
--
Tom Rini
http://gate.crashing.org/~trini/
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: kgdb doesn't respond to Ctrl+C
2004-03-23 15:25 ` Tom Rini
@ 2004-03-29 12:05 ` Amit S. Kale
0 siblings, 0 replies; 3+ messages in thread
From: Amit S. Kale @ 2004-03-29 12:05 UTC (permalink / raw)
To: Tom Rini; +Cc: Linux Kernel, KGDB bugreports
Works for me too now. Looks like a false alarm
-Amit
On Tuesday 23 Mar 2004 8:55 pm, Tom Rini wrote:
> On Tue, Mar 23, 2004 at 12:02:30PM +0530, Amit S. Kale wrote:
> > I guess something's gone wrong with serial port interrupts.
> >
> > Tom, any ideas?
>
> Current CVS works for me. Relevant .config section:
> #
> # Kernel hacking
> #
> CONFIG_DEBUG_KERNEL=y
> CONFIG_EARLY_PRINTK=y
> # CONFIG_DEBUG_STACKOVERFLOW is not set
> # CONFIG_DEBUG_STACK_USAGE is not set
> # CONFIG_DEBUG_SLAB is not set
> # CONFIG_DEBUG_IOVIRT is not set
> CONFIG_MAGIC_SYSRQ=y
> # CONFIG_DEBUG_SPINLOCK is not set
> # CONFIG_DEBUG_PAGEALLOC is not set
> # CONFIG_DEBUG_HIGHMEM is not set
> CONFIG_DEBUG_INFO=y
> # CONFIG_DEBUG_SPINLOCK_SLEEP is not set
> CONFIG_KGDB=y
> CONFIG_KGDB_8250=y
> # CONFIG_PPC_SIMPLE_SERIAL is not set
> CONFIG_KGDB_SIMPLE_SERIAL=y
> CONFIG_KGDB_9600BAUD=y
> # CONFIG_KGDB_19200BAUD is not set
> # CONFIG_KGDB_38400BAUD is not set
> # CONFIG_KGDB_57600BAUD is not set
> # CONFIG_KGDB_115200BAUD is not set
> CONFIG_KGDB_TTYS0=y
> # CONFIG_KGDB_TTYS1 is not set
> # CONFIG_KGDB_TTYS2 is not set
> # CONFIG_KGDB_TTYS3 is not set
> CONFIG_FRAME_POINTER=y
> CONFIG_X86_FIND_SMP_CONFIG=y
> CONFIG_X86_MPPARSE=y
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2004-03-29 12:41 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-03-23 6:32 kgdb doesn't respond to Ctrl+C Amit S. Kale
2004-03-23 15:25 ` Tom Rini
2004-03-29 12:05 ` Amit S. Kale
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox