From: William Lee Irwin III <wli@holomorphy.com>
To: Anthony Lau <anthony@greyweasel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops with HIMEM+VM in 2.4.19,20
Date: Fri, 10 Jan 2003 14:58:35 -0800 [thread overview]
Message-ID: <20030110225835.GC1147@holomorphy.com> (raw)
In-Reply-To: <20030110180953.GB1292@kimagure>
On Fri, Jan 10, 2003 at 02:48:27AM -0800, William Lee Irwin III wrote:
>> Looks like someone e.g. invalidate_inode_pages(), truncate_inode_pages(),
>> etc. etc., left pages hanging around. Borderline VM/vfs stuff. Or swap
>> code mangled something important. This oops either has buttloads of
>> stack noise or some other issue corrupting it. Can you find the first
>> oops? If this is not the first oops, then it's probably not useful.
On Fri, Jan 10, 2003 at 10:09:53AM -0800, Anthony Lau wrote:
> That was the first Oops message logged. System instability starts before
> any oop messages begin to show up in the standard syslogd logs. Something
> does appear in ksymoops. I have setup "klogd -x" and await the next log.
Okay, what filesystem(s) are you using (this usually has something to do
with a filesystem)?
Also, are you applying any patches to 2.4.19/2.4.20?
Thanks,
Bill
next prev parent reply other threads:[~2003-01-10 22:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 8:37 Kernel Oops with HIMEM+VM in 2.4.19,20 Anthony Lau
2003-01-10 9:08 ` Denis Vlasenko
2003-01-10 18:02 ` Anthony Lau
2003-01-10 10:48 ` William Lee Irwin III
2003-01-10 18:09 ` Anthony Lau
2003-01-10 22:58 ` William Lee Irwin III [this message]
2003-01-10 23:29 ` Anthony Lau
2003-01-16 8:34 ` Kernel Oops with HIMEM+VM in 2.4.19,20: More INFO Anthony Lau
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=20030110225835.GC1147@holomorphy.com \
--to=wli@holomorphy.com \
--cc=anthony@greyweasel.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.