Bug 1722164 - Desktop hang with rawhide debug kernels on some hardware
Summary: Desktop hang with rawhide debug kernels on some hardware
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-19 14:54 UTC by Bruno Wolff III
Modified: 2022-02-16 04:48 UTC (History)
17 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-16 04:48:15 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg from 5.2.0-0.rc5.git1.1.fc31 boot (109.67 KB, text/plain)
2019-06-19 14:54 UTC, Bruno Wolff III
no flags Details
dmesg from booting 29f785ff76b65696800b75c3d8e0b58e603bb1d0 kernel (116.42 KB, text/plain)
2019-06-19 14:55 UTC, Bruno Wolff III
no flags Details
Info on the hardware (48.64 KB, text/plain)
2019-06-19 14:56 UTC, Bruno Wolff III
no flags Details

Description Bruno Wolff III 2019-06-19 14:54:04 UTC
Created attachment 1582274 [details]
dmesg from 5.2.0-0.rc5.git1.1.fc31 boot

1. Please describe the problem:
When using kernel-5.2.0-0.rc5.git1.1.fc31.x86_64 my desktop (xfce) will hang after about 5 to 10 minutes. The cursor still tracks the mouse, but nothing else seems to work. kernel-5.2.0-0.rc5.git0.1.fc31.x86_64 works normally. I have reproduced this with the Linus kernel (29f785ff76b65696800b75c3d8e0b58e603bb1d0) 
kernel-5.2.0-0.rc5.git1.1.fc31.x86_64 was built with.

2. What is the Version-Release number of the kernel:
kernel-5.2.0-0.rc5.git1.1.fc31.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
kernel-5.2.0-0.rc5.git1.1.fc31.x86_64

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Doing some minor graphical stuff, such as using a web browser, seems to be adequate for triggering the problem.

5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes.

6. Are you running any modules that not shipped with directly Fedora's kernel?:
Initially yes, but it happens without them as well.

7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

I'm going to try to bisect this using Linus' kernel.

This doesn't happen on a different machine I have at home.

Comment 1 Bruno Wolff III 2019-06-19 14:55:14 UTC
Created attachment 1582276 [details]
dmesg from booting 29f785ff76b65696800b75c3d8e0b58e603bb1d0 kernel

Comment 2 Bruno Wolff III 2019-06-19 14:56:37 UTC
Created attachment 1582277 [details]
Info on the hardware

Comment 3 Bruno Wolff III 2019-06-19 19:04:43 UTC
Bisecting just got a bit tougher. The upstream rc5 failed. I was use the Fedora rc5.git1 config though, so I'm going to see if the config has a change causing problems.

Comment 4 Bruno Wolff III 2019-06-20 14:28:11 UTC
It looks like the config file makes a difference. In this case there was a big change because of the debug/nodebug switch. So now I need to try a nodebug kernel. 5.2.0-0.rc5.git1.2 is already gone, so I'll try 5.2.0-0.rc5.git2.2 instead.

Comment 5 Bruno Wolff III 2019-06-20 15:34:11 UTC
5.2.0-0.rc5.git2.1 hung, but 5.2.0-0.rc5.git2.2 seems OK.
Since I rarely use rawhide debug kernels on this machine, it's possible the issue goes back further than I thought. I have to give up the hardware in about two weeks, so we might not figure out what is really going on.

Comment 6 Bruno Wolff III 2022-02-16 04:48:15 UTC
I haven't seen this behavior in a long time, so I'm going to close this as fixed.


Note You need to log in before you can comment on or make changes to this bug.