[Feisty Regression]Dell Inspiron 630m, does not wake up after suspend

Bug #108349 reported by mexlinux
12
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Feisty by artbeall
linux-source-2.6.20 (Ubuntu)
Won't Fix
Medium
Unassigned
Nominated for Feisty by artbeall

Bug Description

Hi
My laptop ( kubuntu database id ca5b84feb92d322aff4d855e7ec121ce) was workung great in Edgy, I have made a clean install or Feisty, now if I got o suspend to ram, and then try to wake it up, it just stays blocked, nothing happens...

Revision history for this message
William Grant (wgrant) wrote :

Works fine for me. Is there any special hardware in it other than the defaults? (Bluetooth or an alternate graphics card, for example)

Revision history for this message
William Grant (wgrant) wrote :

When you wake it up, does the power light turn back on? If so, try closing the lid again for a few seconds, then reopening it. Sometimes the LCD might not turn on properly again.

Revision history for this message
mexlinux (mcanedo) wrote :

Just default hardware, no bluetooth, not any special device....

When it wakes up the power light turns back on, but the LCD does not turn on, if I type in blind, it does not seem to be responding (not even NumLock, or those keys, I will try the reclose lid, and will come back whit more info.

By the ways Hibernations works very god.

Revision history for this message
mexlinux (mcanedo) wrote :

Nothing happens if I close the lid, and nothing happens if I reopen it.

When it semi-awakes I can hear that the cdrom is being accessed,
Iwas wrong, keys like Num or Caps Lock, work, I mean they swith the leds.
But the sLCD creen keeps turned off.
And I hit keys like Ctrl-Alt-Back nothing happens
Or If I use the front multimedia keys trying to access amarok and start playing music, nothing.
Alt+F4 does nothing either....
I must keep the power button for a while in order to turn it off, and the turn on again.

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message
mexlinux (mcanedo) wrote :

uname -a
Linux mcanedo-laptop 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
mexlinux (mcanedo) wrote :
Changed in linux-source-2.6.20:
assignee: brian-murray → ubuntu-kernel-acpi
importance: Undecided → Medium
status: Needs Info → Confirmed
Revision history for this message
Robby (mail-otr-exchange) wrote :

Me and some other people of the German Ubuntu community have got the same problem:
http://forum.ubuntuusers.de/topic/87457/ (German)
http://forum.ubuntuusers.de/topic/88444/ (German)
http://forum.ubuntuusers.de/topic/88516 (German)
http://forum.ubuntuusers.de/topic/85757 (German)
http://forum.ubuntuusers.de/topic/83136 (German)

my uname -a (same as mexlinux):

Linux rfd 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
penguin (arnav316) wrote :

hey...i use feisty on an IBM t60 and have the same issued with the suspend but if i disable the Beryl manager and just use the gnome window manager that problem seems to get solved...are you using beryl by any chance?

Revision history for this message
mexlinux (mcanedo) wrote :

Just to inform, I have updated the kernel:
uname-a
Linux mcanedo-laptop 2.6.20-16-generic #2 SMP Wed May 23 01:46:23 UTC 2007 i686 GNU/Linux

Problem is still present

Revision history for this message
paenny (christoph900) wrote :

I've got also problems with suspend on my IBM t60p. I always get a black screen after trying to get back from suspend.
The hint of penguin does not work, i still have the problem when i disable Beryl manager.
Is there any chance the problem gets solved soon?

Revision history for this message
Robby (mail-otr-exchange) wrote :

Please set the importance to "high". Because of this bug notebookusers can't use Feisty. A lot downgraded to Edgy.

Revision history for this message
penguin (arnav316) wrote :

paenny..you're right...it only worked a couple of times as a fluke..but it hasn't solved the problem. the screen goes blank (or sometimes stuck on the screen saver) and the suspend to disk light just keeps flashing..seems like forcing the computer to shut down and restarting is the only thing?

Revision history for this message
mexlinux (mcanedo) wrote :

Agree with Roberto, importance should be High.
Why: It affects DELL laptops, which now should be a support target, no?

Revision history for this message
artbeall (artbeall) wrote :

I just want to confirm I am having the same problem but with a different Dell Laptop model. I have a Dell Inspiron 9300. My uname information is: uname -a Linux abeall-laptop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux. I would really like this bug fixed. Thanks.

Revision history for this message
DJ Wings (djwings) wrote :

Same problem on an E1505N. Installing 915resolution helps dramatically, but I still get it from time to time.

Revision history for this message
Robby (mail-otr-exchange) wrote :

Ah... Using a nvidia graphic card installing the nvidia-glx driver solves this problem. So maybe it's a bug in the x-server or the oss drivers...

Revision history for this message
mexlinux (mcanedo) wrote :

I have 915resolution installed since the begining...problem present

Revision history for this message
The Wired (markzep) wrote :

I have the same problem on a ibm t60, the system is set for the screen saver to come on after 5 min. this works fine. then it's set for the monitor to turn off after 10 min.
7 out of 10 times when i touch a key or move the mouse nothing will happen. the drive is spinning and all lights are on but the screen will not wake. if i close the lid and put the system to sleep when i open it it works fine. The temporary work around that works me is i press FN and space bar - this turns the screen back on with it zoomed then i press FN and spacbar again and it resumes the normal size.

Revision history for this message
mexlinux (mcanedo) wrote :

I do not have this problem on Gutsy Beta anymore.

Revision history for this message
gehzumteufel (gehzumteufel) wrote :

i am on gutsy final and have this problem.

2.6.22-14-generic #1 SMP

Revision history for this message
gehzumteufel (gehzumteufel) wrote :

forgot the other file. here it is

Revision history for this message
Charlie Daly (cdaly) wrote :

I have a Toshiba Satellite Pro, U200 running Gutsy with all the latest updates and I have this problem. On suspend to RAM, I briefly see a green grid which makes it look like the screen saver is working. Then the screen goes blank and then the FAN starts, which would indicate to me that the CPU is going full belt.
At this point, the computer doesn't respond to any thing except the power button and this normally has to be pressed for maybe 5 seconds.

If I suspend to RAM by closing the screen, then sometimes, the screen is restored, but the computer doesn't respond.

Linux charlie-laptop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

lspci-wnn.log attached.

Revision history for this message
Launchpad Janitor (janitor) wrote : This bug is now reported against the 'linux' package

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

*This is an automated response*

This bug report is being closed because we received no response to the previous request for information. Please reopen this if it is still an issue in the actively developed pre-release of Jaunty Jackalope 9.04 - http://cdimage.ubuntu.com/releases/jaunty . To reopen the bug report simply change the Status of the "linux" task back to "New".

Changed in linux:
status: Incomplete → Won't Fix
Curtis Hovey (sinzui)
Changed in linux-source-2.6.20 (Ubuntu):
assignee: Registry Administrators (registry) → nobody
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.