You are not logged in.

#1 2014-09-07 08:49:39

Nipsky
Member
From: Germany
Registered: 2011-10-03
Posts: 26

Suspend/Reboot/Shutdown puts Acer TravelMate B115-M-41RQ in limbo

Hey guys,

trying to suspend (via echo mem > /sys/power/state), reboot or shutdown my Acer TravelMate B115-M-41RQ (NX.VA1EG.002, Intel N3530, Bay Trail-M) puts it in a kind if limbo state: The power id stays lit but harddrive and screen turn of. Its a fanless device, so I have not idea what else happens in there. I have to kill the thing off by holding down the power key and restart it manually then.

I tried kernel versions 3.14.17, 3.15.10 and 3.16.1 so far, without luck.

journalctl gives me no real information to investigate further and there are no errors in dmesg regard acpi besides:

[    0.430418] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[    0.430558] acpi PNP0A08:00: _OSC failed (AE_ERROR); disabling ASPM
[    0.431001] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge

Can someone give me hint where to look further?

edit: It gets stranger: I played around with some kernel options. Things like "acpi=off", "acpi=noirq" etc. freeze the system at boot. However, with the kernel option "noapic", suspend works – but the next boot with the option activated results in the system freezing at different stages of the boot process. I tried this several times, I can only boot successfully when I boot the system without touching apic after it worked for one time.

To make it clear:

  • boot with "noapic" → suspend etc. works

  • boot with "noapic" → freeze while booting

  • boot without "noapic" → system boots fine (but suspend etc. doesn't work, obviously)

Last edited by Nipsky (2014-09-08 14:18:47)

Offline

#2 2014-10-01 13:55:10

colo
Member
From: Austria
Registered: 2014-10-01
Posts: 1
Website

Re: Suspend/Reboot/Shutdown puts Acer TravelMate B115-M-41RQ in limbo

Hi,

I'm a Debian user myself, but decided to chime in here regardless. I'm on jessie/testing amd64, using Linux 3.16.3. I got my B-115M today and replaced the Broadcom WiFi card with an Intel 3160, so what I see may not be 100% applicable to your situation due to weird hardware bugs that may or may not exist in either of those cards. My system has a BIOS image version 1.22, dated 2014-09-02, flashed (the most recent as of now according to Acer's B115-M product website) and was installed in UEFI Mode with Secure Boot disabled.

Suspend/resume cycles do work and I did not alter my kernel's default cmdline one bit, however the laptop fails to properly power down after shutdown completes; I have to do that by pressing the power button for four seconds. Upon resume into an Xorg session, the touchpad does not work any more until a reboot is performed, and the kernel reports problems with xhcd_hci in its debug ringbuffer, along the lines of:

[   25.757728] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[   25.757920] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[   25.757931] usb 1-4: hub failed to enable device, error -22
[   25.869458] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[   25.869634] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 2.
[   25.869646] usb 1-4: hub failed to enable device, error -22
[   25.981417] usb 1-4: reset high-speed USB device number 3 using xhci_hcd
[   26.057025] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880079068dc0
[   26.113463] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[   26.113526] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[   26.113537] usb 1-2: hub failed to enable device, error -22
[   26.225318] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[   26.225377] xhci_hcd 0000:00:14.0: Setup ERROR: setup context command for slot 1.
[   26.225389] usb 1-2: hub failed to enable device, error -22
[   26.337384] usb 1-2: reset high-speed USB device number 2 using xhci_hcd
[   26.354207] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880178918cc0

USB devices seem to properly work regardless. I'll update this thread if I happen to find a way to fix the issues I'm seeing.
It'd be helpful to know whether you're in Legacy or UEFI boot mode, I didn't see that info in your initial post.

Offline

Board footer

Powered by FluxBB