mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: linux-kernel@vger.kernel.org
Subject: Suspend on Dell D420
Date: Fri, 4 Aug 2006 18:23:00 +0200	[thread overview]
Message-ID: <20060804162300.GA26148@uio.no> (raw)

[Please Cc me on any followups]

Hi,

Suspend-to-RAM works fine on my new Dell Latitude D420 (with Core Duo) in
2.6.16, but it broke in 2.6.17 -- the machine suspends just fine, but when it
resumes, the disk never spins up, the screen stays black and it just hangs.
Bisecting shows that the following commit is where it broke:

commit 78eef01b0fae087c5fadbd85dd4fe2918c3a015f
Author: Andrew Morton <akpm@osdl.org>
Date:   Wed Mar 22 00:08:16 2006 -0800
 
    [PATCH] on_each_cpu(): disable local interrupts
 
    When on_each_cpu() runs the callback on other CPUs, it runs with local
    interrupts disabled.  So we should run the function with local interrupts
    disabled on this CPU, too.
 
    And do the same for UP, so the callback is run in the same environment on both
    UP and SMP.  (strictly it should do preempt_disable() too, but I think
    local_irq_disable is sufficiently equivalent).
 
    Also uninlines on_each_cpu().  softirq.c was the most appropriate file I could
    find, but it doesn't seem to justify creating a new file.
 
    Oh, and fix up that comment over (under?) x86's smp_call_function().  It
    drives me nuts.

Applying the patch in reverse against 2.6.17 (it doesn't apply cleanly, but
I've done what seems to be the moral equivalent) makes the suspend work
again.

Any ideas? It does not work with the latest git checkout as of today.

/* Steinar */
-- 
Homepage: http://www.sesse.net/

             reply	other threads:[~2006-08-04 16:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04 16:23 Steinar H. Gunderson [this message]
2006-08-04 21:27 ` Rafael J. Wysocki
2006-08-04 22:17   ` Andrew Morton
2006-08-04 23:26     ` Rafael J. Wysocki
2006-08-05  8:23       ` Steinar H. Gunderson
2006-08-05  9:08         ` Rafael J. Wysocki
2006-08-06 11:50           ` Steinar H. Gunderson
2006-08-06 23:10             ` Pavel Machek
2006-08-06 23:15               ` Steinar H. Gunderson
2006-08-17 15:00                 ` Pavel Machek
2006-08-08 14:04             ` Rafael J. Wysocki
2006-08-08 15:01               ` Steinar H. Gunderson
2006-08-08 15:41                 ` Rafael J. Wysocki
2006-08-09  0:21                   ` Pavel Machek
2006-08-09  8:44                     ` Steinar H. Gunderson
2006-08-09  9:02                       ` Pavel Machek
2006-08-09  9:05                         ` Steinar H. Gunderson
2006-08-09  9:08                           ` Pavel Machek
2006-08-09  9:17                             ` Steinar H. Gunderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060804162300.GA26148@uio.no \
    --to=sgunderson@bigfoot.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome