Hi All,
On 4/4/22 21:44, Guillaume Tucker wrote:
> +kernelci
>
> On 29/03/2022 19:44, Guillaume Tucker wrote:
>> On 28/03/2022 13:54, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 3/24/22 23:19, Mark Brown wrote:
>>>> On Thu, Mar 24, 2022 at 09:34:30PM +0100, Hans de Goede wrote:
>>>>
>>>>> Mark, if one of use writes a test patch, can you get that Asus machine to boot a
>>>>> kernel build from next + the test patch ?
>>>>
>>>> I can't directly unfortunately as the board is in Collabora's lab but
>>>> Guillaume (who's already CCed) ought to be able to, and I can generally
>>>> prod and try to get that done.
>>>
>>> Ok, Guillaume, can you try a kernel with commit 5949965ec9340cfc0e65f7d8a576b660b26e2535
>>> ("x86/PCI: Preserve host bridge windows completely covered by E820") + the
>>> attached patch added on top a try on the asus-C523NA-A20057-coral machine please
>>> and see if that makes it boot again ?
>>
>> Sorry I've been busy with a conference. Sure, will put that
>> through KernelCI tomorrow and let you know the outcome.
>
> Well the issue seems to have been fixed on mainline, unless it's
> intermittent. In any case, next-20220404 is booting fine:
>
> https://linux.kernelci.org/test/plan/id/624aed811a5acd09adae071e/
>
> Last time it was seen to fail was next-20220330:
>
> https://linux.kernelci.org/test/plan/id/62442f68e30d6f89a4ae06b7/
>
>
> Ironically, the KernelCI staging linux-next job with the patches
> mentioned in your previous email applied is now failing:
>
> https://staging.kernelci.org/test/plan/id/624b2d3b923f532dc305f4c7/
>
> The kernel branch being used is:
>
> https://github.com/kernelci/linux/commits/staging-next
>
>
> I haven't checked the logs or investigated any further, this is
> just a quick summary based on the boot test results.
>
> Please let us know if we should drop these patches or try
> anything else. I'll be on holiday for the rest of the week but
> others can pick things up if needed.
The reason why next and mainline are building now is because
the patch the bisect pointed out never made it into mainline
and Bjorn has dropped it from -next.
I fully expect that -next with
https://lore.kernel.org/linux-acpi/20220304035110.988712-4-helgaas@xxxxxxxxxx/
or mainline with the entire series from that link applied will
still not boot.
But we do need that last patch to fix various issues on
other boards.
See my previous reply in this thread:
https://lore.kernel.org/linux-pci/76c5de03-a3a4-8444-d7f6-496fa119d830@xxxxxxxxxx/
for some further analysis of what I think is happening here.
As mentioned there I believe this can be fixed by merging
back-to-back resources into a single resource before calling
remove_e820_regions() but I could not find a good example / helper
code to do the merging of the resources.
If someone can give me some pointers wrt this I can try to
come up with something and then provide a set of patches
for testing on the asus-C523NA-A20057-coral .
Regards,
Hans
