[Bug 1906120] [NEW] NetworkManager: error -111 disaptching events on DHCPv4 lease renewal

2020-11-28 Thread Jan Vesely
Public bug reported:

Ubuntu 20.04.1 running on armv7 (IFC6410)

Occasional network interruption with the following message in journal:

Nov 28 12:03:16 drako NetworkManager[4094]:  [1606582996.3983] 
device[dabf59d236aff82b] (enp1s0): activation-stage: complete 
activate_stage5_ip_config_result_6,v6 (id 51751)
Nov 28 12:03:16 drako NetworkManager[4094]:  [1606582996.4026] 
device[dabf59d236aff82b] (enp1s0): ip6-config: update (commit=0, 
new-config=0x803e6140)
Nov 28 12:03:18 drako NetworkManager[4094]:  [1606582998.8611] dhcp4 
(enp1s0): error -111 dispatching events
Nov 28 12:03:18 drako NetworkManager[4094]:   [1606582998.8614] dhcp4 
(enp1s0): state changed extended -> fail
Nov 28 12:03:18 drako NetworkManager[4094]:   [1606582998.8622] device 
(enp1s0): DHCPv4: trying to acquire a new lease within 90 seconds
Nov 28 12:04:49 drako NetworkManager[4094]:   [1606583089.4023] device 
(enp1s0): DHCPv4: grace period expired

the ipv4 connection is then cut (the interface looses ipc4 address and
the ipv4 routes are purged) until NetworkManager is restarted.

The networkmanager-dispatcher.service doesn't indicate any error:

Nov 28 06:04:05 drako systemd[1]: Started Network Manager Script Dispatcher 
Service.
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: new 
request (2 scripts)
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: CONNECTION_FILENAME=/etc/NetworkManager/system-connections/Wired
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: CONNECTION_UUID=fe299e22-2b52-43ff-9a60-fa385e239f41
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: CONNECTION_ID=Wired
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DEVICE_IFACE=enp1s0
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DEVICE_IP_IFACE=enp1s0

Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change'
[enp1s0]: environment: IP4_NUM_ADDRESSES=1

Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change'
[enp1s0]: environment: IP4_NUM_ROUTES=1

Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: IP6_NUM_ROUTES=3
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_DHCP_LEASE_TIME=28800
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_EXPIRY=1606590245

Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_BROADCAST_ADDRESS=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_DOMAIN_NAME=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_DOMAIN_NAME_SERVERS=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_DOMAIN_SEARCH=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_HOST_NAME=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_INTERFACE_MTU=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_MS_CLASSLESS_STATIC_ROUTES=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_NIS_DOMAIN=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_NIS_SERVERS=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_NTP_SERVERS=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_RFC3442_CLASSLESS_STATIC_ROUTES=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_ROOT_PATH=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_ROUTERS=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_STATIC_ROUTES=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_SUBNET_MASK=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_TIME_OFFSET=1
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: DHCP4_REQUESTED_WPAD=1

Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
Nov 28 06:04:05 drako nm-dispatcher[5178]: req:1 'dhcp4-change' [enp1s0]: 
environment: NM_DISPATCHER_ACTION=dhcp4-change
Nov 28 06:04:05 drako nm-dispat

[Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.

2019-11-12 Thread Jan Vesely
I've run into similar problem, and I don't think it's e1000e driver
issue.

My device:
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network 
Connection (Lewisville) (rev 04)
Subsystem: Dell 82579LM Gigabit Network Connection (Lewisville)
Kernel driver in use: e1000e
Kernel modules: e1000e

speedtest-cli gives:
Download: 93.51 Mbit/s
Testing upload Upload: 3.91 Mbit/s

However, if I run speedtest from fedora VM on the same machine it gives:
Download: 93.40 Mbit/s
Upload: 68.75 Mbit/s

it doesn't even have to be a VM. Running docker:
$ docker run --rm  -it fedora:latest /bin/bash
[root@e4d188a07bff /]# dnf install -y speedtest-cli
...
[root@e4d188a07bff /]# speedtest-cli
...
Download: 81.67 Mbit/s
Upload: 39.02 Mbit/s

However:
$ docker run --rm  fedora:latest dnf install -y speedtest-cli && speedtest-cli
...
...
...
Download: 93.48 Mbit/s
Upload: 3.86 Mbit/s

More experiemnts:
$ docker run --rm -it  fedora:latest dnf install -y speedtest-cli && 
speedtest-cli
...
...
...
Download: 93.48 Mbit/s
Upload: 3.86 Mbit/s

finally, $ docker run --rm -it  fedora:latest /bin/bash -c "dnf install -y 
speedtest-cli && speedtest-cli"
...
...
Download: 93.46 Mbit/s
Upload: 66.97 Mbit/s

so it looks like ubuntu is detecting interactive processes and
deprioritizing everything else

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830197

Title:
  e1000e driver - uploading slowed to a crawl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.

2019-11-12 Thread Jan Vesely
Oh and it's also for certain hosts. Connecting to a host on the same
network gives reliable 96Mbps.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830197

Title:
  e1000e driver - uploading slowed to a crawl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.

2019-11-13 Thread Jan Vesely
some more testing:
latest == bionic:
docker run --rm -it  ubuntu:latest /bin/bash -c "apt-get update && apt-get 
upgrade && apt-get install -y speedtest-cli ca-certificates && speedtest-cli"
Download: 93.44 Mbit/s
Upload: 3.95 Mbit/s

xenial:
docker run --rm -it  ubuntu:xenial /bin/bash -c "apt-get update && apt-get 
install -y speedtest-cli ca-certificates && speedtest-cli"
Download: 88.55 Mbit/s
Upload: 37.09 Mbit/s

disco:
docker run --rm -it  ubuntu:disco /bin/bash -c "apt-get update && apt-get 
install -y speedtest-cli ca-certificates && speedtest-cli"
Download: 93.52 Mbit/s
Upload: 36.26 Mbit/s

so the 4 Mbit/s upload limitation exists only on bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830197

Title:
  e1000e driver - uploading slowed to a crawl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874157] [NEW] pypy3 pip broken

2020-04-21 Thread Jan Vesely
Public bug reported:

#run latest bionic
$docker run -it ubuntu:latest

root@78ea77256364:/# apt update
...NO ERRORS...

root@78ea77256364:/# apt upgrade
...NO ERRORS...

root@78ea77256364:/# apt install software-properties-common
...NO ERRORS...

root@78ea77256364:/# apt-add-repository -y ppa:pypy/ppa
...NO ERRORS...

root@78ea77256364:/# apt install -y pypy3-dev
...NO ERRORS...

root@78ea77256364:/# pypy3 --version
Python 3.6.9 (7.3.1+dfsg-1~ppa1~ubuntu18.04, Apr 11 2020, 00:13:00)
[PyPy 7.3.1 with GCC 7.5.0]

root@78ea77256364:/# cd
root@78ea77256364:~# pypy3 -m venv test
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python-pip-whl
package using the following command.

apt-get install python-pip-whl

You may need to use sudo with that command.  After installing the
python-pip-whl package, recreate your virtual environment.

Failing command: ['/root/test/bin/pypy3-c', '-Im', 'ensurepip', '--
upgrade', '--default-pip']

root@78ea77256364:~# apt install -y python-pip-whl
...NO ERRORS...

root@78ea77256364:~# pypy3 -m venv test
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python-pip-whl
package using the following command.

apt-get install python-pip-whl

You may need to use sudo with that command.  After installing the
python-pip-whl package, recreate your virtual environment.

Failing command: ['/root/test/bin/pypy3-c', '-Im', 'ensurepip', '--
upgrade', '--default-pip']

root@78ea77256364:~# apt install -y python3-pip
...NO ERRORS...

root@78ea77256364:~# pypy3 -m venv test
The virtual environment was not created successfully because ensurepip is not
available.  On Debian/Ubuntu systems, you need to install the python-pip-whl
package using the following command.

apt-get install python-pip-whl

You may need to use sudo with that command.  After installing the
python-pip-whl package, recreate your virtual environment.

Failing command: ['/root/test/bin/pypy3-c', '-Im', 'ensurepip', '--
upgrade', '--default-pip']

root@78ea77256364:~# pypy3 -m pip --version
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/pip/__init__.py", line 22, in 
from pip._vendor.requests.packages.urllib3.exceptions import 
DependencyWarning
ModuleNotFoundError: No module named 'pip._vendor.requests'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
  File "/usr/lib/python3/dist-packages/pip/__init__.py", line 24, in 
from urllib3.exceptions import DependencyWarning
ModuleNotFoundError: No module named 'urllib3'

root@78ea77256364:~# apt install -y python3-urllib3

root@78ea77256364:~# pypy3 -m pip --version
Traceback (most recent call last):
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 183, in _run_module_as_main
mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 142, in _get_module_details
return _get_module_details(pkg_main_name, error)
  File "/usr/lib/pypy3/lib-python/3/runpy.py", line 109, in _get_module_details
__import__(pkg_name)
  File "/usr/lib/python3/dist-packages/pip/__init__.py", line 29, in 
from pip.utils import get_installed_distributions, get_prog
  File "/usr/lib/python3/dist-packages/pip/utils/__init__.py", line 30, in 

from pip._vendor.retrying import retry
ModuleNotFoundError: No module named 'pip._vendor.retrying'

** Affects: pypy3 (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/1874157

Title:
  pypy3 pip broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pypy3/+bug/1874157/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874157] Re: pypy3 pip broken

2020-04-21 Thread Jan Vesely
the alternative to use pip bootstrap doesn't work either:

root@8ad116a28545:/# curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py
...NO ERRORS...

oot@8ad116a28545:/# pypy3 get-pip.py 
Collecting pip
  Downloading pip-20.0.2-py2.py3-none-any.whl (1.4 MB)
 || 1.4 MB 4.8 MB/s 
Collecting setuptools
  Downloading setuptools-46.1.3-py3-none-any.whl (582 kB)
 || 582 kB 15.5 MB/s 
Collecting wheel
  Downloading wheel-0.34.2-py2.py3-none-any.whl (26 kB)
Installing collected packages: pip, setuptools, wheel
  WARNING: The scripts pip, pip3 and pip3.6 are installed in 
'/usr/lib/pypy3/../../local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this 
warning, use --no-warn-script-location.
  WARNING: The scripts easy_install and easy_install-3.6 are installed in 
'/usr/lib/pypy3/../../local/bin' which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this 
warning, use --no-warn-script-location.
  WARNING: The script wheel is installed in '/usr/lib/pypy3/../../local/bin' 
which is not on PATH.
  Consider adding this directory to PATH or, if you prefer to suppress this 
warning, use --no-warn-script-location.
Successfully installed pip-20.0.2 setuptools-46.1.3 wheel-0.34.2

root@8ad116a28545:/# pypy3 -m pip --version
/usr/bin/pypy3: No module named pip

the problem is in the package paths:

root@8ad116a28545:/# ls /usr/local/lib/pypy3*/dist-packages
/usr/local/lib/pypy3.6/dist-packages:
__pycache__  pip-20.0.2.dist-info  setuptools-46.1.3.dist-info
easy_install.py  pkg_resources wheel
pip  setuptoolswheel-0.34.2.dist-info

/usr/local/lib/pypy3/dist-packages:


root@8ad116a28545:/# PYTHONPATH=/usr/local/lib/pypy3.6/dist-packages/ pypy3 -m 
pip --version
pip 20.0.2 from /usr/local/lib/pypy3.6/dist-packages/pip (python 3.6)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874157

Title:
  pypy3 pip broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pypy3/+bug/1874157/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1830197] Re: e1000e driver - uploading slowed to a crawl.

2019-12-28 Thread Jan Vesely
I'm not sure if speedtest-cli directly or something in python or one of the 
involved libraries.
I was investigating it because appveyor CI images suffered extremely long 
upload speeds, but that got fixed between Dec 18th and 19th. I haven't 
investigated what the change was, but there was a point release of every python 
version around that time.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830197

Title:
  e1000e driver - uploading slowed to a crawl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1830197/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1874157] Re: pypy3 pip broken

2020-05-01 Thread Jan Vesely
thank you for the swift response. I can confirm that both issues are
fixed for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874157

Title:
  pypy3 pip broken

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pypy3/+bug/1874157/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs