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#33735 - [linux] 3.7.x - 3.8.x Shutdown crash system on Hyper-V after upgrade kernel
Attached to Project:
Arch Linux
Opened by Pawel Kasperek (mappi) - Wednesday, 06 February 2013, 10:34 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:26 GMT
Opened by Pawel Kasperek (mappi) - Wednesday, 06 February 2013, 10:34 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 30 July 2013, 10:26 GMT
|
DetailsDescription:
I've installed Archlinux 2012.10 with kernel 3.6.11 hosted on Hyper-V virtual server (based on Windows 2012). Next, I've upgraded it to new version with kernel 3.7.5 (I used Pacman). After upgrading I have problem during shutdown Archlinux instance from Hyper-V manager or powershell command. The screenshot with failed error is in the attachment file. Maybe this problem is specified but it's very important to me. Additional info: * package version(s) - linux kernel 3.7.5 * config and/or log files etc. Steps to reproduce: |
This task depends upon
Closed by Tobias Powalowski (tpowa)
Tuesday, 30 July 2013, 10:26 GMT
Reason for closing: No response
Tuesday, 30 July 2013, 10:26 GMT
Reason for closing: No response
I don't understand why this bug should be reporting to upstream ? More information about this problem. When I start Archlinux 2013.02 ISO distro on Hyper-V and next I shutdown from Hyper-V manager I have erroer:
BUG: scheduling while atomic: swapper/0/0/0x00000104
bad: scheduling from the idle thread!
BUG: unable to handle kernel
Now I upgrade the Archlinux system on Hyper-V to linux kernel 3.8 and the bug is still again :(.