kernel-packages team mailing list archive

[Stanislav Kukla <stanislavkukla@xxxxxxxxx>]

Hi. Sorry for long delay. I had not so much time for intensive testing. 
After my further intensive testing, it looks the bad commit is known. I tested dozens of kernel versions, then narrowed the selection and kept bisecting it. 
The result is it looks the problem is not among 3.2.60 and 3.2.66, but somewhere in 3.11.0.
My testing ended with this bad commit:

928bea964827d7824b548c1f8e06eccbbc4d0d7d is the first bad commit
commit 928bea964827d7824b548c1f8e06eccbbc4d0d7d
Author: Yinghai Lu <yinghai@xxxxxxxxxx>
Date:   Mon Jul 22 14:37:17 2013 -0700

    PCI: Delay enabling bridges until they're needed
   
    We currently enable PCI bridges after scanning a bus and assigning
    resources.  This is often done in arch code.
   
    This patch changes this so we don't enable a bridge until necessary, i.e.,
    until we enable a PCI device behind the bridge.  We do this in the generic
    pci_enable_device() path, so this also removes the arch-specific code to
    enable bridges.
   
    [bhelgaas: changelog]
    Signed-off-by: Yinghai Lu <yinghai@xxxxxxxxxx>
    Signed-off-by: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>

:040000 040000 92a05476999d94d327a9a9bde707b639ae289b79 703c1e016855c646e0d46f1713e1e950efe665c5 M    arch
:040000 040000 ea2cd89493efd333fb73c88acd229538dcbd9662 ff41b86015d0fd2877a6ee072b95c8aeced83c5d M    drivers
:040000 040000 f6c23efa102fc2c2ead5c86bdb65aa70719b1ab9 f3fdcb7b9e96514e4ca46e79a1208e4f6667abc9 M    include

At the end I tested this bad commit 5 times also with the adjacent (last good) commit 55ed83a615730c2578da155bc99b68f4417ffe20.
I was able to suspend/resume 13 times with kernel built from commit 55ed83a615730c2578da155bc99b68f4417ffe20 - tested 5 times. Suspend/resume always worked properly.
With the bad commit 928bea964827d7824b548c1f8e06eccbbc4d0d7d I always suspended and resumed the pc 3 times and then fourth attempt to suspend ended with the frozen PC (Display off, HDD stopped spinning, but PC kept on and frozen). As I  mentioned above, I repeated this procedure 5 times to prove it is not a coincidence. Interesting it always froze on 4th attempt of suspend.

Is it possible the "PCI: Delay enabling bridges until they're needed"
caused this issue?

I also tested with Fedora core 22 with kernel version 4.0.4-301 and the
suspend issue is present there as well, so I believe this is not related
to Ubuntu system only.


** Changed in: linux (Ubuntu)
       Status: Expired => Confirmed

-- 
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/1412873

Title:
  Ubuntu 14.10 sometimes does not suspend

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  I have this issue since upgrading from ubuntu 13.10 to 14.04. The issue is still present even after upgrade to 14.10.
  The problem is that system sometimes does not suspend correctly. After initiating suspend the display is being turned off completely, HDDs are being stopped, but fan remains ON and the PC LED also stays on. The only possibility is to make hard reset using the HW button on the pc. Pressing power button will neither suspend/turn off computer nor turn in on again. I can reproduce this issue randomly - approximately 1 out of 5 suspends will fail. It looks first suspend after reboot will always work fine. Then some of the suspends after successfull resume will fail (randomly). I also tried fresh install of Ubuntu 14.10, but the suspend kept failing as well. 
  Checking /var/log/pm-suspend.log did not help me as there is always "performing suspend" message either after correct suspend or failed suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-24-generic 3.16.0-24.32
  ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
  Uname: Linux 3.16.0-24-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  ygzo       5008 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Tue Jan 20 17:34:22 2015
  HibernationDevice: RESUME=UUID=5c7a99f0-ca4d-4b61-bf3c-118fa145440d
  InstallationDate: Installed on 2014-04-18 (277 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  IwConfig:
   eth0      no wireless extensions.
   
   lo        no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H61M-D2H
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=0cb350ba-8e96-4ac3-ac78-73547f8ada58 ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.16.0-24-generic N/A
   linux-backports-modules-3.16.0-24-generic  N/A
   linux-firmware                             1.138
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to utopic on 2014-10-28 (84 days ago)
  dmi.bios.date: 05/18/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: H61M-D2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd05/18/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-D2H:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: H61M-D2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1412873/+subscriptions