From: Andreas Schwab <schwab@suse.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] ppc32: pmac sleep support update
Date: Thu, 20 Jan 2005 02:34:24 +0100 [thread overview]
Message-ID: <jed5w0993z.fsf@sykes.suse.de> (raw)
In-Reply-To: <1106182915.5294.57.camel@gaston> (Benjamin Herrenschmidt's message of "Thu, 20 Jan 2005 12:01:54 +1100")
Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>> cpufreq: resume failed to assert current frequency is what timing core thinks it is.
>
> Weird ... Can you try without cpufreq built in the kernel ?
I think this message is unrelated to the problem, it occurs with all
kernels so far.
> Also what is the exact CPU revision ?
It's a 750FX revision 1.18.
> I think you are just experiencing memory corruption...
Yes, I agree, I get completely different crashes whenever I use a slightly
different kernel.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-01-20 1:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-18 1:32 [PATCH] ppc32: pmac sleep support update Benjamin Herrenschmidt
2005-01-19 1:37 ` Andreas Schwab
2005-01-19 2:04 ` Benjamin Herrenschmidt
2005-01-19 21:49 ` Andreas Schwab
2005-01-19 22:57 ` Benjamin Herrenschmidt
2005-01-20 0:43 ` Andreas Schwab
2005-01-20 1:01 ` Benjamin Herrenschmidt
2005-01-20 1:34 ` Andreas Schwab [this message]
2005-01-20 2:23 ` Benjamin Herrenschmidt
2005-01-19 13:45 ` David Woodhouse
2005-01-19 22:44 ` Benjamin Herrenschmidt
2005-02-03 12:57 ` Olaf Hering
2005-02-03 22:15 ` Benjamin Herrenschmidt
2005-02-26 11:28 ` Olaf Hering
2005-02-27 0:24 ` 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=jed5w0993z.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).