[<prev] [next>] [day] [month] [year] [list]
Message-ID: <a44ae5cd0712202218p4ce66ff4r7b74c53ee2c23138@mail.gmail.com>
Date: Fri, 21 Dec 2007 01:18:53 -0500
From: "Miles Lane" <miles.lane@...il.com>
To: "Andrew Morton" <akpm@...ux-foundation.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"Christoph Lameter" <clameter@....com>,
"Pavel Machek" <pavel@...e.cz>, linux-pm@...ts.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)
Resending... Curse GMail's HTML messages!
On Dec 21, 2007 12:58 AM, Miles Lane <miles.lane@...il.com> wrote:
>
> On Dec 20, 2007 12:32 PM, Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> > On Thu, 20 Dec 2007 08:38:03 -0500 Miles Lane <miles.lane@...il.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@...tropy:~$ cat > test.sh
>
> while read i
> do
> echo $i
> sleep 1
> done < /proc/iomem
> ^C
> miles@...tropy:~$ 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?
>
> Thanks,
> Miles
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists