[Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
FWIW, I tried reproducing this artificially by running 200 Kubernetes Pods on a freshly installed Focal and the issue did not occur. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
** Attachment added: "1912331-config-files.zip" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+attachment/5466762/+files/1912331-config-files.zip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
Where would I find those files? systemd-networkd is not something I have consciously installed or configured, it just came with Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912331] Re: Many interfaces lead to "kernel receive buffer overrun"
I don't completely understand it myself. I have a Focal system with k3s installed and about 70 pods (about 150 containers) and about 70 veth devices. In /lib/systemd/system/systemd-networkd.socket under "[Socket]" I have set "ReceiveBuffer=128M". Maybe that "128M" isn't enough but I can't add any more pods without getting "Could not enumerate addresses: No buffer space available" errors, so I *assumed* there's more to that patch than just the ReceiveBuffer setting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1912331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1912331] [NEW] Many interfaces lead to "kernel receive buffer overrun"
Public bug reported: This is about a systemd-networkd bug, described here: https://github.com/systemd/systemd/issues/14417 There's a patch available: https://github.com/systemd/systemd/pull/16982 Can this be backported to Focal? ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1912331 Title: Many interfaces lead to "kernel receive buffer overrun" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1912331/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1076786] [NEW] CUPS serial backend does not work
Public bug reported: In a fresh install /usr/lib/cups/backend/serial has 755: -rwxr-xr-x 1 root root 14664 May 18 10:05 serial For some reason with these permission it doesn't work at all. chmod 700 /usr/lib/cups/backend/serial fixes the problem. Where I got the idea to try that: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516945 ** Affects: cups-filters (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1076786 Title: CUPS serial backend does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-filters/+bug/1076786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 928264] [NEW] Segfault in dmraid when trying to rebuild array
Public bug reported: # dmraid -R "jmicron_GRAID" /dev/sda ERROR: jmicron: wrong # of devices in RAID set "jmicron_GRAID" [1/2] on /dev/sdb Speicherzugriffsfehler # dmesg [...] [13845.567340] dmraid[3769]: segfault at 38 ip b77f363f sp bfc071b0 error 6 in libdmraid.so.1.0.0.rc16[b77e4000+3] # dmraid -s ERROR: jmicron: wrong # of devices in RAID set "jmicron_GRAID" [1/2] on /dev/sdb *** *Inconsistent* Set name : jmicron_GRAID size : 976748544 stride : 2 type : mirror status : inconsistent subsets: 0 devs : 1 spares : 0 # dmraid -r /dev/sdb: jmicron, "jmicron_GRAID", mirror, ok, 976748544 sectors, data@ 0 # lsb_release -rd Description:Ubuntu 10.10 Release:10.10 # apt-cache policy dmraid dmraid: Installiert: 1.0.0.rc16-3ubuntu2 # apt-cache policy libdmraid1.0.0.rc16 libdmraid1.0.0.rc16: Installiert: 1.0.0.rc16-3ubuntu2 ** Affects: dmraid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/928264 Title: Segfault in dmraid when trying to rebuild array To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/928264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
