Bug 592049
Summary: | FC-12 Kernel messages INFO: task * blocked for more than 120 seconds | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Muzi <muzammel.linux> | ||||
Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | low | ||||||
Version: | 12 | CC: | anton, briemers, devjoe, dougsland, fdanapfe, gansalmon, haircut, itamar, jonathan, kernel-maint, torbjorn.lindahl, vedran, warlord, Wojciech.Kicior | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i686 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2010-12-03 14:44:20 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Muzi
2010-05-13 18:30:52 UTC
Fixing version. --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers Hi Any approximate time how it will be resolve, i am facing it again today. Thanks for your reply & comments. Thanks Muzi Same problem here. It seems to occur regularly when rsync is writing to an NFS mounted filesystem: INFO: task rsync:6738 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. rsync D 0000000000000000 0 6738 6726 0x00000080 ffff8800b39519e8 0000000000000086 0000000000000000 0000000000000000 ffff8800b3951998 ffffffff810106db ffff8800b3951fd8 ffff8800b3951fd8 ffff8801061a83d8 000000000000f980 0000000000015740 ffff8801061a83d8 Call Trace: [<ffffffff810106db>] ? __switch_to+0x13e/0x22d [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffff81454c1d>] io_schedule+0x43/0x5d [<ffffffffa0d48559>] nfs_wait_bit_uninterruptible+0xe/0x12 [nfs] [<ffffffff81455170>] __wait_on_bit+0x48/0x7b [<ffffffff81455211>] out_of_line_wait_on_bit+0x6e/0x79 [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffff810748c4>] ? wake_bit_function+0x0/0x33 [<ffffffff810d6187>] ? lock_page+0x29/0x41 [<ffffffffa0d48549>] nfs_wait_on_request+0x28/0x2a [nfs] [<ffffffffa0d4ceb4>] nfs_updatepage+0x17c/0x44e [nfs] [<ffffffffa0d3f286>] nfs_write_end+0x108/0x133 [nfs] [<ffffffff810d6fed>] generic_file_buffered_write+0x175/0x28e [<ffffffff810d74c4>] __generic_file_aio_write+0x251/0x286 [<ffffffff813a3dc2>] ? __sock_recvmsg+0x71/0x7e [<ffffffff810d755c>] generic_file_aio_write+0x63/0xaf [<ffffffffa0d3fec7>] nfs_file_write+0x104/0x180 [nfs] [<ffffffff8111b388>] do_sync_write+0xe8/0x125 [<ffffffff8107488b>] ? autoremove_wake_function+0x0/0x39 [<ffffffff811ef37e>] ? selinux_file_permission+0x5c/0xb3 [<ffffffff811e571d>] ? security_file_permission+0x16/0x18 [<ffffffff8111b94c>] vfs_write+0xae/0x10b [<ffffffff8111ba69>] sys_write+0x4a/0x6e [<ffffffff81011d32>] system_call_fastpath+0x16/0x1b INFO: task kswapd0:50 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kswapd0 D 0000000000000000 0 50 2 0x00000000 ffff8801b59af750 0000000000000046 0000000000000000 ffffffff81017d69 ffff8801b59af6c0 ffffffff8107bb77 ffff8801b59affd8 ffff8801b59affd8 ffff8801b938b298 000000000000f980 0000000000015740 ffff8801b938b298 Call Trace: [<ffffffff81017d69>] ? read_tsc+0x9/0x1b [<ffffffff8107bb77>] ? timekeeping_get_ns+0x1b/0x3d [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffff81454c1d>] io_schedule+0x43/0x5d [<ffffffffa0d48559>] nfs_wait_bit_uninterruptible+0xe/0x12 [nfs] [<ffffffff81455170>] __wait_on_bit+0x48/0x7b [<ffffffff8122a4cf>] ? __lookup_tag+0xbd/0x12d [<ffffffff81455211>] out_of_line_wait_on_bit+0x6e/0x79 [<ffffffffa0d4854b>] ? nfs_wait_bit_uninterruptible+0x0/0x12 [nfs] [<ffffffff810748c4>] ? wake_bit_function+0x0/0x33 [<ffffffffa0d48549>] nfs_wait_on_request+0x28/0x2a [nfs] [<ffffffffa0d4cb4d>] nfs_sync_mapping_wait+0xf6/0x21a [nfs] [<ffffffffa0d4cd08>] nfs_wb_page+0x97/0xc7 [nfs] [<ffffffffa0d3f065>] nfs_release_page+0x4a/0x64 [nfs] [<ffffffff810d564e>] try_to_release_page+0x34/0x3d [<ffffffff810e0e5b>] shrink_page_list+0x2d8/0x457 [<ffffffff811151e6>] ? mem_cgroup_del_lru_list+0x83/0x92 [<ffffffff8111525e>] ? mem_cgroup_del_lru+0x39/0x3b [<ffffffff810e07b4>] ? isolate_pages_global+0xca/0x22a [<ffffffff8101268e>] ? common_interrupt+0xe/0x13 [<ffffffff810e139a>] shrink_inactive_list+0x3c0/0x692 [<ffffffff8123079c>] ? __bitmap_weight+0x40/0x8f [<ffffffff81226782>] ? cpumask_next_and+0x2c/0x39 [<ffffffff810dd4a2>] ? determine_dirtyable_memory+0x1a/0x2d [<ffffffff810dd52b>] ? get_dirty_limits+0x27/0x252 [<ffffffff810e19c3>] shrink_list+0xb7/0xc3 [<ffffffff810e1c85>] shrink_zone+0x2b6/0x357 [<ffffffff810e25b5>] balance_pgdat+0x3a3/0x5a0 [<ffffffff810e06ea>] ? isolate_pages_global+0x0/0x22a [<ffffffff810e28dc>] kswapd+0x12a/0x12c [<ffffffff8107488b>] ? autoremove_wake_function+0x0/0x39 [<ffffffff810e27b2>] ? kswapd+0x0/0x12c [<ffffffff8107459e>] kthread+0x7f/0x87 [<ffffffff81012d6a>] child_rip+0xa/0x20 [<ffffffff8107451f>] ? kthread+0x0/0x87 [<ffffffff81012d60>] ? child_rip+0x0/0x20 The kswapd blocks are extremely painful, as they freeze all the applications on my desktop. Even the mouse cursor won't move. I issued a 'swapoff -a' to workaround that problem. Now it is just individual applications freezing... The applications which freeze seem to be random. Console windows, firefox, thunderbird, konversation, ... Bill BTW. I see on the ubuntu list a patch kernel patch that resolved this problem for some people, but not everyone... I forgot to mention I am an running x86_64 kernel. [docbill@hartnell ~]$ uname -a Linux hartnell.local 2.6.32.11-99.fc12.x86_64 #1 SMP Mon Apr 5 19:59:38 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux *** Bug 598151 has been marked as a duplicate of this bug. *** Created attachment 427362 [details]
dmesg from last kernel crash
(In reply to comment #7) > Created an attachment (id=427362) [details] > dmesg from last kernel crash The exact same thing happens to me too.. and always when I write big files to an nfs share Im running x86_64 Fedora 13, with: 02:00.0 Ethernet controller: Atheros Communications AR8121/AR8113/AR8114 Gigabit or Fast Ethernet (rev b0) I have the proprietary nvidia driver loaded when this happens. $ uname -r 2.6.33.5-124.fc13.x86_64 dmesg of last crash attached above. I have experienced this on FC-13, also using an NFS share. x86_64 also. This was on kernel 2.6.33.6-147.fc13.x86_64 though I have since updated to 2.6.33.6-147.2.4.fc13.x86_64 Different hardware than above poster, though: 02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02) Though I have the Atheros, at the time of the lockup the wired connection via the Realtek was in use. Messages: INFO: task events/0:9 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. events/0 D ffff8800aa39d728 0 9 2 0x00000000 ffff8800ac705ca0 0000000000000046 00000000000157c0 ffffffff8100a66e ffff8800ac705cb0 ffff8800aad0da98 0000000000000000 ffff8800ac705fd8 ffff8800ac705fd8 000000000000f9b0 00000000000157c0 ffff8800ac6d6108 Call Trace: [<ffffffff8100a66e>] ? call_function_single_interrupt+0xe/0x20 [<ffffffff81064431>] ? prepare_to_wait+0x67/0x74 [<ffffffffa005cde1>] ttm_bo_wait_unreserved+0x107/0x123 [ttm] [<ffffffff810641bf>] ? autoremove_wake_function+0x0/0x34 [<ffffffffa005ce6b>] ttm_bo_reserve_locked+0x6e/0xd7 [ttm] [<ffffffffa005d810>] ttm_bo_cleanup_refs+0xd6/0x224 [ttm] [<ffffffffa005c9bd>] ? ttm_bo_release_list+0x0/0xc7 [ttm] [<ffffffffa005d9ee>] ttm_bo_delayed_delete+0x90/0xfb [ttm] [<ffffffffa005da73>] ttm_bo_delayed_workqueue+0x1a/0x30 [ttm] [<ffffffff810606e9>] worker_thread+0x1a4/0x232 [<ffffffffa005da59>] ? ttm_bo_delayed_workqueue+0x0/0x30 [ttm] [<ffffffff810641bf>] ? autoremove_wake_function+0x0/0x34 [<ffffffff81060545>] ? worker_thread+0x0/0x232 [<ffffffff81063d6f>] kthread+0x7a/0x82 [<ffffffff8100a924>] kernel_thread_helper+0x4/0x10 [<ffffffff81063cf5>] ? kthread+0x0/0x82 [<ffffffff8100a920>] ? kernel_thread_helper+0x0/0x10 INFO: task gnome-terminal:2522 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. gnome-termina D ffff880001e957c0 0 2522 1 0x00000080 ffff88008abc3918 0000000000000082 ffff8800abc46800 ffff88008abc2000 ffff8800919ab590 ffff88008abc3fd8 000000008abc38c8 ffff88008abc3fd8 ffff88008abc3fd8 000000000000f9b0 00000000000157c0 ffff8800919ab268 Call Trace: [<ffffffff8103a63d>] ? update_curr+0xbf/0x168 [<ffffffff81428e01>] schedule_timeout+0x31/0xde [<ffffffff810086ff>] ? __switch_to+0x215/0x227 [<ffffffff81428c93>] wait_for_common+0xd1/0x12c [<ffffffff81045f1e>] ? default_wake_function+0x0/0xf [<ffffffff81428d78>] wait_for_completion+0x18/0x1a [<ffffffff81060e92>] flush_work+0x8c/0xa0 [<ffffffff81060a27>] ? wq_barrier_func+0x0/0xf [<ffffffff81061038>] flush_delayed_work+0x50/0x54 [<ffffffff81284d15>] tty_flush_to_ldisc+0x10/0x12 [<ffffffff81280976>] n_tty_poll+0x65/0x14e [<ffffffff8127cdab>] tty_poll+0x5e/0x78 [<ffffffff8110f4ba>] do_sys_poll+0x241/0x3e2 [<ffffffff8110f107>] ? __pollwait+0x0/0xc7 [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff811c6ea3>] ? selinux_file_permission+0xa2/0xae [<ffffffff811bda9f>] ? security_file_permission+0x11/0x13 [<ffffffff8110f7ef>] sys_poll+0x50/0xbb [<ffffffff81009b02>] system_call_fastpath+0x16/0x1b ... a few more of these, eventually Xorg is blocked and everything locks up: INFO: task Xorg:1811 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Xorg D 0000000000000000 0 1811 1808 0x00400084 ffff8800aad0d7e8 0000000000000082 0000000000000000 0000000200000000 ffff8800aad0d8f0 0000000000000008 00000000000157c0 ffff8800aad0dfd8 ffff8800aad0dfd8 000000000000f9b0 00000000000157c0 ffff8800aa8703c8 Call Trace: [<ffffffff81428e01>] schedule_timeout+0x31/0xde [<ffffffff810086ff>] ? __switch_to+0x215/0x227 [<ffffffff81428c93>] wait_for_common+0xd1/0x12c [<ffffffff81045f1e>] ? default_wake_function+0x0/0xf [<ffffffff81428d78>] wait_for_completion+0x18/0x1a [<ffffffff81060e92>] flush_work+0x8c/0xa0 [<ffffffff81060a27>] ? wq_barrier_func+0x0/0xf [<ffffffff81061038>] flush_delayed_work+0x50/0x54 [<ffffffff81284d15>] tty_flush_to_ldisc+0x10/0x12 [<ffffffff81280976>] n_tty_poll+0x65/0x14e [<ffffffff8127cdab>] tty_poll+0x5e/0x78 [<ffffffff8110eef8>] do_select+0x335/0x544 [<ffffffff8110f107>] ? __pollwait+0x0/0xc7 [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110f1ce>] ? pollwake+0x0/0x4f [<ffffffff8110fa16>] core_sys_select+0x16f/0x205 [<ffffffff8100ff25>] ? read_tsc+0x9/0x1b [<ffffffff8106bbd4>] ? ktime_get_ts+0xad/0xba [<ffffffff8110fce6>] sys_select+0x91/0xbb [<ffffffff81009b02>] system_call_fastpath+0x16/0x1b This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. Hi, Many people have reported this in Fedora 13, too, which is NOT EOLed. See Comment #8 and Comment #9 I'm seeing this as well on Fedora 13, running 2.6.34.8-68.fc13.x86_64 INFO: task kjournald:1366 blocked for more than 120 seconds. "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kjournald D 0000000000000000 0 1366 2 0x00000000 ffff88043c589c00 0000000000000046 ffff880002017fa0 0000000000000020 ffff88043c589fd8 ffff88043d342ee0 00000000000153c0 ffff88043c589fd8 00000000000153c0 00000000000153c0 00000000000153c0 00000000000153c0 Call Trace: [<ffffffff8112f767>] ? sync_buffer+0x0/0x44 [<ffffffff8144be26>] io_schedule+0x73/0xb5 [<ffffffff8112f7a7>] sync_buffer+0x40/0x44 [<ffffffff8144c3b7>] __wait_on_bit+0x48/0x7b [<ffffffff8144c458>] out_of_line_wait_on_bit+0x6e/0x79 [<ffffffff8112f767>] ? sync_buffer+0x0/0x44 [<ffffffff81066298>] ? wake_bit_function+0x0/0x33 [<ffffffff8112f6ca>] __wait_on_buffer+0x24/0x26 [<ffffffff811ab4ab>] wait_on_buffer+0x3d/0x41 [<ffffffff811abafe>] journal_commit_transaction+0x57c/0xfe2 [<ffffffff810597f7>] ? lock_timer_base+0x2c/0x52 [<ffffffff81059898>] ? try_to_del_timer_sync+0x7b/0x89 [<ffffffff811af175>] kjournald+0xe8/0x225 [<ffffffff8106625f>] ? autoremove_wake_function+0x0/0x39 [<ffffffff811af08d>] ? kjournald+0x0/0x225 [<ffffffff81065de5>] kthread+0x7f/0x87 [<ffffffff8100aa64>] kernel_thread_helper+0x4/0x10 [<ffffffff81065d66>] ? kthread+0x0/0x87 [<ffffffff8100aa60>] ? kernel_thread_helper+0x0/0x10 Any chance to reopen this bug and update to FC13? |