From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 60644] MPT2SAS drops all HDDs when under high I/O
Date: Mon, 29 Jul 2013 11:27:46 +0000 [thread overview]
Message-ID: <bug-60644-11613-lN9OWyze9h@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-60644-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=60644
Sreekanth Reddy <sreekanth.reddy@lsi.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sreekanth.reddy@lsi.com
--- Comment #3 from Sreekanth Reddy <sreekanth.reddy@lsi.com> ---
Hi,
Can you please provide the driver logs my setting the driver logging level to
0x3f8.
Here are the steps to set the mpt2sas driver logging level
a.While loading the driver
modprobe mpt2sas logging_level=0x3f8
b. If driver is in ramdisk, then in RHEL5/SLES/OEL5 OS, following line has to
be added in /etc/modprobe.conf and reboot the system
options mpt2sas logging_level=0x3f8
(Or)
Add below word at the end of kernel module parameters line in
/boot/grub/menu.lst or /boot/grub/grub.conf file and reboot the system
mpt2sas.logging_level=0x3f8
c. During driver run time
echo 0x3f8 > /sys/module/mpt2sas/parameters/logging_level
Also please provide us the IO rate at which you are faceing this problem.
Regards,
Sreekanth
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-07-29 11:27 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 3:20 [Bug 60644] New: MPT2SAS drops all HDDs when under high I/O bugzilla-daemon
2013-07-29 3:21 ` [Bug 60644] " bugzilla-daemon
2013-07-29 3:32 ` bugzilla-daemon
2013-07-29 11:27 ` bugzilla-daemon [this message]
2013-07-29 14:12 ` bugzilla-daemon
2013-07-29 14:14 ` bugzilla-daemon
2013-07-29 23:24 ` bugzilla-daemon
2013-07-29 23:30 ` bugzilla-daemon
2013-07-30 5:00 ` bugzilla-daemon
2013-07-30 5:26 ` bugzilla-daemon
2013-07-30 5:33 ` bugzilla-daemon
2013-07-30 10:03 ` bugzilla-daemon
2013-07-30 10:11 ` bugzilla-daemon
2013-07-30 10:12 ` bugzilla-daemon
2013-08-01 13:20 ` bugzilla-daemon
2013-08-01 14:24 ` bugzilla-daemon
2013-08-01 14:30 ` bugzilla-daemon
2013-08-02 10:44 ` bugzilla-daemon
2013-08-27 6:48 ` bugzilla-daemon
2013-08-27 7:14 ` bugzilla-daemon
2013-08-27 11:45 ` bugzilla-daemon
2013-08-27 11:46 ` bugzilla-daemon
2013-08-27 15:29 ` bugzilla-daemon
2013-08-28 7:57 ` bugzilla-daemon
2013-08-28 8:32 ` bugzilla-daemon
2013-08-28 8:44 ` bugzilla-daemon
2013-08-28 13:33 ` bugzilla-daemon
2013-08-29 5:51 ` bugzilla-daemon
2013-08-29 10:09 ` bugzilla-daemon
2013-08-29 19:34 ` bugzilla-daemon
2013-08-30 3:08 ` bugzilla-daemon
2013-08-30 4:56 ` bugzilla-daemon
2013-09-17 11:00 ` bugzilla-daemon
2013-09-20 10:13 ` Pasi Kärkkäinen
2013-09-20 10:28 ` bugzilla-daemon
2013-09-20 14:38 ` bugzilla-daemon
2013-12-05 18:00 ` bugzilla-daemon
2014-01-02 14:40 ` bugzilla-daemon
2014-01-13 17:27 ` bugzilla-daemon
2014-01-13 17:31 ` bugzilla-daemon
2014-01-13 18:02 ` bugzilla-daemon
2014-01-13 19:41 ` bugzilla-daemon
2014-01-19 12:14 ` bugzilla-daemon
2014-01-19 12:15 ` bugzilla-daemon
2014-01-19 12:17 ` bugzilla-daemon
2014-01-20 18:27 ` bugzilla-daemon
2014-01-20 18:39 ` bugzilla-daemon
2014-01-20 18:42 ` bugzilla-daemon
2014-01-21 2:54 ` bugzilla-daemon
2014-01-21 19:46 ` bugzilla-daemon
2016-03-29 15:02 ` bugzilla-daemon
2016-12-28 11:15 ` bugzilla-daemon
2016-12-28 11:18 ` bugzilla-daemon
2017-02-19 11:55 ` 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-60644-11613-lN9OWyze9h@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).