From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 16019] Resume from hibernate corrupts ext4
Date: Mon, 24 May 2010 17:00:07 GMT [thread overview]
Message-ID: <201005241700.o4OH07OE029883@demeter.kernel.org> (raw)
In-Reply-To: <bug-16019-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=16019
--- Comment #18 from David Lowe <lowe@brown.edu> 2010-05-24 17:00:01 ---
(In reply to comment #17)
> Based on another internal redhat bug suggestion - does booting with the
> "iommu=soft" kernel parameter affect the bug at all?
>
> thanks,
> -Eric
Back in Fedora 11 everything was working fine. With Fedora 12 so many things
regressed at the same time that testing was impractical (I think mostly intel
stack related...). I think suspend to ram worked fine, and hibernation would
just freeze. However with Fedora 13 I am really just left with this one
problem, hibernation.
iommu=soft gave me one clean hibernation from inside gnome, but the second
attempt gave me the same ext4-fs errors
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
next prev parent reply other threads:[~2010-05-24 17:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 22:49 [Bug 16019] New: Resume from hibernate corrupts ext4 bugzilla-daemon
2010-05-20 22:55 ` [Bug 16019] " bugzilla-daemon
2010-05-20 23:00 ` bugzilla-daemon
2010-05-20 23:36 ` bugzilla-daemon
2010-05-21 0:11 ` bugzilla-daemon
2010-05-21 10:36 ` bugzilla-daemon
2010-05-21 17:11 ` bugzilla-daemon
2010-05-21 18:00 ` bugzilla-daemon
2010-05-21 18:04 ` bugzilla-daemon
2010-05-21 18:25 ` bugzilla-daemon
2010-05-21 19:59 ` bugzilla-daemon
2010-05-22 0:37 ` bugzilla-daemon
2010-05-22 0:40 ` bugzilla-daemon
2010-05-22 4:34 ` bugzilla-daemon
2010-05-22 17:03 ` bugzilla-daemon
2010-05-22 17:10 ` bugzilla-daemon
2010-05-24 14:59 ` bugzilla-daemon
2010-05-24 17:00 ` bugzilla-daemon [this message]
2010-05-28 23:03 ` bugzilla-daemon
2010-06-01 16:02 ` bugzilla-daemon
2010-06-16 3:10 ` bugzilla-daemon
2010-06-17 15:49 ` bugzilla-daemon
2010-06-17 15:51 ` bugzilla-daemon
2010-06-17 16:28 ` bugzilla-daemon
2010-06-17 16:35 ` bugzilla-daemon
2010-06-17 16:47 ` bugzilla-daemon
2010-06-17 19:16 ` bugzilla-daemon
2010-06-17 19:24 ` bugzilla-daemon
2010-06-17 21:37 ` bugzilla-daemon
2010-06-17 21:45 ` bugzilla-daemon
2010-06-17 23:37 ` bugzilla-daemon
2010-06-18 6:32 ` bugzilla-daemon
2010-06-18 9:40 ` bugzilla-daemon
2010-06-18 13:59 ` bugzilla-daemon
2010-06-18 14:39 ` bugzilla-daemon
2010-06-18 14:51 ` bugzilla-daemon
2010-06-18 14:52 ` bugzilla-daemon
2010-07-01 5:04 ` bugzilla-daemon
2010-07-16 21:15 ` bugzilla-daemon
2010-07-27 20:37 ` bugzilla-daemon
2011-01-16 22:34 ` bugzilla-daemon
2011-01-17 18:14 ` bugzilla-daemon
2011-01-30 11:13 ` bugzilla-daemon
2011-02-15 15:31 ` bugzilla-daemon
2011-03-21 15:04 ` bugzilla-daemon
2011-05-25 21:10 ` bugzilla-daemon
2011-05-26 16:32 ` bugzilla-daemon
2012-01-18 2:10 ` bugzilla-daemon
2012-05-24 7:34 ` bugzilla-daemon
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=201005241700.o4OH07OE029883@demeter.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@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.