** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827330
Title:
[block layer] please pull below upstream patch to Ubuntu 19.04 ker
Hi everyone,
It looks like the commit described here, "block: Revert v5.0
blk_mq_request_issue_directly() changes", made it in during our SRU sync
with upstream stable. [1]
It should be included with the 5.0.0-16 Disco kernel that just recently
went out into the "updates" repository. [2]
If you
If you provide us a kernel we can test it here or we can ship HBA's for
your test environment or both.
Laurie
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827330
Title:
[block layer] please pull
Unfortunately, I do not have the hardware to test this. I can load the
driver but without an HBA I can't recreate the crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827330
Title:
[block layer
This also looks to be in upstream stable as of May 19, so I presume will
land in an SRU for Disco at some point.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827330
Title:
[block layer] please pul
Hi Shagun,
Could you also try the upstream builds (info below) and make sure the patch
resolves the issue:
https://wiki.ubuntu.com/Kernel/MainlineBuilds
It looks like this landed upstream right after kernel freeze and thus
wasn't pulled into Disco. Looks like a matter of just very close
timing.
commit fd9c40f64c514bdc585a21e2e33fa5f83ca8811b
Author: Bart Van Assche
Date: Thu Apr 4 10:08:43 2019 -0700
block: Revert v5.0 blk_mq_request_issue_directly() changes
blk_mq_try_issue_directly() can return BLK_STS*_RESOURCE for requests that
have been queued. If that happens wh
We have triaged the issue and mentioned the upstream commit that should
fixes the issue in the bug description.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https