Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Nov 2009 19:13:30 +1100
From:      Peter Jeremy <peterjeremy@acm.org>
To:        Thomas Backman <serenity@exscape.org>
Cc:        freebsd-current@freebsd.org
Subject:   Re: Non-responsive 8.0-RC1
Message-ID:  <20091130081330.GA2202@server.vk2pj.dyndns.org>
In-Reply-To: <3ABF47F1-86EC-4CF2-9D42-86344D0F455B@exscape.org>
References:  <20091128212226.GA9841@server.vk2pj.dyndns.org> <3ABF47F1-86EC-4CF2-9D42-86344D0F455B@exscape.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--T4sUOijqQbZv57TR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2009-Nov-29 08:56:55 +0100, Thomas Backman <serenity@exscape.org> wrote:
>
>On Nov 28, 2009, at 10:22 PM, Peter Jeremy wrote:
>
>> My main server is running 8.0/amd64 from between RC1 and RC2 and I've
>> recently had a couple of long-duration hangs on it during which time
>> processes doing I/O will stop responding.

I forgot to mention that I checked SMART state on the disks and also
did a 'zpool scrub' after the first occurrence - no problems showed up.

It actually "hung" again just after I sent the original mail.  This
time I managed to get console access and could check the kernel state.
This showed that a number of processes were blocked on ZFS locks.
The most commonly reported state was 'tx->tx_quiesce_done_cv)'.

It had been up for about 30 days before I noticed any problems and
seems to have been getting more obvious so it is also possible that
it's related to uptime - either a resource leak somewhere (though
there was nothing obvious) or memory fragmentation.

>Hmm, I know there was some fix to the scheduler re: thread priority,
>and it wouldn't surprise me if it was after your revision.

After looking around in the kernel, I'm now confident that it's not
a priority-inversion issue as the BOINC processes all appeared to be
running normally and not holding locks.

>My advice would be to upgrade to -RELEASE if possible. If not, at
>least check whether your build should be affected.

I have updated to a recent 8-stable and will see what happens.

--=20
Peter Jeremy

--T4sUOijqQbZv57TR
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.13 (FreeBSD)

iEYEARECAAYFAksTfqoACgkQ/opHv/APuIdDiQCeMYxNFM0rgtiJUjt9hKnsC9U/
khMAn3omYgPFukvzSo4XEWISEinxBAAL
=R42y
-----END PGP SIGNATURE-----

--T4sUOijqQbZv57TR--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091130081330.GA2202>