From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 121531] Adaptec 7805H SAS HBA (pm80xx): hangs when writing >80MB at once
Date: Thu, 07 Jul 2016 16:34:31 +0000 [thread overview]
Message-ID: <bug-121531-11613-HCS9sSYYzs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-121531-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=121531
--- Comment #14 from Jack Wang <xjtuwjp@gmail.com> ---
The changes are huge, hard to do it, without help from MicroSemi/PMCs side.
And I don't have hardware to test.
I've asked developer from MicroSemi to upsteam their changes, but
sadly no reply.
2016-07-07 17:36 GMT+02:00 <bugzilla-daemon@bugzilla.kernel.org>:
> https://bugzilla.kernel.org/show_bug.cgi?id=121531
>
> --- Comment #13 from Martin von Wittich <martin.von.wittich@iserv.eu> ---
> Yup, the Debian installation worked and seems to work fine so far. I manually
> installed the pm80xx-1.4.0-11068-debian64.deb package in the target system
> while I was still in the installer by chrooting to /target; then I added
> "pm80xx" to /etc/initramfs/modules (without that update-initramfs wouldn't add
> the pm80xx module, I'm not really sure why).
>
> After booting the system, I've succcessfully written ~500 GB of /dev/zero data
> into a file on an MD raid consisting of both of the disks. No error messages in
> the dmesg either.
>
> Can you include those missing changes into the official kernel, or how can we
> resolve this bug? We'll ask to the customer if we can keep the server for an
> additional two weeks for testing, so if you need me to test builds, let me
> know.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2016-07-07 16:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 15:43 [Bug 121531] New: Adaptec 7805H SAS HBA (pm80xx): hangs when writing >80MB at once bugzilla-daemon
2016-07-06 15:44 ` [Bug 121531] " bugzilla-daemon
2016-07-06 15:44 ` bugzilla-daemon
2016-07-06 15:44 ` bugzilla-daemon
2016-07-06 15:45 ` bugzilla-daemon
2016-07-06 15:45 ` bugzilla-daemon
2016-07-06 15:46 ` bugzilla-daemon
2016-07-06 15:47 ` bugzilla-daemon
2016-07-06 15:48 ` bugzilla-daemon
2016-07-06 15:49 ` bugzilla-daemon
2016-07-06 16:03 ` bugzilla-daemon
2016-07-06 16:15 ` bugzilla-daemon
2016-07-07 11:38 ` bugzilla-daemon
2016-07-07 15:36 ` bugzilla-daemon
2016-07-07 16:34 ` bugzilla-daemon [this message]
2016-07-08 4:47 ` Viswas G
2016-07-08 7:47 ` Jack Wang
2016-07-08 7:47 ` bugzilla-daemon
2016-10-25 15:20 ` bugzilla-daemon
2016-10-25 15:21 ` bugzilla-daemon
2016-10-25 23:03 ` bugzilla-daemon
2016-10-25 23:11 ` bugzilla-daemon
2016-10-26 12:51 ` bugzilla-daemon
2016-10-26 12:52 ` bugzilla-daemon
2016-10-27 21:57 ` bugzilla-daemon
2016-11-01 22:09 ` 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-121531-11613-HCS9sSYYzs@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.