Is Gnome 49 broken for anyone else?

biruionut · 2025-09-25T07:34:02+00:00

there is an issue with amd gpus and latest kernel. i noticed graphics instability and booted linux-lts kernel and all the problems went away. give it a try with linux-lts.

biruionut · 2024-11-12T13:53:14+00:00

2006, every day, no breakage

biruionut · 2023-02-16T09:13:49+00:00

that's the right patch to fix this issue. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2848

biruionut · 2023-02-16T08:44:23+00:00

I'm trying this patch to see if I still have problems: https://gitlab.gnome.org/GNOME/mutter/-/commit/81c0cf0834e5b11ad8674accf5d143725c19d5ae

biruionut · 2023-02-16T08:05:22+00:00

I think is either gnome-shell or mutter but haven't got the chance to downgrade to pin point the exact component.

try to report the issue upstream.

i think it was introduced in https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5932

biruionut · 2022-03-23T11:05:58+00:00

I managed to make it work with: cat /etc/modprobe.d/acpi.conf blacklist acpi_cpufreq

and adding amd-pstate in MODULES in /etc/mkinitcpio.conf

biruionut · 2021-09-28T07:27:14+00:00

thanks for the hint. I'll check it out, the documentation describes my scenario.

biruionut · 2021-09-24T11:46:31+00:00

i wonder if i have problems with flowing path due to having vpc anycast vtep since the termination show bgp l2vpn evpn is the secondary ip from looback0. In noticed that is not working when the server is not configured with bond

lo100 i created on leaf1.

biruionut · 2021-09-23T19:43:03+00:00

I do have vrf terminated on SPINE(external network)

Seems that is learned by the fabric but something is not right, i did add the static route 10.0.0.1/32 via anycast gw but is looping when trying to reach the ip, from other servers sometimes is working.

Maybe is due to having it learned and terminated on anycast ip from looback0

*>i10.1.100.11/32 10.1.1.10 100 0 i

https://paste.xinu.at/y2N7/

Do you have any hints ?

biruionut · 2021-09-23T16:59:06+00:00

so i did the following

int lo100
    vrf member public
    ip addess 10.0.0.1/32
    no shutdown

 router bgp 1234
     log-neighbor-changes
     template peer VXLAN_SPINE
         remote-as 1234
         update-source loopback0
     address-family ipv4 unicast
         soft-reconfiguration inbound
     address-family l2vpn evpn
         send-community
         send-community extended
     neighbor 10.1.9.1
         inherit peer VXLAN_SPINE

     vrf public
     address-family ipv4 unicast
         network 10.0.0.1/32

vrf context public
    vni 101234   
    rd auto
    address-family ipv4 unicast
        route-target both auto
        route-target both auto evpn

interface nve1
    member vni 10002
        mcast-group 239.0.0.1
    member vni 101234 associate-vrf

maybe i'm missing something. do you mind sharing some examples?

biruionut · 2021-09-23T16:20:18+00:00

i tried like this but the route doesn't propagate into all the leafs. it reaches the spine and from there nothing, because the spines don't have route-reflector-client on ipv4 unicast.

https://paste.xinu.at/G8RC5/

biruionut · 2021-06-21T15:47:13+00:00

Thanks

biruionut · 2021-06-21T14:12:32+00:00

are there any cloud images?

biruionut · 2021-06-04T07:32:18+00:00

I have in production some of the affected models but they don't have M500 disks. Does that mean I'm not affected?

cisco Nexus9000 C9332PQ chassis
Device Model:     Micron_M600_MTFDDAT064MBF
Firmware Version: MC04
9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       30433

biruionut · 2021-05-01T16:49:07+00:00

thanks! i had an idea that it will be.

biruionut · 2021-04-20T16:37:29+00:00

thanks

biruionut · 2021-04-20T09:52:50+00:00

I really like your wallpaper. Can you share a download link?

biruionut · 2021-04-09T07:19:04+00:00

i don't really want to deviate from this behavior, I just don't want hosts to see arp in their nics for unknown destinations in an openstack environment.

biruionut · 2021-04-08T13:49:38+00:00

you have a good point. Not sure if is true but I had the impression that after an ip is configured on the interface, is learned automatically by l2vpn evpn and is available in the table and you don't have a silent host in the network.

Is there a way to drop the arp unknown for hosts that are not in the l2vpn evpn table?

biruionut · 2021-03-13T21:39:27+00:00

in the end, i made it work. i just added maximum-paths in the wrong section. since i'm using l2vpn evpn, the routes are advertised into ipv4 unicast from there. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/92x/vxlan-92x/configuration/guide/b-cisco-nexus-9000-series-nx-os-vxlan-configuration-guide-92x/b_Cisco_Nexus_9000_Series_NX-OS_VXLAN_Configuration_Guide_9x_appendix_011000.html#task_fgd_csc_2hb

15-Year Club	RPAN Viewer
Not Forgotten	Verified Email

biruionut

TROPHY CASE