Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Network Manager not working - but Wicked working

  1. #1
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,704
    Blog Entries
    39

    Default Network Manager not working - but Wicked working

    I ran into a problem this morning with Network Manager not working. It was working yesterday (both on LAN and Internet) with ipv6 disabled, with and without a vpn service (where I enabled the vpn yesterday via openVPN). This is a wired connection. I have this same setup on both a laptop and and another desktop and no issue.

    However this morning Network Manager was not working. I re-enabled ipv6 and enabled wicked app (in Yast), rebooted, and I have LAN access and Internet. IMHO that points the finger at Network Manager.

    As a sanity/problem-assessment test, I went to YaST, disabled ipv6 and enabled Network Manager and no LAN nor internet. Re-enabling ipv6 and 'Wicked' app and rebooting, and I again have LAN/Internet (with wicked). I went to an internet 'whats my ip address site' and ipv4 is definitely working with wicked.

    I'm not sure where to start investigating this ... From inxi here is my hardware when booting with NetworkManger (but no LAN/internet) :
    Code:
    Network:   Device-1: Marvell 88E8056 PCI-E Gigabit Ethernet driver: sky2 
               IF: eth1 state: up speed: 100 Mbps duplex: half mac: 00:24:8c:7e:ee:38 
               Device-2: Marvell 88E8056 PCI-E Gigabit Ethernet driver: sky2 
               IF-ID-1: eth0 state: down mac: 00:24:8c:7e:ee:39
    Networkmanager Service when booting with it supposed to be enabled (but no LAN/internet) :
    Code:
    oldcpu@olddarmstadt:~> systemctl status NetworkManager.service
    ● NetworkManager.service - Network Manager
       Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
      Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
               └─NetworkManager-ovs.conf
       Active: active (running) since Sun 2020-06-14 04:19:49 +07; 9min ago
         Docs: man:NetworkManager(8)
     Main PID: 3549 (NetworkManager)
        Tasks: 4
       CGroup: /system.slice/NetworkManager.service
               ├─3549 /usr/sbin/NetworkManager --no-daemon
               └─4293 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth1.pid -lf /var/lib/NetworkManager/dhc>
    I note a "-no-daemon' above under CGroup but I do not know if that is meaningful.

    Again, booting with NetworkManager supposed to be enabled (but no LAN/internet)
    Code:
    oldcpu@olddarmstadt:~> ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
    2: eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
        link/ether 00:24:8c:7e:ee:39 brd ff:ff:ff:ff:ff:ff
    3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 00:24:8c:7e:ee:38 brd ff:ff:ff:ff:ff:ff
        inet6 fe80::547d:57bb:149c:d1df/64 scope link noprefixroute 
           valid_lft forever preferred_lft forever
    and some dmesg extracts when booting with Network Manager supposed to be enabled (but no LAN/internet)
    Code:
    [   13.767521] sky2: driver version 1.30
    [   13.767634] sky2 0000:06:00.0: Yukon-2 EC Ultra chip revision 3
    [   13.767858] sky2 0000:06:00.0 eth0: addr 00:24:8c:7e:ee:39
    [   13.767936] sky2 0000:04:00.0: Yukon-2 EC Ultra chip revision 3
    [   13.768130] sky2 0000:04:00.0 eth1: addr 00:24:8c:7e:ee:38
    ==== snipped =====
    [   21.758893] ip_tables: (C) 2000-2006 Netfilter Core Team
    [   21.834024] ip6_tables: (C) 2000-2006 Netfilter Core Team
    [   22.145502] Ebtables v2.0 registered
    [   22.320803] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
    [   22.735587] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
    [   22.736485] Bridge firewalling registered
    [   23.077273] Netfilter messages via NETLINK v0.30.
    [   23.090277] ip_set: protocol 6
    [   23.367388] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   23.370389] sky2 0000:06:00.0 eth0: enabling interface
    [   23.370503] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [   23.373126] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [   23.376180] sky2 0000:04:00.0 eth1: enabling interface
    [   23.376257] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [   26.736987] sky2 0000:04:00.0 eth1: Link is up at 1000 Mbps, full duplex, flow control both
    [   26.737010] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [   27.496605] NET: Registered protocol family 17
    [   32.098840] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [   41.947765] NETDEV WATCHDOG: eth1 (sky2): transmit queue 0 timed out
    [   41.947765] NETDEV WATCHDOG: eth1 (sky2): transmit queue 0 timed out
    [   41.947781] ------------[ cut here ]------------
    [   41.947787] WARNING: CPU: 0 PID: 0 at ../net/sched/sch_generic.c:463 dev_watchdog+0x214/0x220
    [   41.947788] Modules linked in: af_packet xt_tcpudp ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute br_netfilter bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables x_tables dmi_sysfs vboxnetadp(O) msr vboxnetflt(O) vboxdrv(O) snd_hda_codec_analog snd_hda_codec_generic ledtrig_audio iTCO_wdt iTCO_vendor_support intel_powerclamp coretemp snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm kvm_intel lpc_ich snd_timer kvm asus_atk0110 snd irqbypass soundcore i7core_edac sky2 i5500_temp
    [   41.947820]  i2c_i801 pcspkr pcc_cpufreq acpi_cpufreq ata_generic pata_marvell sr_mod cdrom hid_generic usbhid nouveau crc32c_intel mxm_wmi video i2c_algo_bit drm_kms_helper syscopyarea firewire_ohci sysfillrect sysimgblt xhci_pci fb_sys_fops firewire_core crc_itu_t ehci_pci serio_raw ttm ahci uhci_hcd xhci_hcd ehci_hcd libahci drm usbcore drm_panel_orientation_quirks wmi button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
    [   41.947838] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G          IO     4.12.14-lp151.28.48-default #1 openSUSE Leap 15.1
    [   41.947839] Hardware name: System manufacturer System Product Name/P6T DELUXE V2, BIOS 1108    09/21/2010
    [   41.947840] task: ffffffff820134c0 task.stack: ffffffff82000000
    [   41.947841] RIP: 0010:dev_watchdog+0x214/0x220
    [   41.947842] RSP: 0018:ffff8801b9203e90 EFLAGS: 00010286
    [   41.947843] RAX: 0000000000000038 RBX: 0000000000000000 RCX: 0000000000000000
    [   41.947844] RDX: ffff8801b9220280 RSI: ffff8801b9217a68 RDI: ffff8801b9217a68
    [   41.947845] RBP: ffff8801b1ea145c R08: 00000000000003b9 R09: 0000000000000001
    [   41.947845] R10: ffff8801b9203f08 R11: 0000000000000001 R12: ffff8801af888c80
    [   41.947846] R13: 0000000000000000 R14: ffff8801b1ea1000 R15: 0000000000000001
    [   41.947847] FS:  0000000000000000(0000) GS:ffff8801b9200000(0000) knlGS:0000000000000000
    [   41.947848] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [   41.947849] CR2: 00007fc7c43ec0b0 CR3: 00000001b40b6000 CR4: 00000000000006f0
    [   41.947849] Call Trace:
    [   41.947852]  <IRQ>
    [   41.947855]  ? pfifo_fast_reset+0x110/0x110
    [   41.947857]  call_timer_fn+0x30/0x130
    [   41.947859]  run_timer_softirq+0x3c8/0x420
    [   41.947862]  ? timerqueue_add+0x52/0x80
    [   41.947866]  ? enqueue_hrtimer+0x37/0x80
    [   41.947868]  ? recalibrate_cpu_khz+0x10/0x10
    [   41.947871]  __do_softirq+0xde/0x2c6
    [   41.947874]  irq_exit+0xba/0xc0
    [   41.947875]  smp_apic_timer_interrupt+0x3f/0x60
    [   41.947877]  apic_timer_interrupt+0x8f/0xa0
    [   41.947878]  </IRQ>
    [   41.947881] RIP: 0010:cpuidle_enter_state+0x9f/0x2e0
    [   41.947881] RSP: 0018:ffffffff82003e50 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
    [   41.947882] RAX: ffff8801b9224500 RBX: 00000009c4469bb5 RCX: 000000000000001f
    [   41.947883] RDX: 00000009c4469bb5 RSI: 000000002fe42326 RDI: 0000000000000000
    [   41.947884] RBP: ffffe8ffffa0d090 R08: 0000000000000004 R09: 0000000000023d40
    [   41.947884] R10: ffffffff82003e30 R11: 0000000000000183 R12: 0000000000000002
    [   41.947885] R13: ffffffff820d7ef8 R14: 0000000000000000 R15: 00000009c4426bfd
    [   41.947888]  do_idle+0x183/0x1e0
    [   41.947890]  cpu_startup_entry+0x5d/0x60
    [   41.947893]  start_kernel+0x425/0x42d
    [   41.947895]  ? early_idt_handler_array+0x120/0x120
    [   41.947897]  x86_64_start_kernel+0x139/0x148
    [   41.947900]  secondary_startup_64+0xa5/0xb0
    [   41.947901] Code: 63 8e 60 04 00 00 eb 8f 4c 89 f7 c6 05 1f 83 a4 00 01 e8 40 d2 fc ff 89 d9 48 89 c2 4c 89 f6 48 c7 c7 88 1b ed 81 e8 ec 9f ad ff <0f> 0b eb bd 0f 1f 84 00 00 00 00 00 66 66 66 66 90 41 57 41 56 
    [   41.947918] ---[ end trace edf85cc2b60398c5 ]---
    [   41.947921] sky2 0000:04:00.0 eth1: tx timeout
    [   41.947925] sky2 0000:04:00.0 eth1: transmit ring 19 .. 22 report=19 done=19
    [   44.970552] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [   84.958901] sky2 0000:04:00.0 eth1: tx timeout
    [   84.958906] sky2 0000:04:00.0 eth1: transmit ring 21 .. 23 report=21 done=21
    [   87.981531] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [  105.234715] fuse init (API version 7.26)
    [  127.962131] sky2 0000:04:00.0 eth1: tx timeout
    [  127.962137] sky2 0000:04:00.0 eth1: transmit ring 21 .. 24 report=21 done=21
    [  130.984694] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [  175.833276] sky2 0000:04:00.0 eth1: tx timeout
    [  175.833283] sky2 0000:04:00.0 eth1: transmit ring 21 .. 23 report=21 done=21
    [  178.855929] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    I can see from the dmesg that all is not well with the many "tx timeout" (where the last 3 lines keep repeating).

    I have the same behaviour (NetworkManager not working) with the older 4.12.14-lp151.28.48-default kernel and today's 4.12.14-lp151.28.52-default kernel.

    Again - 'wicked' works, but I would prefer to use NetworkManager with openVPN ....

    My experience is such problems are usually because I did something stupid. My main thought is I somehow messed up the NetworkManager configuration when setting up the openVPN yesterday, but the openVPN (Express VPN) worked fine for many hours (although there was no test reboot after setting it up). Only this morning when booting - did I see the problem. I was NOT using the VPN this morning at all.
    .
    Last edited by oldcpu; 13-Jun-2020 at 21:11.

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,262
    Blog Entries
    1

    Default Re: Network Manager not working - but Wicked working

    Hi Lee. I'm using openSUSE Leap 15.1 with NetworkManager, but not aware of any issues. However, I will note that I'm using the current stable kernel (5.7.2-1.g76290d7-default) as well. Anyway, with respect to the unusual interface negotiation reported (Link is up at 100 Mbps, half duplex), have you checked the NM connection configuration? Is link negotiation set as 'Automatic' or manually set to match your router/switch interface requirelements?
    openSUSE Leap 15.2; KDE Plasma 5

  3. #3
    Join Date
    Sep 2012
    Posts
    5,982

    Default Re: Network Manager not working - but Wicked working

    Quote Originally Posted by oldcpu View Post
    IMHO that points the finger at Network Manager.
    This is kernel driver problem. It is possible that NM does something differently or with different timing but user application must not be able to crash kernel driver. It sounds similar to https://bugzilla.kernel.org/show_bug.cgi?id=199783

    Did you install any updates recently (there was recent kernel update)? Can you reliably reproduce this problem? If yes, try previous kernel and if problem goes away, open bug report.

  4. #4
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,704
    Blog Entries
    39

    Default Re: Network Manager not working - but Wicked working

    Quote Originally Posted by arvidjaar View Post
    This is kernel driver problem. It is possible that NM does something differently or with different timing but user application must not be able to crash kernel driver. It sounds similar to https://bugzilla.kernel.org/show_bug.cgi?id=199783

    Did you install any updates recently (there was recent kernel update)? Can you reliably reproduce this problem? If yes, try previous kernel and if problem goes away, open bug report.
    Initially this worked for two days on the older 4.12.14-lp151.28.48-default kernel. But then this morning it stopped working on the older 4.12.14-lp151.28.48-default kernel.

    So after switching to Wicked, I had LAN/Internet access, so I installed the 4.12.14-lp151.28.52-default kernel (which is a recent kernel update), and with updated kernel switched back to NetworkManager but I get the same NetworkManager failure to connect problem (with the call trace). This is 100% repeatable so far.

    EDIT (correction) - DELETED comment wrt LEAP-15.0 - it works under Wicked (I did not test Network Manager with it).

    This is the NetworkManager general configuration (with LAN/internet not working) on LEAP-15.1.


    This is the NetworkManaager 'wired' tab (with LAN/internet not working)

    The above is identical to another PC I have on our home wired LAN with LEAP-15.1 and same kernel .... albeit different motherboard, different cpu. But everything works on that other PC.

    Selecting "Allow auto-negotiation" does not change the failure to connect to our LAN with the Network manager.

    Note with 'wicked' and the LAN/Interent working, I see this in the dmesg which does make me suspicious of the kernel (as suggested) or an app interacting with the kernel ??

    This first bit of code is with Wicked - internet LAN works:
    Code:
    [   22.001497] sky2 0000:04:00.0 eth1: enabling interface
    [   22.001593] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [   25.340074] sky2 0000:04:00.0 eth1: Link is up at 1000 Mbps, full duplex, flow control both
    [   25.340099] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [   25.440156] NET: Registered protocol family 17
    and then some minutes later, after using YaST to swtich to the Network Manager (and losing LAN/Internet) I get this in the dmesg:
    Code:
    [ 2407.007995] perf: interrupt took too long (2829 > 2500), lowering kernel.perf_event_max_sample_rate to 70500
    [ 2695.338567] sky2 0000:04:00.0 eth1: disabling interface
    [ 2697.117347] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 2697.120307] sky2 0000:06:00.0 eth0: enabling interface
    [ 2697.120389] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
    [ 2697.122918] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 2697.125883] sky2 0000:04:00.0 eth1: enabling interface
    [ 2697.125943] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
    [ 2700.364270] sky2 0000:04:00.0 eth1: Link is up at 1000 Mbps, full duplex, flow control both
    [ 2700.364291] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
    [ 2704.841937] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [ 2715.835432] NETDEV WATCHDOG: eth1 (sky2): transmit queue 0 timed out
    [ 2715.835448] ------------[ cut here ]------------
    [ 2715.835455] WARNING: CPU: 2 PID: 0 at ../net/sched/sch_generic.c:463 dev_watchdog+0x214/0x220
    [ 2715.835456] Modules linked in: joydev fuse af_packet xt_tcpudp ip6t_rpfilter ip6t_REJECT ipt_REJECT xt_conntrack ip_set nfnetlink ebtable_nat ebtable_broute br_netfilter bridge stp llc ip6table_nat nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 ip6table_mangle ip6table_raw ip6table_security iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack libcrc32c iptable_mangle iptable_raw iptable_security ebtable_filter ebtables ip6table_filter iscsi_ibft iscsi_boot_sysfs ip6_tables iptable_filter ip_tables x_tables vboxnetadp(O) vboxnetflt(O) vboxdrv(O) dmi_sysfs msr snd_hda_codec_analog snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_timer intel_powerclamp coretemp snd kvm_intel kvm iTCO_wdt iTCO_vendor_support irqbypass sky2 soundcore
    [ 2715.835500]  lpc_ich i2c_i801 crc32c_intel asus_atk0110 pcspkr i5500_temp i7core_edac pcc_cpufreq acpi_cpufreq ata_generic pata_marvell sr_mod cdrom hid_generic usbhid nouveau video mxm_wmi i2c_algo_bit ahci firewire_ohci drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops xhci_pci serio_raw ttm uhci_hcd firewire_core ehci_pci crc_itu_t xhci_hcd ehci_hcd libahci drm drm_panel_orientation_quirks usbcore wmi button sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua
    [ 2715.835532] CPU: 2 PID: 0 Comm: swapper/2 Tainted: G          IO     4.12.14-lp151.28.52-default #1 openSUSE Leap 15.1
    [ 2715.835533] Hardware name: System manufacturer System Product Name/P6T DELUXE V2, BIOS 1108    09/21/2010
    [ 2715.835535] task: ffff880186e98000 task.stack: ffffc90000ccc000
    [ 2715.835537] RIP: 0010:dev_watchdog+0x214/0x220
    [ 2715.835539] RSP: 0018:ffff8801b9283e90 EFLAGS: 00010286
    [ 2715.835541] RAX: 0000000000000038 RBX: 0000000000000000 RCX: 0000000000000000
    [ 2715.835542] RDX: ffff8801b92a0280 RSI: ffff8801b9297a68 RDI: ffff8801b9297a68
    [ 2715.835543] RBP: ffff8801b5de245c R08: 00000000000003be R09: 0000000000000001
    [ 2715.835544] R10: ffff8801b9283f08 R11: 0000000000000001 R12: ffff8801b457ba80
    [ 2715.835545] R13: 0000000000000002 R14: ffff8801b5de2000 R15: 0000000000000001
    [ 2715.835547] FS:  0000000000000000(0000) GS:ffff8801b9280000(0000) knlGS:0000000000000000
    [ 2715.835548] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
    [ 2715.835550] CR2: 00007fbdf13e9960 CR3: 000000000200a000 CR4: 00000000000006e0
    [ 2715.835551] Call Trace:
    [ 2715.835554]  <IRQ>
    [ 2715.835558]  ? pfifo_fast_reset+0x110/0x110
    [ 2715.835562]  call_timer_fn+0x30/0x130
    [ 2715.835565]  run_timer_softirq+0x3c8/0x420
    [ 2715.835569]  ? timerqueue_add+0x52/0x80
    [ 2715.835572]  ? enqueue_hrtimer+0x37/0x80
    [ 2715.835575]  ? recalibrate_cpu_khz+0x10/0x10
    [ 2715.835580]  __do_softirq+0xde/0x2c6
    [ 2715.835585]  irq_exit+0xba/0xc0
    [ 2715.835588]  smp_apic_timer_interrupt+0x3f/0x60
    [ 2715.835591]  apic_timer_interrupt+0xab/0xb0
    [ 2715.835592]  </IRQ>
    [ 2715.835597] RIP: 0010:cpuidle_enter_state+0x9f/0x2e0
    [ 2715.835598] RSP: 0018:ffffc90000ccfeb8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
    [ 2715.835600] RAX: ffff8801b92a4500 RBX: 000002785467ccdf RCX: 000000000000001f
    [ 2715.835601] RDX: 000002785467ccdf RSI: 000000002fe4257f RDI: 0000000000000000
    [ 2715.835602] RBP: ffffe8ffffa8d090 R08: 0000000000000004 R09: 0000000000023d40
    [ 2715.835604] R10: ffffc90000ccfe98 R11: 0000000000000acf R12: 0000000000000004
    [ 2715.835605] R13: ffffffff820d8038 R14: 0000000000000000 R15: 00000278542b1f4c
    [ 2715.835609]  ? cpuidle_enter_state+0x92/0x2e0
    [ 2715.835612]  do_idle+0x183/0x1e0
    [ 2715.835615]  cpu_startup_entry+0x5d/0x60
    [ 2715.835620]  start_secondary+0x1b0/0x200
    [ 2715.835624]  secondary_startup_64+0xa5/0xb0
    [ 2715.835626] Code: 63 8e 60 04 00 00 eb 8f 4c 89 f7 c6 05 ef 73 a4 00 01 e8 40 d2 fc ff 89 d9 48 89 c2 4c 89 f6 48 c7 c7 28 22 ed 81 e8 5c a5 ad ff <0f> 0b eb bd 0f 1f 84 00 00 00 00 00 66 66 66 66 90 41 57 41 56 
    [ 2715.835658] ---[ end trace 915201088e6b07b8 ]---
    [ 2715.835662] sky2 0000:04:00.0 eth1: tx timeout
    [ 2715.835667] sky2 0000:04:00.0 eth1: transmit ring 19 .. 21 report=19 done=19
    [ 2719.529501] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    [ 2754.746666] sky2 0000:04:00.0 eth1: tx timeout
    [ 2754.746683] sky2 0000:04:00.0 eth1: transmit ring 21 .. 23 report=21 done=21
    [ 2757.770602] sky2 0000:04:00.0 eth1: Link is up at 100 Mbps, half duplex, flow control both
    Having a "Call Trace" can't be good.

    I'm wondering if the "NetworkManager" app (or one of its companion apps) is corrupted? This is a very old core-i7 920 cpu based PC (on a P6T DELUXE V2 motherboard), that I had shipped from Europe to Asia 1-year ago, and only 3 days ago pulled out of storage and installed LEAP-15.1. i.e. Until 3 days ago, it had been 15-months before it was last powered. It has a 1.5 TB hard drive, and I am wondering if maybe NetworkManager somehow (?) was corrupted last night on that hard drive ....

    I am tempted to switch back to 'wicked' and then force a re-install of all the NetworkManager apps, do a reboot, and confirm that a corrupted Network Manager is not a possibility.

    That 'calltrace" really has me puzzled.
    Last edited by oldcpu; 13-Jun-2020 at 23:47.

  5. #5
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,704
    Blog Entries
    39

    Default Re: Network Manager not working - but Wicked working

    I actually have two separate dmesg above (in my two posts) with different kernel versions. Both produce the 'call trace'. I am very tempted (as noted) to force a NetworkManager re-install.

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,262
    Blog Entries
    1

    Default Re: Network Manager not working - but Wicked working

    Quote Originally Posted by oldcpu View Post

    This is the NetworkManager general configuration (with LAN/internet not working).


    This is the NetworkManaager 'wired' tab (with LAN/internet not working)

    The above is identical to another PC I have on our home wired LAN with LEAP-15.1 and same kernel .... albeit different motherboard, different cpu. But everything works on that other PC.

    Selecting "Allow auto-negotiation" does not change the failure to connect to our LAN with the Network manager.
    Can you try 100Mb/s (or 1Gb/s assuming connected to such a compatible interface), and 'Full Duplex'?
    openSUSE Leap 15.2; KDE Plasma 5

  7. #7
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,262
    Blog Entries
    1

    Default Re: Network Manager not working - but Wicked working

    Does unloading and reloading the driver result in a working connection?
    Watch the following in one terminal
    Code:
    journalctl -fu NetworkManager
    and then do in another
    Code:
    modprobe -r sky2;modprobe sky2
    openSUSE Leap 15.2; KDE Plasma 5

  8. #8
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,704
    Blog Entries
    39

    Default Re: Network Manager not working - but Wicked working

    Quote Originally Posted by deano_ferrari View Post
    Can you try 100Mb/s (or 1Gb/s assuming connected to such a compatible interface), and 'Full Duplex'?
    I am making some progress here - give me some minutes as I try to characterise this.

  9. #9
    Join Date
    Mar 2008
    Location
    Phuket, Thailand
    Posts
    26,704
    Blog Entries
    39

    Default Re: Network Manager not working - but Wicked working

    Quote Originally Posted by deano_ferrari View Post
    Can you try 100Mb/s (or 1Gb/s assuming connected to such a compatible interface), and 'Full Duplex'?
    THAT was interesting.

    1. I first tried switching to FULL Duplex with Network Manager (but not reboot). No difference - still no WLAN/LAN connection. I checked the dmesg and I could see FULL duplex had been applied.

      I then applied 1000Mb/s (still full duplex) and Network Manager connected. BUT this was only for this boot. The dmesg still indicated 100Mb/s which made no sense. This LAN/internet connection working was unexpected.

      So WITHOUT rebooting I set to HALF duplex. Still connected. I set 100 Mb/s. Still connected. But no indication in dmesg (that I could see) that those settings were applied.
      .
    2. I rebooted with 100 Mbs and HALF duplex and NO LAN/Inernet connection.
      .
    3. So I changed to FULL duplex and 1000Mb/s, rebooted and Network Manager connected ok.
      .
    4. So I changed to HALF duplex (kept 1000 Mb/s), rebooted and no LAN/internet. The eth1 would not even appear in Network Manager right hand corner "Networks" and could only be seen if I clicked on the configure icon .
      .
    5. So I changed to FULL duplex with 1000 Mb/s, rebooted and Internet/LAN is back. I note dmesg reports "eth1: Link is up at 1000 Mbps, full duplex, flow control both".
      .
    6. So I changed to FULL duplex with 100 Mb/s, rebooted and NO Internet/LAN.
      .
    7. So I changed to FULL duplex with 1000 Mb/s, rebooted and Internet/LAN is back.


    This is most strange, but Network Manager can be made to work with 1000 Mb/s and FULL duplex. It also appears a reboot may be needed in simply and "apply" in NetworkManager" is insufficient on this PC's install.

    I'm still pondering if there may be some hard drive corruption affecting NetworkManager.

    I am puzzling why does it accept FULL duplex and 1000Mb/s on a reboot but not accept the standard 'HALF duplex and 100 Mb/s after a reboot?

    Just to be certain, I rebooted again with FULL duplex and 1000Mb/s multiple times and Network Manager reliably works with that setting.

    Has me scratching my head and asking if my Network Manager app is corrupted?
    Last edited by oldcpu; 14-Jun-2020 at 00:32.

  10. #10
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    22,262
    Blog Entries
    1

    Default Re: Network Manager not working - but Wicked working

    Stay with what works. A duplex mismatch will make for an inefficient or non-working link for sure. Not sure why auto-negotiation is not working (but could be a regression with the driver itself or something strange that NM does when bringing the link up perhaps).
    Last edited by deano_ferrari; 14-Jun-2020 at 00:38.
    openSUSE Leap 15.2; KDE Plasma 5

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •