CD access panic on 5.2RC2 (similar to panic before foraudio/data
CD access)
Lukas Ertl
le at FreeBSD.org
Sun Mar 14 06:58:23 PST 2004
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 at FreeBSD.org http://people.freebsd.org/~le/
More information about the freebsd-current
mailing list