public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Patrick Burns <patrickb@vrlaw.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Oops in kswapd (Kernel 2.4.17)
Date: Sun, 13 Jan 2002 18:13:13 -0800	[thread overview]
Message-ID: <3C423EB9.1E7A933E@zip.com.au> (raw)
In-Reply-To: <3C423A90.2E34D426@vrlaw.com.au>

Patrick Burns wrote:
> 
> Is there some kind of memory problem with kernel 2.4.17? I noticed in an
> article at:
> 
> http://marc.theaimsgroup.com/?l=linux-kernel&m=101096234600708&w=2
> 
> and another at:
> 
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0201.1/0809.html
> 
> that people were getting oopses in kswapd.

One does begin to think that there may be a problem.  The inode,
dentry and buffer caches do involve a lot of pointer chasing,
and do tend to expose hardware problems (memory), and we've tended
to assume that's the reason for all the reports.

But there are a *lot* of reports, and the same argument applies:
the long pointer chases will expose random memory corruption caused
by a kernel bug.

It's starting to look fishy.

-

  reply	other threads:[~2002-01-14  2:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-14  1:55 Oops in kswapd (Kernel 2.4.17) Patrick Burns
2002-01-14  2:13 ` Andrew Morton [this message]
2002-01-14  9:34 ` Alan Cox

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=3C423EB9.1E7A933E@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrickb@vrlaw.com.au \
    /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