Hi,
I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
seems like the longer my uptime, the more likely the problem is to occur
(which makes it hard to reproduce sometimes). This happens even with a
non-preempt kernel.
I posted my .config here
http://people.xiph.org/~jm/config-2.6.13-i386
My hardware is:
Dell Latitude D600 (Bios rev. A14)
Pentium-M 1.6 GHz / 1 GB RAM
ATI Technologies, Inc. Radeon Mobility 9000 M9 (R250 Lf)
Any idea how to solve this?
Jean-Marc
P.S. Please CC to me as I'm not subscribed to the list.
--
Jean-Marc Valin <[email protected]>
Universit? de Sherbrooke
Hi!
> I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> seems like the longer my uptime, the more likely the problem is to occur
> (which makes it hard to reproduce sometimes). This happens even with a
> non-preempt kernel.
Check if it works with minimal drivers and non-preemptible kernel...
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
Hi,
> > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > seems like the longer my uptime, the more likely the problem is to occur
> > (which makes it hard to reproduce sometimes). This happens even with a
> > non-preempt kernel.
>
> Check if it works with minimal drivers and non-preemptible kernel...
I checked with 1) a minimal drivers on a preempt kernel and 2) with a
few more drivers (usb mouse) and a non-preempt kernel. Both didn't wake
up when I suspended after a few days of uptime (right after boot, it's
fine). The default Ubuntu kernel is a preempt-enabled 2.6.10 kernel and
it always resumed from suspend, even with usb devices plugged in (I
still had to reload the driver though). As I said, it's not trivial to
test, because it takes a while before the bug occurs.
Jean-Marc
--
Jean-Marc Valin <[email protected]>
Universit? de Sherbrooke
> > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > seems like the longer my uptime, the more likely the problem is to occur
> > (which makes it hard to reproduce sometimes). This happens even with a
> > non-preempt kernel.
>
> Check if it works with minimal drivers and non-preemptible kernel...
OK, I can confirm failure to resume even on a non-preempt 2.6.13 with no
USB devices and lots of stuff (e.g. wifi card) turned off. So far,
2.6.10 is resuming (running a non-Ubuntu vanilla 2.6.10 now).
Jean-Marc
Hi,
I've done some further testing on suspend to RAM and it seems like it
got broken for me between 2.6.11 and 2.6.12. Does that help narrowing
down the problem?
Jean-Marc
Le vendredi 23 septembre 2005 ? 18:32 +0200, Pavel Machek a ?crit :
> Hi!
>
> > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > seems like the longer my uptime, the more likely the problem is to occur
> > (which makes it hard to reproduce sometimes). This happens even with a
> > non-preempt kernel.
>
> Check if it works with minimal drivers and non-preemptible kernel...
On P? 07-10-05 15:32:25, Jean-Marc Valin wrote:
> Hi,
>
> I've done some further testing on suspend to RAM and it seems like it
> got broken for me between 2.6.11 and 2.6.12. Does that help narrowing
> down the problem?
Well, you'd have to track it down in a bit more specific way. If you
can narrow it down to specific day, or even better with binary search,
it will help.
Pavel
> Le vendredi 23 septembre 2005 ? 18:32 +0200, Pavel Machek a ?crit :
> > Hi!
> >
> > > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > > seems like the longer my uptime, the more likely the problem is to occur
> > > (which makes it hard to reproduce sometimes). This happens even with a
> > > non-preempt kernel.
> >
> > Check if it works with minimal drivers and non-preemptible kernel...
--
if you have sharp zaurus hardware you don't need... you know my address
> > I've done some further testing on suspend to RAM and it seems like it
> > got broken for me between 2.6.11 and 2.6.12. Does that help narrowing
> > down the problem?
>
> Well, you'd have to track it down in a bit more specific way. If you
> can narrow it down to specific day, or even better with binary search,
> it will help.
Any tip on which version to try first, i.e. when were potentially
problematic patches merged? Keep in mind that it can take several days
to trigger the problem (resume always works on a freshly booted system),
so systematically testing everything (even as a binary search) isn't
really an option. Maybe there a way to recover some information about
what exactly went wrong?
Jean-Marc
> > Le vendredi 23 septembre 2005 ? 18:32 +0200, Pavel Machek a ?crit :
> > > Hi!
> > >
> > > > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > > > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > > > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > > > seems like the longer my uptime, the more likely the problem is to occur
> > > > (which makes it hard to reproduce sometimes). This happens even with a
> > > > non-preempt kernel.
> > >
> > > Check if it works with minimal drivers and non-preemptible kernel...
>
>
>
On P? 07-10-05 19:50:49, Jean-Marc Valin wrote:
> > > I've done some further testing on suspend to RAM and it seems like it
> > > got broken for me between 2.6.11 and 2.6.12. Does that help narrowing
> > > down the problem?
> >
> > Well, you'd have to track it down in a bit more specific way. If you
> > can narrow it down to specific day, or even better with binary search,
> > it will help.
>
> Any tip on which version to try first, i.e. when were potentially
> problematic patches merged? Keep in mind that it can take several
>days
No ideas, 2.6.12 is *long* ago :-(.
Pavel
--
if you have sharp zaurus hardware you don't need... you know my address