Need help solving possible corrupt image, kernel won't start after ubootAfter upgrading to linux kernel 3.9,...
How frequently do Russian people still refer to others by their patronymic (отчество)?
How to calculate a conditional PDF in mathematica?
Why does the Batman "crack his knuckles" in "Batman: Arkham Origins"?
Chess problem: Make a crossword in 3 moves
Bypass with wrong cvv of debit card and getting OTP
Isn't "Dave's protocol" good if only the database, and not the code, is leaked?
Does Evolution Sage proliferate Blast Zone when played?
Term for a character that only exists to be talked to
What do you call the angle of the direction of an airplane?
What's the big deal about the Nazgûl losing their horses?
Taking advantage when the HR forgets to communicate the rules
Do intermediate subdomains need to exist?
Contributing to a candidate as a Foreign National US Resident?
Do the 26 richest billionaires own as much wealth as the poorest 3.8 billion people?
How serious is plagiarism in a master’s thesis?
Do I need to be legally qualified to install a Hive smart thermostat?
Interview Question - Card betting
What happens if the limit of 4 billion files was exceeded in an ext4 partition?
How can power levels matter in a magic system that emphasizes control?
Why would "dead languages" be the only languages that spells could be written in?
How can I define a very large matrix efficiently?
Show that there are infinitely more problems than we will ever be able to compute
What is exact meaning of “ich wäre gern”?
Will electrically joined dipoles of different lengths, at right angles, behave as a multiband antenna?
Need help solving possible corrupt image, kernel won't start after uboot
After upgrading to linux kernel 3.9, kde does not start correctlyKernel does not load after modifying parameters and kernel image with SyslinuxCorrupt LVM metadata header after kernel updateLinux/Embedded Linux - Understanding the Kernel and additional BSP specific componentsConsole won't load after update to 4.15.2 kernel
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am working on a design that runs Yocto on the following SOM:
Variscite VAR-SOM-MX6 Quad 996 MHz
We found that sometimes after either power loss or even just a "sudo reboot" that the system won't boot up again. We've pulled serial logs from good and bad systems, but unfortunately they don't tell us much other than the bad unit stops abruptly at:
Starting kernel ...
In the good case, it does all the normal kernel printouts after that such as:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
Any ideas where I could start to look for corruption? Or commands I should try in uboot to debug? I searched the code with grep and even "strings" + grep and couldn't see where the print out comes from for:
Booting Linux on physical CPU
I do have a dump of the two file systems so I can look for files that may be corrupted etc. But I'm not at all sure even where to start looking.
Here are the good and bad serial logs that we get in more detail:
GOOD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 26 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:bf:f9
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 104 ms (416 KiB/s)
7172360 bytes read in 520 ms (13.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7108 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
...
...
BAD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 25 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:c0:07
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 198 ms (217.8 KiB/s)
7172184 bytes read in 3095 ms (2.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7058 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
linux-kernel reboot u-boot yocto
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
add a comment |
I am working on a design that runs Yocto on the following SOM:
Variscite VAR-SOM-MX6 Quad 996 MHz
We found that sometimes after either power loss or even just a "sudo reboot" that the system won't boot up again. We've pulled serial logs from good and bad systems, but unfortunately they don't tell us much other than the bad unit stops abruptly at:
Starting kernel ...
In the good case, it does all the normal kernel printouts after that such as:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
Any ideas where I could start to look for corruption? Or commands I should try in uboot to debug? I searched the code with grep and even "strings" + grep and couldn't see where the print out comes from for:
Booting Linux on physical CPU
I do have a dump of the two file systems so I can look for files that may be corrupted etc. But I'm not at all sure even where to start looking.
Here are the good and bad serial logs that we get in more detail:
GOOD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 26 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:bf:f9
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 104 ms (416 KiB/s)
7172360 bytes read in 520 ms (13.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7108 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
...
...
BAD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 25 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:c0:07
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 198 ms (217.8 KiB/s)
7172184 bytes read in 3095 ms (2.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7058 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
linux-kernel reboot u-boot yocto
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
add a comment |
I am working on a design that runs Yocto on the following SOM:
Variscite VAR-SOM-MX6 Quad 996 MHz
We found that sometimes after either power loss or even just a "sudo reboot" that the system won't boot up again. We've pulled serial logs from good and bad systems, but unfortunately they don't tell us much other than the bad unit stops abruptly at:
Starting kernel ...
In the good case, it does all the normal kernel printouts after that such as:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
Any ideas where I could start to look for corruption? Or commands I should try in uboot to debug? I searched the code with grep and even "strings" + grep and couldn't see where the print out comes from for:
Booting Linux on physical CPU
I do have a dump of the two file systems so I can look for files that may be corrupted etc. But I'm not at all sure even where to start looking.
Here are the good and bad serial logs that we get in more detail:
GOOD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 26 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:bf:f9
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 104 ms (416 KiB/s)
7172360 bytes read in 520 ms (13.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7108 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
...
...
BAD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 25 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:c0:07
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 198 ms (217.8 KiB/s)
7172184 bytes read in 3095 ms (2.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7058 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
linux-kernel reboot u-boot yocto
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
I am working on a design that runs Yocto on the following SOM:
Variscite VAR-SOM-MX6 Quad 996 MHz
We found that sometimes after either power loss or even just a "sudo reboot" that the system won't boot up again. We've pulled serial logs from good and bad systems, but unfortunately they don't tell us much other than the bad unit stops abruptly at:
Starting kernel ...
In the good case, it does all the normal kernel printouts after that such as:
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
Any ideas where I could start to look for corruption? Or commands I should try in uboot to debug? I searched the code with grep and even "strings" + grep and couldn't see where the print out comes from for:
Booting Linux on physical CPU
I do have a dump of the two file systems so I can look for files that may be corrupted etc. But I'm not at all sure even where to start looking.
Here are the good and bad serial logs that we get in more detail:
GOOD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Feb 08 2019 - 02:26:07)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 26 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:bf:f9
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 104 ms (416 KiB/s)
7172360 bytes read in 520 ms (13.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7108 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.9.55-fslc+g6b0fd61e1be8 (oe-user@oe-host) (gcc version 7.2.0 (GCC) ) #1 SMP Thu Feb 14 02:19:29 UTC 2019
[ 0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] OF: fdt:Machine model: Variscite i.MX6 QUAD/DUAL VAR-SOM-MX6 Audacy Gateway
[ 0.000000] cma: Reserved 16 MiB at 0x4f000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] percpu: Embedded 15 pages/cpu @ef797000 s30888 r8192 d22360 u61440
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 260608
[ 0.000000] Kernel command line: console=ttymxc0,115200 root=/dev/mmcblk0p5 ro
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
...
...
BAD
U-Boot SPL 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
DDR LEGACY configuration
NAND : 512 MiB
U-Boot 2015.04+fslc+g1dad2408ad (Jul 25 2018 - 09:35:33)
CPU: Freescale i.MX6Q rev1.5 at 792 MHz
CPU: Temperature 25 C
Reset cause: POR
Board: Variscite VAR-SOM-MX6 Quad 996 MHz
I2C: ready
DRAM: 1 GiB
PMIC: PFUZE100 ID=0x10
NAND: 512 MiB
MMC: FSL_SDHC: 0, FSL_SDHC: 1
auto-detected panel VAR-WVGA MX6CB-R
Display: VAR-WVGA MX6CB-R (800x480)
In: serial
Out: serial
Err: serial
switch to partitions #0, OK
mmc0 is current device
No eMMC
Configuring SD1 pins as inputs
Net: using phy at 7
got MAC-1 address from fuse: f8:dc:7a:04:c0:07
FEC [PRIME]
Normal Boot
Hit any key to stop autoboot: 0
Booting from mmc ...
44340 bytes read in 198 ms (217.8 KiB/s)
7172184 bytes read in 3095 ms (2.2 MiB/s)
Kernel image @ 0x12000000 [ 0x000000 - 0x6d7058 ]
## Flattened Device Tree blob at 18000000
Booting using the fdt blob at 0x18000000
Using Device Tree in place at 18000000, end 1800dd33
switch to ldo_bypass mode!
Starting kernel ...
linux-kernel reboot u-boot yocto
linux-kernel reboot u-boot yocto
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
asked 8 mins ago
EradicatoreEradicatore
1112 bronze badges
1112 bronze badges
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f528124%2fneed-help-solving-possible-corrupt-image-kernel-wont-start-after-uboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f528124%2fneed-help-solving-possible-corrupt-image-kernel-wont-start-after-uboot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
