嵌入式学习小组
直播中

李志静

7年用户 1400经验值
私信 关注

N9H30 SPI LINUX kernel启动死机了怎么解决?

Kernel:启动到以下地方就不动了。
使用的是JFFS2文件系统: SPI FLASH 128MBIT, 内部64M内存。
SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:625
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 4294967286ms
Console: colour dummy device 80x30
console [ttyS0] enabled
Calibrating delay loop... 148.88 BogoMIPS (lpj=744448)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0xc01e99d0 - 0xc01e9a0c
devtmpfs: initialized
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
bio: create slab  at 0
NetWinder Floating Point Emulator V0.97 (double precision)
jffs2: version 2.2. (NAND) (SUMMARY)  漏 2001-2006 Red Hat, Inc.
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
[nuc970fb_probe] 10
Console: switching to colour frame buffer device 100x30
fb0: nuc970fb frame buffer device
nuc970-uart.0: ttyS0 at I/O 0x0 (irq = 36) is a NUC970
nuc970_dma_proxy module initialized
brd: module loaded
nuc970-spi0 nuc970-spi0: master is unqueued, this is deprecated
m25p80: Enable Quad Mode
m25p80 spi0.0: w25q128 (16384 Kbytes)
Creating 2 MTD partitions on "m25p80":
0x000000000000-0x000000200000 : "kernel"
0x000000800000-0x000000e00000 : "rootfs"
nuc970-rtc nuc970-rtc: rtc core: registered nuc970-rtc as rtc0
nuc970-rtc nuc970-rtc: setting system clock to 2005-01-01 00:01:42 UTC (1104537702)
VFS: Mounted root (jffs2 filesystem) on device 31:1.
devtmpfs: error mounting -2
Freeing unused kernel memory: 128K
Kernel panic - not syncing: No init found.  Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
CPU: 0 PID: 1 Comm: swapper Not tainted 3.10.108 #17
Backtrace:
[] (dump_backtrace+0x0/0x10c) from [] (show_stack+0x18/0x1c)
r6:00000000 r5:c02a7328 r4:c025cf2c r3:00000000
[] (show_stack+0x0/0x1c) from [] (dump_stack+0x20/0x28)
[] (dump_stack+0x0/0x28) from [] (panic+0x94/0x1f8)
[] (panic+0x0/0x1f8) from [] (kernel_init+0x130/0x158)
r3:00000000 r2:60000053 r1:0000021f r0:c025cf2c
r7:00000000
[] (kernel_init+0x0/0x158) from [] (ret_from_fork+0x14/0x3c)
r5:c01e3310 r4:00000000


回帖(1)

李鸿洋

2024-1-16 10:12:48
If your N9H30 SPI Linux kernel is stuck at a certain point and won't proceed any further, you may want to try a few steps to resolve the issue:

1. Check the hardware connections: Verify that all hardware components are connected correctly, and there are no loose connections or damaged components. Sometimes, a faulty hardware component can cause the system to freeze during boot up.

2. Check the boot configuration: Make sure that the bootloader settings are correct, and the kernel configuration is accurate. Incorrect settings can cause the kernel to fail during the boot process.

3. Check for kernel errors: The kernel may be failing due to some errors or exceptions. Look for any error messages in the console or system logs. Check the kernel messages for any error codes or segmentation faults.

4. Debug the kernel: You can enable kernel debugging options to get more information about the system's state and any kernel-level issues. Debugging options can help you identify the cause of the kernel freeze.

5. Try a different filesystem: If you're using JFFS2, try a different filesystem, such as ext4 or NTFS. Some filesystems may be more stable than others.

6. Try booting from a different device: If using SPI Flash, try booting from a different flash device or using a different interface. It's possible that the flash device or interface might be causing the kernel freeze.

7. Contact support: If none of the above steps resolve the issue, you may want to reach out to the hardware or software vendor's support team for further assistance.
举报

更多回帖

发帖
×
20
完善资料,
赚取积分