From: bugzilla-daemon@kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 217599] Adaptec 71605z hangs with aacraid: Host adapter abort request after update to linux 6.4.0
Date: Sun, 13 Oct 2024 00:52:23 +0000 [thread overview]
Message-ID: <bug-217599-11613-4JNWf59Fky@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217599-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=217599
--- Comment #64 from Maxim (leyyyyy@gmail.com) ---
I am still encountering issues with the aacraid driver.
While the reverted version has shown significant improvement in terms of
stability and consistency, and I no longer face issues after the system has
successfully booted, there is still one persistent problem: the system hangs
for 120 seconds during the boot process. It is related to NetApp disk shelf
(0000:03:00.0) connected to ASR-78165.
For example Ubuntu Server 24.04 (live ISO):
$ cat dmesg | grep aacraid
[ 0.915806] kernel: Adaptec aacraid driver 1.2.1[50983]-custom
[ 0.916680] kernel: aacraid 0000:03:00.0: can't disable ASPM; OS doesn't
have ASPM control
[ 0.928906] kernel: aacraid: Comm Interface type2 enabled
[ 0.958831] kernel: aacraid 0000:03:00.0: 64 Bit DAC enabled
[ 0.975916] kernel: scsi host0: aacraid
[ 1.275877] kernel: aacraid: Host bus reset request. SCSI hang ?
[ 1.277602] kernel: aacraid 0000:03:00.0: outstanding cmd: midlevel-1
[ 1.279315] kernel: aacraid 0000:03:00.0: outstanding cmd: lowlevel-0
[ 1.280986] kernel: aacraid 0000:03:00.0: outstanding cmd: error handler-0
[ 1.282672] kernel: aacraid 0000:03:00.0: outstanding cmd: firmware-0
[ 1.284357] kernel: aacraid 0000:03:00.0: outstanding cmd: kernel-0
[ 1.292931] kernel: aacraid 0000:03:00.0: Controller reset type is 3
[ 1.294620] kernel: aacraid 0000:03:00.0: Issuing IOP reset
[ 34.039710] kernel: aacraid 0000:03:00.0: IOP reset succeeded
[ 34.045955] kernel: aacraid: Comm Interface type2 enabled
[ 49.015695] kernel: aacraid 0000:03:00.0: Scheduling bus rescan
[ 59.522832] kernel: aacraid: Host bus reset request. SCSI hang ?
[ 59.525823] kernel: aacraid 0000:03:00.0: outstanding cmd: midlevel-1
[ 59.528323] kernel: aacraid 0000:03:00.0: outstanding cmd: lowlevel-0
[ 59.529023] kernel: aacraid 0000:03:00.0: outstanding cmd: error handler-0
[ 59.529707] kernel: aacraid 0000:03:00.0: outstanding cmd: firmware-0
[ 59.530372] kernel: aacraid 0000:03:00.0: outstanding cmd: kernel-0
[ 59.537907] kernel: aacraid 0000:03:00.0: Controller reset type is 3
[ 59.538609] kernel: aacraid 0000:03:00.0: Issuing IOP reset
[ 91.184486] kernel: aacraid 0000:03:00.0: IOP reset succeeded
[ 91.191966] kernel: aacraid: Comm Interface type2 enabled
[ 106.042633] kernel: aacraid 0000:03:00.0: Scheduling bus rescan
[ 116.351867] kernel: aacraid: Host bus reset request. SCSI hang ?
[ 116.354649] kernel: aacraid 0000:03:00.0: outstanding cmd: midlevel-1
[ 116.357268] kernel: aacraid 0000:03:00.0: outstanding cmd: lowlevel-0
[ 116.357904] kernel: aacraid 0000:03:00.0: outstanding cmd: error handler-0
[ 116.358523] kernel: aacraid 0000:03:00.0: outstanding cmd: firmware-0
[ 116.359113] kernel: aacraid 0000:03:00.0: outstanding cmd: kernel-0
[ 116.366903] kernel: aacraid 0000:03:00.0: Controller reset type is 3
[ 116.367580] kernel: aacraid 0000:03:00.0: Issuing IOP reset
[ 147.979313] kernel: aacraid 0000:03:00.0: IOP reset succeeded
[ 147.981970] kernel: aacraid: Comm Interface type2 enabled
[ 162.916919] kernel: aacraid 0000:03:00.0: Scheduling bus rescan
As I mentioned previously, the 5.15 kernel version is fully functional and
performs consistently well. The same boot issue occurs even with RHEL8 forks,
such as Rocky 8.10, likely because the driver has been backported.
On the other hand, Ubuntu 22.04, which relies on the 5.15 kernel, works
exceptionally well. This is the reason I can't use OpenSUSE Leap 15.6 and must
stick with Ubuntu.
In other words, some errors still exist in the driver’s source code, and a
bisect starting from 5.15 is needed to resolve them.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2024-10-13 0:52 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-26 22:36 [Bug 217599] New: Adaptec 71605z hangs with aacraid: Host adapter abort request after update to linux 6.4.0 bugzilla-daemon
2023-06-27 1:31 ` [Bug 217599] " bugzilla-daemon
2023-06-27 1:47 ` bugzilla-daemon
2023-06-27 2:11 ` bugzilla-daemon
2023-06-27 2:39 ` [Bug 217599] New: " Bagas Sanjaya
2023-06-27 2:39 ` [Bug 217599] " bugzilla-daemon
2023-06-28 9:38 ` bugzilla-daemon
2023-07-03 17:21 ` bugzilla-daemon
2023-07-22 18:48 ` bugzilla-daemon
2023-07-23 18:03 ` bugzilla-daemon
2023-07-23 18:14 ` bugzilla-daemon
2023-07-27 21:22 ` bugzilla-daemon
2023-07-31 19:04 ` bugzilla-daemon
2023-08-02 13:01 ` bugzilla-daemon
2023-08-03 15:53 ` bugzilla-daemon
2023-09-05 14:57 ` bugzilla-daemon
2023-09-05 16:04 ` bugzilla-daemon
2023-09-07 17:41 ` bugzilla-daemon
2023-09-07 17:45 ` bugzilla-daemon
2023-09-07 21:38 ` bugzilla-daemon
2023-09-07 21:48 ` bugzilla-daemon
2023-09-26 7:36 ` bugzilla-daemon
2023-10-20 11:08 ` bugzilla-daemon
2023-10-25 10:22 ` bugzilla-daemon
2023-10-25 10:23 ` bugzilla-daemon
2023-10-26 7:35 ` bugzilla-daemon
2023-11-11 6:43 ` bugzilla-daemon
2023-11-16 8:45 ` bugzilla-daemon
2023-11-18 14:23 ` bugzilla-daemon
2023-11-18 22:47 ` bugzilla-daemon
2023-11-21 9:54 ` bugzilla-daemon
2023-11-21 13:24 ` James Bottomley
2023-11-21 13:24 ` bugzilla-daemon
2023-11-21 13:30 ` bugzilla-daemon
2023-11-21 13:34 ` bugzilla-daemon
2023-11-21 15:27 ` bugzilla-daemon
2023-11-22 22:18 ` bugzilla-daemon
2023-11-23 8:02 ` bugzilla-daemon
2023-11-23 14:39 ` bugzilla-daemon
2023-11-23 14:58 ` bugzilla-daemon
2023-11-23 17:26 ` bugzilla-daemon
2023-11-24 6:57 ` bugzilla-daemon
2023-11-24 6:58 ` bugzilla-daemon
2023-11-24 12:19 ` bugzilla-daemon
2023-11-28 14:15 ` bugzilla-daemon
2023-12-06 13:52 ` bugzilla-daemon
2023-12-08 17:20 ` bugzilla-daemon
2023-12-09 0:56 ` bugzilla-daemon
2023-12-09 21:13 ` bugzilla-daemon
2023-12-16 4:07 ` bugzilla-daemon
2023-12-16 5:35 ` bugzilla-daemon
2023-12-16 22:00 ` bugzilla-daemon
2023-12-18 6:58 ` bugzilla-daemon
2023-12-18 7:14 ` bugzilla-daemon
2023-12-18 7:31 ` bugzilla-daemon
2023-12-21 7:49 ` bugzilla-daemon
2023-12-30 0:22 ` bugzilla-daemon
2023-12-30 12:41 ` bugzilla-daemon
2024-01-06 19:38 ` bugzilla-daemon
2024-01-07 10:11 ` bugzilla-daemon
2024-01-07 10:48 ` bugzilla-daemon
2024-01-25 3:07 ` bugzilla-daemon
2024-01-25 18:30 ` bugzilla-daemon
2024-02-01 19:46 ` bugzilla-daemon
2024-02-14 13:11 ` bugzilla-daemon
2024-02-14 14:10 ` bugzilla-daemon
2024-10-13 0:52 ` bugzilla-daemon [this message]
2024-10-14 7:29 ` bugzilla-daemon
2024-10-21 22:56 ` bugzilla-daemon
2025-01-02 10:17 ` bugzilla-daemon
2025-01-03 8:27 ` bugzilla-daemon
2025-01-06 4:31 ` bugzilla-daemon
2025-01-06 13:52 ` bugzilla-daemon
2025-01-07 3:33 ` bugzilla-daemon
2025-01-27 21:59 ` bugzilla-daemon
2025-02-03 18:40 ` bugzilla-daemon
2025-07-22 2:33 ` 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-217599-11613-4JNWf59Fky@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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).