linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Albrecht Dre_ <ad@mpifr-bonn.mpg.de>
To: paulus@linuxcare.com.au
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Lombard Sleep Crash (Was: 2.2.18pre17 again)
Date: Fri, 27 Oct 2000 13:59:16 +0200	[thread overview]
Message-ID: <39F96E14.C06AB6FB@mpifr-bonn.mpg.de> (raw)
In-Reply-To: 14839.53124.753011.489351@argo.linuxcare.com.au


The rsync'ed 2.2.18pre17 kernel hangs if I try to wake up my Lombard after a
sleep. Sleeping seems to work (the LED binks), but upon wakeup it just stops
blinking, and nothing else. No reports in /var/log/messages, I just have to
reboot.

I had somewhat similar problems with Ben's 2.2.17pre20-ben3 kernel (however,
this one reported a panic in /var/log/messages), but 2.2.18pre15-ben1 (from
http://penguinppc.org/~olaf/) works fine.

Any ideas?

Thanks in advance, Albrecht.

--

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-10-27 11:59 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-26  6:30 2.2.18pre17 again Paul Mackerras
2000-10-26 14:19 ` Gabriel Paubert
2000-10-27  1:51 ` Paul Mackerras
2000-10-27  6:21 ` Martin Costabel
2000-10-27 11:59 ` Albrecht Dre_ [this message]
2000-10-27 14:39   ` Lombard Sleep Crash (Was: 2.2.18pre17 again) Olaf Hering
2000-11-02 12:34     ` Albrecht Dreß
2000-11-02 15:07       ` Claus
2000-11-02 15:28         ` Albrecht Dre_
2000-11-02 18:09           ` Benjamin Herrenschmidt
2000-11-03 10:13             ` Albrecht Dre_
2000-11-03 12:22               ` Michael Schmitz
2000-11-03 12:32                 ` Albrecht Dre_
2000-11-03 12:52                   ` Michael Schmitz
2000-11-03 14:11                     ` Albrecht Dre_
2000-11-03 14:52                       ` Michael Schmitz
2000-11-03 21:51                   ` Michael Schmitz
2000-11-02 15:35         ` Benjamin Herrenschmidt
2000-11-02 15:43           ` Michael Schmitz
2000-11-02 16:11             ` Benjamin Herrenschmidt
2000-11-02 17:13           ` Michael Schmitz
2000-11-03 15:22             ` Claus
2000-11-03 15:55               ` Benjamin Herrenschmidt
2000-11-03 21:53                 ` Michael Schmitz
2000-11-09  1:22                   ` Claus
2000-11-09  8:26                     ` Michael Schmitz
2000-11-02 17:23           ` Joseph P. Garcia
2000-11-02 18:06             ` Benjamin Herrenschmidt
2000-11-02 22:18               ` Michael Schmitz
2000-11-02 22:56       ` Olaf Hering
2000-11-08 20:35   ` Michael Schmitz
2000-11-08 20:54     ` Benjamin Herrenschmidt
2000-11-08 21:48       ` Michael Schmitz
2000-10-27 19:02 ` 2.2.18pre17 again Olaf Hering
2000-10-28  0:14   ` Olaf Hering
2000-10-31  6:49 ` Michel Lanners
2000-10-31 11:53   ` Benjamin Herrenschmidt
2000-10-31 14:03     ` Gabriel Paubert
2000-10-31 14:48       ` Benjamin Herrenschmidt
2000-10-31 17:20         ` Gabriel Paubert
2000-11-01  1:20           ` Dan Malek
2000-11-01  7:33     ` Michel Lanners
     [not found] <200011030559.XAA12796@lists.linuxppc.org>
2000-11-03 14:55 ` Lombard Sleep Crash (Was: 2.2.18pre17 again) Derek Homeier
2000-11-03 15:17   ` Michael Schmitz
2000-11-03 15:53   ` Benjamin Herrenschmidt
2000-11-03 15:59     ` Derek Homeier
  -- strict thread matches above, loose matches on Subject: below --
2000-11-03 15:42 nicola cabibbo

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=39F96E14.C06AB6FB@mpifr-bonn.mpg.de \
    --to=ad@mpifr-bonn.mpg.de \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@linuxcare.com.au \
    /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;
as well as URLs for NNTP newsgroup(s).