From: Gordon Cormack <gvcormac@uwaterloo.ca>
To: linux-kernel@vger.kernel.org
Subject: 2.6.test11 bug
Date: Sun, 7 Dec 2003 21:24:27 -0500 [thread overview]
Message-ID: <20031208022427.GA12859@cormack.uwaterloo.ca> (raw)
Hi,
I have read the FAQ but I'm confused about how to report a 2.6
kernel bug, or who to report it to.
Here it is in a nutshell.
--- kernel ---
Linux xxx20.uwaterloo.ca 2.6.0-test11 #2 SMP Thu Nov 27 14:46:01 EST 2003 i686 athlon i386 GNU/Linux
---- log ----
Dec 6 13:16:01 flax20 kernel: Bad page state at free_hot_cold_page
Dec 6 13:16:01 flax20 kernel: flags:0x02000114 mapping:00000000 mapped:1 count:0
Dec 6 13:16:01 flax20 kernel: Backtrace:
Dec 6 13:16:01 flax20 kernel: Call Trace:
Dec 6 13:16:01 flax20 kernel: [<c013f98d>] bad_page+0x5d/0x90
Dec 6 13:16:01 flax20 kernel: [<c0140041>] free_hot_cold_page+0x61/0xf0
Dec 6 13:16:01 flax20 kernel: [<c014063c>] __pagevec_free+0x1c/0x30
Dec 6 13:16:01 flax20 kernel: [<c014527f>] release_pages+0x11f/0x140
Dec 6 13:16:01 flax20 kernel: [<c01544a6>] free_pages_and_swap_cache+0x56/0x90
Dec 6 13:16:01 flax20 kernel: [<c014cf60>] unmap_region+0x150/0x160
Dec 6 13:16:01 flax20 kernel: [<c014d28f>] do_munmap+0x11f/0x170
Dec 6 13:16:01 flax20 kernel: [<c014d325>] sys_munmap+0x45/0x70
Dec 6 13:16:01 flax20 kernel: [<c010adcf>] syscall_call+0x7/0xb
Dec 6 13:16:01 flax20 kernel:
Dec 6 13:16:01 flax20 kernel: Trying to fix it up, but a reboot is needed
Dec 6 16:31:14 flax20 syslogd 1.4.1: restart.
--- comments ---
The problem has occurred only once on one of 13 dual-processor machines.
The one that crashed was one (of seven) with dual AMD 1900+, 2GB RAM,
and 4 ATA hard drives. None of the other machines have crashed in the
9 days since I installed the kernel.
It appears to be related to high memory pressure but I can't reproduce
it with simple programs. The machines run text search software that is
both CPU and IO intensive.
---
I'm not a developer but I am running a pretty significant load on these
machines and am prepared to do instrumentation/investigation in order to
diagnose the problem.
As an aside, all versions of the 2.4 kernel are brought to their knees
in this application ("kswapd problems" hit full force and none of the
suggested patches worked). Even with the occasional crash, 2.6.test11 is
way better.
--
Gordon V. Cormack CS Dept, University of Waterloo, Canada N2L 3G1
gvcormack@uwaterloo.ca http://cormack.uwaterloo.ca/cormack
next reply other threads:[~2003-12-08 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 2:24 Gordon Cormack [this message]
2003-12-08 2:37 ` 2.6.test11 bug Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 3:46 Rafal Skoczylas
2003-12-08 4:17 ` William Lee Irwin III
2003-12-08 5:17 ` Linus Torvalds
2003-12-08 9:02 ` Xavier Bestel
[not found] ` <20031208161742.GB9087@secprog.org>
[not found] ` <Pine.LNX.4.58.0312080848560.13236@home.osdl.org>
2003-12-08 17:12 ` Linus Torvalds
[not found] ` <20031209194827.GA22265@secprog.org>
[not found] ` <Pine.LNX.4.58.0312091221440.21456@home.osdl.org>
2003-12-09 22:31 ` Rafal Skoczylas
2003-12-09 23:26 ` Linus Torvalds
[not found] <10kzo-7mZ-11@gated-at.bofh.it>
[not found] ` <10m88-2wd-1@gated-at.bofh.it>
[not found] ` <10xdJ-28r-23@gated-at.bofh.it>
[not found] ` <10xdJ-28r-25@gated-at.bofh.it>
[not found] ` <10xdJ-28r-21@gated-at.bofh.it>
2003-12-08 22:28 ` Rafal Skoczylas
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=20031208022427.GA12859@cormack.uwaterloo.ca \
--to=gvcormac@uwaterloo.ca \
--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