All of lore.kernel.org
 help / color / mirror / Atom feed
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
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: Thu, 20 Dec 2007 22:29:13 -0800	[thread overview]
Message-ID: <20071220222913.92a2c19f.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0712202158u31c8b4e1lf5b0df89dde20e7e@mail.gmail.com>

On Fri, 21 Dec 2007 00:58:19 -0500 "Miles Lane" <miles.lane@gmail.com> wrote:

> On Dec 20, 2007 12:32 PM, Andrew Morton <akpm@linux-foundation.org> wrote:
> 
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <miles.lane@gmail.com>
> > wrote:
> >
> > > On further investigation, "cat /proc/iomem" does not trigger the stack
> > > trace until after a suspend-to-disk/resume cycle has occurred.
> >
> > I still can't reproduce this.
> >
> > Could you please try this?
> >
> > - cat /proc/iomem
> > - suspend/resume
> > - do
> >
> > while read i
> > do
> > echo $i
> > sleep 1
> > done < /proc/iomem
> >
> > then, with luck, we'll be able to work out which /proc/iomem record
> > immediately precedes the corrupted one.
> >
> 
> miles@syntropy:~$ cat > test.sh
> while read i
> do
> echo $i
> sleep 1
> done < /proc/iomem
> ^C
> miles@syntropy:~$ sh test.sh
> 00000000-0009f7ff : System RAM
> 0009f800-0009ffff : reserved
> 000a0000-000bffff : Video RAM area
> 000c0000-000c7fff : Video ROM
> 000f0000-000fffff : System ROM
> 00100000-7f68ffff : System RAM
> 00100000-0039e4b7 : Kernel code
> 0039e4b8-004f0983 : Kernel data
> 00553000-007ecdfb : Kernel bss
> 7f690000-7f698fff : ACPI Tables
> 7f699000-7f6fffff : ACPI Non-volatile Storage
> 7f700000-7fffffff : reserved
> 88000000-8bffffff : PCI CardBus #05
> 8c000000-8fffffff : PCI CardBus #05
> Segmentation fault
> 
> How do I determine what comes next?
> 

By comparing it with the /proc/iomem from prior to suspending the machine.

  parent reply	other threads:[~2007-12-21  6:29 UTC|newest]

Thread overview: 23+ 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
2007-12-20 17:32       ` Andrew Morton
2007-12-21  5:58         ` Miles Lane
2007-12-21  6:18           ` Miles Lane
2007-12-21  6:18           ` Miles Lane
2007-12-21  6:29           ` Andrew Morton
2007-12-21  6:29           ` Andrew Morton [this message]
2007-12-21 16:06             ` Miles Lane
2007-12-21 20:00               ` Andrew Morton
2007-12-21 21:18                 ` Miles Lane
2007-12-21 21:18                   ` Miles Lane
2007-12-21 20:00               ` Andrew Morton
2007-12-21 16:06             ` Miles Lane
2007-12-20 13:38     ` 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=20071220222913.92a2c19f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --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 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.