[CentOS] Suspend Failure on Toshiba Portege R935

Sun Nov 17 06:48:36 UTC 2013
Michael B Allen <ioplex at gmail.com>

On Sun, Nov 17, 2013 at 1:10 AM, Michael B Allen <ioplex at gmail.com> wrote:
> On Sat, Nov 16, 2013 at 11:14 PM, EGO.II-1 <eoconnor25 at gmail.com> wrote:
>> On 11/16/2013 10:04 PM, Michael B Allen wrote:
>>> Broke affinity for irq 27
>> Found this online....don't know if it pertains to your issue, but check
>> it out.
>> https://www.centos.org/forums/viewtopic.php?t=3941
> Unfortunately updating the BIOS did not fix the problem (even though
> the problem is exactly as described in the post cited and the BIOS was
> quite a few revisions behind).
> Note that suspend worked fine on this machine with the previous
> install (Fedora 19).
> dmesg shows the same sequence of "now offline" and then immediately
> "switching to UP code":
> sd 0:0:0:0: [sda] Stopping disk
> sdhci-pci 0000:01:00.0: PCI INT A disabled
> ehci_hcd 0000:00:1d.0: PCI INT A disabled
> snd_hda_intel 0000:00:1b.0: PCI INT A disabled
> ehci_hcd 0000:00:1a.0: PCI INT A disabled
> e1000e 0000:00:19.0: PCI INT A disabled
> e1000e 0000:00:19.0: PME# enabled
> e1000e 0000:00:19.0: wake-up capability enabled by ACPI
> i915 0000:00:02.0: power state changed by ACPI to D3
> ACPI: Preparing to enter system sleep state S3
> Disabling non-boot CPUs ...
> Broke affinity for irq 25
> CPU 1 is now offline
> Broke affinity for irq 26
> CPU 2 is now offline
> Broke affinity for irq 27
> Broke affinity for irq 30
> Broke affinity for irq 31
> CPU 3 is now offline
> SMP alternatives: switching to UP code
> Are the "Broke affinity for irq" messages wrong or bad in some way?

I have found something interesting.

If I do:

  # init 1

so that virtually nothing is running, I can successfully suspend with:

  # echo mem > /sys/power/state

So it seems something running is maybe stopping the suspend?

I also noticed these error messages during suspend:

  btusb_bulk_complete: hci0 urb ffff88022a230200 failed to resubmit (19)
  btusb_intr_complete: hci0 urb ffff88022a2302c0 failed to resubmit (19)

and then during resume:

  btusb 1-1.2:1.1: no reset_resume for driver btusb?

It looks like the Bluetooth USB driver is touchy.

I don't use Bluetooth. How do I go about disabling Bluetooth entirely
w/ CentOS? It's been a long time since I've messed with modprobe.conf.