From: "Ramón Rey Vicente" <ramon.rey@hispalinux.es>
To: Andrew Morton <akpm@osdl.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.0-test7-bk][OOPS] Unable to handle kernel paging request at virtual address f9a7e857
Date: Mon, 13 Oct 2003 16:59:08 +0200 [thread overview]
Message-ID: <1066057147.1003.3.camel@debian> (raw)
In-Reply-To: <20031013033459.3519f83b.akpm@osdl.org>
[-- Attachment #1.1: Type: text/plain, Size: 925 bytes --]
El lun, 13-10-2003 a las 12:34, Andrew Morton escribió:
> You get the award for the weirdest bug report of the 21st century. There
> is just no way in which kswapd can call ->readpages().
>
> The only thing I can think of is that an inode's superblock's ->put_inode
> pointer somehow got set to point at ext3_readpages(). Or we got a
> completely wild pointer in prune_dcache(). Some sort of memory scribble,
> anyway.
>
> What sort of machine is it? Nice, new and stable or old, nasty and likely
> to tromp its memory?
My machine is a k6-2 450, 256 MiB of RAM, and is stable and solid. I use
it as my desktop system, and the memory keeps coherent always, after
hours of activity. No crashes, no randomly hangs,...
--
Ramón Rey Vicente <ramon dot rey at hispalinux dot es>
jabber ID <rreylinux at jabber dot org>
GPG public key ID 0xBEBD71D5 -> http://pgp.escomposlinux.org/
[-- Attachment #1.2: dmesg.log.gz --]
[-- Type: application/x-gzip, Size: 2847 bytes --]
[-- Attachment #1.3: versions.log.gz --]
[-- Type: application/x-gzip, Size: 505 bytes --]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-13 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-12 11:49 [2.6.0-test7-bk][OOPS] Unable to handle kernel paging request at virtual address f9a7e857 Ramón Rey Vicente
2003-10-13 10:34 ` Andrew Morton
2003-10-13 14:59 ` Ramón Rey Vicente [this message]
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=1066057147.1003.3.camel@debian \
--to=ramon.rey@hispalinux.es \
--cc=akpm@osdl.org \
--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.