You are not logged in.
Pages: 1
My internet is disconnecting constantly. This has been going on for months and I’ve been too busy to really get into it and learn the things I need to in order to diagnose and repair the problem. But it has recently become almost unusable. Disconnecting every few minutes. Other devices on the network do not have any issues.
To deal with it I’ve been just restarting iwd:
systemctl restart iwd.service
and that was working for a while.
I do not have another network manager (that I’m aware of) installed, and have never used anything other than iwd for wifi.
Some things:
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -fcronie.service | multi-user.target.wants
dbus-org.freedesktop.network1.service | system
dbus-org.freedesktop.resolve1.service | system
dbus-org.freedesktop.timesync1.service | system
gcr-ssh-agent.socket | sockets.target.wants
getty@tty1.service | getty.target.wants
gnome-keyring-daemon.socket | sockets.target.wants
iwd.service | multi-user.target.wants
ntpd.service | multi-user.target.wants
p11-kit-server.socket | sockets.target.wants
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-networkd.service | multi-user.target.wants
systemd-networkd.socket | sockets.target.wants
systemd-networkd-wait-online.service | network-online.target.wants
systemd-network-generator.service | sysinit.target.wants
systemd-resolved.service | multi-user.target.wants
systemd-timesyncd.service | sysinit.target.wants
tlp.service | multi-user.target.wants
ufw.service | multi-user.target.wantsand
sudo journalctl -bSep 18 19:23:59 machine kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-15
Sep 18 19:23:59 machine kernel: Linux version 5.19.9-arch1-1 (linux@archlinux) (gcc (GCC) 12.2.0, GNU ld (GNU Binutils) 2.39.0) #1 SMP PREEMPT_DYNAMIC Thu, 15 Sep 2022 16:08:26 +0000
Sep 18 19:23:59 machine kernel: Command line: initrd=\intel-ucode.img initrd=\initramfs-linux.img root=PARTUUID=0f91881d-97f2-4598-9d6b-885979109586 rw intel_pstate=no_hwp
Sep 18 19:23:59 machine kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Sep 18 19:23:59 machine kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Sep 18 19:23:59 machine kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Sep 18 19:23:59 machine kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Sep 18 19:23:59 machine kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Sep 18 19:23:59 machine kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Sep 18 19:23:59 machine kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Sep 18 19:23:59 machine kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Sep 18 19:23:59 machine kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Sep 18 19:23:59 machine kernel: signal: max sigframe size: 2032
Sep 18 19:23:59 machine kernel: BIOS-provided physical RAM map:
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000866b9fff] usable
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000866ba000-0x0000000089c38fff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000089c39000-0x0000000089cb5fff] ACPI data
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000089cb6000-0x0000000089da5fff] ACPI NVS
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000089da6000-0x000000008a40dfff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x000000008a40e000-0x000000008a40efff] usable
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x000000008a40f000-0x000000008fffffff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Sep 18 19:23:59 machine kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046bffffff] usable
Sep 18 19:23:59 machine kernel: NX (Execute Disable) protection: active
Sep 18 19:23:59 machine kernel: e820: update [mem 0x7f75b018-0x7f787657] usable ==> usable
Sep 18 19:23:59 machine kernel: e820: update [mem 0x7f75b018-0x7f787657] usable ==> usable
Sep 18 19:23:59 machine kernel: extended physical RAM map:
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x000000000009f000-0x00000000000fffff] reserved
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x0000000000100000-0x000000007f75b017] usable
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x000000007f75b018-0x000000007f787657] usable
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x000000007f787658-0x00000000866b9fff] usable
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x00000000866ba000-0x0000000089c38fff] reserved
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x0000000089c39000-0x0000000089cb5fff] ACPI data
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x0000000089cb6000-0x0000000089da5fff] ACPI NVS
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x0000000089da6000-0x000000008a40dfff] reserved
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x000000008a40e000-0x000000008a40efff] usable
Sep 18 19:23:59 machine kernel: reserve setup_data: [mem 0x000000008a40f000-0x000000008fffffff] reservedHow do I go about diagnosing this problem? What do I need to learn about?
That's just the head of the journal, we'll need the entire thing.
Don't copy and paste out of the pager.
To redirect the journal into a pastebin service:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
Thank you for the response seth.
http://0x0.st/oVja.txtShould I just paste the link?
What exactly are we looking for?
firmware crashes, beacon losses, … anything to explain the disconnect.
There's no indication for that in the posted log - is it supposed to cover a conneciton loss?
If not, please post an older log (eg. "… -b -1 …" for the previous one) that covers such incident.
Offline
Ok, I'm not exactly sure when it's happened so I don't know which specific logs to post, so I'll just post next time it happens.
But you've already helped me a lot though because now I know where to look and what to look for.
Won't systemd-networkd.service conflict with iwd.service?
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
Not unless you https://wiki.archlinux.org/title/Iwd#En … figuration
systemd-networkd doesn't manage carriers itself, https://wiki.archlinux.org/title/System … ss_adapter
Offline
Pages: 1