Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 25 Jan 2009 23:45:12 +0300
From:      Subscriber <subscr1024@mail.ru>
To:        Kostik Belousov <kostikbel@gmail.com>
Cc:        freebsd-amd64@freebsd.org
Subject:   Re: WINE in jail [Was: i386_set_ldt and wine on AMD64]
Message-ID:  <497CCF58.4000204@mail.ru>
In-Reply-To: <20090124132823.GA6834@deviant.kiev.zoral.com.ua>
References:  <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com> <20061231003901.GA76688@slackbox.xs4all.nl> <ghtjp9$3j0$1@ger.gmane.org> <20081212130631.GC2038@deviant.kiev.zoral.com.ua> <49427649.20006@lapo.it> <20081212145015.GE2038@deviant.kiev.zoral.com.ua> <4979D9F5.6020105@mail.ru> <20090124132823.GA6834@deviant.kiev.zoral.com.ua>

next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Kostik.

Kostik Belousov =EF=E8=F8=E5=F2:
> What is "8C" system ? Eight-core ?

No, 8-CURRENT. :) My system is Turion TL-64 based notebook, 2 cores, 4G o=
f RAM.

> First, what was the version of the patch ? All publically released
> patches are no longer applicable to the HEAD. The latest version is
> at
> http://people.freebsd.org/~kib/misc/amd64_ctx.3.patch

Thanks. Now I start compilation of new kernel, will test it right now.

> Did you tried to run wine/i386 on the box ?

No. My notebook used for working, and unstable xorg is critical issue for=
 me.=20
Thus I rolled back to old kernel and wrote question to this list.

> To debug the issue with Xorg, I need to look at the instruction where
> the code faults. Specifically, please enable coredump from Xorg, load
> coredump in gdb (like gdb Xorg Xorg.core) and then
> 	info registers
> <look for rip value in the output>
> 	disassemble <%rip value> <%rip value>+0x10

Ok. I'll do it, if xorg will crashed again. But now new xorg 7.4 came to =
the=20
ports, so I'll delay my answer for 2 or 3 days.

> Thanks for testing.

It is in my favor too. :)




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