[lkml]   [2000]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Oops: Unable to handle kernel null pointer

On Wed, 20 Sep 100, Sebastian Willing wrote:

It's almost impossible to extract some useful information from your
oops without your kernel symbols (Documentation/oops-tracing.txt).
However, to make a guess, this

> Unable to handle kernel NULL pointer dereference at
virtual address 00000034
looks similar to the quota issue, for wich I've posted a fix some days
ago. If, after applying ksymoops to your trace, you find out the oops
happens in check_idq() called from dquot_transfer() you might be
happy with this patch (search for [PATCH] and dquot_transfer in l-k).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.087 / U:0.120 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site