Skip to contentSkip to conversation

2.6.test11 bug

DISCUSSION Gordon Cormack 2 participants 2 messages Dec 8, 2003

lore
Share & tools
lore
#0 lore 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.

Signature · 2 lines
Gordon V. Cormack     CS Dept, University of Waterloo, Canada N2L 3G1
[email protected]            http://cormack.uwaterloo.ca/cormack
#1 lore raw
Quoted 3 lines · Gordon Cormack

I have read the FAQ but I'm confused about how to report a 2.6 kernel bug, or who to report it to.

This is good.

Quoted 1 line

Here it is in a nutshell.

And we want some more information on what kind of load/machine/config this is. However, I'm guessing from the report..

Quoted 1 line
Dec  6 13:16:01 flax20 kernel: Bad page state at free_hot_cold_page

..that this might be running XFS? We've had this report from XFS users before.

But if it isn't using XFS, holler _loudly_, and please do include more information about what configuration (both hardware and kernel config) the machine has.

Quoted 4 lines

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.

Hey, I don't like the occasional crash either.

Linus