[Macchiato] success (first boot)

[Jeremy Linton]

Hi,

On 01/24/2018 03:43 AM, Marcin Wojtas wrote:
> +Antoine
> 
> Hi Marc,
> 
> 2018-01-24 10:25 GMT+01:00 Marc Zyngier <marc.zyngier at arm.com>:
>> On 23/01/18 23:15, Ard Biesheuvel wrote:
>>> On 23 January 2018 at 23:12, Steve McIntyre <steve at einval.com> wrote:
>>>> On Tue, Jan 23, 2018 at 11:07:53PM +0000, Matthew Bentham wrote:
>>>>> Hi,
>>>>> Thanks. I've got it showing a Linux terminal using an old Radeon 5570 now :-)
>>>>>
>>>>> My problem now is that the network device driver is causing a kernel panic when
>>>>> doing "apt install task-gnome-desktop". I get a lot of warning messages first
>>>>> along the lines of "detected wrong cpu at end of Tx processing".
>>>>
>>>> Aha! Not just me then! I've been seeing the same 2 things for a while,
>>>> but Leif and Stuart have not.
>>>>
>>>> I was wondering if it's memory corruption in the driver, but I've not
>>>> had much chance to dig into it yet.
>>>>
>>>
>>> I think this may be a known issue. Marc?
>>
>> I fixed something along those lines[1]. But this driver is being
>> randomly changed and almost never tested in a production environment, so
>> it it breaks on almost every single effin' change.
>>
>> 4.14 should have the fix though... If it still breaks, I'll dust off the
>> board and give it a spin.
>>
>>          M.
>>
>> [1]
>> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/marvell/mvpp2.c?id=13c249a94f525fe4c757d28854049780b25605c4
>> --
> 
> I saw your patch is already a part of v4.14... Two days ago similar
> bug report was sent to the lists and I Antoine said it will be
> investigated.


That was probably my bug report? 4.15rc9 still has the problem 
(including all the suggested patches) and I picked a couple out of 
net-next to see if they would fix it too, and none of them do.

(this is all with uefi boots)

So while you guys have mentioned the PCIe issue(s) (which isn't limited 
to graphics cards, I have a couple other cards that don't work either), 
the net issue, which should probably include the fact that the 10g phy 
are still not responding either. I'm going to add:

The sd driver works fine, except when its in the initrd. In that case it 
appears to be locking up the machine too. Blacklisting it allows the 
machine to boot. Further its a pain to debug as earlycon doesn't seem to 
be working by default (what should the full earlycon command line be?).

And while I've mentioned that, I will also mention that I have an asix 
usb/net adapter that works in a number of other arm64 machines (same 
kernel/cable/etc) that doesn't seem to be getting interrupt URBs when 
plugged into the machine, which results in a failure to linkup.