[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-11-27 Thread spazy
i have to confirm this problem

Kernel  distribution version
Nov 27 08:34:44 core kernel: [0.00] Linux version 2.6.31-22-server 
(bui...@allspice) (gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) ) #68-Ubuntu SMP 
Tue Oct 26 16:50:02 UTC 2010 (Ubuntu 2.6.31-22.68-serv
er)


kern.log


Nov 27 04:41:54 core kernel: [1242602.033782] INFO: task kjournald2:407 blocked 
for more than 120 seconds.
Nov 27 04:41:54 core kernel: [1242602.033799] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Nov 27 04:41:54 core kernel: [1242602.033813] kjournald2D   
   0   407  2 0x
Nov 27 04:41:54 core kernel: [1242602.033820]  8801205fbad0 
0046 0002 00015880
Nov 27 04:41:54 core kernel: [1242602.033827]  8801210b47c0 
00015880 00015880 00015880
Nov 27 04:41:54 core kernel: [1242602.033832]  00015880 
8801210b47c0 00015880 00015880
Nov 27 04:41:54 core kernel: [1242602.033839] Call Trace:
Nov 27 04:41:54 core kernel: [1242602.033857]  [810da1e0] ? 
sync_page+0x0/0x50
Nov 27 04:41:54 core kernel: [1242602.033864]  [81529cd8] 
io_schedule+0x28/0x40
Nov 27 04:41:54 core kernel: [1242602.033868]  [810da21d] 
sync_page+0x3d/0x50
Nov 27 04:41:54 core kernel: [1242602.033872]  [8152a1f7] 
__wait_on_bit+0x57/0x80
Nov 27 04:41:54 core kernel: [1242602.033876]  [810da38e] 
wait_on_page_bit+0x6e/0x80
Nov 27 04:41:54 core kernel: [1242602.033882]  [810785b0] ? 
wake_bit_function+0x0/0x40
Nov 27 04:41:54 core kernel: [1242602.033888]  [810e4640] ? 
pagevec_lookup_tag+0x20/0x30
Nov 27 04:41:54 core kernel: [1242602.033893]  [810da835] 
wait_on_page_writeback_range+0xf5/0x190
Nov 27 04:41:54 core kernel: [1242602.033899]  [811ee9a9] ? 
jbd2_journal_file_buffer+0x59/0x80
Nov 27 04:41:54 core kernel: [1242602.033903]  [810da8f7] 
filemap_fdatawait+0x27/0x30
Nov 27 04:41:54 core kernel: [1242602.033907]  [811ef896] 
journal_finish_inode_data_buffers+0x56/0x150
Nov 27 04:41:54 core kernel: [1242602.033911]  [811f03b6] 
jbd2_journal_commit_transaction+0x6d6/0x1100
Nov 27 04:41:54 core kernel: [1242602.033917]  [811f5e33] 
kjournald2+0x103/0x270
Nov 27 04:41:54 core kernel: [1242602.033921]  [81078570] ? 
autoremove_wake_function+0x0/0x40
Nov 27 04:41:54 core kernel: [1242602.033926]  [811f5d30] ? 
kjournald2+0x0/0x270
Nov 27 04:41:54 core kernel: [1242602.033929]  [81078186] 
kthread+0xa6/0xb0
Nov 27 04:41:54 core kernel: [1242602.033935]  [8101312a] 
child_rip+0xa/0x20
Nov 27 04:41:54 core kernel: [1242602.033939]  [810780e0] ? 
kthread+0x0/0xb0
Nov 27 04:41:54 core kernel: [1242602.033942]  [81013120] ? 
child_rip+0x0/0x20
Nov 27 04:41:54 core kernel: [1242602.033960] INFO: task bash:13216 blocked for 
more than 120 seconds.
Nov 27 04:41:54 core kernel: [1242602.033970] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Nov 27 04:41:54 core kernel: [1242602.034014] bash  D   
   0 13216  13215 0x
Nov 27 04:41:54 core kernel: [1242602.034019]  88009853d818 
0086 88009853d7a8 00015880
Nov 27 04:41:54 core kernel: [1242602.034025]  88008fa8de70 
00015880 00015880 00015880
Nov 27 04:41:54 core kernel: [1242602.034030]  00015880 
88008fa8de70 00015880 00015880
Nov 27 04:41:54 core kernel: [1242602.034035] Call Trace:
Nov 27 04:41:54 core kernel: [1242602.034040]  [81529cd8] 
io_schedule+0x28/0x40
Nov 27 04:41:54 core kernel: [1242602.034045]  [812664c7] 
get_request_wait+0xc7/0x1a0
Nov 27 04:41:54 core kernel: [1242602.034049]  [81078570] ? 
autoremove_wake_function+0x0/0x40
Nov 27 04:41:54 core kernel: [1242602.034054]  [8125b33b] ? 
elv_merge+0x1cb/0x200
Nov 27 04:41:54 core kernel: [1242602.034058]  [81266633] 
__make_request+0x93/0x440
Nov 27 04:41:54 core kernel: [1242602.034062]  [81114aba] ? 
__slab_alloc+0x8a/0x2d0
Nov 27 04:41:54 core kernel: [1242602.034066]  [8126515b] 
generic_make_request+0x19b/0x4c0
Nov 27 04:41:54 core kernel: [1242602.034070]  [810dc6f0] ? 
mempool_alloc_slab+0x10/0x20
Nov 27 04:41:54 core kernel: [1242602.034076]  [81144f64] ? 
alloc_buffer_head+0x44/0x50
Nov 27 04:41:54 core kernel: [1242602.034080]  [812654fd] 
submit_bio+0x7d/0x110
Nov 27 04:41:54 core kernel: [1242602.034084]  [81145452] 
submit_bh+0xf2/0x130
Nov 27 04:41:54 core kernel: [1242602.034088]  [81146e63] 
ll_rw_block+0x123/0x130
Nov 27 04:41:54 core kernel: [1242602.034092]  [81146e99] 
__breadahead+0x29/0x40
Nov 27 04:41:54 core kernel: [1242602.034097]  [811b3a6e] 
__ext4_get_inode_loc+0x32e/0x3b0
Nov 27 04:41:54 core kernel: [1242602.034101]  [811b3b6e] 
ext4_iget+0x7e/0x7f0
Nov 27 04:41:54 core 

[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-10-04 Thread Thag
This is still happening in 10.04.1, both with the default Ubuntu server
kernel and with the ppa kernel:

Linux topaz 2.6.35-22-server #33~lucid1-Ubuntu SMP Sat Sep 18 13:29:53
UTC 2010 x86_64 GNU/Linux


Oct  4 09:32:44 topaz kernel: [405000.890225] INFO: task scp:27169 blocked for 
more than 120 seconds.
Oct  4 09:32:44 topaz kernel: [405000.890231] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Oct  4 09:32:44 topaz kernel: [405000.890234] scp   D 00010267dc02  
   0 27169  29503 0x0004
Oct  4 09:32:44 topaz kernel: [405000.890241]  88012f8b9c08 
0086 8802 00015980
Oct  4 09:32:44 topaz kernel: [405000.890248]  88012f8b9fd8 
00015980 88012f8b9fd8 88011cdb5b80
Oct  4 09:32:44 topaz kernel: [405000.890254]  00015980 
00015980 88012f8b9fd8 00015980
Oct  4 09:32:44 topaz kernel: [405000.890259] Call Trace:
Oct  4 09:32:44 topaz kernel: [405000.890272]  [81100b60] ? 
sync_page+0x0/0x50
Oct  4 09:32:44 topaz kernel: [405000.890279]  [8159ca93] 
io_schedule+0x73/0xc0
Oct  4 09:32:44 topaz kernel: [405000.890283]  [81100b9d] 
sync_page+0x3d/0x50
Oct  4 09:32:44 topaz kernel: [405000.890287]  [8159d10f] 
__wait_on_bit+0x5f/0x90
Oct  4 09:32:44 topaz kernel: [405000.890292]  [81100d53] 
wait_on_page_bit+0x73/0x80
Oct  4 09:32:44 topaz kernel: [405000.890297]  [8107f120] ? 
wake_bit_function+0x0/0x40
Oct  4 09:32:44 topaz kernel: [405000.890303]  [8110b675] ? 
pagevec_lookup_tag+0x25/0x40
Oct  4 09:32:44 topaz kernel: [405000.890307]  [8110121d] 
filemap_fdatawait_range+0x10d/0x1a0
Oct  4 09:32:44 topaz kernel: [405000.890312]  [811012db] 
filemap_fdatawait+0x2b/0x30
Oct  4 09:32:44 topaz kernel: [405000.890316]  [811015e4] 
filemap_write_and_wait+0x44/0x50
Oct  4 09:32:44 topaz kernel: [405000.890334]  [a01abf3c] 
nfs_setattr+0x14c/0x160 [nfs]
Oct  4 09:32:44 topaz kernel: [405000.890341]  [8116bebb] 
notify_change+0x16b/0x310
Oct  4 09:32:44 topaz kernel: [405000.890347]  [8135cb9e] ? 
tty_ldisc_deref+0xe/0x10
Oct  4 09:32:44 topaz kernel: [405000.890352]  [81152364] 
do_truncate+0x64/0xa0
Oct  4 09:32:44 topaz kernel: [405000.890356]  [811525fb] 
T.782+0xeb/0x110
Oct  4 09:32:44 topaz kernel: [405000.890360]  [8115262e] 
sys_ftruncate+0xe/0x10
Oct  4 09:32:44 topaz kernel: [405000.890366]  [8100a0f2] 
system_call_fastpath+0x16/0x1b
Oct  4 09:32:44 topaz kernel: [405000.890371] INFO: task flush-0:26:27661 
blocked for more than 120 seconds.
Oct  4 09:32:44 topaz kernel: [405000.890373] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
Oct  4 09:32:44 topaz kernel: [405000.890376] flush-0:26D 000102694b5b  
   0 27661  2 0x
Oct  4 09:32:44 topaz kernel: [405000.890383]  8801324fda40 
0046  00015980
Oct  4 09:32:44 topaz kernel: [405000.890388]  8801324fdfd8 
00015980 8801324fdfd8 88015ab28000
Oct  4 09:32:44 topaz kernel: [405000.890394]  00015980 
00015980 8801324fdfd8 00015980
Oct  4 09:32:44 topaz kernel: [405000.890399] Call Trace:
Oct  4 09:32:44 topaz kernel: [405000.890404]  [81100b60] ? 
sync_page+0x0/0x50
Oct  4 09:32:44 topaz kernel: [405000.890410]  [8159ca93] 
io_schedule+0x73/0xc0
Oct  4 09:32:44 topaz kernel: [405000.890415]  [81100b9d] 
sync_page+0x3d/0x50
Oct  4 09:32:44 topaz kernel: [405000.890420]  [8159d10f] 
__wait_on_bit+0x5f/0x90
Oct  4 09:32:44 topaz kernel: [405000.890423]  [81100d53] 
wait_on_page_bit+0x73/0x80
Oct  4 09:32:44 topaz kernel: [405000.890428]  [8107f120] ? 
wake_bit_function+0x0/0x40
Oct  4 09:32:44 topaz kernel: [405000.890432]  [8110b675] ? 
pagevec_lookup_tag+0x25/0x40
Oct  4 09:32:44 topaz kernel: [405000.890436]  [8110121d] 
filemap_fdatawait_range+0x10d/0x1a0
Oct  4 09:32:44 topaz kernel: [405000.890441]  [811012db] 
filemap_fdatawait+0x2b/0x30
Oct  4 09:32:44 topaz kernel: [405000.890446]  [81175648] 
writeback_single_inode+0x2e8/0x3f0
Oct  4 09:32:44 topaz kernel: [405000.890451]  [81175ba5] 
writeback_sb_inodes+0x195/0x280
Oct  4 09:32:44 topaz kernel: [405000.890455]  [811765fc] 
wb_writeback+0x12c/0x2b0
Oct  4 09:32:44 topaz kernel: [405000.890461]  [8106fefc] ? 
lock_timer_base+0x3c/0x70
Oct  4 09:32:44 topaz kernel: [405000.890465]  [810709f2] ? 
del_timer_sync+0x22/0x30
Oct  4 09:32:44 topaz kernel: [405000.890470]  [81176829] 
wb_do_writeback+0xa9/0x190
Oct  4 09:32:44 topaz kernel: [405000.890474]  [81070010] ? 
process_timeout+0x0/0x10
Oct  4 09:32:44 topaz kernel: [405000.890479]  [81176963] 
bdi_writeback_task+0x53/0x160
Oct  4 09:32:44 topaz kernel: [405000.890483]  [8107efa7] ? 
bit_waitqueue+0x17/0xd0
Oct  4 09:32:44 topaz 

[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-06-24 Thread Douglas Bagnall
For the information of this bug's followers, installing cgroup-bin caused me 
lock-ups and
INFO: task * blocked for more than 120 seconds messages.

https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/598335

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-06-15 Thread Manuel Iglesias Alonso
Please check this bug:
https://bugzilla.kernel.org/show_bug.cgi?id=16219

I have same problems described here and I have found that in my case it
is a kernel bug related to GUID partition tables

I am still writing the bug report.


** Bug watch added: Linux Kernel Bug Tracker #16219
   http://bugzilla.kernel.org/show_bug.cgi?id=16219

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-25 Thread tom
Since there are no additional comments in bug #494476, has anyone launched a 
new report?
As Darren pointed out above, it might be useful to have a template to look at 
when submitting related bugs. Searching for bugs where tasks are blocked for 
more than 120 seconds gives heaps of results but it's difficult to tell if 
they're related or not - some are even tagged as fixed.

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-20 Thread Jeremy Foshee
tom,
Please file a new bug regardless. The Ubuntu Kernel Team is moving to a 
model whereby all affected reporters open new bug so that specific data can be 
logged for each of them.

I want all affected reporters to open new bug reports for this issue.

Thanks!

~JFo

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


Re: [Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-20 Thread Sesshomurai
Hi,
 I think this makes sense. Even though it may result in a common fix for all.

But one thing that might help, is maybe provide a set of steps for how to
file information about this sort of bug. Some of us aren't kernel experts,
but if we can gather the information in a common way when we open a new
bug, it could help you.

Darren

 tom,
 Please file a new bug regardless. The Ubuntu Kernel Team is moving to
 a model whereby all affected reporters open new bug so that specific
 data can be logged for each of them.

 I want all affected reporters to open new bug reports for this issue.

 Thanks!

 ~JFo

 --
 Idle-priority scheduling bug blocks tasks
 https://bugs.launchpad.net/bugs/276476
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in “linux” package in Ubuntu: Fix Released

 Bug description:
 INFO: task blocked for more than 120 seconds is a diagnostic message for
 when a process that wants to run is blocked from running for a long time.

 This bug report refers to a specific problem with idle-priority scheduling
 that has now been fixed. If you are up to date and are still getting the
 task blocked message, it is a different bug, so please file a new bug
 report.

 To unsubscribe from this bug, go to:
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/276476/+subscribe


-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-19 Thread Brian Rogers
** Summary changed:

- INFO: task blocked for more than 120 seconds causes system freeze
+ Idle-priority scheduling bug blocks tasks

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-19 Thread Brian Rogers
** Description changed:

- The following commits can be cleanly cherry-picked into 2.6.28 to fix this 
bug:
- cce7ade803699463ecc62a065ca522004f7ccb3d
- 6bc912b71b6f33b041cfde93ca3f019cbaa852bc
+ INFO: task blocked for more than 120 seconds is a diagnostic message
+ for when a process that wants to run is blocked from running for a long
+ time.
  
- Original description:
- Npviewer segfaults when visiting a website on Firefox with flash content. 
After that thunderbird, firefox stop responding and they have to be force 
quitted. Their processes (thunderbird.bin and firefox) can't be killed with 
kill -9 or killall. After a while these messages turn up on terminal: 
- 
- (taken from kern.log)
- Sep 30 22:37:19 ubuntu kernel: [19808.392380] INFO: task 
thunderbird-bin:28288 blocked for more than 120 seconds.
- Sep 30 22:37:19 ubuntu kernel: [19808.392418] echo 0  
/proc/sys/kernel/hung_task_timeout_secs disables this message.
- 
- I have to reboot using Sysreq + reisub.
- 
- This happens at least once a day on fully updated (as of 30.09.2008)
- Intrebid Ibex  on x86_64.
- 
- uname -a: Linux ubuntu 2.6.27-4-generic #1 SMP Wed Sep 24 01:29:06 UTC
- 2008 x86_64 GNU/Linux
- 
- Attached kern.log with relevant bits of two separate occasions.
+ This bug report refers to a specific problem with idle-priority
+ scheduling that has now been fixed. If you are up to date and are still
+ getting the task blocked message, it is a different bug, so please
+ file a new bug report.

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-19 Thread tom
So you're saying people who are still affected by the task blocked for
more than 120 seconds bug should all file their own report (like Alvin
suggested in #50)? Or can we just all add to bug 494476?

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 276476] Re: Idle-priority scheduling bug blocks tasks

2010-05-19 Thread Brian Rogers
If it appears to have the same cause (in this case, ext4 access or
perhaps disk access in general), then follow that bug. If it appears to
be triggered by something else, file a new bug.

If in doubt, file a new bug. It can always be marked as a duplicate
later if after investigation it's revealed to be the same issue.

-- 
Idle-priority scheduling bug blocks tasks
https://bugs.launchpad.net/bugs/276476
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs