From: Tobias Bengtsson <tobbe@tobbe.nu>
To: linux-kernel@vger.kernel.org
Subject: BUG? Bad page state at free_hot_cold_page
Date: Fri, 30 Jan 2004 11:34:09 +0100 [thread overview]
Message-ID: <20040130103409.GA20848@debian.as> (raw)
[-- Attachment #1: Type: text/plain, Size: 2210 bytes --]
Hi, I've had this problem since at least 2.6.1.
This output I got from a 2.6.2-rc2 compiled with the config attached
I looked in include/linux/page-flags.h and found out that flags:0x20000094
probably mean
100000000000000000000010010100
| | |_PG_referenced
| |___PG_dirty
|______PG_slab
which actually don't tell me anything, but you'll probably do better.
this kind of error crash my machine (see below) almost daily.
cheers, Tobias
PS. Please cc me the replies to this thread as I'm not subscribed.
----8<----8<----
Bad page state at free_hot_cold_page
flags:0x20000094 mapping:00000000 mapped:0 count:0
Backtrace:
Call Trace:
[bad_page+69/112] bad_page+0x45/0x70
[free_hot_cold_page+61/256] free_hot_cold_page+0x3d/0x100
[page_remove_rmap+356/368] page_remove_rmap+0x164/0x170
[free_page_and_swap_cache+57/112] free_page_and_swap_cache+0x39/0x70
[zap_pte_range+342/432] zap_pte_range+0x156/0x1b0
[path_release+17/48] path_release+0x11/0x30
[link_path_walk+164/2560] link_path_walk+0xa4/0xa00
[zap_pmd_range+69/96] zap_pmd_range+0x45/0x60
[unmap_page_range+47/96] unmap_page_range+0x2f/0x60
[unmap_vmas+243/512] unmap_vmas+0xf3/0x200
[exit_mmap+105/384] exit_mmap+0x69/0x180
[mmput+92/128] mmput+0x5c/0x80
[do_exit+334/1024] do_exit+0x14e/0x400
[timer_interrupt+79/320] timer_interrupt+0x4f/0x140
[rcu_check_quiescent_state+87/128] rcu_check_quiescent_state+0x57/0x80
[rcu_process_callbacks+70/288] rcu_process_callbacks+0x46/0x120
[tasklet_action+85/112] tasklet_action+0x55/0x70
[do_softirq+91/160] do_softirq+0x5b/0xa0
[do_group_exit+117/176] do_group_exit+0x75/0xb0
[syscall_call+7/11] syscall_call+0x7/0xb
Trying to fix it up, but a reboot is needed
----8<----8<----
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(TM) XP 2600+
stepping : 0
cpu MHz : 1916.547
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow
bogomips : 3776.51
--
http://tobbe.nu/.sig
[-- Attachment #2: config.gz --]
[-- Type: application/octet-stream, Size: 6913 bytes --]
reply other threads:[~2004-01-30 10:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040130103409.GA20848@debian.as \
--to=tobbe@tobbe.nu \
--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.