From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 206123] aacraid ( PM8068) and iommu=nobypass Frozen PHB error on ppc64
Date: Thu, 10 Sep 2020 01:32:11 +0000 [thread overview]
Message-ID: <bug-206123-11613-V89NlnDJQ7@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206123-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206123
--- Comment #10 from gyakovlev@gentoo.org ---
(In reply to Oliver O'Halloran from comment #8)
> Can you see if this patch fixes it?
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20200908015106.79661-
> 1-aik@ozlabs.ru/
ok I applied this patch to linux-5.4.63
looks very good so far, kernel booted with 'iommu=nobypass' and I don't see any
problems with aacraid yet, it works. I can write to all 8 SAS disks in
parallel, and can't trigger the error.
I'll try to generate torture/heavy random IO on the disks a bit later.
also I may give linux-5.8.8 a try.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-09-10 2:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 5:59 [Bug 206123] New: aacraid ( PM8068) and iommu=nobypass Frozen PHB error on ppc64 bugzilla-daemon
2020-01-08 6:00 ` [Bug 206123] " bugzilla-daemon
2020-01-08 6:05 ` bugzilla-daemon
2020-01-08 6:25 ` bugzilla-daemon
2020-04-20 3:18 ` bugzilla-daemon
2020-04-20 18:41 ` bugzilla-daemon
2020-05-06 8:21 ` bugzilla-daemon
2020-09-09 19:07 ` bugzilla-daemon
2020-09-09 23:07 ` bugzilla-daemon
2020-09-09 23:14 ` bugzilla-daemon
2020-09-10 1:32 ` bugzilla-daemon [this message]
2020-09-10 1:46 ` bugzilla-daemon
2020-09-11 3:38 ` bugzilla-daemon
2020-09-11 6:16 ` bugzilla-daemon
2020-09-11 6:22 ` bugzilla-daemon
2020-09-11 18:30 ` bugzilla-daemon
2020-09-11 18:39 ` bugzilla-daemon
2020-09-11 18:48 ` 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-206123-11613-V89NlnDJQ7@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 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.