Lucid freeze after close lid

Bug #538521 reported by Yunkwan
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

sony vaio vgn-n29vn
OS: Ubuntu Lucid Latest

If I manually hit ctrl + alt + del (then I got a shutdown dialog)--> sleep , my laptop can really go to sleep(suspend to ram) correctly.

The setting in power manager is close lid to sleep. But when I actually close the lid, my laptop doesn't go to sleep. I can only see the hard disk light flash quite a short while then the power light is still on and keeps green. (when my vaio sleeps, the power light keeps flashing in orange.) So, apparently it's not sleeping. Then I open the lid, I only got a black screen. I try to move my mouse, nothing happen. I press some keys, still nothing happen. I tried to press ctrl-alt-F(1-6), unfortunatly, I can't even switch to any other tty.

I even tried this method "Reboot Even If System Utterly Broken"
http://mark.koli.ch/2009/02/linux-magic-sysrq-key-r-e-i-s-u-b-reboot-even-if-system-utterly-broken.html
It's surprised to know that even this method can't reboot my laptop.

Finally, I have to press my power button till my laptop shutdown. This happens every single time I close my laptop lid.
I have never experience this issue in Ubuntu Karmic and Ubuntu Jaunty.

Revision history for this message
Yunkwan (chanyunkwan0217) wrote :

hardware information

tags: added: lucid
Revision history for this message
Yunkwan (chanyunkwan0217) wrote :

I found a kernel crash log in /var/crash/ , but not quite sure if it helps.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Date: Sun Mar 14 01:58:45 2010
Failure: oops
OopsText:
 ------------[ cut here ]------------
 WARNING: at /build/buildd/linux-2.6.32/lib/kref.c:43 kref_get+0x21/0x30()
 Hardware name: VGN-N29VN_B
 Modules linked in: binfmt_misc ppdev snd_hda_codec_realtek fbcon tileblit font bitblit softcursor vga16fb vgastate arc4 pcmcia snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device ath5k mac80211 ath i915 drm_kms_helper tifm_7xx1 yenta_socket rsrc_nonstatic snd cfg80211 joydev intel_agp sony_laptop drm i2c_algo_bit tifm_core led_class pcmcia_core psmouse soundcore serio_raw snd_page_alloc agpgart video output lp parport ohci1394 usbhid hid ieee1394 sky2
 Pid: 1014, comm: Xorg Not tainted 2.6.32-16-generic #25-Ubuntu
 Call Trace:
  [<c014a9d2>] warn_slowpath_common+0x72/0xa0
  [<c0348731>] ? kref_get+0x21/0x30
  [<c0348731>] ? kref_get+0x21/0x30
  [<c014aa1a>] warn_slowpath_null+0x1a/0x20
  [<c0348731>] kref_get+0x21/0x30
  [<f82ac003>] drm_gem_handle_create+0x83/0xa0 [drm]
  [<c059cb49>] ? mutex_lock+0x19/0x40
  [<f849a968>] intel_user_framebuffer_create_handle+0x18/0x20 [i915]
  [<f82b5599>] drm_mode_getfb+0x69/0xa0 [drm]
  [<c01c64ad>] ? perf_mmap+0x9d/0x2d0
  [<f82aa7cd>] drm_ioctl+0x25d/0x3e0 [drm]
  [<c01c64ad>] ? perf_mmap+0x9d/0x2d0
  [<f82b5530>] ? drm_mode_getfb+0x0/0xa0 [drm]
  [<c01c7936>] ? unlock_page+0x46/0x50
  [<c01e2210>] ? __do_fault+0x3a0/0x490
  [<f82aa570>] ? drm_ioctl+0x0/0x3e0 [drm]
  [<c0213a11>] vfs_ioctl+0x21/0x90
  [<c0213cf9>] do_vfs_ioctl+0x79/0x310
  [<c05a01e2>] ? do_page_fault+0x152/0x380
  [<c0213ff7>] sys_ioctl+0x67/0x80
  [<c01c64ad>] ? perf_mmap+0x9d/0x2d0
  [<c01033ec>] syscall_call+0x7/0xb
  [<c01c64ad>] ? perf_mmap+0x9d/0x2d0
  [<c01c64ad>] ? perf_mmap+0x9d/0x2d0
 ---[ end trace 1e990dbf92ff663f ]---

Package: linux-image-2.6.32-16-generic
SourcePackage: linux
Tags: kernel-oops

tags: added: freeze
removed: lucid
affects: ubuntu → linux (Ubuntu)
tags: added: lucid
Revision history for this message
gareth (garethpaul) wrote :

This affects me too.

Revision history for this message
Aurélien Leblond (blablack) wrote :

This affects me too

Revision history for this message
Aurélien Leblond (blablack) wrote :

In addition to the lswh.txt I posted, I as well use a recompiled kernel without the ACPI 'Suspend to RAM' and 'Hibernation' activated as I don't use them.

I don't know if it has anything to do with the current bug, but I just suppose that once the lid of my laptop is down, Lucid might try to activate one of these two functionalities.

Finally, this bug occurs only if the lid of my laptop is down for a long enough time. Closing it and opening it immediately doesn't trigger this issue.

If you need any additional information, let me know.

Revision history for this message
Yunkwan (chanyunkwan0217) wrote :

Hey, I just figure out that all of use, who encounter this problem, are using a similar/same graphic card, the Intel Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller.

I tested Ubuntu Lucid on another laptop with an integrated ATI graphic card, this issue doesn't exist on it though. that laptop can sleep correctly by closing the lid. Also it can wake up successfully. However, it's screen keeps flashing after wake up though. That's probably a problem related to the driver though, (maybe plymouth also have something to do with.)

is it the intel driver's problem or the plymouth?

Revision history for this message
oraslaci (oraslaci) wrote :

I'm also affected by this bug, and I have an nvidia card.
Also when switching to another user, after logging out,
the same issue shows up.

Revision history for this message
Yunkwan (chanyunkwan0217) wrote : Re: [Bug 538521] Re: Lucid freeze after close lid

this bug is fixed for a while on my machine that uses intel graphic card

On Thu, Apr 15, 2010 at 7:33 PM, oraslaci <email address hidden> wrote:

> I'm also affected by this bug, and I have an nvidia card.
> Also when switching to another user, after logging out,
> the same issue shows up.
>
>
> ** Attachment added: "lshw.txt"
> http://launchpadlibrarian.net/44254128/lshw.txt
>
> --
> Lucid freeze after close lid
> https://bugs.launchpad.net/bugs/538521
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” package in Ubuntu: New
>
> Bug description:
> sony vaio vgn-n29vn
> OS: Ubuntu Lucid Latest
>
> If I manually hit ctrl + alt + del (then I got a shutdown dialog)--> sleep
> , my laptop can really go to sleep(suspend to ram) correctly.
>
> The setting in power manager is close lid to sleep. But when I actually
> close the lid, my laptop doesn't go to sleep. I can only see the hard disk
> light flash quite a short while then the power light is still on and keeps
> green. (when my vaio sleeps, the power light keeps flashing in orange.) So,
> apparently it's not sleeping. Then I open the lid, I only got a black
> screen. I try to move my mouse, nothing happen. I press some keys, still
> nothing happen. I tried to press ctrl-alt-F(1-6), unfortunatly, I can't even
> switch to any other tty.
>
> I even tried this method "Reboot Even If System Utterly Broken"
>
> http://mark.koli.ch/2009/02/linux-magic-sysrq-key-r-e-i-s-u-b-reboot-even-if-system-utterly-broken.html
> It's surprised to know that even this method can't reboot my laptop.
>
> Finally, I have to press my power button till my laptop shutdown. This
> happens every single time I close my laptop lid.
> I have never experience this issue in Ubuntu Karmic and Ubuntu Jaunty.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/538521/+subscribe
>

tags: added: kj-triage
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Yunkwan,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 538521

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Anthony Ciccarello (a3chic9) wrote :

This also affects my Sony VAIO CW series laptop with an NVIDIA Geforce graphics card running 10.04.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.