From: Andrew Morton <akpm@zip.com.au>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Anton Altaparmakov <aia21@cantab.net>,
"David S. Miller" <davem@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic
Date: Mon, 03 Jun 2002 23:37:50 -0700 [thread overview]
Message-ID: <3CFC603E.A7DC1525@zip.com.au> (raw)
In-Reply-To: <1023096034.19717.62.camel@storm.christs.cam.ac.uk> <3CFB3B87.74C7E9DF@zip.com.au> <shshekkbnrr.fsf@charged.uio.no>
Trond Myklebust wrote:
>
> >>>>> " " == Andrew Morton <akpm@zip.com.au> writes:
>
> > Anton Altaparmakov wrote:
> >>
> >> Hi,
> >>
> >> Just got this (reproducible) kernel panic (BUG in
> >> asm-i386/highmem.h::kmap_atomic(), the if
> >> (!pte_none(*(kmap_pte-idx))) BUG(); triggers). It happens every
> >> time I boot and on an NFS mount do a ./configure.
>
> > Dunno about this one. I'm seeing some (totally different) NFS
> > funnies at present - pagecache data on the client is coming up
> > zeroes under memory pressure. Trond mentioned that NFS
> > recently went to kmap_atomic, so there is a common thread
> > there.
>
> Following an off-list chat with David, I believe that the appended
> patch should fix the problem reported by Anton. It replaces the
> obsolete km_type "KM_SKB_DATA" with an entry that the RPC layer can
> use in the socket bottom half.
>
> I'm less sure whether or not it will fix your problem, Andrew, but I'm
> hoping you'll find time to give it a brief test ;-)...
It fixed it.
The problem was that pagecache data on the NFS client was showing
incorrect chunks of several k's of zeroes. No particuar alignment,
either. And it only happened when the machine is under page-replacement
pressure. And only when the machine has highmem.
It'd be nice to understand _why_ it fixed it. Do we know why NFS
was losing data when using KM_USER0? As far as I can see the new
and old code look pretty darn similar. Interested.
-
next prev parent reply other threads:[~2002-06-04 6:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 9:20 [2.5.20-BUG] 3c59x + highmem + acpi + nfs -> kernel panic Anton Altaparmakov
2002-06-03 9:48 ` Andrew Morton
2002-06-03 11:32 ` Trond Myklebust
2002-06-04 6:37 ` Andrew Morton [this message]
2002-06-04 11:39 ` Trond Myklebust
2002-06-04 10:39 ` David S. Miller
2002-06-04 12:10 ` Trond Myklebust
2002-06-04 11:46 ` Anton Altaparmakov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3CFC603E.A7DC1525@zip.com.au \
--to=akpm@zip.com.au \
--cc=aia21@cantab.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox