All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 71231] New: System unresponsable after a lot of LUNs have been added to the system
Date: Thu, 27 Feb 2014 17:45:40 +0000	[thread overview]
Message-ID: <bug-71231-11613@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 71231
           Summary: System unresponsable after a lot of LUNs have been
                    added to the system
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 3.10.32
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: SCSI
          Assignee: linux-scsi@vger.kernel.org
          Reporter: alexandernaumann@gmx.de
        Regression: No

Created attachment 127581
  --> https://bugzilla.kernel.org/attachment.cgi?id=127581&action=edit
Kernel config

This Kernel crash is reproducable on my system.
Right now I could get it with 3.10.25 and 3.10.32.
I works fine with 3.1.

The system (Dell R910, nut it also happens with other servers) has a QLogic
FC-HBA (qla2xxx driver).
After connection about 30 LUNs the system is working fine, but if I increase
the amount of FC-LUNs to for example 40 the system hangs afetr some seconds.

Maybe this bug has been already fixed by Suse:
http://kernel.suse.com/cgit/kernel-source/tree/patches.fixes/mm-resched-to-avoid-rcu-stall-during-boot-large-machines.patch?h=SLE11-SP3&id=6780159bba20e9f99dd5ac8a4e18f98f9c93adf7

If it is the case I think this patch should be put into current kernel lines.

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

             reply	other threads:[~2014-02-27 17:45 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27 17:45 bugzilla-daemon [this message]
2014-02-27 17:46 ` [Bug 71231] System unresponsable after a lot of LUNs have been added to the system bugzilla-daemon
2014-02-27 17:47 ` bugzilla-daemon
2014-02-28 12:21 ` bugzilla-daemon
2014-02-28 13:09 ` bugzilla-daemon
2014-02-28 16:40 ` bugzilla-daemon
2014-02-28 19:37 ` bugzilla-daemon
2014-03-05 15:56 ` bugzilla-daemon
2014-03-06  9:40 ` bugzilla-daemon
2014-03-19 10:01 ` bugzilla-daemon
2014-03-31  9:57 ` bugzilla-daemon
2014-04-09 10:22 ` bugzilla-daemon
2014-04-09 10:25 ` bugzilla-daemon
2014-04-09 17:50 ` bugzilla-daemon
2014-04-11  8:20 ` bugzilla-daemon
2014-04-11 13:08 ` bugzilla-daemon
2014-04-11 13:15 ` bugzilla-daemon
2014-04-11 13:49 ` bugzilla-daemon
2021-06-28  7:36 ` bugzilla-daemon
2021-06-28  7:39 ` 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-71231-11613@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@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.