From: abusch@gmx.net
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [oops] 2.4.12+i kswapd invalid operand: 0000
Date: Mon, 22 Oct 2001 15:21:09 +0200 (MEST) [thread overview]
Message-ID: <8858.1003756869@www60.gmx.net> (raw)
>> There seems to be a problem with KSWAPD, maybe with the latest vm changes
?
>> Haven't seen oops for a long time. Uptime was only 17 hours.
>>
>> The kernel is 2.4.12 patched with the international crypto patch 2.4.3.1
>> and the 1512 NVidia module is loaded.
>Can you reproduce this bug without the NVIDIA driver or without the crypto
patch ?
The crypto stuff is compiled as modules and they were not used nor loaded at
that time.
An init 3 now on my box, disconnected my ssh-session ??? sorry, so I can
only tell you later when I'm at home to check what happened this time....
sorry. (uptime so far was 21 hours, the mysterious thing is that it happened
almost the same minute ~15:02:00 same as yesterday, I have to check that.)
> >>EIP; c012a17b <__free_pages_ok+1b/1e0> <=====
> Trace; c0129901 <shrink_cache+1c1/300>
> Trace; c0129bbc <shrink_caches+5c/90>
> Trace; c0129c1c <try_to_free_pages+2c/60>
> Trace; c0129cd1 <kswapd_balance_pgdat+51/a0>
> Trace; c0129d46 <kswapd_balance+26/50>
> Trace; c0129e91 <kswapd+a1/c0>
> Trace; c0129df0 <kswapd+0/c0>
But can you tell me what is this memory area coming from ? c000000 should be
free ?
RAM goes here:
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000a0000-000bffff : Video RAM area
000c0000-000c7fff : Video ROM
000f0000-000fffff : System ROM
00100000-0ffeffff : System RAM
Framebuffer here:
d0000000-d7ffffff : PCI Bus #01
other PCI stuff follows...
thx,
Andy.
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
next reply other threads:[~2001-10-22 13:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-22 13:21 abusch [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-22 12:49 abusch
2001-10-22 12:55 ` Rik van Riel
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=8858.1003756869@www60.gmx.net \
--to=abusch@gmx.net \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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
all inboxes | Powered by JetHome®