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: Thu, 26 Oct 2023 07:35:01 +0000 [thread overview]
Message-ID: <bug-217599-11613-FPzDpEKWWB@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 #24 from Maokaman (maokaman@gmail.com) ---
(In reply to Hannes Reinecke from comment #23)
> Can you try with the above patch?
The patch does not fix the issue.
===
Oct 25 21:41:24 server-name kernel: aacraid: Host adapter abort request.
aacraid: Outstanding commands on (0,0,0,0):
Oct 25 21:41:24 server-name kernel: aacraid: Host adapter abort request.
aacraid: Outstanding commands on (0,0,0,0):
Oct 25 21:41:24 server-name kernel: aacraid: Host bus reset request. SCSI hang
?
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: outstanding cmd:
midlevel-0
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: outstanding cmd:
lowlevel-0
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: outstanding cmd:
error handler-0
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: outstanding cmd:
firmware-32
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: outstanding cmd:
kernel-0
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: Controller reset type
is 3
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: Issuing IOP reset
Oct 25 21:41:24 server-name kernel: INFO: task worker:6701 blocked for more
than 122 seconds.
Oct 25 21:41:24 server-name kernel: Not tainted 6.4.7-arch1-61 #1
Oct 25 21:41:24 server-name kernel: "echo 0 >
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 25 21:41:24 server-name kernel: task:worker state:D stack:0
pid:6701 ppid:1 flags:0x00004002
Oct 25 21:41:24 server-name kernel: Call Trace:
Oct 25 21:41:24 server-name kernel: <TASK>
Oct 25 21:41:24 server-name kernel: __schedule+0x3e8/0x13f0
Oct 25 21:41:24 server-name kernel: schedule+0x5e/0xd0
Oct 25 21:41:24 server-name kernel: io_schedule+0x46/0x70
Oct 25 21:41:24 server-name kernel: folio_wait_bit_common+0x13d/0x350
Oct 25 21:41:24 server-name kernel: ? __pfx_wake_page_function+0x10/0x10
Oct 25 21:41:24 server-name kernel: folio_wait_writeback+0x2c/0x90
Oct 25 21:41:24 server-name kernel: __filemap_fdatawait_range+0x80/0xe0
Oct 25 21:41:24 server-name kernel: file_write_and_wait_range+0x8b/0xb0
Oct 25 21:41:24 server-name kernel: xfs_file_fsync+0x5e/0x2a0 [xfs
2be3d2e4a125ddff8482931cb8f078f6393b16a6]
Oct 25 21:41:24 server-name kernel: __x64_sys_fdatasync+0x4c/0x90
Oct 25 21:41:24 server-name kernel: do_syscall_64+0x5c/0x90
Oct 25 21:41:24 server-name kernel: ? syscall_exit_to_user_mode+0x1b/0x40
Oct 25 21:41:24 server-name kernel: ? do_syscall_64+0x6b/0x90
Oct 25 21:41:24 server-name kernel: ? exit_to_user_mode_prepare+0x132/0x1e0
Oct 25 21:41:24 server-name kernel: ? syscall_exit_to_user_mode+0x1b/0x40
Oct 25 21:41:24 server-name kernel: ? do_syscall_64+0x6b/0x90
Oct 25 21:41:24 server-name kernel: ? syscall_exit_to_user_mode+0x1b/0x40
Oct 25 21:41:24 server-name kernel: ? do_syscall_64+0x6b/0x90
Oct 25 21:41:24 server-name kernel: ? syscall_exit_to_user_mode+0x1b/0x40
Oct 25 21:41:24 server-name kernel: ? do_syscall_64+0x6b/0x90
Oct 25 21:41:24 server-name kernel: ? do_syscall_64+0x6b/0x90
Oct 25 21:41:24 server-name kernel: entry_SYSCALL_64_after_hwframe+0x72/0xdc
Oct 25 21:41:24 server-name kernel: RIP: 0033:0x7f9ca1d087aa
Oct 25 21:41:24 server-name kernel: RSP: 002b:00007f93237fd6c0 EFLAGS: 00000293
ORIG_RAX: 000000000000004b
Oct 25 21:41:24 server-name kernel: RAX: ffffffffffffffda RBX: 0000000000000000
RCX: 00007f9ca1d087aa
Oct 25 21:41:24 server-name kernel: RDX: 0000000000000000 RSI: 0000000000000000
RDI: 000000000000000f
Oct 25 21:41:24 server-name kernel: RBP: 0000560d212c66a0 R08: 0000000000000000
R09: 0000000000000000
Oct 25 21:41:24 server-name kernel: R10: 00007f93237fd6e0 R11: 0000000000000293
R12: 0000560d1f112e80
Oct 25 21:41:24 server-name kernel: R13: 0000560d2107b6c8 R14: 0000560d212cd9f0
R15: 00007f9322ffe000
Oct 25 21:41:24 server-name kernel: </TASK>
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: IOP reset succeeded
Oct 25 21:41:24 server-name kernel: aacraid: Comm Interface type2 enabled
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: Scheduling bus rescan
Oct 25 21:41:24 server-name kernel: aacraid 0000:af:00.0: DDR cache data
recovered successfully
Oct 25 21:41:25 server-name kernel: sd 0:0:0:0: [sdb] Very big device. Trying
to use READ CAPACITY(16).
Oct 25 21:41:25 server-name kernel: sd 0:0:1:0: [sda] Very big device. Trying
to use READ CAPACITY(16).
--
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:[~2023-10-26 7:35 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 [this message]
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
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-FPzDpEKWWB@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.