← Back to team overview

kernel-packages team mailing list archive

[Bug 1272945] Re: 8086:2592 [Toshiba Portégé R200-110] Black screen/freeze after resume with i915

 

Hi there, I finally managed to do a bisect on this. It took a while
because the good and bad kernels were in non-linear branches so I had to
do 14 kernel builds on my ancient laptop!

This is the end of the trail:

$ git bisect bad
24576d23976746cb52e7700c4cadbf4bc1bc3472 is the first bad commit
commit 24576d23976746cb52e7700c4cadbf4bc1bc3472
Author: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
Date:   Tue Mar 26 09:25:45 2013 -0700

    drm/i915: enable VT switchless resume v3
    
    With the other bits in place, we can do this safely.
    
    v2: disable backlight on suspend to prevent premature enablement on resume
    v3: disable CRTCs on suspend to allow RTD3 (Kristen)
    
    Signed-off-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
    Reviewed-by: Rodrigo Vivi <rodrigo.vivi@xxxxxxxxx>
    Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxx>

:040000 040000 72fb279ebc4c48824015f43eac459d046dde3204
6797fd617ffd75b6e2a457aaabf5e90f9a4021c0 M      drivers

What do I do now?

Best wishes, Peter

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

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

Title:
  8086:2592 [Toshiba Portégé R200-110] Black screen/freeze after resume
  with i915

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When I suspend (using either the session menu or by closing the lid)
  and resume, my Toshiba Portege R200 fails to wake. The flashing orange
  light changes to blue but the screen remains black and the keyboard is
  unresponsive (Caps Lock doesn't work, Ctrl-Alt-F keys don't work etc).
  The only way to get out is to long-press the power button. This may be
  due to the i915 kms module. This is a regression as it used to work in
  12.04 and 12.10. I did a chop using the mainline kernels and found
  that kernel 3.9.9 (dated 3.Jul.13) works fine but 3.10-rc1 (13.May.13)
  doesn't. In the mean time I'm running with 3.9.9.

  WORKAROUND: Use the VESA driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: linux-image (not installed)
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  peter      1454 F.... pulseaudio
  CurrentDmesg: [  136.627313] init: plymouth-stop pre-start process (2057) terminated with status 1
  Date: Sun Jan 26 16:56:01 2014
  HibernationDevice: RESUME=UUID=d4ddcbdb-5cdd-4c53-a3b4-2b7ef2bcb2c9
  InstallationDate: Installed on 2013-10-14 (103 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1)
  MachineType: TOSHIBA PORTEGE R200
  MarkForUpload: True
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic root=UUID=78b72944-a92e-433a-837d-e66c5d9fefde ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-15-generic N/A
   linux-backports-modules-3.11.0-15-generic  N/A
   linux-firmware                             1.116
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2005
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: Version 1.60
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Version A0
  dmi.chassis.asset.tag: 0000000000
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: Version 1.0
  dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.60:bd10/25/2005:svnTOSHIBA:pnPORTEGER200:pvrPPR20E-01S02REN:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
  dmi.product.name: PORTEGE R200
  dmi.product.version: PPR20E-01S02REN
  dmi.sys.vendor: TOSHIBA

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


References