Bug 605207 - INFO: task mysqld:* blocked for more than 120 seconds.
Summary: INFO: task mysqld:* blocked for more than 120 seconds.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Red Hat Kernel Manager
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 12:28 UTC by Ahmed Medhat
Modified: 2023-09-14 01:21 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-02 13:16:30 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ahmed Medhat 2010-06-17 12:28:52 UTC
Description of problem:
On a Xen VM running only as a DB server, examining the messages log, the following appeared.

Jun 17 05:01:02 hostname kernel: INFO: task mysqld:24980 blocked for more than 120 seconds.
Jun 17 05:01:02 hostname kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 17 05:01:02 hostname kernel: mysqld        D 0000fefc778b5d89     0 24980   1923         24981 24979 (NOTLB)
Jun 17 05:01:02 hostname kernel:  ffff88013adfbd88  0000000000000282  ffff88013adfbd98  ffffffff80262dd3 
Jun 17 05:01:02 hostname kernel:  0000000000000008  ffff8801ab3b80c0  ffffffff804f4b00  00000000000006cb 
Jun 17 05:01:02 hostname kernel:  ffff8801ab3b82a8  0000000000004c17 
Jun 17 05:01:02 hostname kernel: Call Trace:
Jun 17 05:01:02 hostname kernel:  [<ffffffff80262dd3>] thread_return+0x6c/0x113
Jun 17 05:01:02 hostname kernel:  [<ffffffff88036d5a>] :jbd:log_wait_commit+0xa3/0xf5
Jun 17 05:01:02 hostname kernel:  [<ffffffff8029c521>] autoremove_wake_function+0x0/0x2e
Jun 17 05:01:02 hostname kernel:  [<ffffffff8803178a>] :jbd:journal_stop+0x1cf/0x1ff
Jun 17 05:01:02 hostname kernel:  [<ffffffff80231056>] __writeback_single_inode+0x1e9/0x328
Jun 17 05:01:02 hostname kernel:  [<ffffffff802e5775>] sync_inode+0x24/0x33
Jun 17 05:01:04 hostname kernel:  [<ffffffff8804c36d>] :ext3:ext3_sync_file+0xc9/0xdc
Jun 17 05:01:04 hostname kernel:  [<ffffffff80251f3f>] do_fsync+0x52/0xa4
Jun 17 05:01:05 hostname kernel:  [<ffffffff802d370c>] __do_fsync+0x23/0x36
Jun 17 05:01:05 hostname kernel:  [<ffffffff802602f9>] tracesys+0xab/0xb6



Version-Release number of selected component (if applicable):
mysql-5.0.77-4.el5_5.3
mysql-server-5.0.77-4.el5_5.3


Additional info:

If this log means a high load case. During this time, there was nothing noticed to cause any high load, however under high load previously it didn't behave like that.

Probably Related bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=592049

Comment 1 Ahmed Medhat 2010-06-20 10:13:11 UTC
Ping!

BTW I'm running 2.6.18-194.3.1.el5xen, x86_64

Comment 2 intel352 2010-10-05 18:07:50 UTC
Same issue on Centos 5.5, using kernel 2.6.18-194.11.3.el5xen

The similar issue reported on Centos can be found here: http://bugs.centos.org/view.php?id=4515

Comment 3 JDavis4102 2011-10-28 20:45:36 UTC
Any updates as to what could be causing this issue. I am having this issue with kernel 2.6.18-274.3.1.el5.

Comment 4 JDavis4102 2011-11-29 16:23:26 UTC
Seems like kernel 2.6.18-274.7.X resolves this issue.

Comment 5 RHEL Program Management 2014-03-07 12:46:42 UTC
This bug/component is not included in scope for RHEL-5.11.0 which is the last RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX (at the end of RHEL5.11 development phase (Apr 22, 2014)). Please contact your account manager or support representative in case you need to escalate this bug.

Comment 6 RHEL Program Management 2014-06-02 13:16:30 UTC
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).

Comment 7 Red Hat Bugzilla 2023-09-14 01:21:30 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days


Note You need to log in before you can comment on or make changes to this bug.