I get this error when booting. I think everything still works. What does the error mean?
ERROR: C40000002:V3051002 I0 6D33944A-EC75-4855-A54D-809C75241F6C
ERROR: C40000002:V3051002 I0 6D33944A-EC75-4855-A54D-809C75241F6C
GNU GRUB version 0.97 (604K lower / 244604K upper memory)
+-------------------------------------------------------------------------+
| Quark X1000 kernel-SPI initrd-SPI IMR-On IO-APIC/HPET NoEMU |
| Quark X1000 kernel-MassStorage iot-devkit on SD IMR-On IO-APIC/HPET N> |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
+-------------------------------------------------------------------------+
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command-line.
The highlighted entry will be booted automatically in 1 seconds.
Found layout.conf @ 0xffcff000 len 0x00000c14
# WARNING: this file is indirectly included in a Makefile where it
# defines Make targets and pre-requisites. As a consequence you MUST
# run "make clean" BEFORE making changes to it. Failure to do so may
# result in the make process being unable to clean files it no longer
# has references to.
[main]
size=8388608
type=global
[MFH]
version=0x1
flags=0x0
address=0xfff08000
type=mfh
[Flash Image Version]
type=mfh.version
meta=version
value=0x01000400
[ROM_OVERLAY]
address=0xfffe0000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_BOOTROM_OVERRIDE.Fv
type=some_type
[signed-key-module]
address=0xfffd8000
item_file=config/SvpSignedKeyModule.bin
svn_index=0
type=some_type
in_capsule=no
# On a deployed system, the SVN area holds the last known secure
# version of each signed asset.
# TODO: generate this area by collecting the SVN from the assets
# themselves.
[svn-area]
address=0xfffd0000
item_file=config/SVNArea.bin
type=some_type
# A capsule upgrade must implement some smart logic to make sure the
# highest Security Version Number always wins (rollback protection)
in_capsule=no
[fixed_recovery_image]
address=0xfff90000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_RECOVERY_IMAGE1.Fv
sign=yes
type=mfh.host_fw_stage1_signed
svn_index=2
# in_capsule=no
[NV_Storage]
address=0xfff30000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_NVRAM.bin
type=some_type
[RMU]
address=0xfff00000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/RMU. bin
type=none_registered
[boot_stage1_image1]
address=0xffec0000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_BOOT_STAGE1_IMAGE1.Fv
sign=yes
boot_index=0
type=mfh.host_fw_stage1_signed
svn_index=1
[boot_stage1_image2]
address=0xffe80000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_BOOT_STAGE1_IMAGE2.Fv
sign=yes
boot_index=1
type=mfh.host_fw_stage1_signed
svn_index=1
[boot_stage_2_compact]
address=0xffd00000
item_file=../../Quark_EDKII/Build/QuarkPlatform/RELEASE_GCC/FV/FlashModules/EDKI I_BOOT_STAGE2_COMPACT.Fv
sign=yes
type=mfh.host_fw_stage2_signed
svn_index=3
[Ramdisk]
address=0xffa60000
item_file=../../meta-clanton/yocto_build/tmp/deploy/image-spi-galileo/image-spi- galileo-clanton.cpio.lzma
si...
Link Copied
Hi BrechtW,
I recommend you to check the following thread where this same error has been reported:
Regards,
Diego
Hi BrechtW,
I recommend you to check the following thread where this same error has been reported:
Regards,
Diego
Once I started using wifi card intel N 6235, this error is also shown but soon after boot runs normally.
Press [Enter] to directly boot.
Press [F7] to show boot menu options.
ERROR: C40000002:V3051002 I0 6D33944A-EC75-4855-A54D-809C75241F6C
Sure. N 6235 has a Bluetooth module connected via USB. Any USB device (like a web camera or a flash disk) creates an error message like shown above.
It seems that SPI Linux kernel does not handle USB devices and just alerts. So it is not a problem, just a feature
BR,
xbolshe
For more complete information about compiler optimizations, see our Optimization Notice.