Bug 1099406 - Unable to enable ACPI - causes usb bluetooth keyboard/mouse to fail and wireless doesn't work [NEEDINFO]
Summary: Unable to enable ACPI - causes usb bluetooth keyboard/mouse to fail and wirel...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 20
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1099401 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-05-20 08:50 UTC by David Eccleston
Modified: 2014-12-10 15:01 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-12-10 15:01:11 UTC
Type: Bug
Embargoed:
jforbes: needinfo?


Attachments (Terms of Use)
dmesg of failing boot (65.30 KB, text/x-log)
2014-05-20 08:50 UTC, David Eccleston
no flags Details

Description David Eccleston 2014-05-20 08:50:56 UTC
Created attachment 897509 [details]
dmesg of failing boot

Description of problem:
On boot getting message "Unable to enable ACPI" 
Microsoft BlueTooth USB Keyboard/Mouse not working
Wireless not working
Long time to load Plasma Desktop
lsusb hangs

Version-Release number of selected component (if applicable):
3.14.4
3.14.3-200
3.14.2-200

3.13.10-200 works but I get ACPI warnings
ACPI Warning: 0x0000000000000b00-0x0000000000000b07 SystemIO conflicts with Region \_SB_.PCI0.SMB_.SMB0 1 (20131115/utaddress-251)
[   21.033108] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

How reproducible:
Everytime I boot into the kernels above

Steps to Reproduce:
1.Select one of the kernels in Grub and boot
2.
3.

Actual results:
KB?mouse don't work
Wireless doesn't work - wireless detection light doesn't come on
Machine very slow


Expected results:
All should work

Additional info:
ACER Aspire 5560

Comment 1 David Eccleston 2014-05-20 13:26:50 UTC
*** Bug 1099401 has been marked as a duplicate of this bug. ***

Comment 2 Justin M. Forbes 2014-11-13 16:01:39 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs.

Fedora 20 has now been rebased to 3.17.2-200.fc20.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2014-12-10 15:01:11 UTC
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.


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