Re: F41 Qemu crashing system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Fixed subject. :)

Logwatch has something to say about these crashes:

 --------------------- Kernel Begin ------------------------

 WARNING:  Kernel Errors Present
    ACPI: \_SB_.PCI0.LPC0.EC__.HKEY: BCTG evaluated but flagged as error ...:  2
+Time(s)
    WARNING: CPU: 0 PID: 1269 at drivers/gpu/drm/ttm ...:  1 Time(s)
    WARNING: CPU: 3 PID: 1273 at drivers/gpu/drm/ttm ...:  1 Time(s)
    [drm:cik_ib_test [radeon]] *ERROR* radeon: fence w ...:  1 Time(s)
    [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 1  ...:  2 Time(s)
    [drm:cik_ring_test [radeon]] *ERROR* radeon: ring 2  ...:  2 Time(s)
    [drm:radeon_ib_ring_tests [radeon]] *ERROR* radeon: failed ...:  2 Time(s)
    [drm:uvd_v1_0_ib_test [radeon]] *ERROR* radeon: fence w ...:  1 Time(s)
    mce: [Hardware Error]: CPU 0: Machine ...:  1 Time(s)
    mce: [Hardware Error]: Machine check  ...:  1 Time(s)
    mce: [Hardware Error]: PROCESSOR 2:70 ...:  1 Time(s)
    mce: [Hardware Error]: TSC 0 ADDR f15 ...:  1 Time(s)

 --------------------- pam_unix Begin ------------------------

 lightdm:
    Unknown Entries:
       session opened for user rgm(uid=1000) by rgm(uid=0): 2 Time(s)

 lightdm-greeter:
    Unknown Entries:
       session closed for user lightdm: 2 Time(s)
       session opened for user lightdm(uid=987) by (uid=0): 2 Time(s)


So qemu might be doing something Radeon does not like?

On 8/11/25 8:34 AM, Robert Moskowitz via users wrote:
I have a Fedora 21 image that I have been running in Qemm for the past lots of years.  Just some apps from F21 that never moved forward.

With recent updates and a reboot, I restarted qemm and connected to the paused F21 image.  I then went to open the viewer and my system screen shut off, turned back on and the system crashed.

I reboot the system and restarted Qemm.  This time the F21 image was not running, so I started it.  I waited a bit until the activity dropped then opened the screen.  This time the system just did a hard reboot.

I just checked with a "dnf update", and nothing new for qemm.

So I am not restarting qemm until I get some guidance here.  I suppose I should check to see if there are any recent bugs about it...

Anyway, anything I might check on this.  It takes actually opening the viewer? for the system to crash.

thanks


--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux