Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 15 Feb 2007 10:19:59 +0800 (CST)
From:      Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>
To:        Eric Anderson <anderson@freebsd.org>
Cc:        Poul-Henning Kamp <phk@phk.freebsd.dk>, current@freebsd.org
Subject:   Re: X stopped working on my T41p :-/
Message-ID:  <0702150950503.32072@www.mmlab.cse.yzu.edu.tw>
In-Reply-To: <45D3073D.60501@freebsd.org>
References:  <1774.1171445374@critter.freebsd.dk> <45D3073D.60501@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 14 Feb 2007, Eric Anderson wrote:
> On 02/14/07 03:29, Poul-Henning Kamp wrote:
>> X stopped working on my T41p, and I'm wondering if anybody know if
>> this failure indication of hardware trouble, or if there is some
>> trick to getting the attention of the radeon chip ?
>> 
>> I have tried all the usual tricks, holy water, dead chicken, take
>> out batteries for 15 minutes etc.
>> 
>> Failing any good ideas for recovery, recommendations for sensible
>> and solid laptops are welcome in private email.
>> 
>> Poul-Henning
>> 
>> 
>> xauth:  creating new authority file /home/phk/.serverauth.829
>> 
>> 
>> X Window System Version 6.9.0
>> Release Date: 21 December 2005
>> X Protocol Version 11, Revision 0, Release 6.9
>> Build Operating System: FreeBSD 7.0 i386 [ELF] Current Operating System: 
>> FreeBSD critter.freebsd.dk 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Tue Jan  2 
>> 13:14:38 UTC 2007 
>> root@critter.freebsd.dk:/usr/obj/critter/src/sys/TP41P i386
>> Build Date: 02 January 2007
>> 	Before reporting problems, check http://wiki.X.Org
>> 	to make sure that you have the latest version.
>> Module Loader present
>> Markers: (--) probed, (**) from config file, (==) default setting,
>> 	(++) from command line, (!!) notice, (II) informational,
>> 	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
>> (==) Log file: "/var/log/Xorg.0.log", Time: Wed Feb 14 09:06:46 2007
>> (==) Using config file: "/etc/xorg.conf"
>> [drm] failed to load kernel module "radeon"
>> (EE) RADEON(0): [dri] DRIScreenInit failed.  Disabling DRI.
>> (EE) RADEON(0): Idle timed out, resetting engine...
>> (EE) RADEON(0): Idle timed out, resetting engine...
>> (EE) RADEON(0): Idle timed out, resetting engine...
>> [...]
>> 
>
> I've seen this before on an older radeon card, that died on me.  Not saying 
> that's your issue, but it might be.  Also - do you mean to have the radeon 
> kernel module loaded?  I'm not sure what happens if you don't have it and ask 
> for it..

   I've also seen this on my T40(Radeon Mobility 9000) since about a year ago.
It's hard to say which one is the major culprit as there are too many
changes(-CURRENT and X.org ports upgrade) hit to this box.

   The X server hanging appears to be random here. ssh/ping from outside
world still works.  Apart from the following X.org logs, the X server
in question also occupies a lot of CPU resource:

(EE) RADEON(0): Idle timed out, resetting engine...
(EE) RADEON(0): Idle timed out, resetting engine...
(EE) RADEON(0): Idle timed out, resetting engine...
(EE) RADEON(0): Idle timed out, resetting engine...
[...]

   Since the hanging is random here, I can get back to the normal state
after a couple of reboot cycles; otherwise, temporarily booting to Windoze
XP then reboot to FreeBSD also works for me.

-- 
Cheers,

Tai-hwa Liang



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