--- Comment From frederic.bar...@fr.ibm.com 2017-03-24 10:34 EDT---
Hello Canonical,
Same as for bug 1667239 , the fix doesn't seem to be in the yakkety -proposed
kernel Ubuntu-4.8.0-44.47.
Same reason?
--
You received this bug notification because you are a member of Kernel
Packages,
--- Comment From vipar...@in.ibm.com 2017-03-22 04:40 EDT---
(In reply to comment #46)
> Marking won't fix for Yakkety according to comment #19
Hello Canonical,
This bug is marked as "won't fix" for Yaketty,
so there shouldn't be any verification needed for Yaketty.
Can you please
--- Comment From vipar...@in.ibm.com 2017-03-06 23:29 EDT---
*** Bug 152125 has been marked as a duplicate of this bug. ***
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1667599
--- Comment From vajai...@in.ibm.com 2017-03-02 22:52 EDT---
(In reply to comment #44)
> (In reply to comment #41)
> > Yes, that commit adds the surprise hotplug feature to the PowerNV PCI
> > driver. Is the request then that we should add the surprise hotplug
> > feature to yakkety along
--- Comment From vajai...@in.ibm.com 2017-03-02 07:20 EDT---
(In reply to comment #41)
> Yes, that commit adds the surprise hotplug feature to the PowerNV PCI
> driver. Is the request then that we should add the surprise hotplug
> feature to yakkety along with the subsequent bug fixes for
On Wed, Mar 01, 2017 at 12:20:50PM -, bugproxy wrote:
> --- Comment From vipar...@in.ibm.com 2017-03-01 07:11 EDT---
> (In reply to comment #38)
> > I've applied all three patches to zesty. Only the first patch is applicable
> > for 16.04.2 (yakkety 4.8 kernel) as it does not have
--- Comment From vipar...@in.ibm.com 2017-03-01 07:11 EDT---
(In reply to comment #38)
> I've applied all three patches to zesty. Only the first patch is applicable
> for 16.04.2 (yakkety 4.8 kernel) as it does not have 360aebd85a4c
> "drivers/pci/hotplug: Support surprise hotplug in
--- Comment From vajai...@in.ibm.com 2017-02-28 00:41 EDT---
(In reply to comment #34)
> Setting CONFIG_PCIEPORTBUS=n has already been applied to our 4.10 kernel in
> response to bug #1665404. If pcieportdrv is to blame I believe this should
> take care of the problem. Can you confirm?
Leann,
Now that there is some context in this bug, it appears to be patches for
the Kernel Team to evaluate.
Michael
On 02/24/2017 11:41 AM, bugproxy wrote:
> default desc
>
> Default Comment by Bridge
>
> Default Comment by Bridge
>
> --- Comment From
default desc
Default Comment by Bridge
Default Comment by Bridge
--- Comment From frederic.bar...@fr.ibm.com 2017-02-24 03:56 EDT---
> The fix (together with other fixes) were posted and tracked by:
> https://patchwork.ozlabs.org/patch/728419
>
Note that the full series (3 patches)
10 matches
Mail list logo
