Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#33110 - Reboot after Hibernate

Attached to Project: Arch Linux
Opened by dnug (weltio) - Sunday, 16 December 2012, 20:11 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 06 May 2013, 18:49 GMT
Task Type Bug Report
Category Packages: Testing
Status Closed
Assigned To No-one
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When I hibernate, the RAM gets saved in the swap parition but instead of shutdown, the computer reboots.

After changing /sys/power/disk from "platform" to "shutdown" this behavior changed - so the computer stayed powered off.

Additional info:
uname --kernel-release
3.7.0-1-ARCH

cat /proc/acpi/wakeup
Device S-state Status Sysfs node
HUB0 S5 *disabled pci:0000:00:09.0
XVR0 S5 *disabled pci:0000:00:0e.0
XVR1 S5 *disabled pci:0000:00:0d.0
XVR2 S5 *disabled pci:0000:00:0c.0
XVR3 S5 *disabled pci:0000:00:0b.0
UAR1 S5 *disabled pnp:00:07
USB0 S4 *enabled pci:0000:00:02.0
USB2 S4 *enabled pci:0000:00:02.1
MMAC S5 *disabled pci:0000:00:0a.0
MMCI S5 *disabled

At the USB port theres just a keyboard/mouse connector and an external hdd.

This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 06 May 2013, 18:49 GMT
Reason for closing:  No response
Comment by dnug (weltio) - Sunday, 16 December 2012, 20:23 GMT
Mainboard: Asus M2N4-SLI
Bios: 4Mb AWARD BIOS, PnP, DMI2.0, WfM2.0, SM BIOS 2.3
Rev: 1301

#dmidecode --type bios,system,chassis,baseboard
#dmidecode --type 0,13,1,12,15,23,32,2,10,41,3
# dmidecode 2.11
SMBIOS 2.4 present.

Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Phoenix Technologies, LTD
Version: ASUS M2N4-SLI ACPI BIOS Revision 1301
Release Date: 09/15/2010
Address: 0xE0000
Runtime Size: 128 kB
ROM Size: 512 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
Boot from CD is supported
Selectable boot is supported
BIOS ROM is socketed
EDD is supported
5.25"/360 kB floppy services are supported (int 13h)
5.25"/1.2 MB floppy services are supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
3.5"/2.88 MB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
CGA/mono video services are supported (int 10h)
ACPI is supported
USB legacy is supported
LS-120 boot is supported
ATAPI Zip drive boot is supported
BIOS boot specification is supported
Targeted content distribution is supported

Handle 0x0001, DMI type 1, 27 bytes
System Information
Manufacturer: System manufacturer
Product Name: System Product Name
Version: System Version
Serial Number: System Serial Number
UUID: 01CDA114-0151-7592-79D5-0A18DD590295
Wake-up Type: Power Switch
SKU Number:
Family:

Handle 0x0003, DMI type 2, 8 bytes
Base Board Information
Manufacturer: ASUSTeK Computer INC.
Product Name: M2N4-SLI
Version: 1.XX
Serial Number: 123456789000

Handle 0x0004, DMI type 3, 17 bytes
Chassis Information
Manufacturer: Chassis Manufacture
Type: Desktop
Lock: Not Present
Version: Chassis Version
Serial Number: EVAL
Asset Tag: 123456789000
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
OEM Information: 0x00000001

Handle 0x0034, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 3
n|US|iso8859-1
n|US|iso8859-1
r|CA|iso8859-1
Currently Installed Language: n|US|iso8859-1

Handle 0x003F, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Comment by Dave Reisner (falconindy) - Sunday, 16 December 2012, 20:35 GMT
What are you suggesting needs fixing here? As explained to you on IRC, you're getting a wakeup from a USB device. You've already found one of several possible workarounds.

Loading...