http://bugzilla.opensuse.org/show_bug.cgi?id=1206683 http://bugzilla.opensuse.org/show_bug.cgi?id=1206683#c23 --- Comment #23 from Frank Kr�ger <fkrueger@mailbox.org> --- (In reply to Scott Bradnick from comment #22)
(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.
As stated in comment 21, it seems that there are several different issues involved here. As for your system #1 and the USB NetGear Wifi issue, this might be related to https://lore.kernel.org/lkml/35c73172-4e06-3877-56bd-133f9192adc3@leemhuis.i... (see also https://bugzilla.kernel.org/show_bug.cgi?id=216839). Hope this helps. -- You are receiving this mail because: You are the assignee for the bug.