Skip to main content ↑ ↓
Topic: no network after last update: r8168: disagrees about version of symbol ... (Read 1707 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

no network after last update: r8168: disagrees about version of symbol ...

After the last update I lost network.  I'm using lts.

Code: [Select]
[  820.875954] r8168: disagrees about version of symbol netdev_update_features
[  820.875957] r8168: Unknown symbol netdev_update_features (err -22)
[  820.875965] r8168: disagrees about version of symbol unregister_netdev
[  820.875966] r8168: Unknown symbol unregister_netdev (err -22)
[  820.876003] r8168: disagrees about version of symbol netdev_err
[  820.876004] r8168: Unknown symbol netdev_err (err -22)
[  820.876015] r8168: disagrees about version of symbol napi_complete_done
[  820.876016] r8168: Unknown symbol napi_complete_done (err -22)
[  820.876020] r8168: disagrees about version of symbol skb_checksum_help
[  820.876021] r8168: Unknown symbol skb_checksum_help (err -22)
[  820.876029] r8168: disagrees about version of symbol __napi_schedule
[  820.876030] r8168: Unknown symbol __napi_schedule (err -22)
[  820.876035] r8168: disagrees about version of symbol netif_device_detach
[  820.876036] r8168: Unknown symbol netif_device_detach (err -22)
[  820.876043] r8168: disagrees about version of symbol napi_gro_receive
[  820.876044] r8168: Unknown symbol napi_gro_receive (err -22)
[  820.876046] r8168: disagrees about version of symbol netif_device_attach
[  820.876047] r8168: Unknown symbol netif_device_attach (err -22)
[  820.876064] r8168: disagrees about version of symbol netif_napi_add
[  820.876065] r8168: Unknown symbol netif_napi_add (err -22)
[  820.876080] r8168: disagrees about version of symbol register_netdev
[  820.876081] r8168: Unknown symbol register_netdev (err -22)
[  820.876092] r8168: disagrees about version of symbol netif_tx_wake_queue
[  820.876094] r8168: Unknown symbol netif_tx_wake_queue (err -22)
[  820.876106] r8168: disagrees about version of symbol netif_napi_del
[  820.876107] r8168: Unknown symbol netif_napi_del (err -22)
[  820.876115] r8168: disagrees about version of symbol __dev_kfree_skb_any
[  820.876116] r8168: Unknown symbol __dev_kfree_skb_any (err -22)
[  820.876128] r8168: disagrees about version of symbol napi_disable
[  820.876129] r8168: Unknown symbol napi_disable (err -22)
[  820.876133] r8168: disagrees about version of symbol __skb_gso_segment
[  820.876134] r8168: Unknown symbol __skb_gso_segment (err -22)
[  820.876140] r8168: disagrees about version of symbol netdev_info
[  820.876141] r8168: Unknown symbol netdev_info (err -22)

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #1 –
did you compile that module outside of the kernel tree?  It is not lieing to you.  It is telling you you have two different version of the kernel mixed up.  Did you reboot?  if you update the kernel, stop your modules, and try to restart them, they won't restart because the kernel has changed to a different one than the one that is running in RAM. 

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #2 –
some of the r8168 have to be manually rebuilt after a kernel upgrade (linux-ck comes to mind) because artix has the kernel and arch extra has the module, and they're not always on the same page.  I've found r8168-dkms works best for all kernel versions

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #3 –
Yes, I had to reboot my newly installed kernel+drivers (both lts) for the issue to appear.

The r8168 was updated at the same time (r8168-lts).

I'm using lts as it's supposed to be long term support (and thus long-term stability).
I'm reluctant to use other kernels (especially fine-tuned optimized ones) as there is a slightly higher risk of instability (let's not dwell on that).
But that's beside the point.

I was simply reporting there was some discrepancy/issue updating at the time of the update.

Are you suggesting the ck (or another) line of kernel is to be preferred and is not subject to this kind of issues ? (and if yes, why not exclude lts from the repositories)

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #4 –
As seen on git hub it appears that "linux-lts" 4.9 is being superseded by "linux" which is 4.14

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #5 –
Quote from: toxygen – on
some of the r8168 have to be manually rebuilt after a kernel upgrade (linux-ck comes to mind) because artix has the kernel and arch extra has the module, and they're not always on the same page.  I've found r8168-dkms works best for all kernel versions

well everytime you update the kernel binaries, you need to update the kernel headers/src and then compile off of the new kernel.

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #6 –
Quote from: mrbrklyn – on
well everytime you update the kernel binaries, you need to update the kernel headers/src and then compile off of the new kernel.

I think that is exactly what dkms does automatically, On this rolling release it is recommended, so a kernel update does not break the system.
 

Re: no network after last update: r8168: disagrees about version of symbol ...

Reply #7 –
To summarize all I've read (thanks for the feedback) I can kiss lts goodbye if I stay on Artix (for the time being at least).

With Arch (before they got poisoned) I never had this kind of issue.
Am I right to assume it's because when a package is pushed in the repository, all its dependents are not pushed "atomically" with it ? (Thus creating discrepancy and minor snafus)