From: Mike Galbraith <efault@gmx.de>
To: nigel@nigel.suspend2.net
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19.2 oops after resume from ram (corruption?)
Date: Thu, 01 Feb 2007 06:30:34 +0100 [thread overview]
Message-ID: <1170307834.7087.16.camel@Homer.simpson.net> (raw)
In-Reply-To: <1170279722.5389.19.camel@nigel.suspend2.net>
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.
Rebuilding this particular kernel with slab debugging would probably be
a waste of time since stable kernels get very little runtime here, but
I'll re-add it to my config for test kernels just in case a survivable
event should happen.
-Mike
next prev parent reply other threads:[~2007-02-01 5:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 10:56 Mike Galbraith
2007-01-31 21:42 ` Nigel Cunningham
2007-02-01 5:30 ` Mike Galbraith [this message]
2007-02-01 5:39 ` Nigel Cunningham
2007-02-05 7:19 ` Luming Yu
2007-02-04 15:43 ` Pavel Machek
2007-02-05 6:55 ` Mike Galbraith
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=1170307834.7087.16.camel@Homer.simpson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
/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
all inboxes | Powered by JetHome®