From: "Robert Schelander" <rschelander@aon.at>
To: <linux-kernel@vger.kernel.org>
Subject: swap_free: Bad swap offset entry
Date: Thu, 25 Apr 2002 09:35:18 +0200 [thread overview]
Message-ID: <004601c1ec2e$a59e4bb0$fe78a8c0@robert> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0204242313480.8788-100000@dragon.pdx.osdl.net>
I run a 2.4.17 system with high filesystem load and experience the
following problem:
after running some hours with ext2 I got a lot of these messages:
Apr 24 22:19:00 linux kernel: swap_free: Bad swap offset entry 04000000
if I do a swapoff (swap is at /dev/hda6) they turn to:
Apr 24 22:20:29 linux kernel: swap_free: Unused swap file entry 04000000
..and get back to "Bad swap offset entry" if I do the swapon again
Before that I run the machine with ext3 where even worse things happened.
I got a lot of these messages before the machine hangs some hours later:
Apr 22 04:01:04 linux kernel: Unable to handle kernel paging request at
virtual address e71d6478
Apr 22 04:01:04 linux kernel: printing eip:
Apr 22 04:01:04 linux kernel: c013ede8
Apr 22 04:01:04 linux kernel: *pde = 00000000
Apr 22 04:01:04 linux kernel: Oops: 0002
Apr 22 04:01:04 linux kernel: CPU: 0
Apr 22 04:01:04 linux kernel: EIP: 0010:[prune_dcache+24/296] Not
tainted
Apr 22 04:01:04 linux kernel: EFLAGS: 00210212
Apr 22 04:01:04 linux kernel: eax: c027c93c ebx: c71d63f8 ecx: c71d6040
edx: e71d6478
Apr 22 04:01:04 linux kernel: esi: c71d62e0 edi: 00000000 ebp: 00007e35
esp: c3771e04
Apr 22 04:01:04 linux kernel: ds: 0018 es: 0018 ss: 0018
Apr 22 04:01:04 linux kernel: Process mogrify (pid: 913, stackpage=c3771000)
Apr 22 04:01:04 linux kernel: Stack: 00000004 000001d2 00000020 00000006
c013f14b 0000a4d0 c01290e0 00000006
Apr 22 04:01:05 linux kernel: 000001d2 00000006 000001d2 c027bc48
c027bc48 c027bc48 c012913c 00000020
Apr 22 04:01:05 linux kernel: c3770000 00000100 00000000 c0129942
c027bdc4 00000100 00000010 00000000
Apr 22 04:01:05 linux kernel: Call Trace: [shrink_dcache_memory+27/52]
[shrink_caches+108/140] [try_to_free_pages+60/92] [balance_classzone+78/360]
[__alloc_pages+262/356]
Apr 22 04:01:05 linux kernel: [_alloc_pages+22/24]
[do_anonymous_page+52/228] [do_no_page+51/400] [handle_mm_fault+82/176]
[do_page_fault+352/1176] [do_page_fault+0/1176]
Apr 22 04:01:05 linux kernel: [update_wall_time+11/52] [timer_bh+36/604]
[do_timer+63/108] [timer_interrupt+95/264] [bh_action+26/64]
[tasklet_hi_action+68/100]
Apr 22 04:01:05 linux kernel: [do_softirq+90/164] [error_code+52/60]
Apr 22 04:01:05 linux kernel:
Apr 22 04:01:05 linux kernel: Code: 89 02 89 1b 89 5b 04 8d 73 e8 8b 46 54
a8 08 74 27 24 f7 89
Any ideas/help??
Thanks in advance
Robert
next prev parent reply other threads:[~2002-04-25 7:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-19 21:03 unresolved symbol: __udivdi3 Ben Greear
2002-04-19 21:09 ` Randy.Dunlap
2002-04-19 21:58 ` Ben Greear
2002-04-19 21:56 ` David S. Miller
2002-04-19 22:12 ` Ben Greear
2002-04-19 23:33 ` Ben Greear
2002-04-19 23:42 ` Randy.Dunlap
2002-04-20 19:02 ` Chris Caputo
2002-04-25 6:15 ` Randy.Dunlap
2002-04-25 7:35 ` Robert Schelander [this message]
2002-04-25 14:05 ` swap_free: Bad swap offset entry Hugh Dickins
2002-04-19 21:38 ` unresolved symbol: __udivdi3 Andreas Dilger
2002-04-20 16:25 ` GOTO Masanori
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='004601c1ec2e$a59e4bb0$fe78a8c0@robert' \
--to=rschelander@aon.at \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox