From: Volker Lanz <vl@fidra.de>
To: Yinghai Lu <yinghai@kernel.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [BISECTED, REGRESSION] Successful resume from suspend but freezes after I/O
Date: Tue, 8 Dec 2009 02:13:20 +0100 [thread overview]
Message-ID: <200912080213.20502.vl@fidra.de> (raw)
In-Reply-To: <4B1D8A27.6050008@kernel.org>
On Tuesday 08 December 2009 00:05:11 Yinghai Lu wrote:
> the updated e820 table is the same to the one for 2.6.29...
>
> so could be some other patch cause the problem.
>
> please check if revert
> 2547089ca2db132e307ef68848ba029a8ec2f341
> could help.
I reverted to one commit before that, which would be
eaa959df299157e2640fcb3321537501b6afd9e6
if I am not mistaken. I built and booted that kernel and could reproduce the
freeze with it (TBH this was not surprising to me, because I originally pinned
down the problem by bisecting the commits and this commit is after the one
bisecting found. Am I missing a detail here?)
But strangely enough the freeze this time produced an oops before it locked
the machine. I couldn't save it to a file but took a picture. The screenshot
is here:
http://banane.volker-lanz.de/08122009013.jpg
The oops is _not _reproducable. After a reboot with this same kernel, a
suspend/resume cycle and some I/O the machine locks again without showing the
oops.
Volker
next prev parent reply other threads:[~2009-12-08 1:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 17:56 [BISECTED, REGRESSION] Successful resume from suspend but freezes after I/O Volker Lanz
2009-12-07 18:24 ` Yinghai Lu
2009-12-07 19:13 ` Volker Lanz
2009-12-07 19:23 ` Yinghai Lu
2009-12-07 20:36 ` Volker Lanz
2009-12-07 22:01 ` Yinghai Lu
2009-12-08 0:07 ` Volker Lanz
2009-12-07 23:05 ` Yinghai Lu
2009-12-08 1:13 ` Volker Lanz [this message]
2009-12-21 8:54 ` Volker Lanz
2009-12-28 23:40 ` Rafael J. Wysocki
2010-01-13 7:35 ` Yinghai Lu
2010-01-13 18:04 ` Volker Lanz
2010-01-13 19:57 ` Yinghai Lu
2010-01-14 13:05 ` Volker Lanz
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=200912080213.20502.vl@fidra.de \
--to=vl@fidra.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@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.