All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 101751] New: 0009103: INFO: task nginx:2334 blocked for more than 120 seconds.
Date: Mon, 20 Jul 2015 11:45:20 +0000	[thread overview]
Message-ID: <bug-101751-13602@https.bugzilla.kernel.org/> (raw)

https://bugzilla.kernel.org/show_bug.cgi?id=101751

            Bug ID: 101751
           Summary: 0009103: INFO: task nginx:2334 blocked for more than
                    120 seconds.
           Product: File System
           Version: 2.5
    Kernel Version: 3.10.84
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: blocking
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@kernel-bugs.osdl.org
          Reporter: zakrzewskim@wp.pl
        Regression: No

Created attachment 183181
  --> https://bugzilla.kernel.org/attachment.cgi?id=183181&action=edit
dmesg logs

I'm getting constant hangs (random programs) with latest kernel 

Sometimes even saving simple vim file takes about 2 minutes !

I've replaced all hardware, motherboard, CPU disks and nothing.

Filesystem check passed.

It affects all our services but mostly nginx and qmail.

My CPU: Intel(R) Core(TM) i7 CPU X 980 @ 3.33GHz
Board: MSI X58 Pro-E (MS-7522)
Drives: 2x Intel 520 240 GB software RAID 1 + 2x WD RE4 3 TB software RAID 1

Please help me solving this.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

             reply	other threads:[~2015-07-20 11:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 11:45 bugzilla-daemon [this message]
2015-07-20 11:46 ` [Bug 101751] 0009103: INFO: task nginx:2334 blocked for more than 120 seconds bugzilla-daemon
2015-07-20 11:47 ` bugzilla-daemon

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=bug-101751-13602@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ext4@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.