From: "Török Edwin" <edwin@skylable.com>
To: Eric Sandeen <sandeen@sandeen.net>,
Brian Foster <bfoster@redhat.com>,
Dave Chinner <david@fromorbit.com>
Cc: Christopher Squires <christopher.squires@hgst.com>,
Karanvir Singh <karanvir.singh@hgst.com>,
Wayne Burri <wayne.burri@hgst.com>,
Luca Gibelli <luca@skylable.com>,
"xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: PROBLEM: XFS on ARM corruption 'Structure needs cleaning'
Date: Sat, 13 Jun 2015 16:55:04 +0300 [thread overview]
Message-ID: <557C3638.1020903@skylable.com> (raw)
In-Reply-To: <BLUPR04MB593340A765596780F266454F2BB0@BLUPR04MB593.namprd04.prod.outlook.com>
On 06/13/2015 01:52 AM, Dave Chinner wrote:
> Yup, that's looking like a toolchain bug. Thread about arm directory
> read corruption:
>
> http://oss.sgi.com/archives/xfs/2013-02/msg00505.html
>
> cross-gcc version results:
>
> http://oss.sgi.com/archives/xfs/2013-02/msg00563.html
>
> "A quick rundown:
> -cross-gcc4.4: OK
> -cross-gcc4.5: OK
> -cross-gcc4.6: BAD
> -cross-gcc4.7: BAD
> -cross-gcc4.8: OK"
>
Just tested the new kernels, they're both good:
GOOD: 3.14.3-std-00094-g9035cb4, gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-12ubuntu1)
GOOD: 3.14.44-std-00095-g0425932, gcc version 4.9.2 (4.9.2-10)
BAD: 3.14.3-00088-g7651c68, gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)
On 06/12/2015 03:21 PM, Brian Foster wrote:
> I echo Dave's suggestion down thread with regard to toolchain. This
> kernel was compiled with the following cross-gcc (installed via Fedora
> package):
>
> gcc version 4.9.2 20150212 (Red Hat Cross 4.9.2-5) (GCC)
>
> Are you using something different?
>
> Brian
Indeed, it looks like a compiler bug, thanks a lot for helping me track it down.
I'll see if I can find out more about whats different between the two kernels compiled by 4.6 and 4.7.
On 06/13/2015 12:41 AM, Karanvir Singh wrote:
>
> Hi Edwin,
>
>
> PFA the newer uimages:
>
> uImage3.14.44.gcc.4.9.2: its a 3.14.44 compiled with gcc 4.9.4
> uImage.gcc.4.7.2-1: its 3.14.3 compiled with gcc 4.7.2
Thanks, both of these images work correctly: I was not able to reproduce the bug with them (rebooting to the original uImage 3.14.3 with gcc 4.6.3 reproduces bug immediately).
Best regards,
--Edwin
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-06-13 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 6:23 PROBLEM: XFS on ARM corruption 'Structure needs cleaning' Török Edwin
2015-06-11 15:16 ` Brian Foster
2015-06-11 15:28 ` Török Edwin
2015-06-11 15:51 ` Eric Sandeen
2015-06-11 15:58 ` Eric Sandeen
2015-06-11 16:32 ` Török Edwin
2015-06-11 17:10 ` Eric Sandeen
2015-06-11 17:13 ` Török Edwin
2015-06-11 17:16 ` Eric Sandeen
2015-06-11 20:07 ` Eric Sandeen
2015-06-11 20:29 ` Eric Sandeen
2015-06-11 22:53 ` Dave Chinner
2015-06-12 12:21 ` Brian Foster
2015-06-12 12:47 ` Török Edwin
2015-06-12 13:54 ` Brian Foster
2015-06-12 20:19 ` Eric Sandeen
[not found] ` <BLUPR04MB593340A765596780F266454F2BB0@BLUPR04MB593.namprd04.prod.outlook.com>
2015-06-13 13:55 ` Török Edwin [this message]
2015-06-12 22:52 ` Dave Chinner
2015-08-12 0:56 ` katsuki.uwatoko
2015-08-12 3:14 ` Dave Chinner
2015-08-12 6:19 ` katsuki.uwatoko
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=557C3638.1020903@skylable.com \
--to=edwin@skylable.com \
--cc=bfoster@redhat.com \
--cc=christopher.squires@hgst.com \
--cc=david@fromorbit.com \
--cc=karanvir.singh@hgst.com \
--cc=luca@skylable.com \
--cc=sandeen@sandeen.net \
--cc=wayne.burri@hgst.com \
--cc=xfs@oss.sgi.com \
/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