From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 206261] New: LEDs are off for AHCI connected drives on Cisco C125 server
Date: Tue, 21 Jan 2020 05:33:44 +0000 [thread overview]
Message-ID: <bug-206261-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206261
Bug ID: 206261
Summary: LEDs are off for AHCI connected drives on Cisco C125
server
Product: SCSI Drivers
Version: 2.5
Kernel Version: kernel-debug-5.4.11-1.1.g2d02eb4.x86_64.rpm
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Other
Assignee: scsi_drivers-other@kernel-bugs.osdl.org
Reporter: bvardham@cisco.com
Regression: No
Created attachment 286915
--> https://bugzilla.kernel.org/attachment.cgi?id=286915&action=edit
Attaching the support config logs.
Observed that on linux OS the LED of the drives are completely off (both
Presence and Locate LED) for the AHCI connected drives on the Cisco UCS C125
server.
Note : - Tried on Rhel7.7 OS and Sles 12 SP4 OS, on both LEDs were off, but on
Rhel7.7 OS provided "libahci.ahci_em_messages=0" in the grub after with which
LED worked on the Rhel7.7, but on SLes 12SP4 and other linux distributions not
able to pass the "libahci.ahci_em_messages=0" ,and LED of the drives are not
blowing.
Tested with latest upstream kernel of version
"kernel-debug-5.4.11-1.1.g2d02eb4.x86_64.rpm" then also issue is persisting.
Expected Behavior:
The LED of the drives should work even on Linux OSes.
Attached the support config logs with this bug.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-01-21 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 5:33 bugzilla-daemon [this message]
2020-01-22 6:30 ` [Bug 206261] LEDs are off for AHCI connected drives on Cisco C125 server bugzilla-daemon
2020-02-03 11:24 ` bugzilla-daemon
2020-02-03 11:24 ` 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-206261-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 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).