From: Yinghai Lu <yinghai@kernel.org>
To: Volker Lanz <vl@fidra.de>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu
Subject: Re: [BISECTED, REGRESSION] Successful resume from suspend but freezes after I/O
Date: Mon, 07 Dec 2009 10:24:02 -0800 [thread overview]
Message-ID: <4B1D4842.80000@kernel.org> (raw)
In-Reply-To: <200912071856.48125.vl@fidra.de>
Volker Lanz wrote:
> Hi,
>
> updating to my distro's new 2.6.31 kernel on an x86_64 quad core machine with
> 6 GB of RAM I noticed resuming from suspend still worked as before, but the
> machine will now reproducably freeze (have to hard reset) afterwards as soon
> as I do something disk I/O heavy, though the problem is probably not related
> to disk activity at all.
>
> A current mainline 2.6.32 checkout shows the same behaviour.
>
> I git-bisected the problem to this commit:
>
>
> -----------------------------------------------------------------------------
> commit 78a8b35bc7abf8b8333d6f625e08c0f7cc1c3742
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Thu Mar 12 22:36:01 2009 -0700
>
> x86: make e820_update_range() handle small range update
>
> Impact: enhance e820 code to handle more cases
>
> Try to handle new range which could be covered by one entry.
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Cc: jbeulich@novell.com
> LKML-Reference: <49B9F0C1.10402@kernel.org>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> -----------------------------------------------------------------------------
>
>
> A kernel built from this revision does not boot, so the first booting kernel
> to show the problem actually seems to be:
>
>
> -----------------------------------------------------------------------------
> commit 6d7942dc2a70a7e74c352107b150265602671588
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Sat Mar 14 14:32:41 2009 -0700
>
> x86: fix 64k corruption-check
>
> Impact: fix boot crash
>
> Need to exit early if the addr is far above 64k.
>
> The crash got exposed by:
>
> 78a8b35: x86: make e820_update_range() handle small range update
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Cc: <stable@kernel.org>
> LKML-Reference: <49BC2279.2030101@kernel.org>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> -----------------------------------------------------------------------------
>
>
> The last kernel to work without problems thus seems to be this one:
>
>
> -----------------------------------------------------------------------------
> commit 773e673de27297d07d852e7e9bfd1a695cae1da2
> Author: Yinghai Lu <yinghai@kernel.org>
> Date: Thu Mar 12 21:35:18 2009 -0700
>
> x86: fix e820_update_range()
>
> Impact: fix left range size on head
>
> | commit 5c0e6f035df983210e4d22213aed624ced502d3d
> | x86: fix code paths used by update_mptable
> | Impact: fix crashes under Xen due to unrobust e820 code
>
> fixes one e820 bug, but introduces another bug.
>
> Need to update size for left range at first in case it is header.
>
> also add __e820_add_region take more parameter.
>
> Signed-off-by: Yinghai Lu <yinghai@kernel.org>
> Cc: jbeulich@novell.com
> LKML-Reference: <49B9E286.502@kernel.org>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
> -----------------------------------------------------------------------------
>
>
> The problem is 100% reproducable on this machine: Resuming and then copying
> /usr/ to $HOME will freeze after a few hundred MB have been copied. Earlier
> kernels worked fine for the last couple of months.
>
> What additional information is required to help diagnose and hopefully fix the
> problem?
whole boot log with CONFIG_PCI_DEBUG and debug on command line.
YH
next prev parent reply other threads:[~2009-12-07 18:25 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 [this message]
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
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=4B1D4842.80000@kernel.org \
--to=yinghai@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vl@fidra.de \
/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