Joerg Platte <lists <at> naasa.net> writes: > Pid: 14, comm: events/0 Not tainted 2.6.18-4-amd64 #1 > RIP: 0010:[<ffffffff802ec036>] [<ffffffff802ec036>] keyring_destroy+0x32/0x96
[Snip] > Can this oops be caused by a known and already > fixed problem in a newer kernel versions? In this case I would submit a bug > to the Debian BTS. Otherwise what can I do to further reproduce and debug > this oops? > Check out http://bugzilla.kernel.org/show_bug.cgi?id=8067 which is a duplicate of http://bugzilla.kernel.org/show_bug.cgi?id=7727 which is fixed. There is a patch available on the bugzilla if you want to try it out. HTH Parag - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
