On Tue, 20 Feb 2007, Matthew Wakeling wrote:
Well, all the interesting stuff is in libint10, so I'll probably limit myself
to recompiling that.
Okay, done. Most of the time, I get:
#0 0x2b0911cbffcd in X86EMU_exec () at
../../../../hw/xfree86/int10/../x86emu/decode.c:121
#1
On Tue, 20 Feb 2007, Brice Goglin wrote:
You will have to use a server recompiled with debugging symbols to get
line numbers.
Well, all the interesting stuff is in libint10, so I'll probably limit
myself to recompiling that.
If you do 'c' for continue, wait a little bit, hit ctrl-c and
Matthew Wakeling wrote:
When it fails, the X process is busy-looping, using 99% of CPU.
Killing it fails, but kill -9 succeeds. Trying to run X again crashes
the whole system, so I need to reboot after each attempt in order to
get my working X back.
Once the X server is stuck using 99% of
On Tue, 20 Feb 2007, Brice Goglin wrote:
Once the X server is stuck using 99% of CPU, could you try attaching a
GDB with something like:
*gdb* -p $(*pidof* *X*)
(as root). I should help us have an idea what's going on.
I have gdb connected now. I'm afraid my experience with gdb is rather
Matthew Wakeling wrote:
On Tue, 20 Feb 2007, Brice Goglin wrote:
Once the X server is stuck using 99% of CPU, could you try attaching a
GDB with something like:
*gdb* -p $(*pidof* *X*)
(as root). I should help us have an idea what's going on.
I have gdb connected now. I'm afraid my
Update:
I inserted a log statement before hw/xfree86/x86emu/decode.c:122 to just
print on the stderr that it was emulating an instruction at a certain
address. The result of running that was that I got a 500MB log file in
seconds, with it executing instructions all over the BIOS. I had 12
Matthew Wakeling wrote:
Hi all. Julien asked me to check if the bug still exhibits if I use
the open-source nvidia drivers instead of the closed-source drivers.
The answer is yes, it does. Exactly the same thing happens. I have
attached my config and log files.
Seeing this failure while
7 matches
Mail list logo
