Am Freitag, 16. März 2007 03:06 schrieben Sie:
> 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.
Thank you, I'll test this
Am Freitag, 16. März 2007 03:06 schrieben Sie:
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.
Thank you, I'll test this
Joerg Platte naasa.net> writes:
> Pid: 14, comm: events/0 Not tainted 2.6.18-4-amd64 #1
> RIP: 0010:[] [] 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.
Hi!
On our file server we have the following problem (the full dmesg output is
available at http://www-ds.e-technik.uni-dortmund.de/~jplatte/dmesg.txt ):
Unable to handle kernel paging request at 00100108 RIP:
[] keyring_destroy+0x32/0x96
PGD 195d33067 PUD 193202067 PMD 0
Oops: 0002
Hi!
On our file server we have the following problem (the full dmesg output is
available at http://www-ds.e-technik.uni-dortmund.de/~jplatte/dmesg.txt ):
Unable to handle kernel paging request at 00100108 RIP:
[802ec036] keyring_destroy+0x32/0x96
PGD 195d33067 PUD 193202067 PMD
Joerg Platte lists at naasa.net writes:
Pid: 14, comm: events/0 Not tainted 2.6.18-4-amd64 #1
RIP: 0010:[802ec036] [802ec036] 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
6 matches
Mail list logo