Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
On Wed, Sep 11, 2019 at 08:59:58AM -0700, John Kennedy wrote: > For what it's worth, I have a Dell Optiplex 9020 booting r352118: > > FreeBSD 12.1-PRERELEASE #105 r352118+b6945c1f5542(stable/12) > > That's at least after r352025, which may help your bisect. Currently > crunching r352202. I boot off of ZFS (vs UFS), but that might be another > data point for someone. I paid attention to bug 240487 and saw the "Fix miss merge in r352179" r352217 patch land and just booted with that. Looks good to me so far. FreeBSD 12.1-PRERELEASE #106 r352217+0e6a9a9426c7(stable/12) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
On Wed, Sep 11, 2019 at 01:38:14AM -0700, Jack L. wrote: > Yes, I upgraded 2 systems and both experience the same behavior > Dell R610 and Dell 7010 here. Afraid to upgrade any others For what it's worth, I have a Dell Optiplex 9020 booting r352118: FreeBSD FreeBSD 12.1-PRERELEASE #105 r352118+b6945c1f5542(stable/12) That's at least after r352025, which may help your bisect. Currently crunching r352202. I boot off of ZFS (vs UFS), but that might be another data point for someone. > On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy wrote: > > I have a system I updated from r352025 (which worked fine) to r352200. > > Any attempt to boot r352200 results in the system just sitting there after > > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > > message. Nothing further, not even after a half hour. The console is non- > > responsive (not that I'd really expect anything, but...). > > > > This persists across multiple resets, power cycles, etc. Booting the > > previous r352025 works fine, as expected. > > > > Before I start trying to bisect this, is anyone else seeing this? amd64 > > on a standard Dell PowerEdge R730 if that matters. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
Yes, I upgraded 2 systems and both experience the same behavior Dell R610 and Dell 7010 here. Afraid to upgrade any others On Tue, Sep 10, 2019 at 8:25 PM Terry Kennedy wrote: > > I have a system I updated from r352025 (which worked fine) to r352200. > Any attempt to boot r352200 results in the system just sitting there after > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > message. Nothing further, not even after a half hour. The console is non- > responsive (not that I'd really expect anything, but...). > > This persists across multiple resets, power cycles, etc. Booting the > previous r352025 works fine, as expected. > > Before I start trying to bisect this, is anyone else seeing this? amd64 > on a standard Dell PowerEdge R730 if that matters. > > Terry Kennedy http://www.glaver.org New York, NY USA > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
Since I'm not the only one seeing this, I've opened PR 240487: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240487 Terry Kennedy http://www.glaver.org New York, NY USA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Anyone else seeing hangs at "Trying to mount root" after recent commits?
* Terry Kennedy [190911 04:59]: > I have a system I updated from r352025 (which worked fine) to r352200. > Any attempt to boot r352200 results in the system just sitting there after > displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." > message. Nothing further, not even after a half hour. The console is non- > responsive (not that I'd really expect anything, but...). > This persists across multiple resets, power cycles, etc. Booting the > previous r352025 works fine, as expected. > Before I start trying to bisect this, is anyone else seeing this? amd64 > on a standard Dell PowerEdge R730 if that matters. My system r352194 also hangs at boot after successfully finding its usb devices. Console echos input on both connected usb keyboards, but nothing more. Previous kernel r352139 boots ok. Wolfgang ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Anyone else seeing hangs at "Trying to mount root" after recent commits?
I have a system I updated from r352025 (which worked fine) to r352200. Any attempt to boot r352200 results in the system just sitting there after displaying the normal "Trying to mount root from ufs:/dev/da0p3 [rw]..." message. Nothing further, not even after a half hour. The console is non- responsive (not that I'd really expect anything, but...). This persists across multiple resets, power cycles, etc. Booting the previous r352025 works fine, as expected. Before I start trying to bisect this, is anyone else seeing this? amd64 on a standard Dell PowerEdge R730 if that matters. Terry Kennedy http://www.glaver.org New York, NY USA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
