Re: lot's of oops's on 2.4.4 in d_lookup/cached_lookup

Andreas Dilger (adilger@turbolinux.com)
Wed, 23 May 2001 12:08:41 -0600 (MDT)


Nathan writes:
> I've got a system monitoring box, running 2.4.4 with a few patches (ide,
> inode-nr_unused, max-readahead, knfsd, and a couple of basic tuning opts w/o
> code changes). Basically, the server runs anywhere from a few hours to a few
> days, but always seems to get to a point where it gets tons of the following
> type of oops. It is almost ALWAYS in d_lookup.
>
> May 23 10:53:44 sysmon kernel: Unable to handle kernel paging request at
> virtual address 96000000

I can't help you with your specific problem, but I'm curious if someone
can explain exactly what "Unable to handle kernel paging request" means?
Is this a bad pointer deference, a page fault for a non-existent page?
Stack corruption or overflow? What would cause this?

Cheers, Andreas

-- 
Andreas Dilger  \ "If a man ate a pound of pasta and a pound of antipasto,
                 \  would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/               -- Dogbert
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/