From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: weirdness with compiling a 2.6.33 kernel on arm debian
Date: Thu, 11 Mar 2010 13:33:53 +0000 [thread overview]
Message-ID: <20100311133353.GC25011@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <25ae2d691003060224x67ab1c9au5102c8a22518aff@mail.gmail.com>
On Sat, Mar 06, 2010 at 09:24:49PM +1100, dave b wrote:
> I had already reported it to debian -
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572653
>
> I have cc'ed linux-arm-kernel into this email.
I think most of the points have already been convered, but just for
completeness,
What is the history of the hardware you're running these builds on?
Has it proven itself on previous kernel versions running much the same
tests?
Another point to consider: how are you running the compiler - is it
over NFS from a PC?
The reason I ask is that you can suffer from very weird corruption
issues - I have a nice illustration of one which takes a copy of 1GB
worth of data each day, and every once in a while, bytes 8-15 of a
naturally aligned 16 byte block in the data become corrupted somewhere
between the network and disk. The probability of corruption happening
is around 0.0000001%, but it still happens... and that makes it
extremely difficult to track down.
next prev parent reply other threads:[~2010-03-11 13:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25ae2d691003051958x72040b47g29d842f1d389a6cf@mail.gmail.com>
[not found] ` <19346.6765.457769.167118@pilspetsen.it.uu.se>
2010-03-06 10:24 ` weirdness with compiling a 2.6.33 kernel on arm debian dave b
2010-03-06 10:41 ` Daniel Mack
2010-03-07 1:05 ` dave b
2010-03-07 11:01 ` Martin Guy
2010-03-08 9:53 ` Uwe Kleine-König
2010-03-08 10:31 ` Daniel Mack
2010-03-11 13:10 ` dave b
2010-03-11 13:33 ` Russell King - ARM Linux [this message]
2010-03-15 1:02 ` Jamie Lokier
2010-03-26 10:12 ` dave b
2010-04-01 6:08 ` Pavel Machek
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=20100311133353.GC25011@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).