Bug 197079 - Can not boot kernel 4.13 from SD card on Asus TP200SA
Summary: Can not boot kernel 4.13 from SD card on Asus TP200SA
Status: RESOLVED CODE_FIX
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 blocking
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-29 19:49 UTC by Kemal Ilgar Eroğlu
Modified: 2023-01-05 12:03 UTC (History)
1 user (show)

See Also:
Kernel Version: 4.13
Subsystem:
Regression: No
Bisected commit-id:


Attachments
Kernel .config file (174.95 KB, text/x-mpsub)
2017-09-29 19:49 UTC, Kemal Ilgar Eroğlu
Details

Description Kemal Ilgar Eroğlu 2017-09-29 19:49:23 UTC
Created attachment 258647 [details]
Kernel .config file

Hello,

I can not (consistently) boot Linux kernel version 4.13.x on my Asus TP200SA system (it is a 2-in-1 laptop with an Intel Celeron N3050 processor on a Cherryview platform). The 4.12 and older versions used to work fine. To be more precise:

This computer has an internal eMMC storage as the hard drive but I am using an external microSD card to host the Linux partitions. With 4.13.x, boot process begins as normal but after just 3 or 4 seconds, error messages start scrolling down the screen. I can not stop them from scrolling, but I can reboot with the magic keys.

Since the messages scroll too fast I can not read them, but I can catch references to handle_bad_irq, chv_gpio_irqchip and pinctrl_cherryview. I need to load pinctrl_cherryview from the initrd otherwise the SD card will not be recognized. After a Google search I came accross the following threads which caused me to suspect that the recent changes to the gpio and irq-related code could be the culprit:

https://lkml.org/lkml/fancy/2017/9/28/464
https://lkml.org/lkml/fancy/2017/7/11/174

I would welcome any guidance on how to collect more data about the bug.

Now about the consistency remark at the start: If I boot into kernel 4.4.x first (that's the one I have as a stable backup) and then try to boot into 4.13.x, it works. But I get the error above if I reboot from (a working or failed) 4.13.x.

I also have the same kind of inconsistent boot failure with a trimmed-down kernel config (where almost everything needed is compiled-in), but with a completely black screen from the very start and magic keys not working. As in the other case I can successfully boot, however, if I boot into 4.4.x first.

I am attaching my (non-trimmed) kernel config to the message.
Comment 1 Andy Shevchenko 2023-01-04 20:37:11 UTC
The bug #197953 may be also related. In any case.

Would be wonderfull if someone can update this report with the information
regarding behaviour when run the latest vanilla kernel (v6.1.y as of today).
Comment 2 Kemal Ilgar Eroğlu 2023-01-05 12:03:40 UTC
I haven't yet tested it with 6.1.x, but this bug was fixed not long after I reported it (that computer now runs kernel 5.15). I'm marking this as fixed and I apologize for forgetting to do this earlier.

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