Sure. Done.
On 05/03/2018 07:04 PM, Mika Westerberg wrote:
Could you then attach full dmesg of the failure without revert to the
bugzilla bug?
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On Thu, May 03, 2018 at 06:53:13PM +0200, Esokrates wrote:
> Hi,
>
> Thanks very much for pointing out that commit!
> Indeed, reverting makes the problem go away!
> Also, interestingly it also makes the errors in
> https://bugzilla.kernel.org/show_bug.cgi?id=199557
> go away, tested using 4.16.7!
Hi,
Thanks very much for pointing out that commit!
Indeed, reverting makes the problem go away!
Also, interestingly it also makes the errors in
https://bugzilla.kernel.org/show_bug.cgi?id=199557
go away, tested using 4.16.7!
On 05/03/2018 05:18 PM, Mika Westerberg wrote:
Could you try to
On Thu, May 03, 2018 at 04:13:05PM +0300, Mathias Nyman wrote:
> On 03.05.2018 12:30, Esokrates wrote:
> > Hi,> Beginning with Linux 4.16 rc7 (4.16 rc6 was NOT affected), I do
> > find the following regularly in dmesg (often it does not happen during
> > boot, but after suspend to ram / resume):
>
On 03.05.2018 12:30, Esokrates wrote:
Hi,>
Beginning with Linux 4.16 rc7 (4.16 rc6 was NOT affected), I do find the following regularly in dmesg (often it does not happen during boot, but after suspend to ram / resume):
Hi
Can you try 'git bisect' to find the patch that causes the issues?
Hi,
Beginning with Linux 4.16 rc7 (4.16 rc6 was NOT affected), I do find the
following regularly in dmesg (often it does not happen during boot, but
after suspend to ram / resume):
[ 216.443309] pcieport :00:1c.0: AER: Corrected error received: id=00e0
[ 216.443951] pcieport
