From: Jean-Marc Valin <jean-marc.valin@usherbrooke.ca>
To: Pavel Machek <pavel@ucw.cz>
Cc: nigel@nigel.suspend2.net, linux-kernel@vger.kernel.org
Subject: Re: Suspend to RAM generates oops and general protection fault
Date: Fri, 23 Mar 2007 23:34:24 +1100 [thread overview]
Message-ID: <4603C950.30001@usherbrooke.ca> (raw)
In-Reply-To: <20070122132545.GA4493@ucw.cz>
Hi,
Sorry I haven't replied recently about that bug, but I have to admit I
have no idea where to start. There actually seems to be much more
fundamental problems with the kernel on my machines. I initially
realised that even without using suspend to RAM, I was still getting
crashes when docking. So I stopped docking and realised my machine would
sometimes just crash when I plug/unplug the AC adaptor. Just to give an
idea, I've experienced about 10-15 crashes in the past two months -- I
don't think I've even done a single clean shutdown during that period.
To make things worse, the behaviour is always different. Sometimes I get
a panic with keyboard LEDs flashing. Sometimes I get nothing at all and
the machine is just frozen (doesn't respond to pings or to Alt-SysRq
commands). Sometimes, I just lose my keyboard and/or mouse but the
machine stays up. I'm running a vanilla 2.6.20 kernel (not tainted) with
the following configuration: http://jmspeex.livejournal.com/1090.html
Jean-Marc
next prev parent reply other threads:[~2007-03-23 12:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-22 2:34 Suspend to RAM generates oops and general protection fault Jean-Marc Valin
2007-01-22 3:23 ` Nigel Cunningham
2007-01-22 5:16 ` Jean-Marc Valin
2007-01-22 5:19 ` Nigel Cunningham
2007-01-22 13:25 ` Pavel Machek
2007-01-23 4:42 ` Jean-Marc Valin
2007-01-23 7:11 ` Luming Yu
2007-01-23 14:53 ` Jean-Marc Valin
2007-01-23 15:05 ` Luming Yu
2007-03-23 12:34 ` Jean-Marc Valin [this message]
2007-01-22 11:59 ` Rafael J. Wysocki
2007-01-23 4:38 ` Jean-Marc Valin
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=4603C950.30001@usherbrooke.ca \
--to=jean-marc.valin@usherbrooke.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@nigel.suspend2.net \
--cc=pavel@ucw.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