From: Michael Leun <ml@newton.leun.net>
To: linux-kernel@vger.kernel.org
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
richard -rw- weinberger <richard.weinberger@gmail.com>,
nigel@tuxonice.net
Subject: What about bugzilla.kernel.org / Bug 37142 / Tuxonice developer going to quit development
Date: Tue, 1 Nov 2011 11:14:20 +0100 [thread overview]
Message-ID: <20111101111420.1667f3aa@xenia.leun.net> (raw)
Is there any timeline for bringing bugzilla.kernel.org up again?
I'm mainly asking because I was tracking
Bug 37142 – [GM965/KMS/UXA] memory corruption on resume from hibernate
a memory corruption issue which is around for quite some time, see
http://thread.gmane.org/gmane.linux.kernel/1116939/focus=1117113
that was March 2011. I suspect this bug might be there since
introduction of KMS.
My workaround since I noticed that bug was to use tuxonice for suspend
to disk, what works perfectly (that in particular means without memory
corruption), but unfortunately the current developer of tuxonice, Nigel
Cunningham is going to stop development, see
http://lists.tuxonice.net/pipermail/tuxonice-users/2011-November/000945.html
Rafael, Richard: What do you think is the current state of this bug?
Was it ever fixed for you?
As far as I remember in bugzilla 37142 there were patches floating
around, but they did'nt make any change for me. I didn't notice any
change on that bug until kernel.org went down due to that security
issue.
At the moment I'm compiling a vanilla 3.1 to see if I still see this
bug.
--
MfG,
Michael Leun
next reply other threads:[~2011-11-01 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 10:14 Michael Leun [this message]
2011-11-01 10:40 ` Nigel Cunningham
2011-11-01 12:01 ` richard -rw- weinberger
2011-11-01 12:18 ` Michael Leun
2011-11-01 12:20 ` richard -rw- weinberger
2011-11-01 12:35 ` Michael Leun
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=20111101111420.1667f3aa@xenia.leun.net \
--to=ml@newton.leun.net \
--cc=linux-kernel@vger.kernel.org \
--cc=nigel@tuxonice.net \
--cc=richard.weinberger@gmail.com \
--cc=rjw@sisk.pl \
/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
all inboxes | Powered by JetHome®