From: Ben Tebulin <tebulin@googlemail.com>
To: mhocko@suse.cz, mgorman@suse.de, hannes@cmpxchg.org,
bsingharora@gmail.com, kamezawa.hiroyu@jp.fujitsu.com
Cc: linux-mm@kvack.org
Subject: [Bug] Reproducible data corruption on i5-3340M: Please revert 53a59fc67!
Date: Wed, 14 Aug 2013 18:36:53 +0200 [thread overview]
Message-ID: <520BB225.8030807@gmail.com> (raw)
In-Reply-To: <52050382.9060802@gmail.com>
Hello Michal, Johannes, Balbir, Kamezawa and Mailing lists!
Since v3.7.2 on two independent machines a very specific Git repository
fails in 9/10 cases on git-fsck due to an SHA1/memory failures. This
only occurs on a very specific repository and can be reproduced stably
on two independent laptops. Git mailing list ran out of ideas and for me
this looks like some very exotic kernel issue.
After a _very long session of rebooting and bisecting_ the Linux kernel
(fortunately I had a SSD and ccache!) I was able to pinpoint the cause
to the following patch:
*"mm: limit mmu_gather batching to fix soft lockups on !CONFIG_PREEMPT"*
787f7301074ccd07a3e82236ca41eefd245f4e07 linux stable [1]
53a59fc67f97374758e63a9c785891ec62324c81 upstream commit [2]
More details are available in my previous discussion on the Git mailing:
http://thread.gmane.org/gmane.comp.version-control.git/231872
Never had any hardware/stability issues _at all_ with these machines.
Only one repo out of 112 is affected. It's a git-svn clone and even
recreated copies out of svn do trigger the same failure.
I was able to bisect this error to this very specific commit.
Furthermore: Reverting this commit in 3.9.11 still solves the error.
I assume this is a regression of the Linux kernel (not Git) and would
kindly ask you to revert the afore mentioned commits.
Thanks!
- Ben
I'm not subscribed - please CC me.
[1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=787f7301074ccd07a3e82236ca41eefd245f4e07
[2] https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=53a59fc67f97374758e63a9c785891ec62324c81
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2013-08-14 16:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <52050382.9060802@gmail.com>
2013-08-14 16:36 ` Ben Tebulin [this message]
2013-08-14 17:40 ` [Bug] Reproducible data corruption on i5-3340M: Please revert 53a59fc67! Michal Hocko
2013-08-14 17:58 ` Michal Hocko
2013-08-14 18:03 ` Linus Torvalds
2013-08-14 18:28 ` Michal Hocko
2013-08-14 18:35 ` Linus Torvalds
2013-08-15 9:25 ` Ben Tebulin
2013-08-15 12:02 ` Linus Torvalds
2013-08-15 12:37 ` Ben Tebulin
2013-08-15 13:40 ` Michal Hocko
2013-08-15 14:46 ` Michal Hocko
2013-08-15 14:53 ` Michal Hocko
2013-08-15 15:14 ` Michal Hocko
2013-08-15 18:00 ` Linus Torvalds
2013-08-15 18:29 ` Bjørn Mork
2013-08-15 18:42 ` Linus Torvalds
2013-08-15 23:05 ` [Bug] Reproducible data corruption on i5-3340M: Please continue your great work! :-) Ben Tebulin
2013-08-16 0:33 ` Linus Torvalds
2013-08-16 6:22 ` Stephen Rothwell
2013-08-16 7:55 ` richard -rw- weinberger
2013-08-16 11:00 ` Michal Hocko
2013-08-16 11:28 ` Peter Zijlstra
2013-08-16 23:40 ` Tony Luck
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=520BB225.8030807@gmail.com \
--to=tebulin@googlemail.com \
--cc=bsingharora@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
/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).