Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/28, Ye Xiaolong wrote: >On 02/27, Peter Chen wrote: >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >>> [Sorry, resend to correct Felipe's email address] >>> >>> Greetings, >>> >>> This debug patch possibly discloses some USB/I2C bugs. Since the USB >>> warning shows up

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/28, Ye Xiaolong wrote: >On 02/27, Peter Chen wrote: >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >>> [Sorry, resend to correct Felipe's email address] >>> >>> Greetings, >>> >>> This debug patch possibly discloses some USB/I2C bugs. Since the USB >>> warning shows up

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Fengguang Wu
The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Fengguang Wu
The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Peter Chen
On Tue, Feb 28, 2017 at 12:32:55PM +0800, Ye Xiaolong wrote: > On 02/28, Ye Xiaolong wrote: > >On 02/27, Peter Chen wrote: > >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > >>> [Sorry, resend to correct Felipe's email address] > >>> > >>> Greetings, > >>> > >>> This debug patch

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Peter Chen
On Tue, Feb 28, 2017 at 12:32:55PM +0800, Ye Xiaolong wrote: > On 02/28, Ye Xiaolong wrote: > >On 02/27, Peter Chen wrote: > >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > >>> [Sorry, resend to correct Felipe's email address] > >>> > >>> Greetings, > >>> > >>> This debug patch

Re: [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/27, Peter Chen wrote: >On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >> [Sorry, resend to correct Felipe's email address] >> >> Greetings, >> >> This debug patch possibly discloses some USB/I2C bugs. Since the USB >> warning shows up earlier in dmesg, it might also be the

Re: [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Ye Xiaolong
On 02/27, Peter Chen wrote: >On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >> [Sorry, resend to correct Felipe's email address] >> >> Greetings, >> >> This debug patch possibly discloses some USB/I2C bugs. Since the USB >> warning shows up earlier in dmesg, it might also be the

Re: [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Peter Chen
On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > [Sorry, resend to correct Felipe's email address] > > Greetings, > > This debug patch possibly discloses some USB/I2C bugs. Since the USB > warning shows up earlier in dmesg, it might also be the root cause of > the I2C bug. The

Re: [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-27 Thread Peter Chen
On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > [Sorry, resend to correct Felipe's email address] > > Greetings, > > This debug patch possibly discloses some USB/I2C bugs. Since the USB > warning shows up earlier in dmesg, it might also be the root cause of > the I2C bug. The

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-26 Thread Fengguang Wu
[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-26 Thread Fengguang Wu
[Sorry, resend to correct Felipe's email address] Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them.

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-26 Thread Fengguang Wu
Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master

[usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

2017-02-26 Thread Fengguang Wu
Greetings, This debug patch possibly discloses some USB/I2C bugs. Since the USB warning shows up earlier in dmesg, it might also be the root cause of the I2C bug. The attached reproduce-* script may help debug them. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master