public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Patrick <ragamuffin@datacomm.ch>
Cc: linux-kernel@vger.kernel.org
Subject: Re: SB600 AHCI: Hard Disk Corruption
Date: Sun, 25 May 2008 19:38:25 +0200	[thread overview]
Message-ID: <20080525173825.GA4132@ucw.cz> (raw)
In-Reply-To: <1211717435.6038.53.camel@localhost.localdomain>

Hi!

> I've got an annoying problem with my athlon 64bit, 4gb ram, ???asus m2a-vm
> (->SB600 AHCI controller), SAMSUNG HD501LJ SATA Disk. I'm using kernel
> 2.6.26-rc3. Everything works fine, expect for standby/suspend/hibernate.
> Standby freezes, hibernate, I acually ???haven't tested lately cause I
> want suspend to ram to work first.
> 
> "echo mem > /sys/power/state; vbetool post;" (on text console)
> successfully suspends the system and it resumes as well, BUT: After
> resuming, things quickly turn bad: "file not fonund", kernel reports

iommu problem? Try it with mem=3G.

> * I read many threads in which Tejun provided patches for the SB600 AHCI
> Controller which seems to be seriously broken - if only i knew that in
> advance... Maybe he can fix this issue as well - last ressort. Otherwise
> I'll burn that mobo!

I suspect all you need is to burn one dimm.. or send it to me so that
I can reproduce it ;-).

> ???** After my firs install and configuring the system for a day, trying
> out suspend to ram smashed it with no backups, since then i didn't learn
> my lesson and smashed it again 2-3 times, this time with backups at hand
> though, ...

Boot it from cd ;-).

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  parent reply	other threads:[~2008-05-25 17:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-25 12:10 SB600 AHCI: Hard Disk Corruption Patrick
2008-05-25 12:16 ` Patrick
2008-05-25 17:38 ` Pavel Machek [this message]
2008-05-25 20:08   ` Patrick
2008-05-25 20:39     ` >3G => iommu => suspend problems -- was " Pavel Machek
2008-05-25 21:10       ` Pavel Machek
2008-05-26 15:31         ` Patrick
2008-05-27 11:22           ` Pavel Machek
2008-05-29 18:44             ` Patrick
2008-05-29 18:51               ` Patrick
2008-05-29 21:05               ` Patrick
2008-06-03 22:33             ` Rafael J. Wysocki
2008-06-06 13:20               ` Pavel Machek
2008-06-08 22:36                 ` Rafael J. Wysocki
     [not found]                   ` <20080609124630.GA28799@elte.hu>
2008-06-09 22:10                     ` [PATCH] x86 GART: Add resume handling (was: Re: >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption) Rafael J. Wysocki
2008-06-10 10:03                       ` Rafael J. Wysocki
2008-06-12  9:34                         ` Ingo Molnar
2008-06-11 11:43                   ` >3G => iommu => suspend problems -- was Re: SB600 AHCI: Hard Disk Corruption Patrick
2008-06-11 14:38                     ` Rafael J. Wysocki
2008-06-11 15:04                       ` Andi Kleen
2008-07-03 17:35                         ` Patrick
2008-08-07  8:17                           ` Pavel Machek
2008-08-08 22:40                             ` Patrick
2008-09-02  8:05                               ` Pavel Machek
2008-05-27 10:23         ` Pavel Machek

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=20080525173825.GA4132@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ragamuffin@datacomm.ch \
    /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