From grog@mojave.worldwide.lemis.com  Sun Apr 23 17:29:53 2000
Return-Path: <grog@mojave.worldwide.lemis.com>
Received: from yana.lemis.com (yana.lemis.com [192.109.197.140])
	by hub.freebsd.org (Postfix) with ESMTP id 35A6837B9F8
	for <FreeBSD-gnats-submit@freebsd.org>; Sun, 23 Apr 2000 17:29:48 -0700 (PDT)
	(envelope-from grog@mojave.worldwide.lemis.com)
Received: from mojave.worldwide.lemis.com (root@mojave.lemis.com [192.109.197.162])
	by yana.lemis.com (8.8.8/8.8.8) with ESMTP id JAA12585
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 24 Apr 2000 09:59:45 +0930 (CST)
	(envelope-from grog@mojave.worldwide.lemis.com)
Received: (from grog@localhost)
	by mojave.worldwide.lemis.com (8.9.3/8.9.3) id JAA13998;
	Mon, 24 Apr 2000 09:58:56 +0930 (CST)
	(envelope-from grog)
Message-Id: <200004240028.JAA13998@mojave.worldwide.lemis.com>
Date: Mon, 24 Apr 2000 09:58:56 +0930 (CST)
From: Greg Lehey <grog@mojave.worldwide.lemis.com>
Reply-To: grog@mojave.worldwide.lemis.com
To: FreeBSD-gnats-submit@freebsd.org
Subject:
X-Send-Pr-Version: 3.2

>Number:         18182
>Category:       kern
>Synopsis:       Remote serial gdb no longer works since mid-April
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr 23 17:30:00 PDT 2000
>Closed-Date:    Fri Jan 18 08:14:39 PST 2002
>Last-Modified:  Fri Jan 18 08:15:24 PST 2002
>Originator:     Greg Lehey
>Release:        FreeBSD 5.0-CURRENT i386
>Organization:
LEMIS, PO Box 460, Echunga SA 5153, Australia
>Environment:
 
 	i386 machine with remote kernel debugging enabled.
 
>Description:
 
 	Since about mid-April, remote kernel debugging has become
 	non-functional: there are so many transmission errors on the
 	link that communication is effectively impossible.  Debugging
 	printouts in the kernel show that the input routines are
 	dropping several characters in sucession.
 
 	The following examples are from a dual processor Celeron, but
 	this does not appear to be an SMP bug.  Older SP kernels work,
 	and current SP kernels do not.  No older SMP kernel is
 	available for testing, but I am currently building one.
 
 	This example shows that there is no trouble entering gdb from
 	the keyboard (ctrl-alt-esc).  This works reliably.  On the
 	other hand, a breakpoint placed on execve repeatedly fails to
 	communicate, to the point where it is no longer possible to
 	resume execution.  This looks like an interrupt problem, but I
 	checked the ipl at the execve entry point, and as expected it
 	was set to 0.
 
 	$ gdb -k
 	GNU gdb 4.18
 	Copyright 1998 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-unknown-freebsd".
 	Debugger (msg=0xc0354709 "manual escape to debugger") at ../../i386/i386/db_interface.c:325
 	325     }
 	(kgdb) bt
 	#0  Debugger (msg=0xc0354709 "manual escape to debugger") at ../../i386/i386/db_interface.c:325
 	#1  0xc02e088a in scgetc (sc=0xc03aca80, flags=0x2) at ../../dev/syscons/syscons.c:3124
 	#2  0xc02dd2d1 in sckbdevent (thiskbd=0xc03a51a0, event=0x0, arg=0xc03aca80) at ../../dev/syscons/syscons.c:634
 	#3  0xc02d52c6 in atkbd_intr (kbd=0xc03a51a0, arg=0x0) at ../../dev/kbd/atkbd.c:462
 	#4  0xc0306814 in atkbd_isa_intr (arg=0xc03a51a0) at ../../isa/atkbd_isa.c:125
 	(kgdb) b execve
 	Breakpoint 1 at 0xc01aa2bc: file ../../kern/kern_exec.c, line 103.
 	(kgdb) c
 	Continuing.
 
 	Breakpoint 1, 0xc01aa2bc in execve (p=0xcf56b3c0, uap=0xcff72f80) at ../../kern/kern_exec.c:103
 	103     {
 	(kgdb) bt
 	#0  0xc01aa2bc in execve (Ignoring packet error, continuing...
 	p=Reply contains invalid hex digit 116
 	) at ../../kern/kern_exec.c:103
 	#1  0xc02f49e5 in syscall2 (frame={tf_fs = 0x2f, tf_es = 0x2f, tf_ds = 0x2f, tf_edi = 0x7c1c0, tf_esi = 0x7c0a0, 
 	      tf_ebp = 0xbfbffc4c, tf_isp = 0xcff72fd4, tf_ebx = 0x7c170, tf_edx = 0x7c010, tf_ecx = 0x4, tf_eax = 0x3b, 
 	      tf_trapno = 0xc, tf_err = 0x7, tf_eip = 0x20098411, tf_cs = 0x1f, tf_eflags = 0x292, tf_esp = 0xbfbffb7c, 
 	      tf_ss = 0x2f}) at ../../i386/i386/trap.c:1130
 	#2  0x20098411 in ?? ()
 	#3  0xe0ff in ?? ()
 	#4  0xd90b in ??Ignoring packet error, continuing...
 	 ()Reply contains invalid hex digit 116
 	(kgdb) bt
 	#0  0xc01aa2bc in execve (Ignoring packet error, continuing...
 	p=Reply contains invalid hex digit 116
 	) at ../../kern/kern_exec.c:103
 	^C#1  0xc02f49e5 in syscall2 (Ignoring packet error, continuing...
 	frame=Reply contains invalid hex digit 116
 	) at ../../i386/i386/trap.c:1130
 	#2  0x20098411 in ??Ignoring packet error, continuing...
 	 ()Reply contains invalid hex digit 116
 	(kgdb) 
 
>How-To-Repeat:
 
 	As shown above.
 
>Fix:
 	
 	No fix known.
 
 
 
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: gnats-admin->freebsd-bugs 
Responsible-Changed-By: asmodai 
Responsible-Changed-When: Sun Apr 30 06:41:57 PDT 2000 
Responsible-Changed-Why:  
Misfiled PR. 

Greg, I saw a few mails from you on this subject, either on -current 
or on -committers.  And I also think I read that solved something 
with regard to this.  Can you elaborate and if needed reassign the 
PR or close it or whatever other action is needed? 
State-Changed-From-To: open->feedback 
State-Changed-By: joerg 
State-Changed-When: Mon Aug 13 13:48:45 MEST 2001 
State-Changed-Why:  
Greg, i've been using remote gdb a lot lately, it seems to 
work for me (@9600 Bd though).  Does your problem still exist, 
and do you perhaps more datapoints? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=18182 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Fri Jan 18 08:14:39 PST 2002 
State-Changed-Why:  
Automatic feedback timeout.  If additional feedback that warrants 
the re-opening of this PR is available but not included in the 
audit trail, please include the feedback in a reply to this message 
(preserving the Subject line) and ask that the PR be re-opened. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=18182 
>Unformatted:
