Comment # 22 on bug 1206683 from Scott Bradnick

(In reply to Takashi Iwai from comment #21)
> In anyway, can anyone test whether the issue is related with the (i915)
> graphics driver?  Have anyone checked with nomodeset boot option?  Or maybe
> better with i915.modeset=0 option?

I've tried that, made no difference. This seems to be a network related
catalyst vs. graphics. And unless there's an alternative to i915 for the onchip
iGPU, I can't really disable it.

> And, as requested in comment 8, please give the outputs of hwinfo on the
> affected machines, taken from the working kernel.  Also the dmesg outputs
> from the working kernel would be helpful, too.
> 
> After getting the information of the working state, let's try to get the
> logs from the broken state.

I agree w/ others that this seems related to or pointing at network interaction
and manifests itself in a graphics lockup - no clue why.

Just focusing on system #1 - I installed/booted 6.2~rc1-1.1.g769d7ad from
Kernel:HEAD and experienced the same lockup where I can boot to a login screen,
even login to a tty and sit there for extended time but as soon as I login via
lightdm on tty7 I get a hard lock w/in 45-60s (if not quicker).

So I decided to blacklist the r8169 module (for the dual 2.5GbE ports) and
unplug the USB Wifi adapter:

$ inxi --network
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: N/A
  Device-2: Realtek RTL8125 2.5GbE driver: N/A
  Device-3: NetGear A6210 type: USB driver: mt76x2u

And it was up for 2 hours (and a few screensaver locks and monitor poweroffs)
w/o issue, other than what's a computer in 202X w/o internet access good for?
But plugging the NetGear device back in and logging in via lightdm caused it to
hard lock w/in 30-60s (again, I'm not sure how long it's taking but it's not
immediate and it's well under 5m). I ran dmesg before the hard lock and all it
showed between the ~40s of initial boot messages and the ~2h later output was
the fact that I plugged in the NetGear device.

Here's some output from hwinfo [--netcard,--network]:

"--netcard":

42: USB 00.0: 0282 WLAN controller
  [Created at usb.122]
  Unique ID: <snip>
  Parent ID: <snip>
  SysFS ID: /devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2:1.0
  SysFS BusID: 2-2:1.0
  Hardware Class: network
  Model: "NetGear A6210"
  Hotplug: USB
  Vendor: usb 0x0846 "NetGear, Inc."
  Device: usb 0x9053 "A6210"
  Revision: "1.00"
  Serial ID: "100"
  Driver: "mt76x2u"
  Driver Modules: "mt76x2u"
  Device File: wlp0s21f0u2
  Features: WLAN
  HW Address: <snip>
  Permanent HW Address: <snip>
  Link detected: yes
  WLAN channels: 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108
112 116 120 124 128 132 136 140 144 149
  WLAN frequencies: 2.412 2.417 2.422 2.427 2.432 2.437 2.442 2.447 2.452 2.457
2.462 5.18 5.2 5.22 5.24 5.26 5.28 5.3 5.32 5.5 5.52 5.54 5.56 5.58 5.6 5.62
5.64 5.66 5.68 5.7 5.72 5.745
  WLAN encryption modes: WEP40 WEP104 TKIP CCMP
  WLAN authentication modes: open sharedkey wpa-psk wpa-eap
  Module Alias: "usb:v0846p9053d0100dc00dsc00dp00icFFiscFFipFFin00"
  Driver Info #0:
    Driver Status: mt76x2u is active
    Driver Activation Cmd: "modprobe mt76x2u"
  Config Status: cfg=no, avail=yes, need=no, active=unknown
  Attached to: #56 (Hub)

"--network":

54: None 00.0: 10701 Ethernet
  [Created at net.126]
  Unique ID: _hed.ndpeucax6V1
  Parent ID: hSuP.geLYROERbfC
  SysFS ID: /class/net/wlp0s21f0u2
  SysFS Device Link: /devices/pci0000:00/0000:00:15.0/usb2/2-2/2-2:1.0
  Hardware Class: network interface
  Model: "Ethernet network interface"
  Driver: "mt76x2u"
  Driver Modules: "mt76x2u"
  Device File: wlp0s21f0u2
  HW Address: <snip>
  Permanent HW Address: <snip>
  Link detected: yes
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #35 (Ethernet controller)

As for system #2, it's been happy on 6.2~rc1-1.1.g769d7ad for the last 8hrs,
but it runs a "Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi" wireless card and
has no onboard Ethernet port(s) - those are on the Dell dock, which I rarely
use and cause MANY entries in dmesg (or somewhere similar months ago) to the
point where I'd blacklisted the driver for those ports so on the rare occasion
I did use the dock, it wasn't flooded with the messages. I'm going to use
prime-select to switch to intel and see if the same thing happens on #2 that's
happening on #1.