On 30.06.2019 23:29, Karsten Wiborg wrote:
> Hi Heiner,
>
> On 30/06/2019 19:42, Heiner Kallweit wrote:
>> Vendor driver uses this code, do you see the related messages in syslog?
>>
>> if (!is_valid_ether_addr(mac_addr)) {
>> netif_err(tp, probe, dev, "Invalid ether addr %pM\n",
>> mac_addr);
>> eth_hw_addr_random(dev);
>> ether_addr_copy(mac_addr, dev->dev_addr);
>> netif_info(tp, probe, dev, "Random ether addr %pM\n",
>> mac_addr);
>> tp->random_mac = 1;
>> }
>>
>
> did the following:
>
> # cat /var/log/messages |grep -i Invalid
> Jun 30 08:54:00 praktifix kernel: [ 0.229213] DMAR-IR: Queued
> invalidation will be enabled to support x2apic and Intr-remapping.
> Jun 30 08:54:00 praktifix kernel: [ 23.864072] Invalid pltconfig,
> ensure IPC1 device is enabled in BIOS
> Jun 30 10:17:30 praktifix kernel: [ 0.228662] DMAR-IR: Queued
> invalidation will be enabled to support x2apic and Intr-remapping.
> Jun 30 10:17:30 praktifix kernel: [ 24.198033] Invalid pltconfig,
> ensure IPC1 device is enabled in BIOS
>
> But that does not relate to your error.
>
> # cat /var/log/messages |grep -i random
> Jun 30 08:54:00 praktifix kernel: [ 0.228092] random: crng done
> (trusting CPU's manufacturer)
> Jun 30 10:17:30 praktifix kernel: [ 0.227534] random: crng done
> (trusting CPU's manufacturer)
> Jun 30 10:25:53 praktifix kernel: [ 527.540354] r8168 0000:02:00.0
> (unnamed net_device) (uninitialized): Random ether addr 82:c2:81:10:6b:c2
>
This one shows that the vendor driver (r8168) uses a random MAC address.
Means the driver can't read a valid MAC address from the chip, maybe due
to a broken BIOS.
Alternatively you could use r8169 and set a MAC address manually with
ifconfig <if> hw ether <MAC address>
> The last one probably results from my testing with r8169. The compiled
> r8168 went online later. That also is the only message I found.
>
> Thank you for your help in debugging.
>
> Regards and greetings from Hamburg,
> Karsten
>
Heiner
