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!
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!
FS#52131 - [linux] Hanging on 4.8.13-1-x86_64
Attached to Project:
Arch Linux
Opened by Brendan Wood (bwood) - Monday, 12 December 2016, 18:31 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 27 March 2017, 06:39 GMT
Opened by Brendan Wood (bwood) - Monday, 12 December 2016, 18:31 GMT
Last edited by Tobias Powalowski (tpowa) - Monday, 27 March 2017, 06:39 GMT
|
DetailsDescription:
I ran a `pacman -Syu` this morning and it borked my system. Upon successful upgrade and rebooting, I made it to the desktop but everything started hanging. Couldn't launch a browser, search packages, connect to wifi, run htop, etc. I couldn't see an obvious pattern in what was failing and the state was so bad that I couldn't do much to even debug the issue. The hangs are pretty serious, can't interrupt the process in most cases. I booted from a live CD, chrooted, and downgraded the kernel and headers to my previous version (leaving the rest of the upgraded packages untouched). Now everything's working again, so that leaves me to think there's an issue with 4.8.13-1-x86_64. Additional info: Originally (and currently) running 4.8.8-2-x86_64. Apparently busted 4.8.13-1-x86_64. Running on a 2011 MacBook Pro. Happy to attempt to re-bork and gather more information if anyone wants. Steps to reproduce: Upgrade with `pacman -Syu`, reboot, cry. Probably system-dependent, since I don't see anyone else with this issue. |
This task depends upon
Comment by Daniel M. Capella (polyzen) -
Monday, 12 December 2016, 19:18 GMT
I would suggest trying to update to at least 4.8.12-3 due to vulnerabilities, but partial updates are unsupported.
Comment by Tobias Powalowski (tpowa) -
Friday, 24 March 2017, 08:08 GMT
Still an issue with latest packages?
Comment by Brendan Wood (bwood) -
Friday, 24 March 2017, 16:34 GMT
No, everything seems fine now, haven't had an issue after skipping 4.8.13-1-x86_64.