From: Ingo Molnar <mingo@elte.hu>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org, Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [scsi bug] spurious build failures in aic7xxx
Date: Sat, 2 Feb 2008 15:18:57 +0100 [thread overview]
Message-ID: <20080202141857.GA8635@elte.hu> (raw)
In-Reply-To: <20080202140630.GA7939@elte.hu>
i should also specify the build environment:
it's a distcc setup with 5-10 hosts active at a time, so highly parallel
with large, networking related delays. It's make -j130:
nice -15 /usr/bin/time make -j130 bzImage ARCH=i386 \
CROSS_COMPILE='distcc \
/opt/crosstool/gcc-4.2.2-glibc-2.3.6/i686-unknown-linux-gnu-'
the build host is a 64-bit quad CPU box, so highly parallel as well.
before this i did about a thousand x86.git builds/boots a day without
any build (or boot) failure, so i'm 100% sure that the build race was
not present before. It started triggering it a few days ago, roughly
when the commit you suspected went in.
here's all SCSI build failures logged from the past 1-2 days:
2 drivers/scsi/aic7xxx/aic79xx_reg.h
4 drivers/scsi/aic7xxx/aic7xxx.h
4 drivers/scsi/lpfc/lpfc_init.c
12 drivers/scsi/aic7xxx/aic7xxx_osm.h
108 drivers/scsi/aic7xxx/aic7xxx_inline.h
280 drivers/scsi/aic7xxx/aic7xxx_pci.c
first column is the number of error lines from logs.
When i turned off all the AICxxxx builds (all 3 drivers for good
measure), the build failures went away. [but this excludes one of my
testboxes from qa coverage - which has aic7xxx hardware - so it would be
nice to fix this.]
the host box is Fedora 8, make-3.81-10.fc8. gcc-4.2.2 crosscompiler,
built from sources. (i.e. not distro patched)
Ingo
next prev parent reply other threads:[~2008-02-02 14:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 22:50 [scsi bug] spurious build failures in aic7xxx Ingo Molnar
2008-02-01 23:02 ` Sam Ravnborg
2008-02-02 13:59 ` Sam Ravnborg
2008-02-02 14:03 ` Ingo Molnar
2008-02-02 14:06 ` Ingo Molnar
2008-02-02 14:18 ` Ingo Molnar [this message]
2008-02-02 16:26 ` Sam Ravnborg
2008-02-02 17:10 ` Ingo Molnar
2008-02-03 4:54 ` [patch] scsi: fix " Ingo Molnar
2008-02-03 7:41 ` Sam Ravnborg
2008-02-03 19:23 ` James Bottomley
2008-02-03 20:05 ` Sam Ravnborg
2008-02-03 20:15 ` James Bottomley
2008-02-03 20:38 ` Sam Ravnborg
2008-02-03 20:48 ` James Bottomley
2008-02-04 7:33 ` Hannes Reinecke
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=20080202141857.GA8635@elte.hu \
--to=mingo@elte.hu \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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