From owner-freebsd-current Fri Feb 23 9:56:24 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 9579937B503 for ; Fri, 23 Feb 2001 09:56:20 -0800 (PST) (envelope-from dillon@earth.backplane.com) Received: (from dillon@localhost) by earth.backplane.com (8.11.2/8.9.3) id f1NHuAX83112; Fri, 23 Feb 2001 09:56:10 -0800 (PST) (envelope-from dillon) Date: Fri, 23 Feb 2001 09:56:10 -0800 (PST) From: Matt Dillon Message-Id: <200102231756.f1NHuAX83112@earth.backplane.com> To: Kirk McKusick Cc: current@freebsd.org Subject: Re: Any Ideas References: <200102231206.EAA12234@beastie.mckusick.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :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