From: Tim Richardson <tim@tim-richardson.net>
To: linux-kernel@vger.kernel.org
Subject: kernel panic on resume from suspend to ram 2.6.38, with link to photo of screen
Date: Sun, 20 Mar 2011 22:58:50 +1100 [thread overview]
Message-ID: <4D85EBFA.70908@tim-richardson.net> (raw)
My laptop is a Toshiba U400 with intel graphics. BIOS is latest. It's
been running linux for three years, mostly Debian unstable.
Every 2.6.38 kernel I've tried gives a kernel panic on resume from ram
suspend. I have tried three different 2.6.38 kernels from aptosid (all
of them after release of 2.6.38) and the Debian unstable 2.6.38 which
has just entered repositories.
This happens even in run-level 3 (xserver not running).
However, suspend to disk resumes happily.
I don't have any closed source drivers used: video is intel, wireless is
intel, and virtualbox is OSE.
I have a photo of the console screen here:
https://picasaweb.google.com/te.richardson/Aptosid#5585718281112043778
PS I don't know is this is a kernel panic. The machine freezes hard, I
must force a power-down. I can't find the messages in the photo in any
system logs. The LED on the caps lock key flashes. This system has had
no problems with any kernels in recent memory.
reply other threads:[~2011-03-20 11:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4D85EBFA.70908@tim-richardson.net \
--to=tim@tim-richardson.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.