From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 71231] System unresponsable after a lot of LUNs have been added to the system
Date: Wed, 09 Apr 2014 10:22:24 +0000 [thread overview]
Message-ID: <bug-71231-11613-dSeoOLOcW4@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71231-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71231
--- Comment #11 from Alex <alexandernaumann@gmx.de> ---
Does anyboy has any hitn how I can solve this problem?
It occures with any server and any storage with kernel 3.10 and kernel 3.12.
Using bisect has not given my any logical hint which patch might be the reason
why it crashes or why it does not crash anymore.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2014-04-09 10:22 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 17:45 [Bug 71231] New: System unresponsable after a lot of LUNs have been added to the system bugzilla-daemon
2014-02-27 17:46 ` [Bug 71231] " 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 [this message]
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-dSeoOLOcW4@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).