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#41427 - After xorg and kernel updates laptop Y510p does not shut down from KDE

Attached to Project: Arch Linux
Opened by Mike Cloaked (mcloaked) - Friday, 01 August 2014, 14:32 GMT
Last edited by Laurent Carlier (lordheavy) - Sunday, 03 August 2014, 08:50 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andrea Scarpino (BaSh)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
After the update to extra/xorg-server 1.16.0-6 and a kernel update to 3.15.7-1-ARCH the laptop did not shut down from KDE, but after a minute and a half or so gave a console message as per the attached journal log, saying that "kernel: Fixing recursive fault but reboot is needed!"

Additional info:
* package version(s)
xorg-server 1.16.0-6 and related packages
kernel linux 3.15.7-1

* config and/or log files etc.
Journal log attached

Steps to reproduce:
Update laptop with pacman -Syu, reboot and login to KDE. Shutdown - delay occurs dropping to VT with message saying that recursive fault fixed but reboot needed.
Execute # systemctl reboot
System is delayed for another minute and a half with a stop job pending before shutting down.
   journal-shutdown-bug.log (132 KiB)
This task depends upon

Closed by  Laurent Carlier (lordheavy)
Sunday, 03 August 2014, 08:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  linux-3.15.8-1
Comment by Mike Cloaked (mcloaked) - Sunday, 03 August 2014, 08:43 GMT
After a pacman update to the latest kernel 3.15.8-1-ARCH this bug causing a kernel oops on shutdown seems to be resolved. Therefore it looks like it was a kernel bug which has been fixed in 3.15.8-1. Therefore I will mark this bug as closed.

Loading...