From: "Peter B. West" <pbw@pbw.id.au>
To: linux-hotplug@vger.kernel.org
Subject: Bad page state at free_hot_cold_page
Date: Sat, 20 Aug 2005 06:27:27 +0000 [thread overview]
Message-ID: <4306CD4F.4020101@pbw.id.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
I've noticed this recently, but it has gone away on reboot. This one
stayed. udev-068.
Anything else you need?
Peter
[-- Attachment #2: badpagestate --]
[-- Type: text/plain, Size: 3463 bytes --]
Linux version 2.6.12-gentoo-r9_no_sound (root@jezebel) (gcc version 3.3.5-20050130 (Gentoo Linux 3.3.5.20050130-r1, ssp-3.3.5.20050130-1, pie-8.7.7.1)) #2 SMP Wed Aug 17 16:07:56 BST 2005
....
Bad page state at free_hot_cold_page (in process 'udevd', page c16fb4c0)
flags:0x20001004 mapping:00000000 mapcount:0 count:0
Backtrace:
[<c0146565>] bad_page+0x75/0xb0
[<c0146d00>] free_hot_cold_page+0x70/0x140
[<c014759c>] __pagevec_free+0x1c/0x30
[<c014c620>] release_pages+0x60/0x140
[<c0143132>] __generic_file_aio_read+0x202/0x240
[<c0142e40>] file_read_actor+0x0/0xf0
[<c014c897>] __pagevec_lru_add+0xc7/0xe0
[<c014c4f8>] lru_add_drain+0x78/0x80
[<c0155ba0>] exit_mmap+0x20/0x190
[<c02789d9>] secure_ip_id+0x49/0x50
[<c011bb28>] mmput+0x38/0xa0
[<c016cd11>] exec_mmap+0xf1/0x200
[<c016cfca>] flush_old_exec+0xfa/0x7d0
[<c016190f>] vfs_read+0x11f/0x180
[<c016cc0e>] kernel_read+0x4e/0x60
[<c018f3e1>] load_elf_binary+0x2e1/0xc60
[<c014f77f>] kmap_high+0x12f/0x1b0
[<c016c701>] copy_strings+0x1d1/0x220
[<c018f100>] load_elf_binary+0x0/0xc60
[<c016da3e>] search_binary_handler+0x16e/0x2b0
[<c016dd0f>] do_execve+0x18f/0x230
[<c0101e26>] sys_execve+0x46/0xa0
[<c01033b5>] syscall_call+0x7/0xb
Trying to fix it up, but a reboot is needed
Bad page state at free_hot_cold_page (in process 'udev_run_hotplu', page c16ff620)
flags:0x20001004 mapping:00000000 mapcount:0 count:0
Backtrace:
[<c0146565>] bad_page+0x75/0xb0
[<c0146d00>] free_hot_cold_page+0x70/0x140
[<c024228a>] dtSearch+0x30a/0x4c0
[<c023064d>] jfs_lookup+0x16d/0x1f0
[<c011611c>] do_page_fault+0x19c/0x5d5
[<c017abdd>] d_alloc+0x13d/0x1a0
[<c016feb1>] real_lookup+0xd1/0x100
[<c017020d>] do_lookup+0x9d/0xb0
[<c0170927>] __link_path_walk+0x707/0xdb0
[<c0142b5e>] do_generic_mapping_read+0x35e/0x640
[<c0171019>] link_path_walk+0x49/0xe0
[<c0171378>] path_lookup+0x98/0x1a0
[<c016caf0>] open_exec+0x30/0x100
[<c016c701>] copy_strings+0x1d1/0x220
[<c018e59d>] load_script+0x1dd/0x250
[<c014f77f>] kmap_high+0x12f/0x1b0
[<c014ffa9>] page_address+0xa9/0xc0
[<c014ffa9>] page_address+0xa9/0xc0
[<c016c701>] copy_strings+0x1d1/0x220
[<c018e3c0>] load_script+0x0/0x250
[<c016da3e>] search_binary_handler+0x16e/0x2b0
[<c016dd0f>] do_execve+0x18f/0x230
[<c0101e26>] sys_execve+0x46/0xa0
[<c01033b5>] syscall_call+0x7/0xb
Trying to fix it up, but a reboot is needed
Bad page state at free_hot_cold_page (in process 'udev', page c16f0cc0)
flags:0x20001004 mapping:00000000 mapcount:0 count:0
Backtrace:
[<c0146565>] bad_page+0x75/0xb0
[<c0146d00>] free_hot_cold_page+0x70/0x140
[<c024228a>] dtSearch+0x30a/0x4c0
[<c023064d>] jfs_lookup+0x16d/0x1f0
[<c014ee59>] vma_prio_tree_insert+0x29/0x60
[<c0153e6d>] vma_link+0xbd/0xf0
[<c0146910>] prep_new_page+0x60/0x70
[<c0146f06>] buffered_rmqueue+0x116/0x230
[<c017abdd>] d_alloc+0x13d/0x1a0
[<c016feb1>] real_lookup+0xd1/0x100
[<c017020d>] do_lookup+0x9d/0xb0
[<c0170927>] __link_path_walk+0x707/0xdb0
[<c0171019>] link_path_walk+0x49/0xe0
[<c026a0d0>] __copy_to_user_ll+0x70/0x80
[<c026a1a2>] copy_to_user+0x42/0x60
[<c012dc2b>] sys_newuname+0x3b/0x70
[<c0171378>] path_lookup+0x98/0x1a0
[<c0171643>] __user_walk+0x33/0x60
[<c0160325>] sys_access+0x85/0x150
[<c016db2f>] search_binary_handler+0x25f/0x2b0
[<c026a0d0>] __copy_to_user_ll+0x70/0x80
[<c026a1a2>] copy_to_user+0x42/0x60
[<c012dc2b>] sys_newuname+0x3b/0x70
[<c01033b5>] syscall_call+0x7/0xb
Trying to fix it up, but a reboot is needed
reply other threads:[~2005-08-20 6:27 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=4306CD4F.4020101@pbw.id.au \
--to=pbw@pbw.id.au \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).