Re: USB stops working if a malfunctioning USB device is connected

On 7 December 2016 at 01:09, Alan Stern wrote: > On Tue, 6 Dec 2016, PrasannaKumar Muralidharan wrote: > >> > The issue did not appear for a day with 4.9-rc5. Will check for a >> > couple more days and get back. >> >> I have been running 4.9-rc5 for quite some time. Did

Re: USB stops working if a malfunctioning USB device is connected

On Tue, 6 Dec 2016, PrasannaKumar Muralidharan wrote: > > The issue did not appear for a day with 4.9-rc5. Will check for a > > couple more days and get back. > > I have been running 4.9-rc5 for quite some time. Did not observe the > crash so far but some times my USB port stops recognising the

Re: USB stops working if a malfunctioning USB device is connected

> The issue did not appear for a day with 4.9-rc5. Will check for a > couple more days and get back. I have been running 4.9-rc5 for quite some time. Did not observe the crash so far but some times my USB port stops recognising the device. After rebooting the system the USB port starts working.

Re: USB stops working if a malfunctioning USB device is connected

The issue did not appear for a day with 4.9-rc5. Will check for a couple more days and get back. Thanks, PrasannaKumar -- 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

Re: USB stops working if a malfunctioning USB device is connected

> At least Debian started building toolchains with PIE enabled by > default. I've had this problem for a while, actually. I'm building > kernels with: > > $ make CC="gcc -fno-PIE" > > and everything builds fine. Great. Kernel build is going on now. Will post about further developments. -- To

Re: USB stops working if a malfunctioning USB device is connected

Hi, Greg KH writes: > On Wed, Nov 16, 2016 at 12:12:53AM +0530, PrasannaKumar Muralidharan wrote: >> >> scripts/kconfig/conf --silentoldconfig Kconfig >> >> CHK include/config/kernel.release >> >> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG:

Re: USB stops working if a malfunctioning USB device is connected

On Tue, 15 Nov 2016, Greg KH wrote: > On Wed, Nov 16, 2016 at 12:12:53AM +0530, PrasannaKumar Muralidharan wrote: > > >> scripts/kconfig/conf --silentoldconfig Kconfig > > >> CHK include/config/kernel.release > > >> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong > >

Re: USB stops working if a malfunctioning USB device is connected

On Wed, Nov 16, 2016 at 12:12:53AM +0530, PrasannaKumar Muralidharan wrote: > >> scripts/kconfig/conf --silentoldconfig Kconfig > >> CHK include/config/kernel.release > >> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong > >> not supported by compiler > >> make: ***

Re: USB stops working if a malfunctioning USB device is connected

>> scripts/kconfig/conf --silentoldconfig Kconfig >> CHK include/config/kernel.release >> Cannot use CONFIG_CC_STACKPROTECTOR_STRONG: -fstack-protector-strong >> not supported by compiler >> make: *** [prepare-compiler-check] Error 1 >> make: *** Waiting for unfinished jobs > > So turn

Re: USB stops working if a malfunctioning USB device is connected

On Tue, 15 Nov 2016, PrasannaKumar Muralidharan wrote: > I am getting the following error when I compile 4.9-rc5: > *** > scripts/kconfig/conf --silentoldconfig Kconfig > CHK include/config/kernel.release >

Re: USB stops working if a malfunctioning USB device is connected

On Tue, 15 Nov 2016, PrasannaKumar Muralidharan wrote: > Hi, > > My android device does not work sometime when I connect it to my > computer. It works sometime, it does not work sometime. If the device > fails to respond to USB requests then any other USB device that I > connect is not detected.

USB stops working if a malfunctioning USB device is connected

Hi, My android device does not work sometime when I connect it to my computer. It works sometime, it does not work sometime. If the device fails to respond to USB requests then any other USB device that I connect is not detected. dmesg snippet when I connect the malfunctioning USB device: