TINY4412在系统移植时： TINY4412情况：在系统移植时[ 5.885000] Failed to init busfreq.

Question

TINY4412情况：在系统移植时，出现这种情况：
<3>Failed to init busfreq.
[ 5.885000] Failed to init busfreq.
有什么办法吗？各位，求帮助，可有偿！！

U-Boot 2010.12 (Aug 07 2024 - 19:22:01) for TINY4412


CPU:    S5PC220 [Samsung SOC on SMP Platform Base on ARM CortexA9]
        APLL = 1400MHz, MPLL = 800MHz

Board:  TINY4412
DRAM:   1023 MiB

vdd_arm: 1.2
vdd_int: 1.0
vdd_mif: 1.1

BL1 version:  N/A (TrustZone Enabled BSP)


Checking Boot Mode ... EMMC4.41
REVISION: 1.1
MMC Device 0: 3728 MB
MMC Device 1: 0 MB
MMC Device 2: N/A
Net:    No ethernet found.
Hit any key to stop autoboot:  0 
reading kernel..device 0 Start 1057, Count 12288 
MMC read: dev # 0, block # 1057, count 12288 ... 12288 blocks read: OK
completed
reading RFS..device 0 Count 13345, Start 8192 
MMC read: dev # 0, block # 13345, count 8192 ... 8192 blocks read: OK
completed
Boot with zImage
## Loading init Ramdisk from Legacy Image at 41000000 ...
   Image Name:   ramdisk
   Image Type:   ARM Linux RAMDisk Image (uncompressed)
   Data Size:    1010786 Bytes = 1010786    Load Address: 40800000
   Entry Point:  40800000

Starting kernel ...

。。。。。。。。/此处省略。。。。。。。。。。。。。。。/


```c
[    5.285000] dw_mmc dw_mmc: Using internal DMA controller.
dw_mmc dw_mmc: Version ID is 240a
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
[    5.320000] dw_mmc dw_mmc: Version ID is 240a
[    5.320000] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 400000Hz, actual 396825HZ div = 63)
dw_mmc dw_mmc: DW MMC controller at irq 109, 32 bit host data width, 128 deep fifo
[    5.345000] dw_mmc dw_mmc: DW MMC controller at irq 109, 32 bit host data width, 128 deep fifo
s3c-sdhci exynos4-sdhci.2: clock source 2: mmc_busclk.2 (100000000 Hz)
[    5.360000] s3c-sdhci exynos4-sdhci.2: clock source 2: mmc_busclk.2 (100000000 Hz)
<7>Registered led device: mmc1::
mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
[    5.370000] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0)
mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1)
[    5.400000] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1)
<6>mmc0: new high speed DDR MMC card at address 0001
<6>mmc1: SDHCI controller on samsung-hsmmc [exynos4-sdhci.2] using ADMA
[    5.415000] mmc0: new high speed DDR MMC card at address 0001
[    5.415000] mmc1: SDHCI controller on samsung-hsmmc [exynos4-sdhci.2] using ADMA
s3c-sdhci exynos4-sdhci.3: clock source 2: mmc_busclk.2 (100000000 Hz)
[    5.425000] s3c-sdhci exynos4-sdhci.3: clock source 2: mmc_busclk.2 (100000000 Hz)
<7>Registered led device: mmc2::
<6>mmcblk0: mmc0:0001 M4G1FB 3.64 GiB 
[    5.440000] mmcblk0: mmc0:0001 M4G1FB 3.64 GiB 
<6>mmcblk0boot0: mmc0:0001 M4G1FB partition 1 1.00 MiB
[    5.455000] mmcblk0boot0: mmc0:0001 M4G1FB partition 1 1.00 MiB
<6>mmcblk0boot1: mmc0:0001 M4G1FB partition 2 1.00 MiB
[    5.470000] mmcblk0boot1: mmc0:0001 M4G1FB partition 2 1.00 MiB
<6> mmcblk0: p1 p2 p3 p4
<6>mmc2: SDHCI controller on samsung-hsmmc [exynos4-sdhci.3] using ADMA
[    5.485000]  mmcblk0: p1 p2 p3 p4
[    5.485000] mmc2: SDHCI controller on samsung-hsmmc [exynos4-sdhci.3] using ADMA
<6>usbcore: registered new interface driver usbhid
<6> mmcblk0boot1: unknown partition table
[    5.490000] usbcore: registered new interface driver usbhid
[    5.490000]  mmcblk0boot1: unknown partition table
<6>usbhid: USB HID core driver
<6> mmcblk0boot0: unknown partition table
[    5.510000] usbhid: USB HID core driver
[    5.510000]  mmcblk0boot0: unknown partition table
<6>Samsung Audio Subsystem Driver, (c) 2011 Samsung Electronics
[    5.530000] Samsung Audio Subsystem Driver, (c) 2011 Samsung Electronics
<6>audss_init: RCLK SRC[busclk]
[    5.540000] audss_init: RCLK SRC[busclk]
<6>Samsung SRP driver, (c)2011 Samsung Electronics
[    5.550000] Samsung SRP driver, (c)2011 Samsung Electronics
<6>GACT probability NOT on
[    5.560000] GACT probability NOT on
<6>Mirror/redirect action on
[    5.575000] Mirror/redirect action on
<6>u32 classifier
[    5.580000] u32 classifier
<6>    Actions configured
[    5.580000]     Actions configured
<6>Netfilter messages via NETLINK v0.30.
[    5.590000] Netfilter messages via NETLINK v0.30.
<6>nf_conntrack version 0.5.0 (15535 buckets, 62140 max)
[    5.595000] nf_conntrack version 0.5.0 (15535 buckets, 62140 max)
<6>ctnetlink v0.93: registering with nfnetlink.
[    5.600000] ctnetlink v0.93: registering with nfnetlink.
<6>NF_TPROXY: Transparent proxy support initialized, version 4.1.0
[    5.610000] NF_TPROXY: Transparent proxy support initialized, version 4.1.0
<6>NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
[    5.620000] NF_TPROXY: Copyright (c) 2006-2007 BalaBit IT Ltd.
<6>xt_time: kernel timezone is -0000
[    5.640000] xt_time: kernel timezone is -0000
<6>ip_tables: (C) 2000-2006 Netfilter Core Team
[    5.645000] ip_tables: (C) 2000-2006 Netfilter Core Team
<6>arp_tables: (C) 2002 David S. Miller
[    5.650000] arp_tables: (C) 2002 David S. Miller
<6>TCP: cubic registered
[    5.660000] TCP: cubic registered
<6>Initializing XFRM netlink socket
[    5.665000] Initializing XFRM netlink socket
<6>NET: Registered protocol family 10
[    5.675000] NET: Registered protocol family 10
<6>mip6: Mobile IPv6
[    5.680000] mip6: Mobile IPv6
<6>ip6_tables: (C) 2000-2006 Netfilter Core Team
[    5.695000] ip6_tables: (C) 2000-2006 Netfilter Core Team
<6>sit: IPv6 over IPv4 tunneling driver
[    5.695000] sit: IPv6 over IPv4 tunneling driver
<6>NET: Registered protocol family 17
[    5.705000] NET: Registered protocol family 17
<6>NET: Registered protocol family 15
[    5.710000] NET: Registered protocol family 15
<6>Bluetooth: RFCOMM TTY layer initialized
[    5.720000] Bluetooth: RFCOMM TTY layer initialized
<6>Bluetooth: RFCOMM socket layer initialized
[    5.725000] Bluetooth: RFCOMM socket layer initialized
<6>Bluetooth: RFCOMM ver 1.11
[    5.745000] Bluetooth: RFCOMM ver 1.11
<6>Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.745000] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
<6>Bluetooth: BNEP filters: protocol multicast
[    5.750000] Bluetooth: BNEP filters: protocol multicast
<6>Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    5.760000] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
<6>NET: Registered protocol family 35
[    5.770000] NET: Registered protocol family 35
<5>Key type dns_resolver registered
[    5.790000] Key type dns_resolver registered
<6>EXYNOS4X12: Adaptive Support Voltage init
[    5.795000] EXYNOS4X12: Adaptive Support Voltage init
<6>EXYNOS4X12(SG): ORIG : 2 MOD : 0 RESULT : 2
[    5.795000] EXYNOS4X12(SG): ORIG : 2 MOD : 0 RESULT : 2
<6>EXYNOS: Fail to get HPM Value
[    5.805000] EXYNOS: Fail to get HPM Value
<6>VFP support v0.3: [    5.815000] VFP support v0.3: <c>implementor 41 architecture 3 part 30 variant 9 rev 4
implementor 41 architecture 3 part 30 variant 9 rev 4
<6>ThumbEE CPU extension supported.
[    5.830000] ThumbEE CPU extension supported.
<5>Registering SWP/SWPB emulation handler
[    5.845000] Registering SWP/SWPB emulation handler
<3>[ 6 ] Memory Type Undertermined.
[    5.845000] [ 6 ] Memory Type Undertermined.
<6>DVFS : VDD_INT Voltage table set with 0 Group
[    5.850000] DVFS : VDD_INT Voltage table set with 0 Group
<3>Failed to init busfreq.
[    5.885000] Failed to init busfreq.
s3c-rtc s3c64xx-rtc: setting system clock to 2013-01-01 12:00:02 UTC (1357041602)
[    5.895000] s3c-rtc s3c64xx-rtc: setting system clock to 2013-01-01 12:00:02 UTC (1357041602)
[   17.980000] ALSA device list:
<6>  No soundcards found.
[   17.985000]   No soundcards found.
<6>Freeing init memory: 212K
[   17.985000] Freeing init memory: 212K
switch_root: bad newroot /r
<0>Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100

[   18.025000] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000100

Answer 1

以下回复参考：皆我百晓生、券券喵儿等免费微信小程序作答:

要解决这个问题，首先确认failed to init busfreq错误出现在哪里。这可能是因为硬件设备（如内存、硬盘等）没有正确初始化或者系统配置问题导致。

第一步：检查硬件连接和初始化

确保所有硬件（包括内存条、硬盘、电源适配器等）都在正常工作，并且已正确插入到主板上。尝试重新启动计算机，看看是否能进入安全模式以查看更多关于错误的信息。

第二步：检查BIOS设置

检查并调整您的BIOS设置，确保硬件设备的时钟和其他参数都设置为默认值。有些BIOS允许您手动设置这些参数，但大多数情况下，BIOS会自动识别硬件设备的时钟频率。

第三步：检查内存和硬盘性能

检查内存条的频率设置和电压，确保它们与主板兼容。同时，检查硬盘的转速和磁盘控制器的驱动程序状态。如果有必要，更新或重置硬盘驱动器。

第四步：系统配置检查

确保系统的其他组件也处于最佳运行状态。例如，确保网卡和其他网络设备是可用的，以及防火墙和路由器都是开启的。此外，确保系统中的服务和应用程序都是最新的。

第五步：使用诊断工具

有时，某些错误可能是由于软件冲突或驱动程序问题引起的。您可以尝试使用一些流行的Linux系统诊断工具，如lspci, dmesg, 或者专门针对特定错误类型的诊断工具。

第六步：联系制造商或技术支持

如果以上步骤都无法解决问题，建议联系硬件制造商或专业的技术支持团队寻求帮助。他们通常可以提供更详细的诊断和修复建议。

注意：

• 避免自行拆卸硬件进行修理，除非您对硬件非常熟悉。
• 在进行任何硬件或软件更改之前，请备份重要数据。
• 如果您不确定如何操作，不要试图自行修理硬件，以免造成更大的损坏。

希望上述方法能够帮助您解决遇到的问题。如果您在处理硬件故障时感到困惑，请考虑寻求专业人士的帮助。