The update that broke layered build was https://review.opendev.org/#/c/727908 It upversioned the kernels, but failed to follow the guidance to upversion all external kmods. Build avoidance is in use for layered builds, seeing no source or metadata changes for the kmod, it elected to reuse the previous build of the kmod. The previous kmod is only valid for the previous kernel due to embedded paths that include the kernel version. A kernel/kmod mismatch that results in unusable kmods, no network drivers, and an install failure on many pieces of hardware. Build avoidance is not in use for the monolithic build. Short term fix. Upversion the kmods Longer term fix. Extend Don's recent work on GITREVCOUNTS, and allow kmods to automatically inherit revision counts from the kernel. On 2020-05-21 3:14 p.m., Saul Wold wrote:
+starlingx-discuss
These should always go to the -discuss list please.
On 5/21/20 12:10 PM, Scott Little wrote:
investigating this now
Scott
On 2020-05-21 2:58 p.m., Jascanu, Nicolae wrote:
Hi,
I’ve attached the console output. The one from 16 is the good one.
Regards,
Nicolae Jascanu, Ph.D.
*TSD Software Engineer*
intel-logo
*Internet Of Things Group*
*Galati, Romania*
*From:* Jascanu, Nicolae *Sent:* Thursday, May 21, 2020 11:44 *To:* Austin Sun (austin.sun@intel.com) <austin.sun@intel.com>; Lin, Shuicheng <shuicheng.lin@intel.com> *Subject:* RE: StarlingX - fails at setup
Hi Austin,
Please find attached the console output for the good image from 16 and the bad image from 20.
We will try now to boot the bad image from 20 directly from server.
Regards,
Nicolae Jascanu, Ph.D.
*TSD Software Engineer*
intel-logo
*Internet Of Things Group*
*Galati, Romania*
*From:* Jascanu, Nicolae *Sent:* Thursday, May 21, 2020 10:41 *To:* Austin Sun (austin.sun@intel.com <mailto:austin.sun@intel.com>) <austin.sun@intel.com <mailto:austin.sun@intel.com>>; Lin, Shuicheng <shuicheng.lin@intel.com <mailto:shuicheng.lin@intel.com>> *Subject:* FW: StarlingX - fails at setup
Regards,
Nicolae Jascanu, Ph.D.
*TSD Software Engineer*
intel-logo
*Internet Of Things Group*
*Galati, Romania*
*From:* Jascanu, Nicolae *Sent:* Wednesday, May 20, 2020 21:33 *To:* Wold, Saul <saul.wold@intel.com <mailto:saul.wold@intel.com>>; Miller, Frank <Frank.Miller@windriver.com <mailto:Frank.Miller@windriver.com>>; Scott Little <scott.little@windriver.com <mailto:scott.little@windriver.com>> *Subject:* StarlingX - fails at setup
Hi,
An all baremetal configurations the setup fails with the same error. Please find attached the full console log from baremetal simplex.
[ 200.397941] dracut-initqueue[3884]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 200.906800] dracut-initqueue[3884]: Warning: dracut-initqueue timeout - starting timeout scripts
[ 201.4Warning: /dev/root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or /boot
after mounting them and attach it to a bug report.
Regards,
Nicolae Jascanu, Ph.D.
*TSD Software Engineer*
intel-logo
*Internet Of Things Group*
*Galati, Romania*