Comment # 11 on bug 1206683 from Scott Bradnick

(In reply to Markus Ko���mann from comment #10)
> @Scott Bradnick:  What does  "prime-select get-status" report on your second
> system with 6.0.12 ?  Is the Intel graphics still active when using the
> nvidia card ?

I don't think the NVIDIA card has anything to do w/ it. My 1st experience with
this issue was system #1 which doesn't have a dedicated graphics card.

For system #2, "prime-select get-current" shows the T1000 active (as I'd
normally want it to be), but I do a fun song-and-disable-it-dance with bbswitch
when using the .run since I always want the NVIDIA card active and need to use
secure boot [I'm not saying they're 100% related, but getting bbswitch out of
the way has helped tremendously and worked for at least a dozen kernel updates
(i.e. it's not any issue here)] ; but none of that comes into play here because
the system isn't up long enough on 6.1.0+ to even begin to setup NVIDIA. Today
there was a bbswitch update, so it's back in that default state, still froze.

I've been able to boot system #1 into 6.1.1 and switch to tty4 and capture
"hwinfo --all --log <some log file>" and "dmesg -T" ~ also for 6.0.12 but
considering there's no "crash" in either case, I'm not sure how that will help
even if I upload them. Same with crash dumps as these are hard lockups w/ no
indication it'd trigger anything. I'm not arguing against providing one, just
not sure I want to install/configure it for naught.

On system #1 I was using 6.1.1 for 15-20min on tty4 and after about 45s-1m of
logging in via lightdm on tty7 it froze.