Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Apr 2012 15:22:44 -0700
From:      Kevin Oberman <kob6558@gmail.com>
To:        Jose Garcia Juanino <jjuanino@gmail.com>
Cc:        freebsd-x11@freebsd.org
Subject:   Re: Loading i915 module panics my system after patching with Intel GPU patch 14.4 for stable/9
Message-ID:  <CAN6yY1v=_vDvpGmqBrHq%2BDe6iWpKzEU1getO=f0r-r=O8Cu%2Bhg@mail.gmail.com>
In-Reply-To: <20120427211713.GA2379@banach>
References:  <20120424184459.GB2455@banach> <20120424194123.GC2358@deviant.kiev.zoral.com.ua> <20120424201526.GA2045@banach> <20120425053243.GF2358@deviant.kiev.zoral.com.ua> <20120426184933.GA2328@banach> <20120426190219.GU2358@deviant.kiev.zoral.com.ua> <20120427202548.GA2177@banach> <20120427211713.GA2379@banach>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 27, 2012 at 2:17 PM, Jose Garcia Juanino <jjuanino@gmail.com> w=
rote:
> El viernes 27 de abril a las 22:25:48 CEST, Jose Garcia Juanino escribi=
=F3:
>>
>> 2- startx with intel driver
>> X session takes a lot of time until it appears (1 minute). From a ssh
>> session, I see the Xorg process to consume the 100% of cpu time (kernel
>> time, not user time). But once the screen is showed up, it looks fine.
>> Fonts are well displayed and depth color is 24 (vesa only supports 8).
>> After a few minutes, CPU time drops until 0%, and it is possible to use
>> the computer. But if I try to move the mouse, again the cpu time
>> increase until 100% for 1 minute, and the system is unresponsive. Only I
>> can use the computer by mean of the keyboard after cpu consume drops
>> again.
>
> I forget to say that it is not possible to switch between console and X
> session by mean of CTRL+ALT+FN. For example, CTRL+ALT+F1 freeze the
> current image (with a lower resolution, maybe 8 bits). =A0However,
> keystrokes are correctly sent to the console, and it is possible to
> execute any command (blindly). This anomaly does not happen with vesa
> driver.

Switching to vtys is documented as being unimplemented when the
intel-kms driver is used, so this is a well known problem. I'm hoping
it happens rather soon as I really do miss them.

No idea about the mouse causing something to eat the CPU. Sorry.
--=20
R. Kevin Oberman, Network Engineer
E-mail: kob6558@gmail.com



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1v=_vDvpGmqBrHq%2BDe6iWpKzEU1getO=f0r-r=O8Cu%2Bhg>