On Sun, 2019-08-25 at 15:03 +0300, Konstantin Belousov wrote:
> On Sun, Aug 25, 2019 at 12:40:22AM +0200, Trond Endrestøl wrote:
> > On Sun, 25 Aug 2019 01:28+0300, Konstantin Belousov wrote:
> >
> > > On Sun, Aug 25, 2019 at 12:19:43AM +0200, Trond Endrestøl wrote:
> > > > On Sat, 24 Aug 2019 23:
On Tue, Sep 10, 2019 at 10:50:33AM -0600, Ian Lepore wrote:
> On Sun, 2019-08-25 at 15:03 +0300, Konstantin Belousov wrote:
> > On Sun, Aug 25, 2019 at 12:40:22AM +0200, Trond Endrestøl wrote:
> > > On Sun, 25 Aug 2019 01:28+0300, Konstantin Belousov wrote:
> > >
> > > > On Sun, Aug 25, 2019 at 12
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-
resp
* 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 af
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.free
Few hours ago I upgrade FreeBSD-12.0-STABLE (revision 351639) to
FreeBSD-12.0-STABLE (revision 352091).
After running the new version for few hours 2 of my servers crashed and
auto-reboot.
Logs show nothing.
Any idea if a commit between these 2 versions can cause it?
__
