From: Nathan_Lynch@mentor•com (Nathan Lynch)
To: linux-arm-kernel@lists•infradead.org
Subject: Oops: 17 SMP ARM (v3.16-rc2)
Date: Mon, 30 Jun 2014 08:00:40 -0500 [thread overview]
Message-ID: <53B15F78.4000208@mentor.com> (raw)
In-Reply-To: <3FFB61A7A8473C49831AF20FA193534A43CB69F6@ALVA-EXMB01.alv.autoliv.int>
On 06/30/2014 07:30 AM, Fredrik Noring wrote:
>>
>> On Fri, Jun 27, 2014 at 04:16:57PM +0000, Fredrik Noring wrote:
>>> Please find below a trace that appeared once with 3.16-rc2. Perhaps it
>>> is of some interest?
>>
>> It's not that serious... I know that the FEC ethernet driver is horrendously
>> racy (I have had a patch set for about the last six months which fixes some of
>> its problems) but as I've had a lot of patches to deal with, and it's been
>> pushed to the back of the queue...
>>
>> The races don't lead to data corruption though, merely timeouts and some
>> lost packets.
> It seems to be a compiler issue, where (GCC) 4.8.2 does not produce a
properly
> working kernel. Happily, (Fedora 2013.11.24-2.fc19) 4.8.1 appears to
do a lot
> better. No crashes so far with v3.16-rc2!
>
Did you narrow it down to a particular GCC bug? The symptoms you
reported remind me of:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58854
Sadly, unpatched GCC 4.8.1 and 4.8.2 are unsuitable for building ARM
kernels.
next prev parent reply other threads:[~2014-06-30 13:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C4A61A5CA4AD2246942F4BA6F20ACB804356534D@ALVA-EXMB04.alv.autoliv.int>
[not found] ` <20140626140115.GQ32514@n2100.arm.linux.org.uk>
2014-06-26 14:44 ` Oops: 17 SMP ARM (v3.16-rc2) Mattis Lorentzon
2014-06-26 15:14 ` Russell King - ARM Linux
2014-06-27 11:21 ` Russell King - ARM Linux
2014-06-27 16:16 ` Fredrik Noring
2014-06-27 16:31 ` Russell King - ARM Linux
2014-06-30 6:22 ` Fredrik Noring
2014-06-30 12:30 ` Fredrik Noring
2014-06-30 13:00 ` Nathan Lynch [this message]
2014-07-02 6:02 ` Fredrik Noring
2014-08-05 13:31 ` Mattis Lorentzon
2014-08-05 13:53 ` Fabio Estevam
2014-08-06 6:48 ` Mattis Lorentzon
2014-08-06 9:50 ` Russell King - ARM Linux
2014-08-06 11:10 ` Mattis Lorentzon
2014-08-06 12:55 ` Russell King - ARM Linux
2014-08-07 11:11 ` Mattis Lorentzon
2014-08-07 12:12 ` Russell King - ARM Linux
2014-08-07 14:20 ` Fabio Estevam
2014-08-07 14:38 ` Fabio Estevam
2014-08-08 1:30 ` Troy Kisky
2014-08-08 14:05 ` Fabio Estevam
2014-08-08 18:09 ` Russell King - ARM Linux
2014-08-11 13:32 ` Mattis Lorentzon
2014-08-11 17:41 ` Fabio Estevam
2014-08-13 13:39 ` Mattis Lorentzon
2014-08-25 10:18 ` Russell King - ARM Linux
2014-08-26 13:11 ` Iain Paton
2014-08-14 14:43 ` Mattis Lorentzon
2014-08-14 15:30 ` Fabio Estevam
2014-08-15 5:42 ` Mattis Lorentzon
2014-08-17 21:34 ` Iain Paton
2014-08-17 21:46 ` Fabio Estevam
2014-08-19 6:03 ` Iain Paton
2014-08-21 9:39 ` Iain Paton
2014-08-22 0:01 ` Fabio Estevam
2014-08-22 6:39 ` Mattis Lorentzon
2014-08-22 10:36 ` Iain Paton
2014-08-27 6:32 ` Mattis Lorentzon
2014-08-27 10:43 ` Iain Paton
2014-08-29 10:57 ` Mattis Lorentzon
2014-08-29 11:30 ` Fabio Estevam
2014-12-16 14:50 ` Mattis Lorentzon
2014-08-26 13:12 ` Iain Paton
2014-08-22 8:27 ` Russell King - ARM Linux
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=53B15F78.4000208@mentor.com \
--to=nathan_lynch@mentor$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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