All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 07 Jan 2025 03:33:59 +0000	[thread overview]
Message-ID: <bug-217599-11613-5ReMht2qWA@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 #71 from Sagar (sagar.biradar@microchip.com) ---
(In reply to Steve from comment #70)
> (In reply to Sagar from comment #69)
> > Hi all,
> > Currently the patch which caused the issue has been reverted.
> > I have reworked and I have a fix ready for this issue.
> > 
> > I am working towards submitting the patch sometime this week.
> 
> this is my dmesg log if it can help:
> 
> [    0.801036] Adaptec aacraid driver 1.2.1[50983]-custom
> [    0.801047] aacraid 0000:03:00.0: can't disable ASPM; OS doesn't have
> ASPM control
> [    0.805979] aacraid: Comm Interface type2 enabled
> [    0.839258] scsi host0: aacraid
> [    1.933550] scsi 0:3:0:0: Enclosure         NETAPP   DS424IOM6       
> 0191 PQ: 0 ANSI: 5
> [    1.947104] aacraid: Host bus reset request. SCSI hang ?
> [    1.947113] aacraid 0000:03:00.0: outstanding cmd: midlevel-1
> [    1.947114] aacraid 0000:03:00.0: outstanding cmd: lowlevel-0
> [    1.947115] aacraid 0000:03:00.0: outstanding cmd: error handler-0
> [    1.947115] aacraid 0000:03:00.0: outstanding cmd: firmware-0
> [    1.947116] aacraid 0000:03:00.0: outstanding cmd: kernel-0
> [    1.954062] aacraid 0000:03:00.0: Controller reset type is 3
> [    1.954063] aacraid 0000:03:00.0: Issuing IOP reset
> [   78.145262] aacraid 0000:03:00.0: IOP reset succeeded
> [   78.151156] aacraid: Comm Interface type2 enabled
> [   87.187835] aacraid 0000:03:00.0: Scheduling bus rescan
> [   97.589026] aacraid: Host bus reset request. SCSI hang ?
> [   97.589047] aacraid 0000:03:00.0: outstanding cmd: midlevel-1
> [   97.589054] aacraid 0000:03:00.0: outstanding cmd: lowlevel-0
> [   97.589057] aacraid 0000:03:00.0: outstanding cmd: error handler-0
> [   97.589061] aacraid 0000:03:00.0: outstanding cmd: firmware-0
> [   97.589064] aacraid 0000:03:00.0: outstanding cmd: kernel-0
> [   97.599053] aacraid 0000:03:00.0: Controller reset type is 3
> [   97.599066] aacraid 0000:03:00.0: Issuing IOP reset
> [  173.373888] aacraid 0000:03:00.0: IOP reset succeeded
> [  173.380165] aacraid: Comm Interface type2 enabled
> [  182.417010] aacraid 0000:03:00.0: Scheduling bus rescan
> [  192.812389] scsi 0:3:0:0: tag#164 timing out command, waited 120s

Hi Steve,
Thanks for your efforts with providing the logs.
Yes,  we are aware of the issue and I have put together a patch that works for
me.
I will submit it to the community sometime this week and please feel free to
provide me your inputs.

I will post the link of the patch once I submit it.
Thanks

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2025-01-07  3:34 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
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 [this message]
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-5ReMht2qWA@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 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.