On Sat, 28 Sep 2013, 17:27 +0200, Oliver Pinter wrote:
> On 9/28/13, John Marshall <john.marsh...@riverwillow.com.au> wrote:
> > On Fri, 27 Sep 2013, 11:12 +0300, Konstantin Belousov wrote:
> >> On Fri, Sep 27, 2013 at 10:07:28AM +1000, John Marshall wrote:
> >> > The first two panics were triggered when shutting down the ntpd daemon
> >> > (a recent development snapshot version of ntpd: 4.2.7p387).  Exiting a
> >> > later release (p388) has not triggered the panic.  The system panicked
> >> > again overnight, this time while acting as an sftp server receiving
> >> > large (GB) files from another system.
> >
> >> > I have made the core.txt.[0-2] files available in the following
> >> > directory.  The directory is not browsable.
> >> >
> >> >   http://www.riverwillow.net.au/~john/92rc4/
> >>
> >> This might be fixed by r254087-r254090 on stable/9.
> >
> > Thank you.  Those patches applied cleanly to releng/9.2 so I rebuilt a
> > patched 9.2.  I double-checked and verified that the following patched
> > files in my releng/9.2@255904 working copy were identical to the same
> > files in stable/9@254090, then I removed /usr/obj/* and built a fresh
> > system.

> > The system panicked as follows during shutdown after its first boot.
> > The corresponding core.txt.3 file is available at the same location
> > previously posted.

> > I have now seen this panic on a second server as well (also amd64 but
> > different hardware vendor).  This second (unpatched) system also
> > panicked during shutdown as follows. Corresponding file named
> > core.txt.0.system2 is available at the same location as above.

> try this from 9-STABLE:
> https://github.com/freebsd/freebsd/commit/98362329be8e2cdefda1988e5e9d32efbc94855f

Thanks Oliver.  If I followed the links correctly, that looks like
r255507 on stable/9.  The second part of that patch didn't apply cleanly
to 9.2.  I investigated and it looks like that is because r254442 had
also been applied since 9.2.  I'm guessing I should also apply r254442
as well (first)?  I shall proceed with applying both patches, rebuild,
and see what happens.

-- 
John Marshall

Attachment: pgpYlMb8rKbe3.pgp
Description: PGP signature

Reply via email to