From: Stefan Seyfried <seife@suse.de>
To: Shawn Starr <shawn.starr@rogers.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [2.6.12-rc3][SUSPEND] qla1280 (QLogic 12160 Ultra3) blows up on A7M266-D
Date: Fri, 06 May 2005 23:34:02 +0200 [thread overview]
Message-ID: <427BE2CA.7030007@suse.de> (raw)
In-Reply-To: <20050503181018.37973.qmail@web88008.mail.re2.yahoo.com>
Shawn Starr wrote:
> I was feeling lucky yesterday and decided to try my
> luck on an A7M266-D with suspend-to-disk. I noticed
> two things
> 1) If I use XFS /w the SCSI controller (connected to 2
> IBM HD 10K Ultra3 SCSI disks) I can suspend to disk no
> problem, but resuming all hell breaks loose. It takes
> a half an hour to reload the swap memory dumped to
> disk.
Known, XFS was broken / breaking wrt suspend. Pavel fixed this with the
XFS guys IIRC and i think those patches were on lkml also, but am not
sure. => this should work soon.
> 2) If I use EXT3, suspending to disk is fine resuming
> is fine there is no long delay to load the swap memory
> back to RAM. But when it finishes resuming I get the
> same ISP error and the partition table gets corrupt as
> well.
> Is it likely this SCSI driver doesn't know how to
> handle suspend events?
Yes. Almost all drivers that are not commonly used in notebooks are
totally ignorant of suspend / resume. Even the brand new SATA driver
stuff (that is actually in almost every new notebook) had no suspend
support until some days ago.
--
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
next prev parent reply other threads:[~2005-05-06 22:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 18:10 [2.6.12-rc3][SUSPEND] qla1280 (QLogic 12160 Ultra3) blows up on A7M266-D Shawn Starr
2005-05-06 21:34 ` Stefan Seyfried [this message]
2005-05-07 8:25 ` Christoph Hellwig
2005-05-07 13:27 ` Stefan Seyfried
2005-05-09 6:45 ` Shawn Starr
2005-05-09 8:45 ` Stefan Seyfried
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=427BE2CA.7030007@suse.de \
--to=seife@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=shawn.starr@rogers.com \
/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;
as well as URLs for NNTP newsgroup(s).