Date: Thu, 1 Aug 2019 07:58:12 -0600 From: Scott Long <scottl@samsco.org> To: Nick Wolff <darkfiberiru@gmail.com> Cc: "Clay Daniels Jr." <clay.daniels.jr@gmail.com>, "Rodney W. Grimes" <freebsd-rwg@gndrsh.dnsmgr.net>, Hans Petter Selasky <hps@selasky.org>, lausts@acm.org, freebsd-current@freebsd.org Subject: Re: Boot still broken from r349133-r349160 - Was re:(Problem with USB after r349133) Message-ID: <B19A2E3D-1297-4AFE-884A-C738DA4CDA58@samsco.org> In-Reply-To: <CACxAneDCay32KyDg_Rf%2BjKAg261=khnRa__r7EMEZCFNJvecLw@mail.gmail.com> References: <CAGLDxTXSiiuLCoobhQdmNsAivOajLdcs1BmDY2EUWTO7wk5t0A@mail.gmail.com> <201907300011.x6U0BO8w046636@gndrsh.dnsmgr.net> <CAGLDxTVP=bjVtC73waVjP04idgSZU_rw760q%2BPtMc4E5zuV7eg@mail.gmail.com> <CACxAneDCay32KyDg_Rf%2BjKAg261=khnRa__r7EMEZCFNJvecLw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I’m 99% sure that the boot breakage is due to this commit: Author: jkim Date: Tue Jul 9 18:02:36 2019 New Revision: 349863 URL: https://svnweb.freebsd.org/changeset/base/349863 Log: MFV: r349861 Import ACPICA 20190703. I have two systems now that are affected, and both of them are “fixed” by reverting this. I don’t know the root cause yet, see my email to the svn-src-all mailing list. Scott > On Jul 29, 2019, at 8:29 PM, Nick Wolff <darkfiberiru@gmail.com> wrote: > > Sorry boot is broken from harddrive or iso(as cdrom) for some users(at > least 3) since somewhere in the revisions listed above and that still > stands as of the Head snapshot of 072519. Sorry for lack of clarity. There > was a thread under Problem with USB after r349133 but I decided to rename > it to try to catch more people's eyes/get more reports in if people run > into the issue. Don't think or at least know for sure USB is the problem as > when you bypass the waiting for USB you get a different hang farther into > system booting. > > I will try to bisect the build in that magic revision range once I figure > out on what system as it's my primary builder that's having this issue. Not > that I have a lack of hardware I guess just time to setup something else. > > > > > On Mon, Jul 29, 2019, 21:45 Clay Daniels Jr. <clay.daniels.jr@gmail.com> > wrote: > >> Rodney, you are right that the .iso "should work", and a lot of other >> projects, from Microsoft Windows 10 to Trident BSD only a furnish an iso, >> and no img file. FreeBSD is one of the few that give you both choices. The >> problem goes deeper than any one operating system. If you've ever used the >> Rufus tool to make a bootable usb, which is all Rufus does, you may have >> come across problems with "mount root". I found this article, answered by a >> Rufus developer very enlightening. >> >> https://superuser.com/questions/1170832/why-are-there-different-options-for-creating-bootable-usb-compared-to-a-cd >> >> I have a collection of usb thumbdrives here at my desk, and use them a >> lot, but I also bought me some blank dvd disks and use them too. >> >> But I think you are right, Nick Wolff's problem may be a a bug to be >> reported. All I know is I took the same file, >> FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso >> <https://download.freebsd.org/ftp/snapshots/amd64/amd64/ISO-IMAGES/13.0/FreeBSD-13.0-CURRENT-amd64-20190725-r350322-disc1.iso>; >> , burned it to a dvd, and I'm now writing this email from the FreeBSD >> 13.0-CURRENT r350322 partition of my computer. >> >> Clay >> > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B19A2E3D-1297-4AFE-884A-C738DA4CDA58>