From owner-freebsd-current@FreeBSD.ORG  Wed Nov 10 20:46:40 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7829016A4D1
	for <current@FreeBSD.org>; Wed, 10 Nov 2004 20:46:40 +0000 (GMT)
Received: from fledge.watson.org (fledge.watson.org [204.156.12.50])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7AB8F43D2D
	for <current@FreeBSD.org>; Wed, 10 Nov 2004 20:46:39 +0000 (GMT)
	(envelope-from robert@fledge.watson.org)
Received: from fledge.watson.org (localhost [127.0.0.1])
	by fledge.watson.org (8.13.1/8.13.1) with ESMTP id iAAKjRee084706
	for <current@FreeBSD.org>; Wed, 10 Nov 2004 15:45:28 -0500 (EST)
	(envelope-from robert@fledge.watson.org)
Received: from localhost (robert@localhost)iAAKjR0G084703
	for <current@FreeBSD.org>; Wed, 10 Nov 2004 20:45:27 GMT
	(envelope-from robert@fledge.watson.org)
Date: Wed, 10 Nov 2004 20:45:27 +0000 (GMT)
From: Robert Watson <rwatson@FreeBSD.org>
X-Sender: robert@fledge.watson.org
To: current@FreeBSD.org
Message-ID: <Pine.NEB.3.96L.1041110204022.60848D-100000@fledge.watson.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Some problems with KDB/scheduler?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Nov 2004 20:46:40 -0000


I've been having some problems with KDB this evening; right now what I'm
bumping into appears to be a problem with interrupts and KDB/DDB.  An
example below.

(debugger entered using sysctl debug.kdb.enter=1)

db> break vlan_start
db> cont
tiger-3# 
tiger-3# 
tiger-3# ifconfig vlan0 create
tiger-3# ifconfig vlan0 vlan 100 vlandev em0
tiger-3# ifconfig vlan0 inet 192.168.60.1
[thread 100167]
Breakpoint at   vlan_start:     pushl   %ebp
db> cont
[thread 100167]
Breakpoint at   vlan_start:     pushl   %ebp
db> cont
[thread 100167]
Breakpoint at   vlan_start:     pushl   %ebp
db> cont
tiger-3# [thread 100071]
Breakpoint at   vlan_start:     pushl   %ebp
db> cont

tiger-3# [thread 100071]
Breakpoint at   vlan_start:     pushl   %ebp
db> cont
KDB: stack backtrace:
mi_switch(6,c5457300,c5457450,c5457300,e7868c48) at mi_switch+0x2ce
maybe_preempt(c5457300,e7868c40,c06033ce,197,c080c288) at
maybe_preempt+0xf9
sched_add(c5457300) at sched_add+0x26a
ithread_schedule(c5455500,c5404a80,12,0,c554da00) at ithread_schedule+0x8a
intr_execute_handlers(c53fc5e0,e7868ca8,12,e7868cec,c0793e03) at
intr_execute_ha
ndlers+0x65
lapic_handle_intr(42) at lapic_handle_intr+0x23
Xapic_isr2() at Xapic_isr2+0x33
--- interrupt, eip = 0xc0a27b71, esp = 0xe7868cec, ebp = 0xe7868cec ---
acpi_cpu_c1(e7868d04,c0619321,c08d1520,1,fffffffe) at acpi_cpu_c1+0x5
acpi_cpu_idle(c05f8328,c5403600,e7868d34,c05f811e,0) at acpi_cpu_idle+0xe1
idle_proc(0,e7868d48,0,c05f8328,0) at idle_proc+0x65
fork_exit(c05f8328,0,e7868d48) at fork_exit+0x7e
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe7868d7c, ebp = 0 ---
panic: mi_switch: did not reenter debugger
cpuid = 0
boot() called on cpu#0
Uptime: 1m26s