Bug 759211 - Macmini2,1 EFI fails to power off
Summary: Macmini2,1 EFI fails to power off
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-01 17:07 UTC by Mads Kiilerich
Modified: 2012-05-25 16:47 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-25 16:47:59 UTC
Type: Bug

Attachments (Terms of Use)
messages (117.94 KB, text/plain)
2011-12-01 17:07 UTC, Mads Kiilerich 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mads Kiilerich 2011-12-01 17:07:33 UTC 
Created attachment 539293 [details]
messages

'init 0' on Macmini2,1 brings it to a state where it says

  Powering off.
  [timestamp] Power down.

and the power LED turns off ... but the display stays turned on and the machine keeps using power and cooling/spinning.

A reboot works fine.

I guess this is a variant of the challenges mentioned on http://mjg59.dreamwidth.org/3561.html .

http://www.smolts.org/client/show/pub_f8de9376-1430-4cea-9095-c78df3bb7235
kernel-PAE-3.1.2-1.fc16.i686
grub2-efi-1.99-12.fc16.i686
Comment 1 Josh Boyer 2012-03-01 15:57:58 UTC 
Is this still happening with the 3.2.7 or newer kernels?
Comment 2 Dave Jones 2012-03-22 16:57:20 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 3 Dave Jones 2012-03-22 17:01:25 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 4 Dave Jones 2012-03-22 17:12:35 UTC 
[mass update]
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
Comment 5 Mads Kiilerich 2012-05-25 16:47:59 UTC 
Seems to be solved.
Note You need to log in before you can comment on or make changes to this bug.