semetzge...@gmail.com;
>> mj...@coreos.com; kbo...@gmail.com; jun...@freescale.com;
>> robert.schlabb...@gmx.net; linux-usb@vger.kernel.org
>> Subject: Re: 答复: 答复: 答复: 答复: 【xhci】suspend and resume core dump problem
>>
>> Hi,
>>
>> On 03/25/2016 03:39 PM, Lipengcheng wrote:
..@coreos.com; kbo...@gmail.com; jun...@freescale.com;
> robert.schlabb...@gmx.net; linux-usb@vger.kernel.org
> Subject: Re: 答复: 答复: 答复: 答复: 【xhci】suspend and resume core dump problem
>
> Hi,
>
> On 03/25/2016 03:39 PM, Lipengcheng wrote:
> > Hi,
> >Thanks B
Hi,
On 03/25/2016 03:39 PM, Lipengcheng wrote:
> Hi,
>Thanks Baolu very much!
>The kernel is 3.10.Before the problem is inevitable emergence. But we fix
> patch number:b630d4b9d05ba2e66878ca4614946d0f950d4111 and your suggest.
> Then we resume and suspend the seventh and it is ok only if
: Lipengcheng; Mathias Nyman; gre...@linuxfoundation.org
> Cc: st...@rowland.harvard.edu; ba...@ti.com; chasemetzge...@gmail.com;
> mj...@coreos.com; kbo...@gmail.com; jun...@freescale.com;
> robert.schlabb...@gmx.net; linux-usb@vger.kernel.org
> Subject: Re: 答复: 答复: 答复: 答复: 【xhci】sus
Hi,
On 03/23/2016 11:38 AM, Lipengcheng wrote:
>> It looks like a wild pointer exists after xhci_mem_cleanup() is called.
>> >Let me try to reproduce it and seek for a fix.
>
> Hi,
>Thanks very much.
>The kernel is 3.10 and is inevitable emergence. The kernel 3.18 is
> accidental, but
On 03/22/2016 08:09 PM, Lipengcheng wrote:
>> >diff --git a/drivers/usb/host/xhci-mem.c b/drivers/usb/host/xhci-mem.c
>> >index fbf75e5..406c872 100644
>> >--- a/drivers/usb/host/xhci-mem.c
>> >+++ b/drivers/usb/host/xhci-mem.c
>> >@@ -1856,6 +1856,7 @@ no_bw:
>> >
On 22.03.2016 08:05, Lipengcheng wrote:
Hi,
Why is that function failing? That seems suspicious.
According to the analysis, in list_for_each_entry_safe(tt, n,
>rh_bw[i].tts, tt_list) function, (tt->tt_list).prev=0x0. When
list_del(>tt_list) causing to core dump.
Looks like you
On Mon, 2016-03-21 at 23:41 -0400, gre...@linuxfoundation.org wrote:
> On Tue, Mar 22, 2016 at 03:17:08AM +, Lipengcheng wrote:
> > Hi,
> > Thanks for your reply.
> > When the suspend and resume process , the operation of press ctrl + c
> > will produce an interruput and cause to allocate
On Tue, Mar 22, 2016 at 03:51:27AM +, Lipengcheng wrote:
> Hi,
>Thanks Lu Baolu,
> >The core dump says "PC is at xhci_mem_cleanup+0x4e4/0x574 [xhci_hcd] ".
> >But this call flow shows error happens in dma allocation. Which is correct?
> >Or, anything I misunderstood?
> Sorry . I am not
On Tue, Mar 22, 2016 at 11:36:47AM +0800, Lu Baolu wrote:
> Hi,
>
> On 03/22/2016 11:17 AM, Lipengcheng wrote:
> > Hi,
> > Thanks for your reply.
> > When the suspend and resume process , the operation of press ctrl + c
> > will produce an interruput and cause to allocate memory failed. It
On Tue, Mar 22, 2016 at 03:17:08AM +, Lipengcheng wrote:
> Hi,
> Thanks for your reply.
> When the suspend and resume process , the operation of press ctrl + c will
> produce an interruput and cause to allocate memory failed. It causes the usb3
> module can not be used and core dump
Hi,
On 03/22/2016 11:17 AM, Lipengcheng wrote:
> Hi,
> Thanks for your reply.
> When the suspend and resume process , the operation of press ctrl + c will
> produce an interruput and cause to allocate memory failed. It causes the usb3
> module can not be used and core dump after resume
12 matches
Mail list logo
