Server has been upgradeded to bullseye.
Booting takes 2 minutes... quite long...
> Could you please share your /etc/network/interfaces?
# cat /etc/network/interfaces
auto lo lan
iface lo inet loopback
iface lan inet static
address 192.168.18.3/21
gateway 192.168.18.1
# cat /etc/udev/rules.d/69-leszek-net.rules | sed -r 's/^#.*//;
s/^\s+//' | sort | uniq
SUBSYSTEM=="net", ATTR{address}=="00:19:99:ee:2c:87", NAME="lan"
SUBSYSTEM=="net", ATTR{address}=="00:e0:4c:68:0f:61", NAME="lan"
SUBSYSTEM=="net", ATTR{address}=="4c:cc:6a:4a:14:6f", NAME="wan"
SUBSYSTEM=="net", ATTR{address}=="74:d4:35:99:d4:ed", NAME="wan"
SUBSYSTEM=="net", ATTR{address}=="aa:aa:aa:00:75:9c", NAME="lan"
SUBSYSTEM=="net", ATTR{address}=="b4:2e:99:37:41:5d", NAME="lan"
SUBSYSTEM=="net", ATTR{address}=="bc:5f:f4:c0:8f:82", NAME="lan"
> If I am not wrong, ifupdown-pre.service relies on udevadm. Could you add
> some debugging on it, and could you share its log please?
# systemd-analyze blame | head -n5
1min 28.234s systemd-journal-flush.service
5.107s ifupdown-pre.service
4.663s dev-sda2.device
3.751s ssh.service
3.676s smartmontools.service
# systemctl status ifupdown-pre.service
● ifupdown-pre.service - Helper to synchronize boot up for ifupdown
Loaded: loaded (/lib/systemd/system/ifupdown-pre.service; static)
Active: active (exited) since Thu 2022-01-20 13:20:15 CET; 8h ago
Process: 261 ExecStart=/bin/sh -c if [ "$CONFIGURE_INTERFACES" !=
"no" ] && [ -n "$(ifquery --read-environment --list --exclude=lo)" ] &&
[ -x /bin/udevadm ]; then udevadm settle; fi (code=exited, status=0/>
Main PID: 261 (code=exited, status=0/SUCCESS)
CPU: 30ms
sty 20 13:20:15 pegaz systemd[1]: Finished Helper to synchronize boot up
for ifupdown.
# cat /var/log/kern.log | grep -E 'net|ifup|rtl|eth|lan|wan'
Jan 20 13:21:40 pegaz kernel: [ 0.217092] audit: initializing netlink
subsys (disabled)
Jan 20 13:21:40 pegaz kernel: [ 1.083508] r8169 0000:03:00.0 eth0:
RTL8168evl/8111evl, 74:d4:35:99:d4:ed, XID 2c9, IRQ 30
Jan 20 13:21:40 pegaz kernel: [ 1.083510] r8169 0000:03:00.0 eth0:
jumbo features [frames: 9194 bytes, tx checksumming: ko]
Jan 20 13:21:40 pegaz kernel: [ 1.086417] r8169 0000:05:03.0 eth1:
RTL8169sb/8110sb, aa:aa:aa:00:75:9c, XID 100, IRQ 18
Jan 20 13:21:40 pegaz kernel: [ 1.086419] r8169 0000:05:03.0 eth1:
jumbo features [frames: 7146 bytes, tx checksumming: ok]
Jan 20 13:21:40 pegaz kernel: [ 1.087414] r8169 0000:03:00.0 wan:
renamed from eth0
Jan 20 13:21:40 pegaz kernel: [ 1.108361] r8169 0000:05:03.0 lan:
renamed from eth1
Jan 20 13:21:40 pegaz kernel: [ 41.027982] RTL8211C Gigabit Ethernet
r8169-0-518:00: attached PHY driver [RTL8211C Gigabit Ethernet]
(mii_bus:phy_addr=r8169-0-518:00, irq=IGNORE)
Jan 20 13:21:40 pegaz kernel: [ 41.089635] r8169 0000:05:03.0 lan:
Link is Down
Jan 20 13:21:40 pegaz kernel: [ 43.407167] r8169 0000:05:03.0 lan:
Link is Up - 1Gbps/Full - flow control rx/tx
Jan 20 13:21:40 pegaz kernel: [ 43.407187] IPv6:
ADDRCONF(NETDEV_CHANGE): lan: link becomes ready
# cat /var/log/kern.log | grep fault.addr | sed -r 's/.*DMAR://; s/addr
[a-z0-9]+/addr XXXXX/' | uniq -c
550 [DMA Read] Request device [05:00.0] PASID ffffffff fault addr
XXXXX [fault reason 06] PTE Read access is not set
> I wonder if this has something to do with the interfaces being renamed.
> If possible, could you change your configuration to avoid renaming them
> and confirm this?
This is production server, I don't have free phisical access to it, so I
can't do experiments...
> And, could you give a try to the latest version in sid?
I can't unfortunatelly, because this is production server.
After upgrade to bullseye there are lots of errors:
[29466.139246] DMAR: DRHD: handling fault status reg 2
[29466.139255] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff97f000 [fault reason 06] PTE Read access is not set
[29483.284987] DMAR: DRHD: handling fault status reg 2
[29483.284997] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff97e000 [fault reason 06] PTE Read access is not set
[29483.285137] DMAR: DRHD: handling fault status reg 2
[29483.285144] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff9e9000 [fault reason 06] PTE Read access is not set
[29483.286685] DMAR: DRHD: handling fault status reg 2
[29483.286692] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ffbcf000 [fault reason 06] PTE Read access is not set
[29483.286762] DMAR: DRHD: handling fault status reg 2
[29667.451183] dmar_fault: 20 callbacks suppressed
[29667.451184] DMAR: DRHD: handling fault status reg 2
[29667.451204] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff9c4000 [fault reason 06] PTE Read access is not set
[29720.179279] DMAR: DRHD: handling fault status reg 2
[29720.179301] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff9a2000 [fault reason 06] PTE Read access is not set
[29720.179725] DMAR: DRHD: handling fault status reg 2
[29720.179738] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ffabe000 [fault reason 06] PTE Read access is not set
[29720.179913] DMAR: DRHD: handling fault status reg 2
[29720.179923] DMAR: [DMA Read] Request device [05:00.0] PASID ffffffff
fault addr ff8b1000 [fault reason 06] PTE Read access is not set
[29720.180654] DMAR: DRHD: handling fault status reg 2
