lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 23 Sep 2007 15:08:06 +0200
From:	Frans Pop <elendil@...net.nl>
To:	Alexey Starikovskiy <aystarik@...il.com>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [2.6.23-rc7] main.c: undefined reference to `acpi_sleep_prepare'

On Sunday 23 September 2007, Alexey Starikovskiy wrote:
> Frans Pop wrote:
> > drivers/built-in.o: In function `acpi_power_off_prepare':
> > main.c:(.text+0x32282): undefined reference to `acpi_sleep_prepare'
> > drivers/built-in.o: In function `acpi_hibernation_prepare':
> > main.c:(.text+0x3228c): undefined reference to `acpi_sleep_prepare'
>
> yep... acpi_sleep_prepare was put under CONFIG_SUSPEND spanning half of
> the file... this patch moves it out.

Compiles and works fine with that patch applied. Thanks.


One thing I noticed after booting with the kernel without CONFIG_SUSPEND.
/proc/acpi/sleep no longer lists S3 (as expected), but /proc/acpi/wakeup 
does still list the device status for S3, which seems somewhat 
inconsistent:

Device	S-state	  Status   Sysfs node
VIY0	  S3	 disabled  pci:0000:01:0b.0
USB1	  S3	 disabled  pci:0000:00:1d.0
USB2	  S3	 disabled  pci:0000:00:1d.1
USB4	  S3	 disabled  pci:0000:00:1d.7
AMDM	  S3	 disabled  pci:0000:00:1f.6
LID	  S4	*enabled   
PWRB	  S4	*enabled   

Not sure if it's worth fixing though.

Cheers,
FJP
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ