All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <Ian.Jackson@eu.citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [linux-mingo-tip-master test] 12632: tolerable FAIL - PUSHED
Date: Wed, 11 Apr 2012 16:55:56 +0100	[thread overview]
Message-ID: <20357.43404.718457.235113@mariner.uk.xensource.com> (raw)
In-Reply-To: <1334159286.16387.28.camel@zakaz.uk.xensource.com>

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.

      reply	other threads:[~2012-04-11 15:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10 22:23 [linux-mingo-tip-master test] 12632: tolerable FAIL - PUSHED xen.org
2012-04-11 15:48 ` Ian Campbell
2012-04-11 15:55   ` Ian Jackson [this message]

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=20357.43404.718457.235113@mariner.uk.xensource.com \
    --to=ian.jackson@eu.citrix.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.