[Virtual-pkg-base-maintainers] Bug#790458: base: kernel panics after wakeup from suspend

[nikola]

Package: base
Severity: normal

Dear Maintainer(s),

during the last several weeks, I have started noticing regular lockups
after waking my computer up from suspend to RAM. This has started
happening after an upgrade of stretch, and has been happening
consistently after every attempt at waking up from a suspend since.

In the meantime, I have tried "upgrading" to unstable to see if a newer
version of a package (e.g. the kernel) would help remedy the issue, to
no avail.

Although I often had no information about the error whatsoever in the
system logs, at several points the panic log has been written, and is
attached towards the end of the report. The panics received seem to be
pretty diverse to my untrained eye.

Booting into an older version of the kernel doesn't help (3.16.0.4 and
3.10.3 exhibit the same behaviour).

What I found is that using "systemctl suspend" works slightly better
than "pm-suspend" -- the systemctl version panics sooner or later as
well, but seems to give me approx. 1-2 "usable" minutes with the
machine, while pm-suspend just presents a black screen with no activity.
Systemctl also seems to be more consistent in writing debug information
into the system log.

I think it might be possibly useful to notice that every kernel panic
seems to be preceeded by wireless networking activity. I have tried to
"rmmod" iwlwifi before suspending, but after waking up and re-loading
the iwlwifi module, it hangs again. Not sure if it's directly
correlated, though.

The outputs of my `lspci` and `uname -a` commands, as well as the kernel
panics I managed to extract from the logs, can be found at the following
links:
- lspci: http://paste.debian.net/plain/266172/
- uname -a: http://paste.debian.net/plain/266173/
- panics:
  - http://paste.debian.net/plain/266176/
  - http://foo.com.hr/kernel_panics2.log (this one was too big for
    paste.debian.org).

I have tried to collect as many panic logs as possible, sorry if I
overdid it. They are separated by the string "--- SNIP ---".

Please let me know if there's anything else I can do to help reproduce
and remedy the issue. I can reproduce it with 100% confidence, and I'll
gladly do it a few more times if it helps. :)

Thank you!

- Nikola

-- System Information:
Debian Release: stretch/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)