Timeline for The question is the same as mine, the accepted answer does not apply to me, how can I raise my own case?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 9, 2016 at 17:48 | vote | accept | XavierStuvw | ||
| Nov 9, 2016 at 21:00 | history | tweeted | twitter.com/AskUbuntu/status/796457521779212288 | ||
| Nov 8, 2016 at 16:57 | comment | added | Elder Geek | I would tend to agree that if you make it clear in your question that you tried this and this and provide other pertinent info such as the content of /var/log/syslog, I have no doubt that your question will be taken seriously as a separate case. It would also help if you point out that you have already checked the likely culprits such as askubuntu.com/questions/528072/… | |
| Nov 4, 2016 at 21:25 | history | edited | ZannaMod | CC BY-SA 3.0 |
edited title
|
| Nov 2, 2016 at 13:37 | answer | added | Jacob Vlijm | timeline score: 7 | |
| Nov 2, 2016 at 13:28 | comment | added | Zanna Mod | that question is a duplicate - that processor is affected by a kernel bug. But freezes could happen for other reasons; it could be a graphics card issue in your case or something else... My system dies at the login screen unless I blacklist a particular module. It's a difficult problem to diagnose :( | |
| Nov 2, 2016 at 13:20 | answer | added | Mark Kirby | timeline score: 20 | |
| Nov 2, 2016 at 12:59 | history | asked | XavierStuvw | CC BY-SA 3.0 |