From: ludovic.desroches@atmel.com (Ludovic Desroches)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression: at24 eeprom writing
Date: Mon, 5 Oct 2015 16:00:32 +0100 [thread overview]
Message-ID: <20151005150032.GA12137@odux.rfo.atmel.com> (raw)
In-Reply-To: <561238A9.1060406@lysator.liu.se>
Hi Peter
On Mon, Oct 05, 2015 at 10:45:29AM +0200, Peter Rosin wrote:
> On 2015-10-03 01:05, Peter Rosin wrote:
[...]
> Ok, I found the culprit, and I double and triple checked it this time...
>
> If I move to the very latest on the linux-3.18-at91 branch, the bug is
> there too. Which made it vastly more palatable to bisect the bug.
>
> The offender (in the 4.2 kernel) is 93563a6a71bb69dd324fc7354c60fb05f84aae6b
> "i2c: at91: fix a race condition when using the DMA controller"
> which is far more understandable. Ao, adding Cyrille Pitchen to the Cc list.
>
Thanks for the bisecting effort. I am currently at ELCE where I have
met someone with the same kind of issue. Is it easily reproducible? It
doesn't seem to be the case for him.
I'll have a look once back.
> If I add that patch on top of my previously working tree, it behaves just
> as newer kernels, i.e. equally bad. The patch doesn't revert cleanly, but
> reverting the patch and quick-n-dirty-fixing the conflict on vanilla 4.2
> makes the problem go away.
>
> I have attached what I actually reverted.
>
> Cheers,
> Peter
>
Ludovic
next prev parent reply other threads:[~2015-10-05 15:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 23:05 Regression: at24 eeprom writing Peter Rosin
2015-10-04 19:50 ` Peter Rosin
2015-10-05 6:16 ` Christian Gmeiner
2015-10-06 16:41 ` Peter Rosin
2015-10-05 8:45 ` Peter Rosin
2015-10-05 8:59 ` kbuild test robot
2015-10-05 15:00 ` Ludovic Desroches [this message]
2015-10-05 15:09 ` Peter Rosin
2015-10-12 15:13 ` Peter Rosin
2015-10-12 16:13 ` Cyrille Pitchen
2015-10-13 10:38 ` Peter Rosin
2015-10-13 12:57 ` Nicolas Ferre
2015-10-13 14:35 ` Peter Rosin
2015-10-13 13:26 ` ludovic.desroches at atmel.com
2015-10-05 15:28 ` Cyrille Pitchen
2015-10-05 15:54 ` Peter Rosin
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=20151005150032.GA12137@odux.rfo.atmel.com \
--to=ludovic.desroches@atmel.com \
--cc=linux-arm-kernel@lists.infradead.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 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).