[SOLVED] Network behaves strangely with 4.20.0-5.2
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 14
Reply Quote

Back to top
techAdmin
Status: Site Admin
Joined: 26 Sep 2003
Posts: 3922
Location: East Coast, West Coast? I know it's one of them.
Reply Quote
You want to show: inxi -xxxiz
That will give more useful information about your actual interfaces etc. The -z will hide IP and mac addresses.
Back to top
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 14
Reply Quote
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: d000
bus ID: 03:00.0 chip ID: 10ec:8168
IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> scope: global broadcast: <filter>
IP v6: <filter> scope: link
WAN IP: <filter>

So, now the same thing appears with Liquorix 4.20.0-5.1, but not always ...

[ 4.928428] r8169 0000:03:00.0 eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 14.918132] ------------[ cut here ]------------
[ 14.918137] NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
[ 14.918163] WARNING: CPU: 1 PID: 0 at net/sched/sch_generic.c:461 dev_watchdog+0x215/0x220
[ 14.918165] Modules linked in: pci_stub vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) joydev binfmt_misc nvidia_drm(PO) nvidia_modeset(PO) fuse intel_rapl x86_pkg_temp_thermal intel_powerclamp kvm_intel snd_hda_codec_hdmi kvm irqbypass nvidia(PO) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel snd_hda_codec_realtek drm_kms_helper snd_hda_codec_generic evdev drm snd_ice1712 ipmi_devintf snd_hda_intel snd_cs8427 aesni_intel snd_i2c eeepc_wmi ipmi_msghandler nvidiafb aes_x86_64 snd_ice17xx_ak4xxx crypto_simd vgastate snd_ak4xxx_adda snd_ac97_codec asus_wmi cryptd iTCO_wdt snd_mpu401_uart sparse_keymap fb_ddc snd_hda_codec glue_helper wmi_bmof rfkill mxm_wmi ac97_bus sg i2c_algo_bit iTCO_vendor_support snd_hda_core acpi_pad button pcc_cpufreq acpi_cpufreq snd_aloop snd_usb_audio snd_usbmidi_lib snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm asus_atk0110 coretemp snd_seq_dummy snd_seq_midi snd_seq_oss snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device snd_timer snd soundcore ip_tables
[ 14.918238] x_tables ipv6 crc_ccitt autofs4 hid_generic usbhid ext4 crc16 mbcache jbd2 fscrypto sd_mod ahci libahci i2c_i801 libata r8169 crc32c_intel scsi_mod i2c_core ehci_pci xhci_pci lpc_ich realtek ehci_hcd xhci_hcd fan thermal rtc_cmos wmi video
[ 14.918270] CPU: 1 PID: 0 Comm: MuQSS/1 Tainted: P O 4.20.0-5.1-liquorix-amd64 #1 liquorix 4.20-3.1~sid
[ 14.918272] Hardware name: ASUS All Series/Z97-K, BIOS 2902 03/31/2016
[ 14.918277] RIP: 0010:dev_watchdog+0x215/0x220
[ 14.918281] Code: 49 63 4c 24 e0 eb 8c 4c 89 ef c6 05 28 80 b8 00 01 e8 df 63 fc ff 89 d9 4c 89 ee 48 c7 c7 e8 a9 08 82 48 89 c2 e8 f0 47 93 ff <0f> 0b eb be 0f 1f 80 00 00 00 00 48 c7 47 08 00 00 00 00 48 c7 07
[ 14.918284] RSP: 0018:ffff88840ea83e98 EFLAGS: 00010292
[ 14.918287] RAX: 0000000000000039 RBX: 0000000000000000 RCX: 0000000000000006
[ 14.918290] RDX: 0000000000000007 RSI: 0000000000000096 RDI: ffff88840ea96380
[ 14.918293] RBP: ffff88840ebc849c R08: 00000000000003ad R09: 0000000000000003
[ 14.918295] R10: 0000000000000001 R11: 0000000000000039 R12: ffff88840ebc84c0
[ 14.918298] R13: ffff88840ebc8000 R14: 0000000000000001 R15: ffff88840762a280
[ 14.918302] FS: 0000000000000000(0000) GS:ffff88840ea80000(0000) knlGS:0000000000000000
[ 14.918305] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 14.918308] CR2: 0000564eeec17050 CR3: 000000000220a002 CR4: 00000000001606e0
[ 14.918310] Call Trace:
[ 14.918314] <IRQ>
[ 14.918321] ? qdisc_put_unlocked+0x30/0x30
[ 14.918327] call_timer_fn+0x26/0x150
[ 14.918332] ? qdisc_put_unlocked+0x30/0x30
[ 14.918337] run_timer_softirq+0x3f1/0x4e0
[ 14.918343] ? __hrtimer_run_queues+0x153/0x2d0
[ 14.918351] ? recalibrate_cpu_khz+0x10/0x10
[ 14.918356] ? ktime_get+0x31/0x90
[ 14.918362] ? sched_clock+0x5/0x10
[ 14.918369] __do_softirq+0xe7/0x32a
[ 14.918375] irq_exit+0x6c/0x90
[ 14.918381] smp_apic_timer_interrupt+0x6f/0x160
[ 14.918387] apic_timer_interrupt+0xf/0x20
[ 14.918390] </IRQ>
[ 14.918396] RIP: 0010:cpuidle_enter_state+0xb5/0x540
[ 14.918399] Code: e8 f0 e5 a1 ff 80 7c 24 0b 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 04 00 00 31 ff e8 f2 1e a6 ff fb 66 0f 1f 44 00 00 <45> 85 e4 0f 88 27 02 00 00 48 b8 ff ff ff ff f3 01 00 00 48 2b 1c
[ 14.918402] RSP: 0018:ffffc9000192bec8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
[ 14.918406] RAX: ffff88840eaa0300 RBX: 000000037930750e RCX: 000000000000001f
[ 14.918409] RDX: 000000037930750e RSI: 000000001ff1c979 RDI: 0000000000000000
[ 14.918412] RBP: ffff88840eaa9948 R08: 0000000000000002 R09: 000000000001fbc0
[ 14.918414] R10: 00000021af3bce34 R11: ffff8884078e3838 R12: 0000000000000005
[ 14.918417] R13: ffffffff82295718 R14: 0000000000000005 R15: 0000000000000000
[ 14.918424] ? cpuidle_enter_state+0x90/0x540
[ 14.918430] do_idle+0x1af/0x1e0
[ 14.918436] cpu_startup_entry+0x14/0x20
[ 14.918441] secondary_startup_64+0xa4/0xb0
[ 14.918446] ---[ end trace 00f3f26db67393cb ]---
[37693.393826] usb 3-4: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd

Booting Windows on the same computer is fine, so I exclude a hardware fault.
I reckon a driver is the culprit.
Back to top
damentz
Status: Assistant
Joined: 09 Sep 2008
Posts: 757
Reply Quote
It seems that a lot of people have problems with the r8169 driver that you're using. All I can recommend is try another ethernet cable or buy a ethernet card to replace your onboard.

Looking at your motherboard online, you have plenty of expansion ports to pick from, both PCI and PCIe: www.asus.com/Motherboards/Z97K/websites/global/products/3wvOh4rV4y53ywKS/img/hp/overview/overview.png

I personally would use the older PCI ports so you can reserve your PCIe ports for newer hardware. Here's a decent one made by Intel on Newegg: www.newegg.com/Product/Product.aspx?Item=9SIA4A08GT2322

Not the answer you probably wanted to hear, but swiftly replacing hardware that doesn't work well with linux is the best choice to solving these problems if you can afford it.
Back to top
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 14
Reply Quote
I will look into that.
Thank you Damentz :)
Back to top
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 14
Reply Quote
Just to add, for future reference :

Reboot -> network doesn't work
Cold boot -> network works ...

See bugzilla.redhat.com/show_bug.cgi?id=1650984 -- 2019-02-01 02:20:28 UTC , same thing here.
Back to top
gelabs
Status: Interested
Joined: 02 May 2017
Posts: 14
Reply Quote
Ah, looks like it's fixed with 4.20.0-7.1 ...
Back to top
Display posts from previous:   

All times are GMT - 8 Hours