From owner-freebsd-current@FreeBSD.ORG  Sun Mar 14 06:58:23 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 26B4E16A4CE
	for <freebsd-current@FreeBSD.org>;
	Sun, 14 Mar 2004 06:58:23 -0800 (PST)
Received: from mailbox.univie.ac.at (mailbox.univie.ac.at [131.130.1.27])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8DC0F43D1D
	for <freebsd-current@FreeBSD.org>;
	Sun, 14 Mar 2004 06:58:22 -0800 (PST)	(envelope-from le@FreeBSD.org)
Received: from wireless (adslle.cc.univie.ac.at [131.130.102.11])
	i2EEwEHJ888554;	Sun, 14 Mar 2004 15:58:16 +0100
Date: Sun, 14 Mar 2004 15:58:13 +0100 (CET)
From: Lukas Ertl <le@FreeBSD.org>
To: Kaarthik Sivakumar <kaarthik@comcast.net>
In-Reply-To: <86r7vvwkin.fsf@comcast.net>
Message-ID: <20040314155729.F657@korben.in.tern>
References: <86r7vvwkin.fsf@comcast.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-DCC-ZID-Univie-Metrics: mailbox 4261; Body=0 Fuz1=0 Fuz2=0
cc: freebsd-current@FreeBSD.org
Subject: Re: CD access panic on 5.2RC2 (similar to panic before foraudio/data
 CD access)
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: Sun, 14 Mar 2004 14:58:23 -0000

On Sun, 14 Mar 2004, Kaarthik Sivakumar wrote:

> The stacktrace is (copied by hand, so possibility of a typo exists):
>
> devstat_remove_entry(c2ee3870, 0, 0, c2f0a600, d89a1ccc) at
>        devstat_remove_entry+0x83
> g_destroy_provider(c2f0a600, c06542bc, c2f0a654, c2f0a600, c04b68a0)
>        at g_destroy_provider+0x48
> g_orphan_register(c2f0a600, 0, c0654283, a6, 66666667) at
>        g_orphan_register+0x65
> one_event(d89a1d10, c04b68c5, c06a0654, 0, 4c) at one_event+0xc0
> g_run_events(c06a0654, 0, 4c, c06536b9, a) at g_run_events+0x15
> g_event_procbody(0, d89a1d48, c0655a40, 311, 0) at
>        g_event_procbody+0x25
> fork_exit(c04b68a0, 0, d89a1d48) at fork_exit+0x7e
> fork_trampoline() at fork_trampoline+0x8
> --- trap 0x1, eip = 0, esp = 0xd89a1d7c, ebp = 0 ---

What's the panic message?  Would it be possible for you to get a coredump
and a gdb backtrace out of that?

Thanks,
le

-- 
Lukas Ertl                           http://mailbox.univie.ac.at/~le/
le@FreeBSD.org                       http://people.freebsd.org/~le/