[Kgdb-bugreport] ctrl+c and echo -e "\003" > /dev/ttySX do not work?
Status: Beta
Brought to you by:
jwessel
From: Arkadiusz M. <ar...@pl...> - 2004-05-26 13:26:18
|
Hi, The problem is that if I run kgdb-2 patched linux 2.6.6 kernel, attach gdb = to=20 it, quit from gdb (so kernel continutes booting) and then trying to attach= =20 again by doing echo -e "\003" > /dev/ttySX gdb; target remote /dev/ttySX then it says Ignoring packet error, continuing... Couldn't establish connection to remote target Also if I won't exit from gdb then it boots until: Limiting direct PCI/PCI transfers. Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker and stops here. When I run and quit gdb at ,,Waiting for connection from remote gdb...'' then it boots fine: Serial: 8250/16550 driver $Revision: 1.90 $ 8 ports, IRQ sharing disabled ttyS0 at I/O 0x3f8 (irq =3D 4) is a 16550A ne2k-pci.c:v1.03 9/22/2003 D. Becker/P. Gortmaker http://www.scyld.com/network/ne2k-pci.html PCI: Found IRQ 10 for device 0000:00:0a.0 eth0: RealTek RTL-8029 found at 0xb400, IRQ 10, 00:C0:DF:E8:BF:1A. Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=3D= xx PIIX4: IDE controller at PCI slot 0000:00:04.1 PIIX4: chipset revision 1 PIIX4: not 100% native mode: will probe irqs later ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:pio ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:pio hda: Maxtor 90650U2, ATA DISK drive Using anticipatory io scheduler ide0 at 0x1f0-0x1f7,0x3f6 on irq 14 hdc: CRD-8400B, ATAPI CD/DVD-ROM drive ide1 at 0x170-0x177,0x376 on irq 15 hda: max request size: 128KiB hda: 12594960 sectors (6448 MB) w/2048KiB Cache, CHS=3D13328/15/63 hda: hda1 hda2 hda3 hdc: ATAPI 40X CD-ROM drive, 128kB Cache but of course I can't reaatach to it. This would not be big problem if ctrl+c or echo -e "\003" were working :/ kernel has all kernel debugging stuff enabled # CONFIG_DEBUG_DRIVER is not set CONFIG_DEBUG_KERNEL=3Dy CONFIG_DEBUG_STACKOVERFLOW=3Dy CONFIG_DEBUG_STACK_USAGE=3Dy CONFIG_DEBUG_SLAB=3Dy CONFIG_DEBUG_SPINLOCK=3Dy CONFIG_DEBUG_PAGEALLOC=3Dy CONFIG_DEBUG_INFO=3Dy CONFIG_DEBUG_SPINLOCK_SLEEP=3Dy =2D-=20 Arkadiusz Mi=B6kiewicz CS at FoE, Wroclaw University of Technology arekm.pld-linux.org, 1024/3DB19BBD, JID: arekm.jabber.org, PLD/Linux |