Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 16 Aug 2012 07:04:56 +0100
From:      Matthew Seaman <matthew@FreeBSD.org>
To:        freebsd-questions@FreeBSD.org
Subject:   Re: 9.0 release hang in quiescent X
Message-ID:  <502C8D88.9040901@FreeBSD.org>
In-Reply-To: <502C7AFB.2020303@dreamchaser.org>
References:  <502C7AFB.2020303@dreamchaser.org>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigEBBD11865E3E61428739CEA2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On 16/08/2012 05:45, Gary Aitken wrote:
> I've been struggling trying to ignore something and it refuses to go
> away :-(.
>=20
> Running 9.0 release on an amd 64 box, standard kernel, 16GB, SSD (/,
> /usr, /var, /tmp) + HDDs, visiontek 900331 graphics card (ati radeon
> hd5550).
>=20
> As long as I am using the system, things seem to be fine.  However,
> when I leave the system idle for an extended period of time (e.g.
> overnight, out for the day, etc.), it often refuses to return from
> whatever state it is in.  The screen is blank and in standby for
> power saving, and <ctl><alt> Fn won't get me a console prompt.  The
> only way I know to recover is to power off and reboot.
>=20
> When this first happened, the file systems would come up trashed and
> I needed to manually fsck everything.  I've gotten in the habit of
> doing a sync prior to leaving the system, and they now seem to come
> up clean when I have to reboot, but that's obviously not a solution
> to the problem.
>=20
> Xorg.0.log shows the following errors: (EE) RADEON(0): Acceleration
> initialization failed However, the display works fine and I'm
> assuming I'm just getting slow rendering, which is ok in this case.
>=20
> Can someone suggest a good way to proceed to figure out what's going
> on?

Can you get network access to the machine when it gets into this state?

If you can't, that suggests the OS is hanging or crashing, possibly in
response to going into some sort of power-saving mode.

If you can get in, then there are many more possibilities.  Firstly, you
should be able to kill and restart the X server, which might get your
display back without rebooting.  Or else you could shutdown and reboot
cleanly.

As to working out what the underlying cause of the problem is: that's
harder.  I'd try experimenting with the power saving settings for your
graphics display.  If you can turn them off as a test, and the machine
then survives for an extended period of idleness, you'll have gone a
long way towards isolating the problem.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.
PGP: http://www.infracaninophile.co.uk/pgpkey



--------------enigEBBD11865E3E61428739CEA2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.16 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlAsjYgACgkQ8Mjk52CukIyieACeMYfl68A5rFV2SqyWw5lcGlZK
L1kAnA95j7EthTanUG1imWlA7TgFdyfv
=bMCx
-----END PGP SIGNATURE-----

--------------enigEBBD11865E3E61428739CEA2--



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?502C8D88.9040901>