[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#695351: marked as done (task stress: blocked for more than 120 seconds)

Your message dated Sat, 24 Apr 2021 07:22:13 -0700 (PDT)
with message-id <60842995.1c69fb81.bd91f.3e5a@mx.google.com>
and subject line Closing this bug (BTS maintenance for src:linux bugs)
has caused the Debian Bug report #695351,
regarding task stress: blocked for more than 120 seconds
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
695351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695351
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-3.2.0-0.bpo.4-amd64
Version: 3.2.32-1~bpo60+1

Hello,

Hardware: Dell R320, 2x300GB SAS disk RAID 1(01:00.0 RAID bus
controller: LSI Logic / Symbios Logic MegaRAID SAS 9240 (rev 03)
Both Dom0 and DomU runs Debian Squeeze with linux-image-3.2.0-0.bpo.4-amd64

Although errors occurs, domU seems to work OK.

domU - 8 cores, 8GB RAM

To reproduce run both:
stress --cpu 8 --io 4 --vm 2 --vm-bytes 128M -d 5
dbench 150

Errors in kern.log:

Dec  7 14:14:26 web1 kernel: [    1.646137] EXT4-fs (xvda2):
re-mounted. Opts: (null)
Dec  7 14:14:26 web1 kernel: [    1.705457] EXT4-fs (xvda2):
re-mounted. Opts: errors=remount-ro
Dec  7 14:14:26 web1 kernel: [    2.399820] sshd (591):
/proc/591/oom_adj is deprecated, please use /proc/591/oom_score_adj
instead.
Dec  7 14:14:36 web1 kernel: [   12.484101] eth0: no IPv6 routers present
Dec  7 14:17:08 web1 kernel: [  164.555649] sched: RT throttling activated
Dec  7 14:18:24 web1 kernel: [  240.180036] INFO: task stress:626
blocked for more than 120 seconds.
Dec  7 14:18:24 web1 kernel: [  240.180048] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec  7 14:18:24 web1 kernel: [  240.180057] stress          D
ffff8801f3ee3850     0   626    624 0x00000000
Dec  7 14:18:24 web1 kernel: [  240.180067]  ffff8801f3ee3850
0000000000000282 ffff8801f53c9e50 ffff8801f5c3c8b0
Dec  7 14:18:24 web1 kernel: [  240.180079]  0000000000013740
ffff8801f53c9fd8 ffff8801f53c9fd8 0000000000013740
Dec  7 14:18:24 web1 kernel: [  240.180091]  ffff8801f3ee3850
ffff8801f53c8010 000000000000000d ffffffff8103d330
Dec  7 14:18:24 web1 kernel: [  240.180102] Call Trace:
Dec  7 14:18:24 web1 kernel: [  240.180114]  [<ffffffff8103d330>] ?
select_task_rq_fair+0x55f/0x820
Dec  7 14:18:24 web1 kernel: [  240.180122]  [<ffffffff81366bd9>] ?
schedule_timeout+0x2d/0xd7
Dec  7 14:18:24 web1 kernel: [  240.180133]  [<ffffffff8122fcbd>] ?
HYPERVISOR_event_channel_op+0x11/0x42
Dec  7 14:18:24 web1 kernel: [  240.180141]  [<ffffffff810139d4>] ?
sched_clock+0x5/0x8
Dec  7 14:18:24 web1 kernel: [  240.180148]  [<ffffffff8122feda>] ?
info_for_irq+0x9/0x1a
Dec  7 14:18:24 web1 kernel: [  240.180156]  [<ffffffff8136681f>] ?
wait_for_common+0xd1/0x14e
Dec  7 14:18:24 web1 kernel: [  240.180164]  [<ffffffff81367b65>] ?
_raw_spin_unlock_irqrestore+0x10/0x11
Dec  7 14:18:24 web1 kernel: [  240.180172]  [<ffffffff8104602d>] ?
try_to_wake_up+0x191/0x191
Dec  7 14:18:24 web1 kernel: [  240.180182]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180189]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180196]  [<ffffffff8112605b>] ?
sync_inodes_sb+0x93/0x16b
Dec  7 14:18:24 web1 kernel: [  240.180204]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180211]  [<ffffffff81128f76>] ?
__sync_filesystem+0x44/0x79
Dec  7 14:18:24 web1 kernel: [  240.180220]  [<ffffffff81108408>] ?
iterate_supers+0x5e/0xab
Dec  7 14:18:24 web1 kernel: [  240.180227]  [<ffffffff81129003>] ?
sys_sync+0x44/0x58
Dec  7 14:18:24 web1 kernel: [  240.180235]  [<ffffffff8136d192>] ?
system_call_fastpath+0x16/0x1b
Dec  7 14:18:24 web1 kernel: [  240.180244] INFO: task stress:637
blocked for more than 120 seconds.
Dec  7 14:18:24 web1 kernel: [  240.180250] "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dec  7 14:18:24 web1 kernel: [  240.180258] stress          D
ffff8801f41f8870     0   637    624 0x00000000
Dec  7 14:18:24 web1 kernel: [  240.180267]  ffff8801f41f8870
0000000000000282 ffff8801f4a61e50 ffff8801f6c9c7b0
Dec  7 14:18:24 web1 kernel: [  240.180278]  0000000000013740
ffff8801f4a61fd8 ffff8801f4a61fd8 0000000000013740
Dec  7 14:18:24 web1 kernel: [  240.180289]  ffff8801f41f8870
ffff8801f4a60010 000000000000000d 0000000000000000
Dec  7 14:18:24 web1 kernel: [  240.180300] Call Trace:
Dec  7 14:18:24 web1 kernel: [  240.180305]  [<ffffffff81366bd9>] ?
schedule_timeout+0x2d/0xd7
Dec  7 14:18:24 web1 kernel: [  240.180313]  [<ffffffff810bd7a8>] ?
filemap_fdatawait_range+0x10b/0x150
Dec  7 14:18:24 web1 kernel: [  240.180321]  [<ffffffff8136681f>] ?
wait_for_common+0xd1/0x14e
Dec  7 14:18:24 web1 kernel: [  240.180329]  [<ffffffff81367b65>] ?
_raw_spin_unlock_irqrestore+0x10/0x11
Dec  7 14:18:24 web1 kernel: [  240.180336]  [<ffffffff8104602d>] ?
try_to_wake_up+0x191/0x191
Dec  7 14:18:24 web1 kernel: [  240.180343]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180351]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180358]  [<ffffffff8112605b>] ?
sync_inodes_sb+0x93/0x16b
Dec  7 14:18:24 web1 kernel: [  240.180365]  [<ffffffff81128fab>] ?
__sync_filesystem+0x79/0x79
Dec  7 14:18:24 web1 kernel: [  240.180373]  [<ffffffff81128f76>] ?
__sync_filesystem+0x44/0x79
Dec  7 14:18:24 web1 kernel: [  240.180380]  [<ffffffff81108408>] ?
iterate_supers+0x5e/0xab
Dec  7 14:18:24 web1 kernel: [  240.180387]  [<ffffffff81129003>] ?
sys_sync+0x44/0x58
Dec  7 14:18:24 web1 kernel: [  240.180395]  [<ffffffff8136d192>] ?
system_call_fastpath+0x16/0x1b

--- End Message ---
--- Begin Message --- 
Hi

This bug was filed for a very old kernel or the bug is old itself
without resolution.

If you can reproduce it with

- the current version in unstable/testing
- the latest kernel from backports

please reopen the bug, see https://www.debian.org/Bugs/server-control
for details.

Regards,
Salvatore

--- End Message ---
Reply to: