* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

quoted text
> Ingo Molnar wrote:
>> i'm testing on multiple systems in parallel, each is running randconfig 
>> kernels. One 64-bit system found a build bug, the other one found a 
>> boot crash.
>>
>> This can happen if certain configs build fine (but crash), certain 
>> configs dont even build. Each system does a random walk of the config 
>> space.
>
> Yes, but the URL for both the crash and the build failure pointed to 
> the same config.  Is one of them a mistake?

yeah, i guess so. Right now i only ran into the build failure so there's 
hope :) Here's a config that fails to build for sure:

  http://redhat.com/~mingo/misc/config-Fri_Jun_27_17_54_32_CEST_2008.bad

note, on 32-bit there's a yet unfixed initrd corruption bug i've 
bisected back to:

| 510be56adc4bb9fb229637a8e89268d987263614 is first bad commit
| commit 510be56adc4bb9fb229637a8e89268d987263614
| Author: Yinghai Lu <yhlu.kernel@gmail.com>
| Date:   Tue Jun 24 04:10:47 2008 -0700
|
|    x86: introduce init_memory_mapping for 32bit

so if you see something like that it's probably not a bug introduced by 
your changes. (and maybe you'll see why the above commit is buggy, i 
havent figured it out yet)

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/