Subject: RE: Is kgdb development version working with 2.6.15 kernel? - msg#00038

Previous Message by Date: click to view message preview

Re: Is kgdb development version working with 2.6.15 kernel?

Actually if you look in linux-2.6.15/kernel/kgdb.c the message is still there: void breakpoint(void) 1867 { 1868 if (kgdb_initialized != 1) { 1869 kgdb_early_entry(); 1870 if (kgdb_initialized == 1) 1871 printk(KERN_CRIT "Waiting for connection from remote " 1872 "gdb...\n"); ... Anyway, I did attempt to connect to Kgdb/test machine but gdb timed out: [devel machine]$ gdb ./vmlinux GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) set remotebaud 115200 (gdb) set remote debug 1 Undefined set remote command: "debug 1". Try "help set remote". (gdb) set debug remote 1 (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: $qC#b4...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) q [devel machine]$ It seemed no Ack from the test machine. --- Milind Dumbare <milind@xxxxxxxxxxxxxx> wrote: > This message "Kgdb: Waiting for connection from remote" is no more > there. Try connecting to Kgdb machine (from remote gdb) after you see > "Uncompressing Linux..." > Or if you want the machine to be fully booted remove, "kgdbwait" from > kernel command line. > > On Tue, 2006-03-07 at 13:52 -0800, hp wrote: > > Hi, > > > > I saw a similar email last month but thought I post again for this might > be a > > real problem. > > > > I checked out kgdb the development verion using instructions here > > http://kgdb.linsyssoft.com/cvs.htm yesterday (3/6/2006). According to > the > > ChangeLog, this version had moved to 2.6.15 on 1/6/2006. I applied > patches > > in kgdb-2 to a 2.6.15 kernel > > (http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2) and > built > > it alright. The kernel booted ok without the "kgdbwait" parameter; > however, > > when I gave it "kgdbwait kgdb8250=0,115200" as the commandline > parameters. > > It just hang after displaying this message: "Uncompressing Linux... Ok, > > booting the kernel." I didn't even see the "kgdb: Waiting for connection > > from remote" message. > > > > Yes, I had KGDB turned on and tested the serial cable to make sure they > were > > good too. Fired up a minicom session on the development machine showed > > nothing coming from the kgdb kernel. > > > > So my question is: has anyone able to boot a kgdb-2.6.15-kernel on x86 > yet? > > How about on PPC? > > > > Thanks for any response, > > Andy > > > > p.s. attached is my .config if anyone's curious. > -- > ...Miline > LinSysSoft Technologies > Ask me about KGDB Pro > http://www.linsyssoft.com/Kgdbpro.html > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Next Message by Date: click to view message preview

Re: Fix 8250.patch to support CONFIG_KGDB_SIMPLE_SERIAL

On Tue, Mar 07, 2006 at 08:05:24PM -0800, Wessel, Jason wrote: > Amit, > > After further digging I am reasonable certain that the RS232 code is > broken for quiet a few boards. Take for instance the ebony 440. Ebony really is a fun one for a number of reasons, yeah. [snip] > On the ebony it really is an MMIO channel and there is no way to set > membase from the old RS232 definitions or the newly added command line. > Right now you specify the mapbase. That is how I drew the conclusion > that I could not use the RS232 for KGDB on the ebony platform. In fact > on the other PPC board I was playing with it just happens to work. The > original driver is not actually getting shutdown properly, and a new > uart_port is getting defined. That is where the ttyS3 was coming into > play. It was actually happening even without the patch I submitted for > adding in the SIMPLE configuration. Thinking back, but you turn mapbase into membase by a mapping function, yes? > I mad some changes to: > serial_core:uart_report_port() > So I could see more data about the printk's. > > serial8250: ttyS0 at MMIO 0x0 0xfdfeb200 (irq = 0) is a 16550A > serial8250: ttyS1 at MMIO 0x0 0xfdfea300 (irq = 1) is a 16550A > > So 0x0 is map base and 0xfdfea300 is membase for ttyS1. > > Next some edits 8250_kgdb.c to use membase instead of mapbase in the > kgdb driver, and suddenly it started working again. IE: What changes exactly? It is possible that some of the *base semantics changed around and we need to fix things up. > At this point the 8250_kgdb needs some overhauling to get it working > correctly. To fix up the "simple" dynamic configuration will require > adding a new function to the core 8250 driver to obtain the runtime port > mappings. Personally, I'd rather not have to know if it is an MMIO or > IO port, let alone the address. This is the problem with the "give me ttyS1" style approach. There's simply far too much that can go wrong since really the static port definitions are junk outside of i386 (there's some fun & luck on many but not all PPCs, as you note). A thought that needs real thinking about is does drivers/serial/8250.c register all port information with drivers/serial/serial_core.c ? If so, perhaps we should make 8250_kgdb be more of a 'real' drivers/serial driver so we could find out really all of the port information as it is registered and therefore get the main serial driver to give up (or reclaim) a port. > While you could call the "simple" configuration a dropped feature which > should be added back, I feel the MMIO mappings between the 8250_kgdb > driver and the core 8250 driver need to be fixed before you can consider > a release. Indeed we do want the 8250 driver to be quite solid before doing another release. -- Tom Rini http://gate.crashing.org/~trini/ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Previous Message by Thread: click to view message preview

Re: Is kgdb development version working with 2.6.15 kernel?

Actually if you look in linux-2.6.15/kernel/kgdb.c the message is still there: void breakpoint(void) 1867 { 1868 if (kgdb_initialized != 1) { 1869 kgdb_early_entry(); 1870 if (kgdb_initialized == 1) 1871 printk(KERN_CRIT "Waiting for connection from remote " 1872 "gdb...\n"); ... Anyway, I did attempt to connect to Kgdb/test machine but gdb timed out: [devel machine]$ gdb ./vmlinux GNU gdb 6.3-debian Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-linux"...Using host libthread_db library "/lib/tls/libthread_db.so.1". (gdb) set remotebaud 115200 (gdb) set remote debug 1 Undefined set remote command: "debug 1". Try "help set remote". (gdb) set debug remote 1 (gdb) target remote /dev/ttyS0 Remote debugging using /dev/ttyS0 Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: $qC#b4...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Sending packet: $qOffsets#4b...Timed out. Timed out. Timed out. Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) q [devel machine]$ It seemed no Ack from the test machine. --- Milind Dumbare <milind@xxxxxxxxxxxxxx> wrote: > This message "Kgdb: Waiting for connection from remote" is no more > there. Try connecting to Kgdb machine (from remote gdb) after you see > "Uncompressing Linux..." > Or if you want the machine to be fully booted remove, "kgdbwait" from > kernel command line. > > On Tue, 2006-03-07 at 13:52 -0800, hp wrote: > > Hi, > > > > I saw a similar email last month but thought I post again for this might > be a > > real problem. > > > > I checked out kgdb the development verion using instructions here > > http://kgdb.linsyssoft.com/cvs.htm yesterday (3/6/2006). According to > the > > ChangeLog, this version had moved to 2.6.15 on 1/6/2006. I applied > patches > > in kgdb-2 to a 2.6.15 kernel > > (http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2) and > built > > it alright. The kernel booted ok without the "kgdbwait" parameter; > however, > > when I gave it "kgdbwait kgdb8250=0,115200" as the commandline > parameters. > > It just hang after displaying this message: "Uncompressing Linux... Ok, > > booting the kernel." I didn't even see the "kgdb: Waiting for connection > > from remote" message. > > > > Yes, I had KGDB turned on and tested the serial cable to make sure they > were > > good too. Fired up a minicom session on the development machine showed > > nothing coming from the kgdb kernel. > > > > So my question is: has anyone able to boot a kgdb-2.6.15-kernel on x86 > yet? > > How about on PPC? > > > > Thanks for any response, > > Andy > > > > p.s. attached is my .config if anyone's curious. > -- > ...Miline > LinSysSoft Technologies > Ask me about KGDB Pro > http://www.linsyssoft.com/Kgdbpro.html > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642

Next Message by Thread: click to view message preview

RE: Is kgdb development version working with 2.6.15 kernel?

Yes. As I mentioned in my original message, if I removed the kgdbwait; the kernel booted fine. btw, I'm trying this on my X86 PIII box. Andy p.s. It seemed like maybe the serial drivers in not turned on or something? I do have these in my .config ... # Serial drivers # CONFIG_SERIAL_8250=y # CONFIG_SERIAL_8250_CONSOLE is not set # CONFIG_SERIAL_8250_CS is not set # CONFIG_SERIAL_8250_ACPI is not setCONFIG_KGDB=y CONFIG_KGDB_CONSOLE=y # CONFIG_KGDB_ONLY_MODULES is not set CONFIG_KGDB_8250_NOMODULE=y # CONFIG_KGDBOE_NOMODULE is not set # CONFIG_KGDB_MPSC is not set # CONFIG_KGDB_CPM_UART is not set # CONFIG_KGDB_SIBYTE is not set # CONFIG_KGDBOE is not set CONFIG_KGDB_8250=y CONFIG_KGDB_SIMPLE_SERIAL=y CONFIG_KGDB_BAUDRATE=115200 CONFIG_KGDB_PORT_NUM=1 CONFIG_EARLY_PRINTK=y ... --- "Wessel, Jason" <jason.wessel@xxxxxxxxxxxxx> wrote: > Had you tried removing the kgdbwait yet? > > Unless the early printk() is defined for your architecture and you turn > on CONFIG_SERIAL_TEXT_DEBUG you are not going to see that message until > after console_init() runs. > > Jason. > > > -----Original Message----- > > From: kgdb-bugreport-admin@xxxxxxxxxxxxxxxxxxxxx > > [mailto:kgdb-bugreport-admin@xxxxxxxxxxxxxxxxxxxxx] On Behalf Of hp > > Sent: Wednesday, March 08, 2006 8:43 AM > > To: Milind Dumbare > > Cc: amitkale@xxxxxxxxxxxxxx; KGDB-bugreport > > Subject: Re: [Kgdb-bugreport] Is kgdb development version > > working with 2.6.15 kernel? > > > > Actually if you look in linux-2.6.15/kernel/kgdb.c the > > message is still > > there: > > > > void breakpoint(void) > > 1867 { > > 1868 if (kgdb_initialized != 1) { > > 1869 kgdb_early_entry(); > > 1870 if (kgdb_initialized == 1) > > 1871 printk(KERN_CRIT "Waiting for > > connection from > > remote " > > 1872 "gdb...\n"); > > ... > > > > Anyway, I did attempt to connect to Kgdb/test machine but gdb > > timed out: > > > > [devel machine]$ gdb ./vmlinux > > GNU gdb 6.3-debian > > Copyright 2004 Free Software Foundation, Inc. > > GDB is free software, covered by the GNU General Public > > License, and you are welcome to change it and/or distribute > > copies of it under certain conditions. > > Type "show copying" to see the conditions. > > There is absolutely no warranty for GDB. Type "show > > warranty" for details. > > This GDB was configured as "i386-linux"...Using host > > libthread_db library "/lib/tls/libthread_db.so.1". > > > > (gdb) set remotebaud 115200 > > (gdb) set remote debug 1 > > Undefined set remote command: "debug 1". Try "help set remote". > > (gdb) set debug remote 1 > > (gdb) target remote /dev/ttyS0 > > Remote debugging using /dev/ttyS0 > > Sending packet: $Hc-1#09...Sending packet: $Hc-1#09...Sending packet: > > $Hc-1#09...Sending packet: $Hc-1#09...Timed out. > > Timed out. > > Timed out. > > Ignoring packet error, continuing... > > Sending packet: $qC#b4...Sending packet: $qC#b4...Sending packet: > > $qC#b4...Sending packet: $qC#b4...Timed out. > > Timed out. > > Timed out. > > Ignoring packet error, continuing... > > Sending packet: $qOffsets#4b...Sending packet: > > $qOffsets#4b...Sending packet: > > $qOffsets#4b...Sending packet: $qOffsets#4b...Timed out. > > Timed out. > > Timed out. > > Ignoring packet error, continuing... > > Couldn't establish connection to remote target Malformed > > response to offset query, timeout > > (gdb) q > > [devel machine]$ > > > > It seemed no Ack from the test machine. > > > > --- Milind Dumbare <milind@xxxxxxxxxxxxxx> wrote: > > > > > This message "Kgdb: Waiting for connection from remote" is no more > > > there. Try connecting to Kgdb machine (from remote gdb) > > after you see > > > "Uncompressing Linux..." > > > Or if you want the machine to be fully booted remove, > > "kgdbwait" from > > > kernel command line. > > > > > > On Tue, 2006-03-07 at 13:52 -0800, hp wrote: > > > > Hi, > > > > > > > > I saw a similar email last month but thought I post again > > for this > > > > might > > > be a > > > > real problem. > > > > > > > > I checked out kgdb the development verion using instructions here > > > > http://kgdb.linsyssoft.com/cvs.htm yesterday (3/6/2006). > > According > > > > to > > > the > > > > ChangeLog, this version had moved to 2.6.15 on 1/6/2006. > > I applied > > > patches > > > > in kgdb-2 to a 2.6.15 kernel > > > > > > (http://www.kernel.org/pub/linux/kernel/v2.6/linux-2.6.15.tar.bz2) > > > > and > > > built > > > > it alright. The kernel booted ok without the "kgdbwait" > > parameter; > > > however, > > > > when I gave it "kgdbwait kgdb8250=0,115200" as the commandline > > > parameters. > > > > It just hang after displaying this message: > > "Uncompressing Linux... > > > > Ok, booting the kernel." I didn't even see the "kgdb: > > Waiting for > > > > connection from remote" message. > > > > > > > > Yes, I had KGDB turned on and tested the serial cable to > > make sure > > > > they > > > were > > > > good too. Fired up a minicom session on the development machine > > > > showed nothing coming from the kgdb kernel. > > > > > > > > So my question is: has anyone able to boot a > > kgdb-2.6.15-kernel on > > > > x86 > > > yet? > > > > How about on PPC? > > > > > > > > Thanks for any response, > > > > Andy > > > > > > > > p.s. attached is my .config if anyone's curious. > > > -- > > > ...Miline > > > LinSysSoft Technologies > > > Ask me about KGDB Pro > > > http://www.linsyssoft.com/Kgdbpro.html > > > > > > > > > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by xPML, a groundbreaking > > scripting language that extends applications into web and > > mobile media. Attend the live webcast and join the prime > > developer group breaking into this new coding territory! > > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720& > > dat=121642 > > _______________________________________________ > > Kgdb-bugreport mailing list > > Kgdb-bugreport@xxxxxxxxxxxxxxxxxxxxx > > https://lists.sourceforge.net/lists/listinfo/kgdb-bugreport > > > ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642