From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [PATCH] ppc32: pmac sleep support update
Date: Thu, 20 Jan 2005 12:01:54 +1100 [thread overview]
Message-ID: <1106182915.5294.57.camel@gaston> (raw)
In-Reply-To: <jehdld7wx0.fsf@sykes.suse.de>
On Thu, 2005-01-20 at 01:43 +0100, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
>
> > Even when building xmon into the kernel ?
>
> Doh! I didn't think of that. This is what I get from xmon:
>
> <2>kernel BUG in unlock_page at mm/filemap.c:430!
> vector: 700 at pc = c003f098, lr = c0041654
> msr = 29032, sp = e71b1c80 [e71b1bd0]
> current = e7bbec70, pid = 2915, comm = syslogd
>
> c0041654 = generic_file_buffered_write
>
> Last kernel messages:
>
> radeonfb: switching to D0 state...
> HID1, after: 70000044
> cpufreq: resume failed to assert current frequency is what timing core thinks it is.
Weird ... Can you try without cpufreq built in the kernel ? Also what is
the exact CPU revision ? I think you are just experiencing memory
corruption...
Ben.
next prev parent reply other threads:[~2005-01-20 1:02 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 [this message]
2005-01-20 1:34 ` Andreas Schwab
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=1106182915.5294.57.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=akpm@osdl.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=schwab@suse.de \
--cc=torvalds@osdl.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.