The QEMU x86_64 Q35 fails verification for branch master as of commit
The following tests failed: BOOT_FAILURE
Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem 1e70cda soc/intel/apollolake: Avoid UART BAR relocation at ramstage e953dce soc/intel/apollolake: Add ids of internal SoC PCI devices
<172 commits skipped>
a95baf9 device: Add device path display support 800e964 arch/arm64: Compile arm-trusted-firmware with coreboot timestamp 21111be intel/kunimitsu: Set USB Type A current limit to 2A 9f54297 board_status.sh: Be smarter about cbfstool usage f43e51d board_status: Add script that will set up a ubuntu live image
See attached log for details
This message was automatically generated from Raptor Engineering's QEMU x86_64 Q35 test stand Want to test on your own equipment? Check out https://www.raptorengineeringinc.com/content/REACTS/intro.html
Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineeringinc.com for more information
Please contact Timothy Pearson at Raptor Engineering tpearson@raptorengineeringinc.com regarding any issues stemming from this notification
Dear coreboot folks,
Am Donnerstag, den 10.03.2016, 19:24 -0600 schrieb REACTS:
The QEMU x86_64 Q35 fails verification for branch master as of commit
The following tests failed: BOOT_FAILURE
Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem 1e70cda soc/intel/apollolake: Avoid UART BAR relocation at ramstage e953dce soc/intel/apollolake: Add ids of internal SoC PCI devices
<172 commits skipped>
a95baf9 device: Add device path display support 800e964 arch/arm64: Compile arm-trusted-firmware with coreboot timestamp 21111be intel/kunimitsu: Set USB Type A current limit to 2A 9f54297 board_status.sh: Be smarter about cbfstool usage f43e51d board_status: Add script that will set up a ubuntu live image
See attached log for details
``` […] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. [ 1.379745] FS-Cache: Loaded [ 1.384622] RPC: Registered named UNIX socket transport module. [ 1.385805] RPC: Registered udp transport module. [ 1.387000] RPC: Registered tcp transport module. [ 1.388245] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.398715] FS-Cache: Netfs 'nfs' registered for caching IP-Config: eth0 hardware address 80:80:80:80:80:ff mtu 1500 [ 1.408488] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IP-Config: eth0 guessed broadcast address 10.100.1.255 IP-Config: eth0 complete: address: 10.100.1.11 broadcast: 10.100.1.255 netmask: 255.255.255.0 gateway: 10.100.1.1 dns0 : 0.0.0.0 dns1 : 0.0.0.0 host : embed-o-matic rootserver: 0.0.0.0 rootpath: filename : connect: Connection timed out NFS over TCP not available from 10.100.1.100 chroot: can't execute 'test': No such file or directory Begin: Retrying nfs mount ... ```
This looks strange, at the error seems to be with the network connection and the operating system, so unrelated to coreboot.
If it’s related to coreboot it might be fixed by commit with Change- Id Ib8e1add3547cda01f71bf1dea14d3e58bdd99730 [1].
Thanks,
Paul
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 03/11/2016 01:58 AM, Paul Menzel wrote:
Dear coreboot folks,
Am Donnerstag, den 10.03.2016, 19:24 -0600 schrieb REACTS:
The QEMU x86_64 Q35 fails verification for branch master as of commit
The following tests failed: BOOT_FAILURE
Commits since last successful test: c7a1a3e northbridge/i945/gma: Re-enable NVRAM tft_brightness a2176d8 soc/apollolake: Add memory and reserve MMIO resources 555d6c2 cbmem: Add utility to get memory region occupied by cbmem 1e70cda soc/intel/apollolake: Avoid UART BAR relocation at ramstage e953dce soc/intel/apollolake: Add ids of internal SoC PCI devices
<172 commits skipped>
a95baf9 device: Add device path display support 800e964 arch/arm64: Compile arm-trusted-firmware with coreboot timestamp 21111be intel/kunimitsu: Set USB Type A current limit to 2A 9f54297 board_status.sh: Be smarter about cbfstool usage f43e51d board_status: Add script that will set up a ubuntu live image
See attached log for details
[…] Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/nfs-top ... done. Begin: Running /scripts/nfs-premount ... done. [ 1.379745] FS-Cache: Loaded [ 1.384622] RPC: Registered named UNIX socket transport module. [ 1.385805] RPC: Registered udp transport module. [ 1.387000] RPC: Registered tcp transport module. [ 1.388245] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.398715] FS-Cache: Netfs 'nfs' registered for caching IP-Config: eth0 hardware address 80:80:80:80:80:ff mtu 1500 [ 1.408488] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready IP-Config: eth0 guessed broadcast address 10.100.1.255 IP-Config: eth0 complete: address: 10.100.1.11 broadcast: 10.100.1.255 netmask: 255.255.255.0 gateway: 10.100.1.1 dns0 : 0.0.0.0 dns1 : 0.0.0.0 host : embed-o-matic rootserver: 0.0.0.0 rootpath: filename : connect: Connection timed out NFS over TCP not available from 10.100.1.100 chroot: can't execute 'test': No such file or directory Begin: Retrying nfs mount ...
This looks strange, at the error seems to be with the network connection and the operating system, so unrelated to coreboot.
If it’s related to coreboot it might be fixed by commit with Change- Id Ib8e1add3547cda01f71bf1dea14d3e58bdd99730 [1].
Thanks,
Paul
It does look strange, but I wonder if memory was corrupted in this area. There were no issues with the test net at the time these tests were run (see the other three failure reports), so unless this happens again I'm going to assume it was a side effect of the same failure.
- -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) http://www.raptorengineeringinc.com