[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <3877989d0702042319x61230492nc0fc1ed0fa3d58a4@mail.gmail.com>
Date: Mon, 5 Feb 2007 15:19:33 +0800
From: "Luming Yu" <luming.yu@...il.com>
To: "Mike Galbraith" <efault@....de>
Cc: nigel@...el.suspend2.net, LKML <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19.2 oops after resume from ram (corruption?)
On 2/1/07, Mike Galbraith <efault@....de> wrote:
> On Thu, 2007-02-01 at 08:42 +1100, Nigel Cunningham wrote:
> > Hi.
> >
> > On Wed, 2007-01-31 at 11:56 +0100, Mike Galbraith wrote:
> > > Greetings,
> > >
> > > I received the below upon first poke of firefox icon after a resume.
> >
> > Are you able to reproduce it reliably? Failing that, could you try
> > enabling some the kernel configuration options that help with debugging
> > memory corruption (slab corruption checking in particular will probably
> > be the most useful thing here).
>
> No, it's a never before seen event. That said, I have had a couple of
> dead box after resume events with other kernels in the last few months,
> so I may have had corruption of a more deadly variety. Unfortunately,
> when I'm resuming, my serial console box is almost guaranteed to be off.
if you have dead serial console, or no serial console at all on you
laptop. Probably you can try the alternative of firewire with
http://www.suse.de/~bk/firewire/
Ah, linux S3 resume is still a problem.
-
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