Bug 1677438

Summary: Kernel crash during boot
Product: [Fedora] Fedora Reporter: Ernesto <equistango>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: airlied, bskeggs, equistango, hdegoede, ichavero, itamar, jarodwilson, jeremy, jglisse, john.j5live, jonathan, josef, kernel-maint, labbott, linville, mchehab, mjg59, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-05-09 19:49:15 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot none

Description Ernesto 2019-02-14 22:48:51 UTC 
Description of the problem:
The system shows a trace during boot and hangs.

Kernel version:
5.0.0-0.rc4.git0, 5.0.0-0.rc6.git0 and 5.0.0-0.rc6.git1.

Kernel 5.0.0-0.rc3.git0 boots ok. Version 4.20.3-200 also worked ok back in Fedora 29.

Reproducible:
Always.

No extra modules or proprietary drivers.

journalctl --no-hostname -k --boot=-1 (or -2 or -3) only shows previous successful boots. Please instruct me on how to gather information about a failed boot attempt (other than taking a picture with my phone).

My hardware is a Chuwi Lapbook SE Chinese notebook. Celeron N4100, Intel chipset and graphics.

BTW: seamless boot works. If I leave rhgb and quiet params, all I see is the Chuwi logo forever. I have to remove rhgb to actually see the trace.
Comment 1 Ernesto 2019-02-14 23:00:13 UTC 
Created attachment 1534998 [details]
Screenshot
Comment 2 Ernesto 2019-02-14 23:04:55 UTC 
I can guess the problem is related to the mmc driver, and I have to add that Fedora is installed on the integrated 32 GB eMMC on this notebook.
Comment 3 Laura Abbott 2019-02-15 01:09:25 UTC 
If you try the debug version of the 4.20 kernel do you see the same issue? I ask because I left debugging code on a couple of times recently and that crash is coming from debug code 

https://koji.fedoraproject.org/koji/packageinfo?packageID=8 you can install kernel-debug from here
Comment 4 Ernesto 2019-02-15 02:16:43 UTC 
Yes, I tried kernel 4.20 debug and it crashed.
Comment 5 Laura Abbott 2019-02-18 19:30:31 UTC 
Okay today's -rc7 build should have debugging enabled. Please try that. I also started a thread with the mmc maintainers upstream.
Comment 6 Laura Abbott 2019-02-22 22:03:25 UTC 
https://koji.fedoraproject.org/koji/taskinfo?taskID=32976235 can you test this scratch build when it finishes? This has debugging enabled and a potential fix from upstream.
Comment 7 Ernesto 2019-02-23 01:02:25 UTC 
rc7 git 2.1 doesn't work, but rc7 git 3.1 does!
Comment 8 Ernesto 2019-05-09 18:52:31 UTC 
So this is fixed in FC30. Should I close this bug?
Comment 9 Laura Abbott 2019-05-09 19:49:15 UTC 
Yes I'll close it, the fix should have been picked up.