Bug 2222823

Summary: 6.5 kernel broken configuration for all rockchip based devices
Product: [Fedora] Fedora Reporter: bonin' o'brien <jaxiel.kaise>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED COMPLETED QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: rawhideCC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-27 04:33:03 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
good boot log over uart
none
bad boot log over uart none

Description bonin' o'brien 2023-07-13 23:03:09 UTC 
fedora server rawhide aarch64

sometime after 6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39 and before 6.5.0-0.rc0.20230706gitc17414a273b8.12.fc39, it broke
6.5.0-0.rc1.11.fc39 also does not work
Comment 1 bonin' o'brien 2023-07-13 23:04:22 UTC 
Created attachment 1975660 [details]
good boot log over uart
Comment 2 bonin' o'brien 2023-07-13 23:04:55 UTC 
Created attachment 1975661 [details]
bad boot log over uart
Comment 3 bonin' o'brien 2023-07-16 01:06:47 UTC 
also tried 
   6.5.0-0.rc0.20230629git3a8a670eeeaa.3.fc39
   6.5.0-0.rc0.20230630gite55e5df193d2.5.fc39
   6.5.0-0.rc0.20230703gita901a3568fd2.8.fc39
   6.5.0-0.rc0.20230705gitd528014517f2.10.fc39
   6.5.0-0.rc1.20230711git3f01e9fed845.12.fc39
none worked
Comment 4 bonin' o'brien 2023-07-16 01:55:39 UTC 
since the breakdown happened between 2 and 3, this simplifies things, so looking at the diffs in linux-next, i see some rockchip changes to the rk8xx, so i checked what was defined in the builds

% grep _RK8 /boot/config-6.5.0-0.rc*
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_INPUT_RK805_PWRKEY=m
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_PINCTRL_RK805=m
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_CHARGER_RK817=m
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_MFD_RK808=y
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_REGULATOR_RK808=y
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_SND_SOC_RK817=m
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_RTC_DRV_RK808=m
/boot/config-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64:CONFIG_COMMON_CLK_RK808=y
/boot/config-6.5.0-0.rc0.20230629git3a8a670eeeaa.3.fc39.aarch64:# CONFIG_MFD_RK8XX_I2C is not set
/boot/config-6.5.0-0.rc0.20230629git3a8a670eeeaa.3.fc39.aarch64:# CONFIG_MFD_RK8XX_SPI is not set

also noticed the inbuilt rtc on the voltage regulator didn't seem to be showing up in the logs for non-booting systems

looks like there are no rk805 drivers in kernel-modules-core, which are kind of critical to the system

% rpm -ql kernel-modules-core-6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64 | grep -i rk8
/lib/modules/6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64/kernel/drivers/input/misc/rk805-pwrkey.ko.xz
/lib/modules/6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64/kernel/drivers/pinctrl/pinctrl-rk805.ko.xz
/lib/modules/6.5.0-0.rc0.20230628git6aeadf7896bf.2.fc39.aarch64/kernel/drivers/rtc/rtc-rk808.ko.xz
% rpm -ql kernel-modules-core-6.5.0-0.rc0.20230629git3a8a670eeeaa.3.fc39.aarch64 | grep -i rk8
Comment 5 bonin' o'brien 2023-07-18 20:25:46 UTC 
6.5.0-0.rc2.17.fc39.aarch64 also does not address this
Comment 6 bonin' o'brien 2023-07-27 04:33:03 UTC 
fixed in 6.5.0-0.rc3.23.fc39.aarch64