LM 21.1 Screen Flickering After Kernel Update [Solved]

Alexzee

Well-Known Member
Joined
Jun 1, 2019
Messages
3,834
Reaction score
2,056
Credits
23,027
After allowing the new kernel update (5.15.0-82-generic)
and rebooting the display on the screen appeared and reappeared, flickering
repeatedly.

This performance appeared after a reboot of the new kernel and after I walked away and Mint generated the black screen after no use that I had it set to. Upon moving the mouse to wake the system up that's when the flickering began and the system was unstable/unresponsive.

Dropping to a shell and running sudo shutdown -h now didn't work. The command failed and bash produced "Expanded Security Maintenance wasn't enabled".
Curious I ran: 'apt list --upgradable' to see what was available.
This entailed and pointed to Intel Microcode. I don't have and Intel tech on this rig:-

The dmesg log shows apparmor as being denied:-
I'm not an expert with the dmesg log. There's a lot of output in that log so it could be something else. IDK.

Code:
ZFS: Loaded module v2.1.5-1ubuntu6~22.04.1, ZFS pool version 5000, ZFS filesystem version 5
[    6.321536] audit: type=1400 audit(1693236010.431:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-senddoc" pid=798 comm="apparmor_parser"
[    6.321708] audit: type=1400 audit(1693236010.431:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-xpdfimport" pid=800 comm="apparmor_parser"
[    6.322360] audit: type=1400 audit(1693236010.431:4): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/man" pid=794 comm="apparmor_parser"
[    6.322363] audit: type=1400 audit(1693236010.431:5): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_filter" pid=794 comm="apparmor_parser"
[    6.322365] audit: type=1400 audit(1693236010.431:6): apparmor="STATUS" operation="profile_load" profile="unconfined" name="man_groff" pid=794 comm="apparmor_parser"
[    6.322519] audit: type=1400 audit(1693236010.431:7): apparmor="STATUS" operation="profile_load" profile="unconfined" name="lsb_release" pid=790 comm="apparmor_parser"
[    6.322567] audit: type=1400 audit(1693236010.431:8): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=791 comm="apparmor_parser"
[    6.322571] audit: type=1400 audit(1693236010.431:9): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=791 comm="apparmor_parser"
[    6.322806] audit: type=1400 audit(1693236010.431:10): apparmor="STATUS" operation="profile_load" profile="unconfined" name="libreoffice-oosplash" pid=797 comm="apparmor_parser"
[    6.325396] audit: type=1400 audit(1693236010.435:11): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/usr/bin/redshift" pid=795 comm="apparmor_parser"
[   95.921701] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   95.921705] Bluetooth: BNEP filters: protocol multicast
[   95.921710] Bluetooth: BNEP socket layer initialized
[   95.924955] NET: Registered PF_ALG protocol family
[   95.939298] kauditd_printk_skb: 18 callbacks suppressed
[   95.939301] audit: type=1400 audit(1693236100.047:30): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=938 comm="cupsd" capability=12  capname="net_admin"
[   96.020227] Generic FE-GE Realtek PHY r8169-0-500:00: attached PHY driver (mii_bus:phy_addr=r8169-0-500:00, irq=MAC)
[   96.224341] r8169 0000:05:00.0 enp5s0: Link is Down
[   97.776401] Bluetooth: RFCOMM TTY layer initialized
[   97.776407] Bluetooth: RFCOMM socket layer initialized
[   97.776410] Bluetooth: RFCOMM ver 1.11
[   99.729002] wlp4s0: authenticate with dc:bf:e9:fd:39:ea
[   99.730108] wlp4s0: send auth to dc:bf:e9:fd:39:ea (try 1/3)
[   99.826451] wlp4s0: authenticated
[   99.828223] wlp4s0: associate with dc:bf:e9:fd:39:ea (try 1/3)
[   99.832147] wlp4s0: RX AssocResp from dc:bf:e9:fd:39:ea (capab=0x1411 status=0 aid=2)
[   99.835647] wlp4s0: associated
[  100.088889] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[  103.455177] audit: type=1400 audit(1693236107.563:31): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=1208 comm="cups-browsed" capability=23  capname="sys_

There are a handful of entries for patches to the microcode and one update for the microcode driver.
See the file attached:-

Hopefully it's not a kernel bug or a Wayland or X11 driver issue. I'll be back to see what you guys think of this.:)

I hope I can walk away, fire up the grill and when I come back to move the mouse this doesn't become a repeat.
 

Attachments

  • TTY.jpg_001.png
    TTY.jpg_001.png
    1.2 MB · Views: 206
  • Micro Code.png
    Micro Code.png
    539.3 KB · Views: 162
Last edited:


This entailed and pointed to Intel Microcode. I don't have and Intel tech on this rig:-
I am assuming you mean that you dont have any intel tech on this rig....

I would update that....based soley on the premise(guess) that there is something on that rig that needs that update

If you have timeshift set up, it won't do any harm to try.
 
This entailed and pointed to Intel Microcode. I don't have and Intel tech on this rig:-

We discussed this recently and determined that this is perfectly normal. (I'd never noticed it before.)

You'll have both AMD and Intel microcode on your system, as they're kind of generic titles that reference some bits about architecture. I didn't dig too deep once I learned it was the expected behavior.
 
Yes, I thought that there wasn't any Intel tech however I quickly found out that my nic is a Intel Wireless AC 9260.


Code:
No Ubuntu Pro services are available to this system.

For a list of all Ubuntu Pro services, run 'pro status --all'

This machine is not attached to an Ubuntu Pro subscription.
See https://ubuntu.com/pro

Supported livepatch kernels are listed here: https://ubuntu.com/security/livepatch/docs/kernels

Code:
Alex:  pro status --all
SERVICE          AVAILABLE  DESCRIPTION
cc-eal           no         Common Criteria EAL2 Provisioning Packages
cis              no         Security compliance and audit tools
esm-apps         no         Expanded Security Maintenance for Applications
esm-infra        no         Expanded Security Maintenance for Infrastructure
fips             no         NIST-certified core packages
fips-updates     no         NIST-certified core packages with priority security updates
livepatch        no         Current kernel is not supported
realtime-kernel  no         Ubuntu kernel with PREEMPT_RT patches integrated
ros              no         Security Updates for the Robot Operating System
ros-updates      no         All Updates for the Robot Operating System

So I went ahead and applied the update-

Code:
Listing... Done
intel-microcode/jammy-updates,jammy-security 3.20230808.0ubuntu0.22.04.1 amd64 [upgradable from: 3.20230214.0ubuntu0.22.04.1]
N: There are 2 additional versions. Please use the '-a' switch to see them.
Alex:  sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
#
# You can verify the status of security fixes using the `pro fix` command.
# E.g., a recent Ruby vulnerability can be checked with: `pro fix USN-6219-1`
# For more detail see: https://ubuntu.com/security/notices/USN-6219-1
#
The following packages will be upgraded:
  intel-microcode
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 standard LTS security update
Need to get 6,117 kB of archives.
After this operation, 364 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 intel-microcode amd64 3.20230808.0ubuntu0.22.04.1 [6,117 kB]
Fetched 6,117 kB in 2s (2,820 kB/s)         
(Reading database ... 594486 files and directories currently installed.)
Preparing to unpack .../intel-microcode_3.20230808.0ubuntu0.22.04.1_amd64.deb ...
Unpacking intel-microcode (3.20230808.0ubuntu0.22.04.1) over (3.20230214.0ubuntu0.22.04.1) ...
Setting up intel-microcode (3.20230808.0ubuntu0.22.04.1) ...
update-initramfs: deferring update (trigger activated)
intel-microcode: microcode will be updated at next boot
Processing triggers for initramfs-tools (0.140ubuntu13.4) ...
update-initramfs: Generating /boot/initrd.img-5.15.0-82-generic
W: Possible missing firmware /lib/firmware/amdgpu/yellow_carp_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/vangogh_gpu_info.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_rlc.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec2.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_mec.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_me.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_pfp.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_ce.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma1.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/cyan_skillfish_sdma.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/sienna_cichlid_mes.bin for module amdgpu
W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu
Alex:
 
We discussed this recently and determined that this is perfectly normal. (I'd never noticed it before.)

You'll have both AMD and Intel microcode on your system, as they're kind of generic titles that reference some bits about architecture. I didn't dig too deep once I learned it was the expected behavior.
I had forgotten that this Asus Tuf Gaming mobo has Intel tech for the wireless card:-

:)

Rebooting to see if the screen starts the flickering issue again.
 
It seems like the issue is gone.
Moved the mouse after Mint shut the monitor down and no signs of flickering.

Thanks for the help Condobloke!
 

Members online


Top