Hello,
Coming back to this old thread. I enabled the xhci debug, with little success.
I am running now kernel 4.8.4; there is no dmesg dump anymore, the
system just reboots by itself.
As I am running kernel crash dump, the system loads the kdump kernel,
but doesn't find anything to save.
The int
Forgot to mention, I just reproduced it on the mainline 4.8.1 kernel.
On Wed, Oct 12, 2016 at 5:13 PM, Alex Damian wrote:
> Hello,
>
> To follow up on the original bug report. I am still experiencing
> memory corruption problems in the xhci stack.
>
> One thing I noticed is t
.2016 17:41, Alex Damian wrote:
>>
>> On Fri, Jul 29, 2016 at 2:53 PM, Greg KH wrote:
>>>
>>> On Fri, Jul 29, 2016 at 10:58:03AM +0100, Alex Damian wrote:
>>>>
>>>> Hi Greg,
>>>>
>>>> I managed to reproduce with a untainte
On Fri, Jul 29, 2016 at 2:53 PM, Greg KH wrote:
> On Fri, Jul 29, 2016 at 10:58:03AM +0100, Alex Damian wrote:
>> Hi Greg,
>>
>> I managed to reproduce with a untainted kernel, see dmesg paste below.
>> The stack seemed corrupted as well ?
>>
>> I refered t
4 00 00 48 89
f8 48 89 d1 a4 c3 0f 1f 80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e
40 38
[10035.840429] RIP [] memcpy_erms+0x6/0x10
[10035.840445] RSP
[10035.856879] ---[ end trace affc0ce74aea10c7 ]---
On Thu, Jul 28, 2016 at 2:40 PM, Greg KH wrote:
> On Thu, Jul 28, 2016 at 11:29:41AM +0
Hello all,
Hope this is the right place to report a bug; if not, please direct me
to where it should go.
I am running a mainline kernel build by the Ubuntu mainline PPA, on a
2015 Macbook. It is being tainted by use of the vboxdrv module. I am
repeatedly getting errors on xhci_hcd irq handler.
T
