Re: xhci_hcd crash on linux 4.7.0

2016-11-01 Thread Alex Damian
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

Re: xhci_hcd crash on linux 4.7.0

2016-10-13 Thread Felipe Balbi
Hi, (please avoid top-posting, see: http://daringfireball.net/2007/07/on_top) Alex Damian writes: > 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, >> >>

Re: xhci_hcd crash on linux 4.7.0

2016-10-12 Thread Alex Damian
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

Re: xhci_hcd crash on linux 4.7.0

2016-10-12 Thread Alex Damian
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 that the corruption always occur on a secondary CPU (ie. the stack trace starts on cpu_startup_entry) and it is always going on when trying to handle an

Re: xhci_hcd crash on linux 4.7.0

2016-08-25 Thread Mathias Nyman
On 29.07.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 untainted kernel, see dmesg paste below. The stack seemed corrupted as well ? I refered

Re: xhci_hcd crash on linux 4.7.0

2016-07-29 Thread Alex Damian
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 to it as a crash since

Re: xhci_hcd crash on linux 4.7.0

2016-07-29 Thread Greg KH
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 to it as a crash since after a couple of these issues, the > machine hard freezes - I set up a

Re: xhci_hcd crash on linux 4.7.0

2016-07-29 Thread Alex Damian
Hi Greg, I managed to reproduce with a untainted kernel, see dmesg paste below. The stack seemed corrupted as well ? I refered to it as a crash since after a couple of these issues, the machine hard freezes - I set up a serial console via a USB cable, but I don't get the kernel oops out of the

Re: xhci_hcd crash on linux 4.7.0

2016-07-28 Thread Greg KH
On Thu, Jul 28, 2016 at 11:29:41AM +0100, Alex Damian wrote: > 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

xhci_hcd crash on linux 4.7.0

2016-07-28 Thread Alex Damian
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.