From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Derrik Pates <dpates@dsdk12.net>, <linuxppc-dev@lists.linuxppc.org>
Subject: Re: 2.4.17-pre[12]-ben0 trees hang on unsuspend
Date: Sun, 2 Dec 2001 17:01:30 +0100 [thread overview]
Message-ID: <20331103021714.8497@smtp.wanadoo.fr> (raw)
In-Reply-To: <Pine.LNX.4.40.0112020854520.27544-100000@andromeda.dsdk12.net>
>On Sun, 2 Dec 2001, Benjamin Herrenschmidt wrote:
>
>> Could be one of my sleep.S changes, let me check...
>
>I diff'd 2.4.16-ben0's sleep.S and 2.4.17-pre2-ben0's sleep.S, then
>commented out the added stuff for register save/restore on 74x0 PPCs. That
>seems to have corrected the problem - the system now wakes up correctly
>from sleep, exactly as before. Any idea what's happening there? It looks
>like that stuff shouldn't even be getting called for non-74x0 PPC
>processors (/proc/cpuinfo IDs this system's CPU as a 750CX), so one of the
>processor-type checks apparently isn't working quite right.
Some bug in the assembly. I fixed it.
Ben.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-12-02 16:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-02 4:45 2.4.17-pre[12]-ben0 trees hang on unsuspend Derrik Pates
2001-12-02 9:51 ` Benjamin Herrenschmidt
2001-12-02 15:58 ` Derrik Pates
2001-12-02 16:01 ` Benjamin Herrenschmidt [this message]
2001-12-02 21:03 ` Derrik Pates
2001-12-02 21:07 ` Derrik Pates
2001-12-04 22:53 ` Jörn Nettingsmeier
2001-12-04 22:52 ` Jörn Nettingsmeier
2001-12-04 23:12 ` Benjamin Herrenschmidt
2001-12-05 10:06 ` Jörn Nettingsmeier
2001-12-05 10:37 ` Benjamin Herrenschmidt
[not found] <3C1222A8.59C17879@folkwang-hochschule.de>
[not found] ` <20011208164612.1404@smtp.wanadoo.fr>
2001-12-08 19:31 ` Jörn Nettingsmeier
2001-12-08 20:05 ` Benjamin Herrenschmidt
2001-12-09 18:00 ` Michael Schmitz
2001-12-09 22:29 ` Jörn Nettingsmeier
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=20331103021714.8497@smtp.wanadoo.fr \
--to=benh@kernel.crashing.org \
--cc=dpates@dsdk12.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.