From: Pavel Machek <pavel@ucw.cz>
To: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
Cc: Olivier Galibert <galibert@pobox.com>,
Andrew Robinson <andrew.rw.robinson@gmail.com>,
linux-kernel@vger.kernel.org
Subject: suspend to disk (was Re: ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means))
Date: Fri, 22 Dec 2006 20:34:17 +0000 [thread overview]
Message-ID: <20061222203417.GA3960@ucw.cz> (raw)
In-Reply-To: <4583B748.2080809@wolfmountaingroup.com>
Hi!
> >Stop spreading fud. Take powersave + suspend from
> >suse10.2, and see
> >if you can break it.
> >
> >sata_nv seems to have problem, that's it. and it
> >triggered problem in
> >reiserfs. Use ext3 if you care about your data, and yes
> >your drivers
> >need to support suspend/resume.
> >
> My Compaq laptop, a Presario 2200, has video lockups
> using suspend to disk and a dead system everytime I use
> it. I don't
Try with vga=1 (no framebuffer) and minimum number of modules.
> think its fud. I also conceed its not Linux's fault most
> of the time. These vendors put Windows specific hardware
suspend to ram is usually video bios problem; suspend to disk tends to
be linux problem.
Pavel
--
Thanks for all the (sleeping) penguins.
next prev parent reply other threads:[~2006-12-23 9:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-12 18:44 ReiserFS corruption with 2.6.19 (Was 2.6.19 is not stable with SATA and should not be used by any meansis not stable with SATA and should not be used by any means) Andrew Robinson
2006-12-12 19:28 ` Phillip Susi
2006-12-12 20:22 ` Jeff V. Merkey
2006-12-12 22:27 ` Phillip Susi
2006-12-12 22:16 ` Jeff V. Merkey
2006-12-12 22:45 ` Olivier Galibert
2006-12-15 16:15 ` Pavel Machek
2006-12-16 9:07 ` Jeffrey V. Merkey
2006-12-22 20:34 ` Pavel Machek [this message]
2006-12-13 8:37 ` Tejun Heo
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=20061222203417.GA3960@ucw.cz \
--to=pavel@ucw.cz \
--cc=andrew.rw.robinson@gmail.com \
--cc=galibert@pobox.com \
--cc=jmerkey@wolfmountaingroup.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome