Re: [Wg-test-framework] linux 3.14.34 failure to detect disks on C600 storage controller

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2015-04-16 at 19:11 +0100, Ian Jackson wrote:
> Dugger, Donald D writes ("RE: linux 3.14.34 failure to detect disks on C600 
> storage controller"):
> > I still think it's the initfs.  There's a lot of magic that happens when 
> > creating the initfs and I've been burned by the magic getting confused in 
> > the past.
> > 
> > I guess I need to understand your build process better.  If you are 
> > building a kernel on machine A and then booting on machine B you can get 
> > hit by subtle issues in the build process.  The biggest issue is that, when 
> > creating the initfs, by default the system identifies which kernel modules 
> > to include in the initfs based upon what kernel modules are currently 
> > loaded on the build machine.  If your build machine, for example, is using 
> > IDE disks and the target machine is running SCSI expect to have problems.
> 
> The initramfs is built on the target machine.  So I don't think this
> can be relevant.

FWIW I agree, AFAIK osstest does the completely sensible things here
which should be expected to work.

> > On a related note, I've run into issues where Linux has split a
> > module into 2 separate modules which confuses the initfs magic and >
> required manual intervention.
> 
> That would be a potential cause.

One thing I wondered about was an interaction between bits which are =y
and bits which are =m, i.e. some bug where FOO=m relies on BAR=m and if
BAR=y it gets confused (i.e. because the initialisation ordered is
perturbed by making BAR=y).

Ian.


_______________________________________________
Wg-test-framework mailing list
Wg-test-framework@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/wg-test-framework