Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1412000 - System will not shutdown or reboot without using physical power switch
Summary: System will not shutdown or reboot without using physical power switch
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2017-01-11 00:12 UTC by Geoffrey Marr
Modified: 2019-01-09 12:54 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Type: Bug

Attachments (Terms of Use)
Select output of "journalctl" on system where reboot was attempted (56.69 KB, text/plain)
2017-01-11 00:12 UTC, Geoffrey Marr
no flags Details

Description Geoffrey Marr 2017-01-11 00:12:38 UTC
Created attachment 1239276 [details]
Select output of "journalctl" on system where reboot was attempted

Description of problem:
When using either the GUI icons to "Shutdown" or "Reboot" or the CLI commands (sudo reboot, sudo shutdown -h now), the system begins to shutdown, but hangs at the CLI reporting "Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code. device-mapper: remove ioctl on fedora00-root failed: Device or resource busy". I have to use the physical switch on the machine to shut the system down.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Install Fedora-Workstation-Live-x86_64-Rawhide-20170110.n.0
2. Attempt to shutdown or reboot either from the GUI or the CLI
3. Encounter error

Comment 1 Kazutoshi Morioka 2017-01-23 07:34:49 UTC
I had a similar problem on my old AMD motherboard.
Shutdown by CLI command almost always failed and hang-up with error.
Shutdown with power-switch succeeded (but occasionally failed).
In my case, fortunately, shows oops message at pata_atiixp driver, and by removeing pata_atiixp module, the problem is gone completely.

Comment 2 Kazutoshi Morioka 2017-01-23 08:50:14 UTC
> the problem is gone completely.
Sorry, this is my mistake. Today, I experienced similar problem again.
It's clear that removing pata_atiixp is not enough.

Comment 3 Kazutoshi Morioka 2017-02-02 07:13:26 UTC
I updated to 4.9.6-200.fc25.x86_64.
It seems that 4.9.6-200.fc25.x86_64 almost fixes this problem, but still causes panic at shutdown in a rare case, only once in my ten shutdown attempt.
I will continue testing 4.9.6 with workaround wrote before, disabling unused device driver modules (radeon, pata_atiixp, pata_acpi, ata_generic, parport_pc, ppdev).

Note You need to log in before you can comment on or make changes to this bug.