| K.S. Bhaskar via plug on 26 Apr 2022 08:09:28 -0700 |
[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]
| Re: [PLUG] Kubuntu 22.04 loses network connectivity spontaneously |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On Tue, 2022-04-26 at 06:09 -0400, K.S. Bhaskar via plug wrote:
> We have decided to revert to Arch (which is my personal Linux distro
> preference for my laptop; in our development environment we run a
> variety of machines and distros). In our testing environment, Fedora
> 35 had userspace and utility issues like Arch, so we decided to stay
> with what we are comfortable with.
>
I've been following this thread and I think that possibly the answer
might be found in the kernel source of the debian based distro and the
arch based distro. You mignt want to do a diff on the configuration
file of the kernel. Each distribution compiles their own kernels. As
Arch is a rolling distribution, you always have the latest kernel
version.
https://archlinux.org/packages/core/x86_64/linux/
when you click on the source files you see the PKGBUILD and the config
files. You might want to compair the config files of the working Arch
Distribution with the Debian based Distribution. There might be
differences in the timers and such.
> Thank you for your help.
>
> Regards
> - Bhaskar
>
> On Tue, Apr 26, 2022 at 12:34 AM Rich Mingin (PLUG) <plug@frags.us>
> wrote:
> > Very odd. The Intel gig drivers are generally well behaved and well
> > tested. I'm not sure what's most likely at this point, maybe bad
> > firmware/power management options.
> >
> > On Mon, Apr 25, 2022 at 17:14 K.S. Bhaskar via plug
> > <plug@lists.phillylinux.org> wrote:
> > > Rich -
> > >
> > > I installed Fedora 35 on yet another partition, and the network
> > > remains up on Fedora. This is what Fedora's lshw says is the NIC:
> > >
> > > *-network
> > > description: Ethernet interface
> > > product: Ethernet Connection (2) I219-V
> > > vendor: Intel Corporation
> > > physical id: 1f.6
> > > bus info: pci@0000:00:1f.6
> > > logical name: enp0s31f6
> > > version: 00
> > > serial: 70:85:c2:38:ed:51
> > > size: 1Gbit/s
> > > capacity: 1Gbit/s
> > > width: 32 bits
> > > clock: 33MHz
> > > capabilities: pm msi bus_master cap_list ethernet
> > > physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
> > > configuration: autonegotiation=on broadcast=yes
> > > driver=e1000e driverversion=5.17.4-200.fc35.x86_64 duplex=full
> > > firmware=0.2-4 ip=<IPv4 ADDRESS> latency=0 link=yes multicast=yes
> > > port=twisted pair speed=1Gbit/s
> > > resources: irq:144 memory:df200000-df21ffff
> > >
> > > Ubuntu 22.04 is really our preferred OS distro for this machine.
> > > Thank you.
> > >
> > > Regards
> > > - Bhaskar
> > >
> > >
> > > On Mon, Apr 25, 2022 at 1:37 PM Rich Mingin (PLUG)
> > > <plug@frags.us> wrote:
> > > > Apologies, originally replied to the wrong person. What nic is
> > > > it? There are no documented universal issues with that part of
> > > > the network stack, making me think it’s likely device specific.
> > > > Knowing what device that is will help troubleshoot.
> > > >
> > > > Running system level tests and looping shell scripts to tell
> > > > you what you already know (nic goes away, comes back, seems
> > > > related to idle/sleep/low power, but unclear how exactly)
> > > > doesn’t seem likely to be fruitful.
> > > >
> > > > Since we have one known good state (same hardware running arch)
> > > > and one known bad state (running 22.04, no other changes), we
> > > > are at least close to knowing the variables.
> > > >
> > > >
> > > > On Mon, Apr 25, 2022 at 11:20 AM K.S. Bhaskar via plug
> > > > <plug@lists.phillylinux.org> wrote:
> > > > > No luck with fiddling with the power saving settings: it
> > > > > still randomly drops the network connection. This has to be
> > > > > one of the most puzzling issues I have encountered.
> > > > >
> > > > > Thanks for the suggestions, all.
> > > > >
> > > > > Regards
> > > > > - Bhaskar
> > > > >
> > > > > On Sat, Apr 23, 2022 at 6:09 AM K.S. Bhaskar
> > > > > <ksbhaskar@gmail.com> wrote:
> > > > > > Thanks, that's a good thought. I'll check it when I'm back
> > > > > > in the office next week.
> > > > > >
> > > > > > Regards
> > > > > > - Bhaskar
> > > > > >
> > > > > > On Sat, Apr 23, 2022 at 5:29 AM Joe Rosato
> > > > > > <rosatoj@gmail.com> wrote:
> > > > > > > Looks like I'm late to the party but figured I throw a
> > > > > > > thought in... Could it be power saving settings? I read
> > > > > > > this pretty quickly but didn't see that mentioned...
> > > > > > >
> > > > > > > Joe
> > > > > > >
> > > > > > > On Fri, Apr 22, 2022, 9:45 PM K.S. Bhaskar via plug
> > > > > > > <plug@lists.phillylinux.org> wrote:
> > > > > > > > Here's how it played out.
> > > > > > > >
> > > > > > > > dmesg was not helpful. It merely recorded that the NIC
> > > > > > > > was down, and that some time later it was up. At least
> > > > > > > > it told us that Linux knew the NIC was down.
> > > > > > > >
> > > > > > > > I tried JP's ugly hack, having it run once a minute. No
> > > > > > > > luck. When it went down, it stayed down until it
> > > > > > > > decided to come up, for reasons known only to itself.
> > > > > > > >
> > > > > > > > Debugging it by logging in at the console was no help,
> > > > > > > > because the moment anyone logged in, moved a mouse or
> > > > > > > > did something at the console, the network came back to
> > > > > > > > life. It did not go down when I was logged in at the
> > > > > > > > console (that's not to say that it would; just that it
> > > > > > > > didn't on those occasions when I was logged in to see
> > > > > > > > whether I could be logged in when it went down).
> > > > > > > >
> > > > > > > > As I installed Kubuntu into a different partition from
> > > > > > > > the prior Arch Linux, which was untouched by the
> > > > > > > > Kubuntu installation, I reverted to Arch Linux and
> > > > > > > > that's what it's running for the weekend. Since the
> > > > > > > > Arch has not lost the network for several hours (vs.
> > > > > > > > 20-30 minutes for Kubuntu), I'm confident that it's not
> > > > > > > > a hardware problem.
> > > > > > > >
> > > > > > > > All in all, it has been a very frustrating day.
> > > > > > > >
> > > > > > > > Regards
> > > > > > > > – Bhaskar
> > > > > > > >
> > > > > > > > On Fri, Apr 22, 2022 at 7:02 PM Rich Mingin (PLUG) via
> > > > > > > > plug <plug@lists.phillylinux.org> wrote:
> > > > > > > > > What nic? If it was a universal issue it would have
> > > > > > > > > been reported plenty by now. More likely a device
> > > > > > > > > specific bug.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Fri, Apr 22, 2022 at 3:52 PM JP Vossen via plug
> > > > > > > > > <plug@lists.phillylinux.org> wrote:
> > > > > > > > > > On 4/22/22 15:25, K.S. Bhaskar via plug wrote:
> > > > > > > > > > > I did a fresh install of Kubuntu 22.04 this
> > > > > > > > > > > morning and a bizarre behavior has me scratching
> > > > > > > > > > > my head. As the machine (a 2017 PC, high end at
> > > > > > > > > > > the time) is used primarily as a server, and
> > > > > > > > > > > occasionally as a desktop, most of the time the
> > > > > > > > > > > monitor is powered down and the wireless mouse is
> > > > > > > > > > > turned off to conserve the battery. Every so
> > > > > > > > > > > often, it loses its network connection. ...
> > > > > > > > > > Really ugly hack?
> > > > > > > > > > ```
> > > > > > > > > > */5 * * * * root /bin/ping -c2 10.10.10.10 >
> > > > > > > > > > /dev/null || { echo 'Resetting eth0!' ;
> > > > > > > > > > /sbin/ifconfig eth0 down ; /sbin/ifconfig eth0 up ;
> > > > > > > > > > ip route add default via 10.10.10.10 dev eth0 ; }
> > > > > > > > > >
> > > > > > > > > > ```
> > > > > > > > > >
> > > > > > > > > > Where 10.10.10.10 is the node's default gateway,
> > > > > > > > > > and "eth0" is the buggy interface. That's from
> > > > > > > > > > when I had a box with a wonky USB Ethernet
> > > > > > > > > > adapter. It didn't fix the problem, and it didn't
> > > > > > > > > > always work, but...it worked sometimes.
> > > > > > > > > >
> > > > > > > > > > Much better to find and fix the root cause, of
> > > > > > > > > > course, but maybe this is a help until then, and
> > > > > > > > > > might allow more data collection to find the
> > > > > > > > > > problem.
> > > > > > > > > >
> > > > > > > > > > Later,
> > > > > > > > > > JP
> > > > > > > > > > -- -----------------------------------------------
> > > > > > > > > > --------------------
> > > > > > > > > > JP Vossen, CISSP | http://www.jpsdomain.org/ |
> > > > > > > > > > http://bashcookbook.com/
> > > > > > > > > > ___________________________________________________
> > > > > > > > > > ________________________
> > > > > > > > > > Philadelphia Linux Users Group --
> > > > > > > > > > http://www.phillylinux.org
> > > > > > > > > > Announcements -
> > > > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > > > > > > > > > General Discussion --
> > > > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug
> > > > > > > > > _____________________________________________________
> > > > > > > > > ______________________
> > > > > > > > > Philadelphia Linux Users Group --
> > > > > > > > > http://www.phillylinux.org
> > > > > > > > > Announcements -
> > > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > > > > > > > > General Discussion --
> > > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug
> > > > > > > > _______________________________________________________
> > > > > > > > ____________________
> > > > > > > > Philadelphia Linux Users Group --
> > > > > > > > http://www.phillylinux.org
> > > > > > > > Announcements -
> > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > > > > > > > General Discussion --
> > > > > > > > http://lists.phillylinux.org/mailman/listinfo/plug
> > > > > _____________________________________________________________
> > > > > ______________
> > > > > Philadelphia Linux Users Group --
> > > > > http://www.phillylinux.org
> > > > > Announcements -
> > > > > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > > > > General Discussion --
> > > > > http://lists.phillylinux.org/mailman/listinfo/plug
> > > _________________________________________________________________
> > > __________
> > > Philadelphia Linux Users Group --
> > > http://www.phillylinux.org
> > > Announcements -
> > > http://lists.phillylinux.org/mailman/listinfo/plug-announce
> > > General Discussion --
> > > http://lists.phillylinux.org/mailman/listinfo/plug
- --
Rev. LeRoy D. Cressy
mailto:rev.cressy@prontonmail.com
/\_/\
( o.o )
> ^ <
Cell Phone: 267-668-9686
GnuPG Fingerprint:
D234 65D6 2822 211B F82F A6CA B332 4CC8 ACBF D200
Jesus saith unto him, I am the way, the truth, and the life:
no man cometh unto the Father, but by me. (John 14:6)
You can find me on the following:
Telegram:
(My Main Channel)
https://t.me/RevLeRoy
(Send Me A Message)
https://t.me/LeRoy_Cressy
(My Videos)
https://t.me/rev_cressy_videos
Video Channels:
ugetube.com:
https://ugetube.com/@the-rev
bitchute.com:
https://www.bitchute.com/channel/the-rev/
brighteon.com:
https://www.brighteon.com/channels/therev
rumble.com:
https://rumble.com/user/lrcressy
odysee.com:
https://odysee.com/@the-rev
-----BEGIN PGP SIGNATURE-----
iHUEARYKAB0WIQS0AKJCtCv8k5X07DIuVTWo1KllbwUCYmfjUQAKCRAuVTWo1Kll
bx/7AP90l4Qgtrg1Oio04Vi95PaBdu2pREZ0fJzKdZG94yEfdQEAhlcnuOLhF7Wu
Jpz0hnr2CTdTKdKVKofmmIPNY9B7Ywc=
=xCsp
-----END PGP SIGNATURE-----
___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug