Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42604 - [linux] 3.17.1-1 suspend/resume issues on various Thinkpad models

Attached to Project: Arch Linux
Opened by Glenn (grepfor) - Wednesday, 29 October 2014, 23:07 GMT
Last edited by Tobias Powalowski (tpowa) - Sunday, 15 February 2015, 06:08 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 9
Private No

Details

In this Arch forum post

https://bbs.archlinux.org/viewtopic.php?id=189022

several users with the following Thinkpad models/CPUs:

TP X220i i3-2310M
TP X220 i5-2520M
T-43 Pentium M
TP X220t i7-2620M
TP X230t Unknown

are reporting similar (but not identical) problems with suspend/resume that
have shown up after upgrading from kernel 3.16.4 to 3.17.1.

One user (message #6 in the above thread) states that the problem is due to
BIOS low-mem corruption, and gives some journal dump info supporting this.

Another user (message #5) reports that the problem appears to be fixed in
linux-mainline from AUR (presumably from 3.18 rc series, but not specified
in the thread message.)

Just reporting this for completeness.
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Sunday, 15 February 2015, 06:08 GMT
Reason for closing:  Fixed
Comment by Matthias (master_of_jellyfish) - Friday, 31 October 2014, 08:41 GMT
For the sake of completeness: I am also expieriencing this bug on 3.17 on a i5-3320M Thinkpad x230t.
Comment by Jonas Jelten (TheJJ) - Friday, 31 October 2014, 15:48 GMT
http://www.spinics.net/lists/linux-input/msg33611.html upstream bug report
Comment by Glenn (grepfor) - Sunday, 09 November 2014, 16:22 GMT
Update and question for devs:

Several users in the Arch forum post (the URL listed in the ticket) have reported that 3.17.2 fixes their issue.

However at least one user (me, unfortunately, per message #3 in the above forum post) does not see any behavioral difference between 3.17.1 and 3.17.2; the problem still occurs. Otoh, the symptoms I was reporting differed somewhat from those of most of the other users, suggesting that the underlying problem is probably different. (Also, my Thinkpad model, T-43, is considerably older than the other users' models.)

So the question is: Given the above, should I file a separate ticket for my issue and you can close this one? Or ... ?
Comment by Glenn (grepfor) - Saturday, 14 February 2015, 13:47 GMT
Just FYI for anyone who may still be suffering from this issue: On my system, this problem continued to occur in various forms thru all the 3.17 kernels, as well as early 3.18 series, but was evidently fixed in 3.18.5.

Looking thru the kernel changelogs between 3.18.4 and 3.18.5, I was unable to determine which commit may have been responsible for the fix, or even whether the fix was intentional or just a pleasant side effect of some other work.

So... requesting ticket closure and hoping that it doesn't recur.

Loading...