Public bug reported:
I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0
motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power
was fully cut, including standby power, and Windows has not been run
since then, Ubuntu will quickly wake from S3 sleep without any apparent
reason. Procedure to reproduce:
1. Shut down computer normally from the operating system.
2. When computer appears off, cut power either via the switch on the back or by
unplugging it.
3. Wait some time. 10 seconds is probably enough and a minute should be 100%
certain.
4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7
boot menu. Do not actually boot into Windows itself though; if you do that you
must restart at step 1.
5. Initiate S3 sleep. I have tried both of these with the same results:
dbus-send --print-reply --system --dest=org.freedesktop.login1
/org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true
sudo sh -c "echo mem > /sys/power/state"
6. Wait. The system should wake up within a few seconds, and certainly in less
than a minute. The delay varies.
The only problem is that the system won't stay sleeping. Everything
works fine after the system wakes. Repeated attempts to sleep give the
same result.
I have disabled everything in /proc/acpi/wakeup using the following in
/etc/rc.local:
sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 > /proc/acpi/wakeup,p'
/proc/acpi/wakeup | sh
I confirm that it appears disabled before and after sleep.
I have also disabled all wakeup files in sys (found via sudo find /sys
-iname wakeup -type f), and it didn't help.
The logs don't seem to show a wakeup reason.
If I boot into Windows 7 and then boot into Linux, this problem stops
happening. Shutting down from either operating system or pressing the
reset button does not cause the problem to reoccur. It only reoccurs if
standby power has been cut. I am assuming that Linux fails to perform
some initialization which Windows performs, and that initialization
persists as long as standby power is available. I am assuming this is a
kernel bug because it occurs even if I use "echo mem > /sys/power/state"
to enter sleep.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 2280 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Wed Apr 29 10:39:49 2015
HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11
InstallationDate: Installed on 2012-01-19 (1196 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P35-DS3R
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic
root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-24 (5 days ago)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug vivid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1450088
Title:
Wakes from S3 in a few seconds unless WIndows has been run
Status in linux package in Ubuntu:
New
Bug description:
I'm running 64-bit Ubuntu 15.04 on a Gigabyte GA-P35-DS3R rev 1.0
motherboard with BIOS F13. I also have 32-bit Windows 7 SP1. If power
was fully cut, including standby power, and Windows has not been run
since then, Ubuntu will quickly wake from S3 sleep without any
apparent reason. Procedure to reproduce:
1. Shut down computer normally from the operating system.
2. When computer appears off, cut power either via the switch on the back or
by unplugging it.
3. Wait some time. 10 seconds is probably enough and a minute should be 100%
certain.
4. Boot directly into Ubuntu. It's okay to boot into Ubuntu via the Windows 7
boot menu. Do not actually boot into Windows itself though; if you do that you
must restart at step 1.
5. Initiate S3 sleep. I have tried both of these with the same results:
dbus-send --print-reply --system --dest=org.freedesktop.login1
/org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true
sudo sh -c "echo mem > /sys/power/state"
6. Wait. The system should wake up within a few seconds, and certainly in
less than a minute. The delay varies.
The only problem is that the system won't stay sleeping. Everything
works fine after the system wakes. Repeated attempts to sleep give the
same result.
I have disabled everything in /proc/acpi/wakeup using the following in
/etc/rc.local:
sed -n '/enabled/s,\([^\t]\+\)\s.*$,echo \1 > /proc/acpi/wakeup,p'
/proc/acpi/wakeup | sh
I confirm that it appears disabled before and after sleep.
I have also disabled all wakeup files in sys (found via sudo find /sys
-iname wakeup -type f), and it didn't help.
The logs don't seem to show a wakeup reason.
If I boot into Windows 7 and then boot into Linux, this problem stops
happening. Shutting down from either operating system or pressing the
reset button does not cause the problem to reoccur. It only reoccurs
if standby power has been cut. I am assuming that Linux fails to
perform some initialization which Windows performs, and that
initialization persists as long as standby power is available. I am
assuming this is a kernel bug because it occurs even if I use "echo
mem > /sys/power/state" to enter sleep.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
Uname: Linux 3.19.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: bgjenero 2280 F.... pulseaudio
CurrentDesktop: X-Cinnamon
Date: Wed Apr 29 10:39:49 2015
HibernationDevice: RESUME=UUID=a44c3385-e1ba-4456-91ec-be27c892ff11
InstallationDate: Installed on 2012-01-19 (1196 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
IwConfig:
eth0 no wireless extensions.
lo no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. P35-DS3R
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic
root=UUID=e59328d8-57ee-4106-aa49-41ceffea8161 ro
RelatedPackageVersions:
linux-restricted-modules-3.19.0-15-generic N/A
linux-backports-modules-3.19.0-15-generic N/A
linux-firmware 1.143
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-24 (5 days ago)
dmi.bios.date: 06/19/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F13
dmi.board.name: P35-DS3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias:
dmi:bvnAwardSoftwareInternational,Inc.:bvrF13:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-DS3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-DS3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: P35-DS3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1450088/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
