Just one more FYI, by blacklisting the ses module, the oops goes away.
On Tue, Feb 3, 2015 at 6:05 PM, Alan Stern st...@rowland.harvard.edu wrote:
On Tue, 3 Feb 2015, Athlion wrote:
On Mon, Feb 2, 2015 at 7:27 PM, Alan Stern st...@rowland.harvard.edu wrote:
Had you made any changes
On Mon, Feb 2, 2015 at 7:27 PM, Alan Stern st...@rowland.harvard.edu wrote:
Had you made any changes to the runtime suspend settings?
blk_post_runtime_resume wouldn't be called unless the drive had gone
into runtime suspend. And even then, it's not likely to be called
after you unplug the
Hello again,
I tried setting up netconsole (I don't have a null-modem serial cable
with usb adaptor) and although it *does* capture some of the dump, it
does not capture everything. The dump is from 3.18.5. Here goes (from
the USB connection):
[ 169.827703] usb 2-1.2: new high-speed USB device
Hello all.
On my Thunkpad T420i with 3.18.2 and 3.18.3 kernels, I can reproduce
the following behaviour 100% of the time:
1. Connect one of my (NTFS-formatted) WD 1TB 'My Passport' drives via USB.
2. Disconnect the cable.
3. Kernel Ooops.
For last entries of the journal (it actually caught the
