public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 23 Jan 2007 15:42:33 +1100	[thread overview]
Message-ID: <45B59239.90403@usherbrooke.ca> (raw)
In-Reply-To: <20070122132545.GA4493@ucw.cz>

>>> will be a device driver. Common causes of suspend/resume problems from
>>> the list you give below are acpi modules, bluetooth and usb. I'd also be
>>> consider pcmcia, drm and fuse possibilities. But again, go for unloading
>>> everything possible in the first instance.
>> Actually, the reason I sent this is that when I showed the oops/gpf to
>> Matthew Garrett at linux.conf.au, he said it looked like a CPU hotplug
>> problem and suggested I send it to lkml. BTW, with 2.6.20-rc5, the
>> suspend to RAM now works ~95% of the time.
> 
> Try a kernel without CONFIG_SMP... that will verify if it is SMP
> related.

Well, this happens to be my main work machine, which I'm not willing to
have running at half speed for several weeks. Anything else you can suggest?

	Jean-Marc

  reply	other threads:[~2007-01-23  4:42 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 [this message]
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
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=45B59239.90403@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