public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jeffrey V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Olivier Galibert <galibert@pobox.com>,
	Andrew Robinson <andrew.rw.robinson@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: 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: Sat, 16 Dec 2006 02:07:20 -0700	[thread overview]
Message-ID: <4583B748.2080809@wolfmountaingroup.com> (raw)
In-Reply-To: <20061215161544.GC4551@ucw.cz>

Pavel Machek wrote:

>On Tue 12-12-06 23:45:27, Olivier Galibert wrote:
>  
>
>>On Tue, Dec 12, 2006 at 11:44:18AM -0700, Andrew Robinson wrote:
>>    
>>
>>>When I said hibernate, I did mention it was to disk, not to ram.
>>>      
>>>
>>Suspend to disk is not trustable on Linux, and does not look like it
>>will be any time soon.  Suspend to ram has a better chance of becoming
>>    
>>
>
>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.
>							Pavel
>  
>
My Compaq laptop, a Presario 2200, has video lockups using suspend to 
disk and a dead system everytime I use it. I don't
think its fud. I also conceed its not Linux's fault most of the time. 
These vendors put Windows specific hardware support
into these systems. My laptop has a dozen strange keys that work only on 
Windows and if you push one of them in Linux,
the system looses state with the keyboard and croaks ( have to reboot to 
recover). If I close the lid of my latop or do any other
suspend to disk state, the video display is croaked.

Jeff

  reply	other threads:[~2006-12-16  7:56 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 [this message]
2006-12-22 20:34       ` 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)) Pavel Machek
2006-12-13  8:37 ` 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) 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=4583B748.2080809@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=andrew.rw.robinson@gmail.com \
    --cc=galibert@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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