On 07.03.2016 09:31, Stefan Assmann wrote: > On 06.03.2016 20:10, Theodore Ts'o wrote: >> On Sat, Mar 05, 2016 at 11:24:46AM +0100, Stefan Assmann wrote: > It is 4.5-rc6 without any changes. > >> I don't see anything in ext4_release_file() that would obviously be a >> potential problem after a suspend/reasume. One possibly is that some >> other piece of code is corrupting memory. >> >>> [ 882.459687] CPU: 7 PID: 5299 Comm: dhclient Tainted: G W 4.5.0-0.rc6.git1.1.vanilla.knurd.1.fc23.x86_64 #1 >> >> Is it always dhclient which is trying to exit? > > Most of the time the screen just stays black, so it's hard to tell. But > while trying to reproduce just now I hit a null pointer exception in > anon_vma_interval_tree_remove(), which happened right after initializing > the exact same USB hub. Your corruption theory is getting more likely. It's not a USB problem. I disconnected the USB hub and the corruption remained. However, the backtrace was preceded by [ 32.778070] snd_hda_codec_hdmi hdaudioC0D0: HDMI: pin nid 4 not registered After making sure snd_hda_codec_hdmi did not get loaded during boot I've not experienced the issue anymore. Of course I've only tried this a few times so far, but it looks promising. Anyway thanks for taking a look, I'll probably follow up on this with the sound folks. Stefan -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
