public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: davidw@dedasys.com (David N. Welton)
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@lists.linuxppc.org>,
	j.s@lmu.de, Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.8 (or 7?) regression: sleep on older tibooks broken
Date: 16 Aug 2004 16:10:55 +0200	[thread overview]
Message-ID: <873c2n41hs.fsf@dedasys.com> (raw)
In-Reply-To: 1092569364.9539.16.camel@gaston

Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:

> On Sun, 2004-08-15 at 18:45, David N. Welton wrote:

> > but it's not the same problem... I removed the ohci_hcd module
> > from the kernel (it's present at boot), and sleep still doesn't
> > happen.  I don't even get the "breathing" light, and yet the
> > computer still seems warm after some time, seemingly indicative
> > that it's not really asleep or dead.  I can only restart it via
> > the Ctrl-Command-Power combination.

> Best thing at this point is to hack out the sleep code in the video
> driver to see where it dies during the sleep process...

I made the video driver's sleep routing return 0 immediately.

That was enough to at least get a couple of reports from xmon about a
vector 200 corresponding to an address in powerbook_sleep_Core99...
Still investigating, but this is new territory for me, and it's
certainly at a tricky moment in the life of the kernel.  Suggestions
appreciated as to what might have changed and what to look for.

Thankyou,
-- 
David N. Welton
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/
       Photos: http://www.dedasys.com/photos/

  reply	other threads:[~2004-08-16 14:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-15  8:45 2.6.8 (or 7?) regression: sleep on older tibooks broken David N. Welton
2004-08-15 11:29 ` Benjamin Herrenschmidt
2004-08-16 14:10   ` David N. Welton [this message]
2004-08-16 15:08     ` Benjamin Herrenschmidt
2004-08-16 16:02       ` David N. Welton
2004-08-16 18:38         ` David N. Welton
2004-08-17  7:52           ` Benjamin Herrenschmidt
2004-08-17  8:26             ` David N. Welton
2004-08-17  8:52               ` Benjamin Herrenschmidt
2004-08-17 12:57                 ` David N. Welton
2004-08-21 20:42                   ` David N. Welton
2004-08-21 22:11                     ` Eugene Surovegin
2004-08-22  1:58                     ` Benjamin Herrenschmidt
2004-08-17  3:42         ` Benjamin Herrenschmidt

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=873c2n41hs.fsf@dedasys.com \
    --to=davidw@dedasys.com \
    --cc=benh@kernel.crashing.org \
    --cc=j.s@lmu.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.linuxppc.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