On Sun, 2011-11-27 at 21:11 -0500, Brenda J. Butler wrote:
YES!!! Thank you! (from my graphical desktop on my dom0).
Great!
Let me know if there are any other things you'd like me to try.
I think this is actually a kernel rather than hypervisor issue. Can you
confirm which version of the
YES!!! Thank you! (from my graphical desktop on my dom0).
Let me know if there are any other things you'd like me to try.
bjb
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
On Fri, 2011-11-25 at 21:22 -0500, Brenda J. Butler wrote:
But we see this message in kern.log:
Xorg:2967 map pfn expected mapping type write-back for
d000-e000, got write-combining
This comes from reserve_pfn_range in arch/x86/mm/pat.c.
Does nopat on your kernel command line
The function that returns ENOMEM is actually copy_mm. It returns
ENOMEM when dup_mm returns 0.
copy_mm receives clone_flags and task_struct * tsk. I think tsk
is pointing to the new task (the process being forked).
copy_mm assigns some values into *tsk, then:
tsk-mm = NULL;
On Fri, Nov 25, 2011 at 09:03:03PM -0500, Brenda J. Butler wrote:
If clone_flags does not include CLONE_VM, we try to set
mm = dup_mm(tsk)
which presumably means we are trying to duplicate the
-mm of the task being created?!? and if that fails (0 return)
then we return with -ENOMEM.
The thing that returns ENOMEM in fork.c when this failure occurs is:
dup_mm
I still have to see why.
To try distinguishing between the ENOMEM returns, I tried adding
a flag to the return value (eg:
retval = -(ENOMEM | 0x8000)
retval = -(ENOMEM | 0x4000)
retval = -(ENOMEM | 0x2000)
etc
One more clue:
in kern.log, when xserver is running under hypervisor, this appears:
Nov 21 22:05:13 blueeyes kernel: [ 45.899070] Xorg:2949 map pfn expected
mapping type writ
e-back for d000-e000, got write-combining
Nov 21 22:05:13 blueeyes kernel: [ 46.067758] Xorg:2949 freeing
On Thu, Nov 10, 2011 at 09:30:58AM -0500, Brenda J. Butler wrote:
Please let me know if there is any other info you need. I'm not
sure what to do next.
I've gotten the source for the kernel I'm using, and put a bunch
of debug statements in the kernel/fork.c:do_fork routine (to
distinguish
On Sat, Nov 05, 2011 at 12:35:32PM +0100, Julien Cristau wrote:
apt is being stupid and trying to satisfy build-deps for the backports
xorg-server. Try apt-get build-dep xorg-server=2:1.7.7-13.
Thank you! I also had to apt-get source xorg-server=2:1.7.7-13,
as I had gotten the source package
On Fri, Nov 4, 2011 at 21:58:39 -0400, Brenda J. Butler wrote:
On Sat, Nov 05, 2011 at 01:11:36AM +0100, Julien Cristau wrote:
On Fri, Nov 4, 2011 at 19:39:32 -0400, Brenda J. Butler wrote:
I can't help thinking I started out wrong, to be having all these problems
building a stock
Coming back to this - I see that the command line will be printed out
if a debug flag is set - how do I set it?
in ddxList.c on lines 206-207:
if (xkbDebugFlags)
DebugF([xkb] xkbList executes: %s\n,buf);
How can I set xbkDebugFlags? I'd like to try the exact invocation
at
On Fri, Nov 4, 2011 at 13:41:02 -0400, Brenda J. Butler wrote:
Coming back to this - I see that the command line will be printed out
if a debug flag is set - how do I set it?
in ddxList.c on lines 206-207:
if (xkbDebugFlags)
DebugF([xkb] xkbList executes:
On Fri, Nov 04, 2011 at 10:00:33PM +0100, Julien Cristau wrote:
On Fri, Nov 4, 2011 at 13:41:02 -0400, Brenda J. Butler wrote:
Coming back to this - I see that the command line will be printed out
if a debug flag is set - how do I set it?
in ddxList.c on lines 206-207:
Cannot build: I probably did something wrong, but what?
did apt-get build-dep xserver-xorg
then tried fakeroot debian/rules binary and had to install
quilt and xutils-dev separately because they didn't get
installed with build-dep, then this:
On Fri, Nov 04, 2011 at 06:19:53PM -0400, Brenda J. Butler wrote:
Cannot build: I probably did something wrong, but what?
I had to install libtool:
sudo apt-get install libtool libtool-doc
Found the solution in ubuntu forums, now it's in debian bug tracker
too : - )
On to the next hurdle:
On to the next hurdle: installing libudev-dev, because it didn't
get installed with build-dep either.
Installing libudev-dev, as well as x11proto-gl-dev was no problem.
Then it wanted me to install x11proto-xf86dri-dev, which I did,
but the subsequent build attempt gave this error:
On Fri, Nov 4, 2011 at 19:39:32 -0400, Brenda J. Butler wrote:
On to the next hurdle: installing libudev-dev, because it didn't
get installed with build-dep either.
Installing libudev-dev, as well as x11proto-gl-dev was no problem.
Then it wanted me to install x11proto-xf86dri-dev,
On Sat, Nov 05, 2011 at 01:11:36AM +0100, Julien Cristau wrote:
On Fri, Nov 4, 2011 at 19:39:32 -0400, Brenda J. Butler wrote:
I can't help thinking I started out wrong, to be having all these problems
building a stock debian package on a debian stable system.
It doesn't sound like
On Fri, Oct 28, 2011 at 22:35:20 -0400, Brenda J. Butler wrote:
Package: xinit
Version: 1.2.0-2
Severity: important
File: /usr/bin/xinit
using 2.6.32-5-xen-amd64 I can run an X server, but using
2.6.32-5-xen-amd64 (the same) under the Xen 4.0 hypervisor, I cannot.
The Xorg.log file
On Sat, Oct 29, 2011 at 12:02:43PM +0200, Julien Cristau wrote:
On Fri, Oct 28, 2011 at 22:35:20 -0400, Brenda J. Butler wrote:
Package: xinit
Version: 1.2.0-2
Severity: important
File: /usr/bin/xinit
using 2.6.32-5-xen-amd64 I can run an X server, but using
On Sat, Oct 29, 2011 at 09:57:23 -0400, Brenda J. Butler wrote:
I don't have any .xkb or .xkm files on my system (the xkbcomp man
page says it uses and produces files of those names) although I
do have a directory /usr/share/X11/xkb.
The .xkm files are created by xkbcomp in /tmp or
21 matches
Mail list logo
