From: Robert Noland on
On Mon, 2010-03-15 at 16:29 +0100, Henri-Pierre Charles wrote:
> Hello,
>
> On Sat, Mar 13, 2010 at 1:48 PM, Robert Noland <rnoland(a)freebsd.org> wrote:
> > On Fri, 2010-03-12 at 20:10 +0100, Torfinn Ingolfsen wrote:
> > Ok, now that agp seems to be working... I have created a port for the
> > 2.9.1 version of the Intel driver. You will need to uninstall the
> > existing intel driver and install this one. You still won't have drm,
> > but should be a good bit better than vesa...
> >
> > http://people.freebsd.org/~rnoland/xf86-video-intel29.tar.gz
> > Please let me know how it goes. You will likely want to use UXA
> > acceleration with this driver.
>
> Good to know that a new intel driver version is available.
>
> I've tried the new 7.5 xorg version and I still have difficulties
> with my atom based machine :
>
>
> asus:tmp/>dmesg | grep agp
> agp0: <Intel 82945G (945G GMCH) SVGA controller> on vgapci0
> agp0: detected 7932k stolen memory
> agp0: aperture size is 256M
> asus:tmp/>uname -a
> FreeBSD asus.hpch.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #3: Wed
> Jan 13 14:49:40 CET 2010
> root(a)asus.hpch.net:/usr/obj/usr/src/sys/GENERIC i386
> asus:tmp/>dmesg | grep CPU
> CPU: Intel(R) Atom(TM) CPU 230 @ 1.60GHz (1596.01-MHz 686-class CPU)
> p4tcc0: <CPU Frequency Thermal Control> on cpu0
>
> On this machine the symptom are a 30s to 1mn freeze then switching
> from console mode to graphic (when xdm start), and same hang when
> doing graphic stuff like dvd play, or using xv or qiv.
>
> Yesterday I've try to compile xorg 7.5 and xfce4. Same symptom.
>
> The only workaround I've found is to disable acpi
> 'hint.acpi.0.disabled="1" in /boot/loader.conf
> And even with that, I've a corrupted screen.
>
> Vesa is not an option, because it can not recognize my 1920x1200 screen.
>
> Is there any chance that the 2.9 intel driver behave better ?

It is very unlikely... The 2.9 series driver will not support drm
without GEM and so it is really slow. The only reason to try and use it
that I can think of is if you have an Ironlake chipset with isn't
supported in the 2.7 driver.

I have an Atom 330 with the 945 chipset and I haven't had any issues
with it. It is possible that it is waiting for resources. How much ram
do you have?

robert.

> HPC
>
--
Robert Noland <rnoland(a)FreeBSD.org>
FreeBSD

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Henri-Pierre Charles on
Hello

On Mon, Mar 15, 2010 at 6:06 PM, Robert Noland <rnoland(a)freebsd.org> wrote:
> On Mon, 2010-03-15 at 16:29 +0100, Henri-Pierre Charles wrote:
>> Hello,
>>
>> On Sat, Mar 13, 2010 at 1:48 PM, Robert Noland <rnoland(a)freebsd.org> wrote:
>> > On Fri, 2010-03-12 at 20:10 +0100, Torfinn Ingolfsen wrote:
>> > Ok, now that agp seems to be working... I have created a port for the
>> > 2.9.1 version of the Intel driver.  You will need to uninstall the
>> > existing intel driver and install this one.  You still won't have drm,
>> > but should be a good bit better than vesa...
>> >
>> > http://people.freebsd.org/~rnoland/xf86-video-intel29.tar.gz
>> > Please let me know how it goes.  You will likely want to use UXA
>> > acceleration with this driver.
>>
>> Good to know that a new intel driver version is available.
>>
>> I've tried the new 7.5 xorg  version and I still have difficulties
>> with my atom based machine  :
>> asus:tmp/>dmesg | grep agp
>> agp0: <Intel 82945G (945G GMCH) SVGA controller> on vgapci0
>> agp0: detected 7932k stolen memory
>> agp0: aperture size is 256M
>> asus:tmp/>uname -a
>> FreeBSD asus.hpch.net 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #3: Wed
>> Jan 13 14:49:40 CET 2010
>> root(a)asus.hpch.net:/usr/obj/usr/src/sys/GENERIC  i386
>> asus:tmp/>dmesg | grep CPU
>> CPU: Intel(R) Atom(TM) CPU  230   @ 1.60GHz (1596.01-MHz 686-class CPU)
>> p4tcc0: <CPU Frequency Thermal Control> on cpu0
>>
>> On this machine the symptom are a 30s to 1mn freeze then switching
>> from console mode to graphic (when xdm start), and same hang when
>> doing graphic stuff like dvd play, or using xv or qiv.
>>
>> Yesterday I've try to compile xorg 7.5 and xfce4. Same symptom.
>>
>> The only workaround I've found is to disable acpi
>> 'hint.acpi.0.disabled="1" in /boot/loader.conf
>> And even with that, I've a corrupted screen.
>>
>> Vesa is not an option, because it can not recognize my 1920x1200 screen.
>>
>> Is there any chance that the 2.9 intel driver behave better ?
>
> It is very unlikely... The 2.9 series driver will not support drm
> without GEM and so it is really slow.  The only reason to try and use it
> that I can think of is if you have an Ironlake chipset with isn't
> supported in the 2.7 driver.
>
> I have an Atom 330 with the 945 chipset and I haven't had any issues
> with it.  It is possible that it is waiting for resources.  How much ram
> do you have?

dmesg | grep -i memory
real memory = 2147483648 (2048 MB)
avail memory = 2082623488 (1986 MB)
agp0: detected 7932k stolen memory

What kind of ressources ?

I have try to add comment to a bug here :
http://bugs.freedesktop.org/show_bug.cgi?id=24789#c22 but I have no
working options so far. I'm not even sure that this is the correct bug
id

It's a shame to have to disable multhreading on an dual thread atom :-)

HPC

--
HPC http://ticetmensonges.blog.free.fr
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Torfinn Ingolfsen on
On Sun, Mar 14, 2010 at 9:43 PM, Garrett Cooper <yanefbsd(a)gmail.com> wrote:

> Could you compile xfce4-session with -g and attach gdb to it as
> it's starting up to get a backtrace please?


So I am guessing that running gdb on the core file I already have (from
xfce4-session) isn't of any use?
I'll have to figure out how to compil with -g and how to "attach gdb" then.


> You may have to compile a
> few other XFCE4 pieces with -g in order to get things up and going,
> but first things first...
>

Yes, I'll cross that bridge when I have to.

--
Regards,
Torfinn Ingolfsen
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Robert Noland on
On Mon, 2010-03-15 at 22:40 +0100, Torfinn Ingolfsen wrote:
> On Sun, Mar 14, 2010 at 9:43 PM, Garrett Cooper <yanefbsd(a)gmail.com> wrote:
>
> > Could you compile xfce4-session with -g and attach gdb to it as
> > it's starting up to get a backtrace please?
>
>
> So I am guessing that running gdb on the core file I already have (from
> xfce4-session) isn't of any use?
> I'll have to figure out how to compil with -g and how to "attach gdb" then.

"make -DWITH_DEBUG all deinstall reinstall"

works in most cases. If your existing core doesn't have symbols, then
no it won't offer much insight.

robert.

> > You may have to compile a
> > few other XFCE4 pieces with -g in order to get things up and going,
> > but first things first...
> >
>
> Yes, I'll cross that bridge when I have to.

--
Robert Noland <rnoland(a)FreeBSD.org>
FreeBSD

_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"

From: Torfinn Ingolfsen on
Update:

On Mon, Mar 15, 2010 at 11:02 PM, Robert Noland <rnoland(a)freebsd.org> wrote:

> On Mon, 2010-03-15 at 22:40 +0100, Torfinn Ingolfsen wrote:
> > On Sun, Mar 14, 2010 at 9:43 PM, Garrett Cooper <yanefbsd(a)gmail.com>
> wrote:
> >
> > > Could you compile xfce4-session with -g and attach gdb to it as
> > > it's starting up to get a backtrace please?
> >
> >
> > So I am guessing that running gdb on the core file I already have (from
> > xfce4-session) isn't of any use?
> > I'll have to figure out how to compil with -g and how to "attach gdb"
> then.
>
> "make -DWITH_DEBUG all deinstall reinstall"
>

Ok, I finally found time to try this. After recompiling xfce4-session as
stated above, I did a 'startxfce4' as root. After that I did 'gdb
xfce4-session xfce4-session.core'
Correct so far?
On loading gdb prints:
Core was generated by `xfce4-session'.
Program terminated with signal 6, Aborted.

then proceeds and load symbols.
I then try a backtrace:
(gdb) bt
#0 0x0000000804bbf91c in kill () from /lib/libc.so.7
#1 0x0000000804bbe71b in abort () from /lib/libc.so.7
#2 0x0000000804171c75 in dbus_malloc () from /usr/local/lib/libdbus-1.so.3
#3 0x000000080416df55 in dbus_watch_handle () from
/usr/local/lib/libdbus-1.so.3
#4 0x0000000804163046 in dbus_message_new_signal () from
/usr/local/lib/libdbus-1.so.3
#5 0x00000008040271e9 in dbus_g_connection_register_g_object () from
/usr/local/lib/libdbus-glib-1.so.2
#6 0x00000008042909ef in g_closure_invoke () from
/usr/local/lib/libgobject-2.0.so.0
#7 0x00000008042a4547 in g_signal_parse_name () from
/usr/local/lib/libgobject-2.0.so.0
#8 0x00000008042a5f96 in g_signal_emit_valist () from
/usr/local/lib/libgobject-2.0.so.0
#9 0x00000008042a6353 in g_signal_emit () from
/usr/local/lib/libgobject-2.0.so.0
#10 0x000000000040f664 in xfsm_client_set_state (client=0x804e56400,
state=XFSM_CLIENT_SAVINGLOCAL) at xfsm-client.c:344
#11 0x0000000000414c35 in xfsm_manager_register_client (manager=0x804e1e810,
client=0x804e56400, previous_id=0x0) at xfsm-manager.c:909
#12 0x000000000040da34 in sm_register_client (sms_conn=0x804e39300,
client_data=0x804e56400, previous_id=0x0) at sm-layer.c:210
#13 0x0000000800f25abe in _SmsProcessMessage () from
/usr/local/lib/libSM.so.6
#14 0x0000000801039cd0 in IceProcessMessages () from
/usr/local/lib/libICE.so.6
#15 0x000000000040aeb2 in ice_process_messages (channel=0x804e8c100,
condition=G_IO_IN, user_data=0x804e72f80) at ice-layer.c:111
#16 0x00000008043fe692 in g_main_context_dispatch () from
/usr/local/lib/libglib-2.0.so.0
#17 0x0000000804401a2e in g_main_context_check () from
/usr/local/lib/libglib-2.0.so.0
#18 0x0000000804401d19 in g_main_loop_run () from
/usr/local/lib/libglib-2.0.so.0
#19 0x0000000801384743 in gtk_main () from
/usr/local/lib/libgtk-x11-2.0.so.0
#20 0x000000000040bbea in main (argc=1, argv=0x7fffffffea08) at main.c:299
(gdb)

What next?


>
> works in most cases. If your existing core doesn't have symbols, then
> no it won't offer much insight.
>

Noted.


--
Regards,
Torfinn Ingolfsen
_______________________________________________
freebsd-ports(a)freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe(a)freebsd.org"