Re: failure to resume from suspend cause by 84ebc102

2013-08-31 Thread Alan Stern
On Sat, 31 Aug 2013, Adam Borowski wrote: > > Is there any way to get the dmesg information when the system locks up? > > For example, serial console, or netconsole? Seeing that, along with > > CONFIG_USB_DEBUG enabled, would help. > > Network doesn't work after a failed resume. > > I obtaine

Re: failure to resume from suspend cause by 84ebc102

2013-08-30 Thread Adam Borowski
(Sorry for the delay, the CPU fan _and_ one of disks took offense for so many frequent hard power-offs.) On Tue, Aug 27, 2013 at 02:25:36PM -0400, Alan Stern wrote: > On Tue, 27 Aug 2013, Adam Borowski wrote: > > > > What happens if go back to a kernel without that commit and enable > > > CONFIG_

Re: failure to resume from suspend cause by 84ebc102

2013-08-27 Thread Alan Stern
On Tue, 27 Aug 2013, Adam Borowski wrote: > > What happens if go back to a kernel without that commit and enable > > CONFIG_USB_SUSPEND? The behavior should be identical -- basically the > > commit is supposed to have the effect of always assuming that > > CONFIG_USB_SUSPEND has the same value as

Re: failure to resume from suspend cause by 84ebc102

2013-08-26 Thread Alan Stern
On Mon, 26 Aug 2013, Adam Borowski wrote: > Hi! > > I'm afraid that your kernel patch 84ebc10294a3d7be4c66f51070b7aedbaa24de9b > ("USB: remove CONFIG_USB_SUSPEND option") causes lockups on resume from > suspend on at least some machines. > > On kernels from this patch forward up to some point in