<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On 4. juuni 2017, at 20:13, Jean-Pierre André <<a href="mailto:jean-pierre.andre@wanadoo.fr" class="">jean-pierre.andre@wanadoo.fr</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Jean-Pierre André wrote:<br class=""><blockquote type="cite" class="">ken mays via oi-dev wrote:<br class=""><blockquote type="cite" class="">On that note, be aware of prior notice on AMD64 Athlon 64-based<br class="">computers and the use of software from:<br class=""></blockquote><br class="">I have such a computer, which I intended to upgrade to 2017.04<br class=""><br class="">Is booting on a live-usb a valid test for presence/absence of<br class="">further problems ahead ? (IOW is the problem in the new loader or<br class="">in the kernel ?)<br class=""></blockquote><br class="">As nobody told whether the issue lies within the new loader or<br class="">in the kernel, and bug #8169 pointed at an issue in the loader,<br class="">I tried updating the current installation with the grub loader<br class="">kept in place (BE_HAS_GRUB=true in /etc/default/be).<br class=""><br class="">After the update, I can only boot into the new BE in single user<br class="">mode. Two kinds of errors are displayed :<br class=""><br class="">1) svc:/system/metainit: default:<br class=""> method "lib/svc/method/svc-metainit"<br class=""> failed with exit status 127<br class="">(shown three times then transitioned to maintenance).<br class=""></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>thats issue about SMF, just run svccfg delete svc:/system/metainit:default - it does not affect booting.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">2) APIC Error interrupt on CPU 1. Status 0 = 0, Status 1 = 80<br class="">This second error is traditional on this computer and is<br class="">normally avoided by the boot option "acpi-user-options=0x2"<br class="">which was in place.<br class=""></div></div></blockquote><div><br class=""></div><div>you can always test by: ok boot -B acpi-user-options=0x2 , or check the loader options menu;</div><div><br class=""></div><div>also prtconf -v and tr ‘\0’ ‘\n’ < /system/boot/environment from OS.</div><div><br class=""></div><div>This issue is worth to be filed in <a href="http://illumos.org/issues" class="">illumos.org/issues</a> if not done already.</div><br class=""><blockquote type="cite" class=""><div class=""><div class=""><br class="">Are these the errors which I was warned against ?<br class=""><br class="">Have they something to do with bug #8169 ?<br class=""><br class="">Do they mean I am kicked out, or is there a way to update<br class="">to the latest state before the bug was created ?<br class=""></div></div></blockquote></div><div class=""><br class=""></div><div class="">8169 is fixed in later builds, it was unfortunate the ISO’s got published just a bit before the issue and the fix. However, the 8169 is only affecting systems with ACPI v1 and only if you boot the latest iso/usb, pkg update will give you the fix. The 8169 does make kernel startup to fail as the boot loader was passing wrong size for ACPI table - if you got the single user, you are not affected.</div><div class=""><br class=""></div><div class="">However, if you did end up in single user mode, it means that some essential service did fail for some reason, does svcs -vx reveal anything?</div><div class=""><br class=""></div><div class="">rgds,</div><div class="">toomas</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></body></html>