I am unable to get KDB_ENTER() to work properly in either 2.6.11 or 2.6.12. I've spent most of the day googling for the answer as to why it's not working, but no dice. I am trying to run KDB_ENTER() at two places. One is just by using the kdb=early param to the kernel and the other by adding a line to a simple device driver I'm trying to debug. Both places I have the same issue -
Entering kdb (current=0xc0398c80, pid 0) kdb: unexpected reason code: 0 I'm running with the latest kdb code, as of today that was v4.4 6/17/05. I've looked through the code as best I can, but honestly I do not know much about this stuff. Any help would be appreciated. Below are some screencaps of what I am seeing. Thanks Josh When I pass the kdb=early option to the kernel at boot - Linux version 2.6.12.1-KDB (root@) (gcc version 3.4.2 20041017 (Red Hat 3.4.2-65BIOS-provided physical RAM map: BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved) BIOS-e820: 0000000000100000 - 0000000018000000 (usable) BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) 0MB HIGHMEM available. 384MB LOWMEM available. On node 0 totalpages: 98304 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 94208 pages, LIFO batch:31 HighMem zone: 0 pages, LIFO batch:1 DMI 2.1 present. Allocating PCI resources starting at 18000000 (gap: 18000000:e7fc0000) Built 1 zonelists Kernel command line: ro root=/dev/VolGroup00/LogVol00 rhgb debug kdb=early console=tty0 console=ttyS0,96 Initializing CPU#0 CPU 0 irqstacks, hard=c043d000 soft=c043c000 PID hash table entries: 2048 (order: 11, 32768 bytes) Detected 497.866 MHz processor. Using tsc for high-res timesource Console: colour VGA+ 80x25 Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) Memory: 384496k/393216k available (2331k kernel code, 8080k reserved, 793k data, 160k init, 0k highmem) Checking if this processor honours the WP bit even in supervisor mode... Ok. Calibrating delay loop... 983.04 BogoMIPS (lpj=491520) kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved kdb_cmd[0]: defcmd archkdb "" "First line arch debugging" kdb_cmd[6]: defcmd archkdbcpu "" "archkdb with only tasks on cpus" kdb_cmd[12]: defcmd archkdbshort "" "archkdb with less detailed backtrace" kdb_cmd[18]: defcmd archkdbcommon "" "Common arch debugging" Entering kdb (current=0xc0398c80, pid 0) kdb: unexpected reason code: 0 and also in from a driver I am loading as a module - [root@ mouse]# insmod ./psmouse.ko Entering kdb (current=0xd781b000, pid 140) kdb: unexpected reason code: 0 In psmouse-base.c I am calling KDB_ENTER() b/c I am trying to learn more about linux device drivers and chose this simple mouse driver to start with. --------------------------- Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
