From: Andrew Morton <akpm@linux-foundation.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"Christoph Lameter" <clameter@sgi.com>,
"Pavel Machek" <pavel@suse.cz>,
linux-pm@lists.linux-foundation.org,
Dave Airlie <airlied@linux.ie>
Subject: Re: OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume)
Date: Fri, 21 Dec 2007 12:00:00 -0800 [thread overview]
Message-ID: <20071221120000.b319b735.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0712210806i7f020a71k8c552953f7aeef4d@mail.gmail.com>
On Fri, 21 Dec 2007 11:06:49 -0500 "Miles Lane" <miles.lane@gmail.com> wrote:
> > >
> > > How do I determine what comes next?
> > >
> >
> > By comparing it with the /proc/iomem from prior to suspending the machine.
> >
>
> The offending information seems to be "90000000-90000fff : Intel Flush Page"
ah-hah. git-agpgart.patch
> I hope this helps,
It does, thanks.
Dave, a `cat /proc/iomem' crashes after a suspend/resume cycle when it
reaches the intel_private.ifp_resource record.
intel_i915_configure() is called on each resume and it calls
intel_i9xx_setup_flush() which zeroes out the already-registered `struct
resource', causing core kernel to oops over a deref of
parent/sibling/child.
Probably this:
--- a/drivers/char/agp/intel-agp.c~a
+++ a/drivers/char/agp/intel-agp.c
@@ -883,8 +883,6 @@ static void intel_i965_g33_setup_chipset
static void intel_i9xx_setup_flush(void)
{
/* setup a resource for this object */
- memset(&intel_private.ifp_resource, 0, sizeof(intel_private.ifp_resource));
-
intel_private.ifp_resource.name = "Intel Flush Page";
intel_private.ifp_resource.flags = IORESOURCE_MEM;
_
will be enough to prevent the crash, but I suspect a bit more than that
will be needed.
next prev parent reply other threads:[~2007-12-21 20:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-20 4:40 OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 Miles Lane
2007-12-20 4:48 ` OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem") Miles Lane
2007-12-20 5:35 ` Miles Lane
2007-12-20 6:03 ` Andrew Morton
2007-12-20 10:53 ` Alexey Dobriyan
2007-12-20 11:37 ` David Howells
2007-12-20 12:54 ` Miles Lane
2007-12-20 9:10 ` Russell King
2007-12-20 13:38 ` OOPS: 2.6.24-rc5-mm1 -- EIP is at r_show+0x2a/0x70 -- (triggered by "cat /proc/iomem" AFTER suspend-to-disk/resume) Miles Lane
2007-12-20 17:32 ` Andrew Morton
[not found] ` <a44ae5cd0712202158u31c8b4e1lf5b0df89dde20e7e@mail.gmail.com>
2007-12-21 6:18 ` Miles Lane
2007-12-21 6:29 ` Andrew Morton
2007-12-21 16:06 ` Miles Lane
2007-12-21 20:00 ` Andrew Morton [this message]
2007-12-21 21:18 ` Miles Lane
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=20071221120000.b319b735.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@linux.ie \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=miles.lane@gmail.com \
--cc=pavel@suse.cz \
/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