All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Tebulin <tebulin@googlemail.com>
To: Ben Tebulin <tebulin@googlemail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Reproducible data corruption since 3.7.x on i5-3340M machines
Date: Mon, 12 Aug 2013 10:04:38 +0200	[thread overview]
Message-ID: <52089716.4040008@gmail.com> (raw)
In-Reply-To: <52050382.9060802@gmail.com>

Shameless self-bump: Since kernel 3.7.x i can reproduce a sporadic data
corruption using git on 2 different machine (same model, though).

Can anybody give me a hint who can help to trace down/fix this regression?

For more information please refer to my first post on Friday.

Sorry to bother again, but I have no clue where to ask elsewhere.

  reply	other threads:[~2013-08-12  8:04 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 14:58 Reproducible git-fsck/SHA1 failures since 3.7.x on a Dell E6430 / i5-3340M Ben Tebulin
2013-08-12  8:04 ` Ben Tebulin [this message]
2013-08-14 16:36 ` [Bug] Reproducible data corruption on i5-3340M: Please revert 53a59fc67! Ben Tebulin
2013-08-14 17:40   ` Michal Hocko
2013-08-14 17:40     ` Michal Hocko
2013-08-14 17:58     ` Michal Hocko
2013-08-14 17:58       ` Michal Hocko
2013-08-14 18:03     ` Linus Torvalds
2013-08-14 18:03       ` Linus Torvalds
2013-08-14 18:28       ` Michal Hocko
2013-08-14 18:28         ` Michal Hocko
2013-08-14 18:35         ` Linus Torvalds
2013-08-14 18:35           ` Linus Torvalds
2013-08-15  9:25           ` Ben Tebulin
2013-08-15  9:25             ` Ben Tebulin
2013-08-15 12:02             ` Linus Torvalds
2013-08-15 12:02               ` Linus Torvalds
2013-08-15 12:37               ` Ben Tebulin
2013-08-15 12:37                 ` Ben Tebulin
2013-08-15 13:40               ` Michal Hocko
2013-08-15 13:40                 ` Michal Hocko
2013-08-15 14:46                 ` Michal Hocko
2013-08-15 14:46                   ` Michal Hocko
2013-08-15 14:53                   ` Michal Hocko
2013-08-15 14:53                     ` Michal Hocko
2013-08-15 15:14                     ` 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:29                   ` Bjørn Mork
2013-08-15 18:29                   ` Bjørn Mork
2013-08-15 18:42                   ` Linus Torvalds
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-15 23:05                   ` 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  7:55                       ` richard -rw- weinberger
2013-08-16 11:00                     ` Michal Hocko
2013-08-16 11:00                       ` Michal Hocko
2013-08-16 11:28                       ` Peter Zijlstra
2013-08-16 11:28                         ` Peter Zijlstra
2013-08-16 23:40                     ` Tony Luck
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=52089716.4040008@gmail.com \
    --to=tebulin@googlemail.com \
    --cc=linux-kernel@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.