It appears that the "no route to host" issue was caused by a missing
default route. "route add default gw 192.168.1.1 dev bond0" fixed the
issue. The question is why my routing table was missing such a default
route. My /etc/network/interfaces file specifically references the
gateway, as indicate
Package: src:linux
Version: 4.9.25-1~bpo8+1
Severity: important
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
I upgraded my kernel from linux-image-4.9.0-0.bpo.2-amd64 to
linux-image-4.9.0-0.bpo.2-amd64. Witho
Processing commands for cont...@bugs.debian.org:
> notfound 828826 1:1.2.8-9
Bug #828826 {Done: Andreas Henriksson } [nfs-common]
nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd
No longer marked as found in versions nfs-utils/1:1.2.8-9.
> thanks
Stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> found 828826 1:1.2.8-9.1
Bug #828826 {Done: Andreas Henriksson } [nfs-common]
nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd
Marked as found in versions nfs-utils/1:1.2.8-9.1.
> thanks
Stopping processing here.
Please contact m
Package: src:linux
Version: 4.9.25-1
Severity: normal
Hello,
The arm64 kernel appears missing a couple of DRM modules in the configuration:
# CONFIG_DRM_HDLCD is not set
# CONFIG_DRM_MALI_DISPLAY is not set
# CONFIG_DRM_RADEON is not set
# CONFIG_DRM_AMDGPU is not set
Considering the fact that
5 matches
Mail list logo