Announcement

Collapse
No announcement yet.

Linux 6.1 Released With MGLRU, Initial Rust Code

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
  • Franco Castillo
    replied
    Originally posted by Tian View Post

    because thats my wifi driver and it had some bugs in the 5.15 and 5.16 kernel releases (its this https://bugzilla.kernel.org/show_bug.cgi?id=215703), I dont think its my ethernet driver given that I only use wifi.
    In OpenWrt I have a similar error having ath10k and Linux 5.15. The mode is WDS Station. The device is a CPE210 v2.

    Code:
    Sun Dec 11 06:21:51 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:54 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:55 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:56 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:57 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:58 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:21:59 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:00 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:02 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:03 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:05 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:06 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:09 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:10 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:11 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:19 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:20 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:21 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:22 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:23 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:25 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:26 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:27 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:28 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:29 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:33 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:36 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:39 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:40 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:42 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:44 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:45 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:46 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:47 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:47 2022 daemon.notice netifd: Network device '2g_wds' link is down
Sun Dec 11 06:22:47 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-DISCONNECTED bssid=50:c7:bf:75:81:b0 reason=4 locally_generated=1
Sun Dec 11 06:22:47 2022 kern.info kernel: [2290444.887774] br-lan: port 4(2g_wds) entered disabled state
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: SME: Trying to authenticate with 50:c7:bf:75:81:b0 (SSID='WDS' freq=2437 MHz)
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.053358] 2g_wds: authenticate with 50:c7:bf:75:81:b0
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.059653] 2g_wds: send auth to 50:c7:bf:75:81:b0 (try 1/3)
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: Trying to associate with 50:c7:bf:75:81:b0 (SSID='WDS' freq=2437 MHz)
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.073580] 2g_wds: authenticated
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.084062] 2g_wds: associate with 50:c7:bf:75:81:b0 (try 1/3)
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.094809] 2g_wds: RX AssocResp from 50:c7:bf:75:81:b0 (capab=0x431 status=0 aid=1)
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.103722] 2g_wds: associated
Sun Dec 11 06:22:49 2022 daemon.notice netifd: Network device '2g_wds' link is up
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: Associated with 50:c7:bf:75:81:b0
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: Unknown event 37
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: WPA: Key negotiation completed with 50:c7:bf:75:81:b0 [PTK=CCMP GTK=CCMP]
Sun Dec 11 06:22:49 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-CONNECTED - Connection to 50:c7:bf:75:81:b0 completed [id=1 id_str=]
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.133365] br-lan: port 4(2g_wds) entered blocking state
Sun Dec 11 06:22:49 2022 kern.info kernel: [2290446.139211] br-lan: port 4(2g_wds) entered forwarding state
Sun Dec 11 06:22:50 2022 daemon.notice wpa_supplicant[915]: 2g_wds: Unknown event 37
Sun Dec 11 06:22:50 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:51 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:52 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
Sun Dec 11 06:22:53 2022 daemon.notice wpa_supplicant[915]: 2g_wds: CTRL-EVENT-BEACON-LOSS
    ​

    Leave a comment:

  • spiral_23
    replied
    Originally posted by Franco Castillo View Post

    Kernel version does not make your distribution more or less stable. Yeah the way you handle it.
    maybe you missunderstoot me - i didn't mean the kernel - i meant the different versions of the distributions - eg -stable-testing-unstable-experimental - in debian. but we are going off topic now.

    Leave a comment:

  • Franco Castillo
    replied
    Originally posted by spiral_23 View Post

    indeed it is! - except you are on kernel-hopping - like me. i mean they release the lts tag every year not as fun - they maintain those kernels for serveral years - which is mandatory for easier maintainance of stable distros - like eg. debian - redhhat - suse or even android. i am personaly on debian sid - on my laptop - pc's+ workstations - but anyway - on servers i would recommend - stable declared distributions- if you wont go to dependency hell/mess/breaks.
    Kernel version does not make your distribution more or less stable. Yeah the way you handle it.

    Leave a comment:

  • Tian
    replied
    Originally posted by Franco Castillo View Post

    And why do you think it's because of ath9k?
    because thats my wifi driver and it had some bugs in the 5.15 and 5.16 kernel releases (its this https://bugzilla.kernel.org/show_bug.cgi?id=215703), I dont think its my ethernet driver given that I only use wifi.
    • Likes 1

    Leave a comment:

  • Henk717
    replied
    Originally posted by Danny3 View Post

    I wish they make the 6.2 the LTS version, to get more performance improvements around BTRFS, Zstd and MGLRU!
    But if not, this will be a pretty good LTS release too.
    I also wish the 6.2 becomes the LTS, thats the one that has a wifi driver for my laptop.
    • Likes 1

    Leave a comment:

  • spiral_23
    replied
    Originally posted by Franco Castillo View Post

    Is it mandatory to release an LTS kernel every year?
    indeed it is! - except you are on kernel-hopping - like me. i mean they release the lts tag every year not as fun - they maintain those kernels for serveral years - which is mandatory for easier maintainance of stable distros - like eg. debian - redhhat - suse or even android. i am personaly on debian sid - on my laptop - pc's+ workstations - but anyway - on servers i would recommend - stable declared distributions- if you wont go to dependency hell/mess/breaks.

    Leave a comment:

  • Franco Castillo
    replied
    Originally posted by spiral_23 View Post

    it is the last stable kernel of the year - so it is tratitionally lts!
    Is it mandatory to release an LTS kernel every year?
    • Likes 1

    Leave a comment:

  • Franco Castillo
    replied
    Originally posted by Tian View Post

    Everytime I install any 5.16+ kernel the machine will boot, get me to the login screen and from there things will get messy, basically networkmanager will be in D state making the desktop enviroment unusable (kde totally unusable, gnome a little better but anything related to network like settings will not work), then for reboot the machine will take at least 10 min because it cant stop 4 process (networkmanager, dnslocation, geoip, wpa_suplicant i think) and most of the time a hard reset is required. On linux 6.0 (tested the zen kernel) the issue does not happen as often as in 5.19- (on 5.19 the machine is so unusable that I cant even install endevour os cuz as soon as I start it the whole xfce DE become unresponsive) but it still happens. The issue does not happens on 5.15 although it used to happen that the wifi would stop sending and reciving data from time to time (already fixed from 5.15.18 onwards) after some investigation the conclusion was that the ath9k driver was crashing making networkmanager wait for an adapter it would never show up thus lagging the whole system with it (really surprised by the dependency of linux desktops on networkmanager/wifi, like if I have a wifi problem I expect the wifi not to work (gnome) not the whole desktop to feel laggy and unresponsive (kde) or unusable at all (xfce))
    And why do you think it's because of ath9k?

    Leave a comment:

  • Alliancemd
    replied
    Quite excited about the Rust integration. Sadly, they are limited in where they are allowed to use it - would love to see some zero-copy APIs exposed to user-space.

    Leave a comment:

  • Tian
    replied
    Originally posted by Franco Castillo View Post

    What problem do you have?
    Everytime I install any 5.16+ kernel the machine will boot, get me to the login screen and from there things will get messy, basically networkmanager will be in D state making the desktop enviroment unusable (kde totally unusable, gnome a little better but anything related to network like settings will not work), then for reboot the machine will take at least 10 min because it cant stop 4 process (networkmanager, dnslocation, geoip, wpa_suplicant i think) and most of the time a hard reset is required. On linux 6.0 (tested the zen kernel) the issue does not happen as often as in 5.19- (on 5.19 the machine is so unusable that I cant even install endevour os cuz as soon as I start it the whole xfce DE become unresponsive) but it still happens. The issue does not happens on 5.15 although it used to happen that the wifi would stop sending and reciving data from time to time (already fixed from 5.15.18 onwards) after some investigation the conclusion was that the ath9k driver was crashing making networkmanager wait for an adapter it would never show up thus lagging the whole system with it (really surprised by the dependency of linux desktops on networkmanager/wifi, like if I have a wifi problem I expect the wifi not to work (gnome) not the whole desktop to feel laggy and unresponsive (kde) or unusable at all (xfce))
    • Likes 1

    Leave a comment:

Previous 1 2 3 template Next
Working...
X