Date: Fri, 23 Feb 2001 09:56:10 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Kirk McKusick <mckusick@mckusick.com> Cc: current@freebsd.org Subject: Re: Any Ideas Message-ID: <200102231756.f1NHuAX83112@earth.backplane.com> References: <200102231206.EAA12234@beastie.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Are you aware of any recent changes that would have caused this
:problem? I do not believe that the soft updates changes would
:have caused this problem since they were all related to `under
:stress' conditions which are not applicable here.
:
: ~Kirk
I haven't made any commits to -current for a while, like several
weeks. It's possible that the specfs fsync fixes I did few weeks
ago could be involved, but the syncing problem seems to have
come up recently... long after I had made those changes.
It seems more likely that the problems are related to scheduler
and interrupt subsystem changes in -current.
If someone were to generate a core during the failing synchronization
attempt I'd be happy to look at it. It can only be one of a few
possibilities: (1) The buffer cannot be synced because a background
write is in progress and the background write never finishes (not likely),
(2) the I/O for the buffer synchronization is initiated but interrupts
are winding up being disabled by the halt code due to holding Giant
and not sleeping (more likely). That all I can think of. We've hit
the interrupt disablement problem before in -current, it's probably
something simliar.
-Matt
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200102231756.f1NHuAX83112>