ctl-alt-esc not taking me to kernel debugger
Is ctl-alt-esc working for others on 8.x 9.x? See http://forums.freebsd.org/showthread.php?t=40111 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Attempting to use the kernel debugger over the serial port not working (well)
All, Cannot seem to find anything on the net to collaborate my experience with remote KGDB over a serial port. Here is my setup - +--+-+--- | | | bce0 eth1 bce0 | | | +---+--+ +---++ +---+---+ | HP Proliant GL360 G5 | | Cyclades ACS32 || HP Proliant GL360 G5 | +---+--+ ++---+ +---+ | | ttyu0(uart0)port 28 | | +---+ The Cyclades is a 32 port terminal server that has serial port 28 connected to the DB9 locate on the back of the HP server. I am running KGDB inside of an emacs session on the Sony Vaio. The HP's are running in 64-bit (amd64) FreeBSD 8.0. The uart0 on the target is configured as (from dmesg.boot): uart0: 16550 or compatible port 0x3f8-0x3ff irq 4 flags 0x90 on acpi0 uart0: [FILTER] uart0: console (9600,n,8,1) The Cyclades port is configured the same. My kernel is built with the following options: options KDB options DDB options GDB The kernel is built with -O2 -g In /boot/loader.conf I have the following lines: console=comconsole vidconsole comconsole_speed=9600 hint.uart.0.flags=0x90 I invoke the kernel debugger on the target using: 'sysctl debug.kdb.enter=1' Which gets me to the DB prompt where I enter the following: DBgdb Step to enter the gdb debugger DBs I am invoking KGDB inside of emacs on the build server in the 'obj' tree where the kernel build is located. kgdb -fullname kernel.debug Once I have the gdb prompt, I enter the following target command: target remote 10.10.29.111:7028 Where 10.10.29.111 is the address of the Cyclades and port 7028 connects me to serial port 28 on the Cyclades. This brings up the kernel with the break point. I then set my break point(s) and enter 'c' to continue. Sometimes the break points fire, sometimes they don't. However, in some indeterminant time (seconds) I start seeing the following on the Video console (not the serial one). Fatal double fault rip = 0x8055bdc4 rsp = 0xff8078405000 rbp = 0xff8078405000 cpuid = 1; apic id = 01 panic: double fault cpuid = 1 KDB: stack backtrace: db_trace_self_wrapper() at db_trace_self_wrapper+0x2a kdb_backtrace() at kdb_backtrace+0x32 mi_switch() at mi_switch+0x70 sched_bind() at sched_bind+0x60 boot() at boot+0x45 panic() at panic+0x1f2 dblfault_handler() at dblfault_handler+0xab Xdblfault() at Xdblfault+0xac --- trap 0x17, rip = 0x8055bdc4, rsp = 0xff817ff0, rbp = 0xff8078405000 --- _thread_lock_flags() at _thread_lock_flags+0x4 critical_exit() at critical_exit+0x5d spinlock_exit() at spinlock_exit+0x17 mi_switch() at mi_switch+0x6b Then it repeats over and over again, the box becomes unresponsive and I am unable to proceed. My googling turned up this issue only in relation to lock order reversals, but I am not seeing that issue here and I don't have the kernel compiled with 'options WITNESS'. Any pointers would be appreciated. Thanks, Patrick ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.0 how to enter kernel debugger inside vmware
Hi all I have an unstable machine running FreeBSD 8.0-RELEASE inside vmware. It freezes on average once a week but doesn't panic, so i would like to enter the kernel debugger, to at least being able to force a panic. Unfortunately, i have no serial interface and can't enter into the debugger on the console using ctrl-alt-esc either, because it conflicts with the key sequence to leave the console in the vmware client. What can i do? many thanks and best regards -Daniel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 how to enter kernel debugger inside vmware
You might want to recompile your kernel with the ALT_BREAK_TO_DEBUGGER option. This allows you to use CR~^b to enter the debugger instead of ctrl-alt-esc. Andrew 2010/1/27 Daniel Mueller d...@imp.ch: Hi all I have an unstable machine running FreeBSD 8.0-RELEASE inside vmware. It freezes on average once a week but doesn't panic, so i would like to enter the kernel debugger, to at least being able to force a panic. Unfortunately, i have no serial interface and can't enter into the debugger on the console using ctrl-alt-esc either, because it conflicts with the key sequence to leave the console in the vmware client. What can i do? many thanks and best regards -Daniel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
freeze after entering kernel debugger
I've been having problem with the kernel debugger on one of my machines, and the time has come to try and hunt the critter down. The machine in question is running -CURRENT; I'm not posting to that list because I first noticed the problem when it was running -Stable somewhere in 5.very smallnum. Hardware: Asus P4-S533 Intel P4 2.26 ghz 512 mb RAM USB keyboard boot probe appended Software (now running): FreeBSD 7.0-CURRENT #0: Mon Mar 13 09:23:39 EST 2006 kernel config appended Symptoms: System crashes, and I end up here: KDB: enter: manual escape to debugger [thread pid 20 tid 100024] db Stopped at kdb_enter+0x30 There's prompt waiting for input, and the machine freezes. No keyboard activity registers, not even the caps or numlock keys. Moving on requires the reset button. Any ideas? boot probe Mar 13 10:46:36 jerusalem kernel: Copyright (c) 1992-2006 The FreeBSD Project. Mar 13 10:46:36 jerusalem kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 Mar 13 10:46:36 jerusalem kernel: The Regents of the University of California. All rights reserved. Mar 13 10:46:36 jerusalem kernel: FreeBSD 7.0-CURRENT #0: Mon Mar 13 09:23:39 EST 2006 Mar 13 10:46:36 jerusalem kernel: [EMAIL PROTECTED]:/usr/obj/usr/src/sys/JERUSALEM Mar 13 10:46:36 jerusalem kernel: WARNING: WITNESS option enabled, expect reduced performance. Mar 13 10:46:36 jerusalem kernel: WARNING: MPSAFE network stack disabled, expect reduced performance. Mar 13 10:46:36 jerusalem kernel: Timecounter i8254 frequency 1193182 Hz quality 0 Mar 13 10:46:36 jerusalem kernel: CPU: Intel(R) Pentium(R) 4 CPU 2.26GHz (2261.01-MHz 686-class CPU) Mar 13 10:46:36 jerusalem kernel: Origin = GenuineIntel Id = 0xf24 Stepping = 4 Mar 13 10:46:36 jerusalem kernel: Features=0x3febfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM Mar 13 10:46:36 jerusalem kernel: real memory = 536854528 (511 MB) Mar 13 10:46:36 jerusalem kernel: avail memory = 515940352 (492 MB) Mar 13 10:46:36 jerusalem kernel: npx0: [FAST] Mar 13 10:46:36 jerusalem kernel: npx0: math processor on motherboard Mar 13 10:46:36 jerusalem kernel: npx0: INT 16 interface Mar 13 10:46:36 jerusalem kernel: acpi0: ASUS P4S533 on motherboard Mar 13 10:46:36 jerusalem kernel: acpi0: Power Button (fixed) Mar 13 10:46:36 jerusalem kernel: Timecounter ACPI-safe frequency 3579545 Hz quality 1000 Mar 13 10:46:36 jerusalem kernel: acpi_timer0: 24-bit timer at 3.579545MHz port 0xe408-0xe40b on acpi0 Mar 13 10:46:36 jerusalem kernel: cpu0: ACPI CPU on acpi0 Mar 13 10:46:36 jerusalem kernel: acpi_throttle0: ACPI CPU Throttling on cpu0 Mar 13 10:46:36 jerusalem kernel: acpi_button0: Power Button on acpi0 Mar 13 10:46:36 jerusalem kernel: pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 Mar 13 10:46:36 jerusalem kernel: pci0: ACPI PCI bus on pcib0 Mar 13 10:46:36 jerusalem kernel: agp0: SiS 645DX host to AGP bridge on hostb0 Mar 13 10:46:36 jerusalem kernel: pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 Mar 13 10:46:36 jerusalem kernel: pci1: ACPI PCI bus on pcib1 Mar 13 10:46:36 jerusalem kernel: vgapci0: VGA-compatible display mem 0xfc00-0xfdff,0xf380-0xf3803fff,0xf300-0xf37f irq 11 at device 0.0 on pci1 Mar 13 10:46:36 jerusalem kernel: drm0: Matrox G400/G450 (AGP) on vgapci0 Mar 13 10:46:36 jerusalem kernel: info: [drm] AGP at 0xf400 64MB Mar 13 10:46:36 jerusalem kernel: info: [drm] Initialized mga 3.2.1 20051102 Mar 13 10:46:36 jerusalem kernel: isab0: PCI-ISA bridge at device 2.0 on pci0 Mar 13 10:46:36 jerusalem kernel: isa0: ISA bus on isab0 Mar 13 10:46:36 jerusalem kernel: ohci0: SiS 5571 USB controller mem 0xf280-0xf2800fff irq 14 at device 2.2 on pci0 Mar 13 10:46:36 jerusalem kernel: ohci0: [GIANT-LOCKED] Mar 13 10:46:36 jerusalem kernel: usb0: OHCI version 1.0, legacy support Mar 13 10:46:36 jerusalem kernel: usb0: SMM does not respond, resetting Mar 13 10:46:36 jerusalem kernel: usb0: SiS 5571 USB controller on ohci0 Mar 13 10:46:36 jerusalem kernel: usb0: USB revision 1.0 Mar 13 10:46:36 jerusalem kernel: uhub0: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb0 Mar 13 10:46:36 jerusalem kernel: uhub0: 3 ports with 3 removable, self powered Mar 13 10:46:36 jerusalem kernel: ohci1: SiS 5571 USB controller mem 0xf200-0xf2000fff irq 5 at device 2.3 on pci0 Mar 13 10:46:36 jerusalem kernel: ohci1: [GIANT-LOCKED] Mar 13 10:46:36 jerusalem kernel: usb1: OHCI version 1.0, legacy support Mar 13 10:46:36 jerusalem kernel: usb1: SMM does not respond, resetting Mar 13 10:46:36 jerusalem kernel: usb1: SiS 5571 USB controller on ohci1 Mar 13 10:46:36 jerusalem kernel: usb1: USB revision 1.0 Mar 13 10:46:36 jerusalem kernel: uhub1: SiS OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 on usb1 Mar 13 10:46
kernel debugger
Hi! We have some networking problem, with PF and route-to, actually, system locks and sends junk to net. But I'm able to enter debugger. Is it possible to localize problem using it? I have acess to console and get do debugger prompt. I'd like to make proper report using debugger to send to freebsd-pf list. Thanks a lot! Sergey Lapin System Administrator ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help on kernel debugger
On Tuesday, 24 February 2004 at 11:23:40 +0530, [EMAIL PROTECTED] wrote: I need to use a kernel debugger on FreeBSD 4.8 to check if my messages to the kernel have all the info required and if Is being processed. I don't really understand what you mean here. DDB is the debugger mentioned in the handbook. Will DDB help Me debug the kernel on the target itself? That's one possibility. All that I have read abt DDB is debugging from a remote box over a serial line. No, that's gdb. I have rebuilt my kernel with the options # Kernel debugger support options DDB options DDB_UNATTENDED A lot depends on exactly what you want to do. There's an man page gdb(4) in -CURRENT which will, to some extent, help you with remote debugging. Note that the macros mentioned are in 4.8, but they're in a different form in the directory /usr/src/sys/modules/vinum. You'll have to play around with them to get them to work. Also, 4.8 does not support debugging over firewire. If you have specific questions, I suggest you follow up on [EMAIL PROTECTED] Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Note: I discard all HTML mail unseen. Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
Help on kernel debugger
I need to use a kernel debugger on FreeBSD 4.8 to check if my messages to the kernel have all the info required and if Is being processed. DDB is the debugger mentioned in the handbook. Will DDB help Me debug the kernel on the target itself? All that I have read abt DDB is debugging from a remote box over a serial line. I have rebuilt my kernel with the options # Kernel debugger support options DDB options DDB_UNATTENDED -sundeep Confidentiality Notice The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender at Wipro or [EMAIL PROTECTED] immediately and destroy all copies of this message and any attachments. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: escape to kernel debugger
[Format recovered--see http://www.lemis.com/email/email-format.html] Your MUA is not handling quoted-printable correctly. On Friday, 26 December 2003 at 9:35:05 +0200, Danny Braniss wrote: On Friday, 26 December 2003 at 9:13:57 +0200, Danny Braniss wrote: hi, how can i break into the kernel debugger when the console is a serial one? (Ctrl-Alt-Esc has now ascii equivalent :-) Try: sysctl debug.enter_debugger=gdb to go into gdb, or sysctl debug.enter_debugger=ddb to go into ddb. wups, sorry, forgot to mention, the machine is hung In that case, you could have trouble either way. There are possibilities with firewire, but you've probably lost. If you can't get local access, I think it's time for the Big Red Button. Greg -- When replying to this message, please copy the original recipients. If you don't, I may ignore the reply or reply to the original recipients. For more information, see http://www.lemis.com/questions.html Finger [EMAIL PROTECTED] for PGP public key. See complete headers for address and phone numbers. pgp0.pgp Description: PGP signature
