From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Jackson Subject: Re: [linux-mingo-tip-master test] 12632: tolerable FAIL - PUSHED Date: Wed, 11 Apr 2012 16:55:56 +0100 Message-ID: <20357.43404.718457.235113@mariner.uk.xensource.com> References: <1334159286.16387.28.camel@zakaz.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1334159286.16387.28.camel@zakaz.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Ian Campbell writes ("Re: [Xen-devel] [linux-mingo-tip-master test] 12632: tolerable FAIL - PUSHED"): > At least some of these xen-boot failures (I looked at > http://www.chiark.greenend.org.uk/~xensrcts/logs/12632/test-amd64-amd64-xl-win7-amd64/serial-itch-mite.log) have missing firmware: > > Apr 10 13:57:11.884530 [ 28.946844] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw" Thanks for looking into this. > That'll be because the new kernel needs something newer than what is > provided by Squeeze's linux-firmware* packages. I usually set > CONFIG_FIRMWARE_IN_KERNEL to avoid this (mostly, sometimes they forget > to even include the firmware update, which happened once recently with > bnx2 IIRC, so watch out for that): Hrmf. At least I guess that'll be a real regression upstream if that happens. I have submitted a change to set CONFIG_FIRMWARE_IN_KERNEL. > The other option, as noted below, is to run "make firmware_install". That's less appealing because of the need to mess around more with initrds and build scripts. Ian.