Comment # 17 on bug 1000482 from Takashi Iwai

Sorry to be late, as I've been on vacation in the last weeks.

So, it confirms that the problem is still present with the latest TW kernel
(4.7.x at that time?).  One more check just to be sure: add the blacklist of
iwlwifi, and confirm that it doesn't hang -- i.e. the problem is in iwlwifi.
For example, put the following line to /etc/modprobe.d/99-local.conf

blacklist iwlwifi

And reboot with oS-42.2 and TW kernels.

If the system works fine without iwlwifi, then try to set up kdump to catch the
crash.  You can use YaST2 kdump module.  You'd likely need to put a larger
reserved RAM there than suggested, e.g. 256MB lower memory.

Once after kdump is set up, reboot again with iwlwifi blacklisted.  After
login, load iwlwifi module manually

% modprobe iwlwifi

Then WiFi stack will appear.  Continue using it until it reaches to a crash.

If kdump doesn't work well, but if you can still do remote-login or such, it'd
be helpful.  What we inevitably need is the kernel Oops / bug messages.

In anyway, please attach the kernel boot messages (the output of dmesg) after
loading iwlwifi driver on both 4.4.x and TW kernels.

Thanks!