b: core : hub: Fix
BOS 'NULL pointer' kernel panic"), which has already been applied
upstream. It looks to me like that patch might have fixed the same
problem in a different way, in which case Changbin's patch is not
needed. But I haven't been involved in developing or testing that
patch, so I can't say for sure. At the very least, 464ad8c43a9e
conflicts with Changbin's patch.
Changbin, can you take a look at 464ad8c43a9e and see if that fixes the
same problem that your patch did?
Thanks,
Tony Battersby
--
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 http://vger.kernel.org/majordomo-info.html
So my testing also applies to Changbin's new patch.
Tony Battersby
Cybernetics
On 04/04/2016 05:26 AM, Roger Quadros wrote:
> Hi Greg,
>
> This commit [1] mentions that it affects certain stable versions but
> I didn't see cc: stable in it nor could find it in any mailing list
Thanks, that fixes it. Tested on 4.5.0-rc5 and 3.18.27. Just to be
clear, I tested it *without* reverting d8f00cd685f5. So this patch is
in addition to d8f00cd685f5 instead of replacing it.
Tested-by: Tony Battersby <to...@cybernetics.com>
On 02/21/2016 09:27 PM, Du, Changbin wrote:
&g
ata+0xb/0x20
RSP
CR2: ffd8
---[ end trace a3bcfa253dbef568 ]---
Fixing recursive fault but reboot is needed!
With the patch reverted, everything works fine.
So far I have been unable to reproduce the problem using EHCI (USB 2.0).
Tony Battersby
Cybernetics
--
To unsubscribe from th
