Debian Bug report logs - #404885
lockup and illegal extended x86 opcode

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Robert de Bath <robert$@debath.co.uk>

To: bugs@debian.org

Subject: xserver-xorg-video-vesa VERY SLOW

Date: Thu, 28 Dec 2006 21:48:51 +0000 (GMT)

[Message part 1 (text/plain, inline)]

Package: xserver-xorg-video-vesa
Version: 1:1.3.0-1

Linux version 2.6.14-2-686 (Debian 2.6.14-6bpo1) (nobse@debian.org) (gcc 
version 3.3.5 (Debian 1:3.3.5-13)) #2 Fri Dec 30 03:19:34 CET 2005

For normal use with the shadowFB in use the 'feel' of the speed of the 
display is ok. The problem occurs when playing video using mplayer.

For a small video the CPU usage with vesa is around six times the cpu 
that's used by the xserver-xorg-video-fbdev video driver.

From the log file it appears that the X vesa driver is NOT using a linear
frame buffer for some reason, as the fbdev driver only works for a linear
frame buffer this seems a little weird.

$ sudo fbset -i

mode "1024x768-76"
    # D: 78.653 MHz, H: 59.949 kHz, V: 75.694 Hz
    geometry 1024 768 1024 768 32
    timings 12714 128 32 16 4 128 4
    rgba 8/16,8/8,8/0,0/0
endmode

Frame buffer device information:
    Name        : VESA VGA
    Address     : 0xf0000000
    Size        : 6291456
    Type        : PACKED PIXELS
    Visual      : TRUECOLOR
    XPanStep    : 0
    YPanStep    : 0
    YWrapStep   : 0
    LineLength  : 4096
    Accelerator : No
$

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                             <http://www.debath.co.uk/>

[xorg.conf (text/plain, attachment)]

[Xorg.1.log (text/plain, attachment)]

Message #10 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Brice Goglin <Brice.Goglin@ens-lyon.org>

To: Robert de Bath <robert$@debath.co.uk>

Cc: 404885@bugs.debian.org

Subject: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Sun, 29 Apr 2007 23:15:00 +0200

Hi Robert,

A couple months ago, you reported a bug to the Debian BTS regarding the
X server being very slow with the vesa driver. Does this problem still
happen today? There has not been many changes upstream in the vesa
driver, but the X server core changed at lot. Could you try with
xserver-xorg-core 1.3 currently in unstable (and possibly a recent
kernel too)?

Thanks,
Brice

Message #15 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Robert de Bath <robert$@debath.co.uk>

To: Brice Goglin <Brice.Goglin@ens-lyon.org>

Cc: 404885@bugs.debian.org

Subject: Re: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Mon, 30 Apr 2007 20:12:51 +0100 (BST)

On Sun, 29 Apr 2007, Brice Goglin wrote:

> Hi Robert,
>
> A couple months ago, you reported a bug to the Debian BTS regarding the
> X server being very slow with the vesa driver. Does this problem still
> happen today? There has not been many changes upstream in the vesa

For stable and testing ...
xserver-xorg: 1:7.1.0-18
xserver-xorg-video-vesa: 1:1.3.0-1
Kernel: Linux version 2.6.18-4-686 (Debian 2.6.18.dfsg.1-12) (waldi@debian.org) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Mon Mar 26 17:17:36 UTC 2007

--> xorg
" (II) VESA(0): VESA VBE OEM Vendor: TRIDENT MICROSYSTEMS INC.
" (II) VESA(0): VESA VBE OEM Product: CYBER 2100
" (II) VESA(0): VESA VBE OEM Product Rev: RXT  7.3 (16.28)
" (II) VESA(0): virtual address = 0xb7b3b000,
"         physical address = 0xa0000, size = 65536
" (==) VESA(0): Default visual is TrueColor
" (==) VESA(0): Backing store disabled

--> mplayer
" VO: [x11] 480x352 => 480x352 Planar YV12  [zoom]
" SwScaler: using unscaled yuv420p -> rgb32 special converter

--> top
"   PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
"  3095 root       5 -10 30044  22m 6064 S 46.9  4.4   1:13.40 Xorg
"  4166 robert    15   0 50444  22m  15m S  2.7  4.4   0:05.50 mplayer

The problem still exists in "testing".

For unstable ...

" The following packages will be REMOVED
"   tzdata util-linux util-linux-locales
" The following packages will be upgraded:
"   libc6 libc6-dev libdrm-dev libdrm2 locales xserver-xorg xserver-xorg-core
" WARNING: The following essential packages will be removed.
" This should NOT be done unless you know exactly what you are doing!
"   util-linux tzdata (due to util-linux)

so I really don't want to try to upgrade to unstable right now :-)

Still I _think_ the problem is in the vesa driver itself which is the
same version across all of stable, testing and unstable.

However, I will try again next week.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                             <http://www.debath.co.uk/>

Message #20 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Robert de Bath <robert$@debath.co.uk>

To: Brice Goglin <Brice.Goglin@ens-lyon.org>

Cc: 404885@bugs.debian.org

Subject: Re: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Fri, 4 May 2007 19:27:03 +0100 (BST)

[Message part 1 (text/plain, inline)]

On Sun, 29 Apr 2007, Brice Goglin wrote:

> Hi Robert,
>
> A couple months ago, you reported a bug to the Debian BTS regarding the
> X server being very slow with the vesa driver. Does this problem still
> happen today? There has not been many changes upstream in the vesa
> driver, but the X server core changed at lot. Could you try with
> xserver-xorg-core 1.3 currently in unstable (and possibly a recent
> kernel too)?

Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
with 100% cpu. The process can be kill -9'd and the attached log is what
remains. In addition after resetting the console I can see the messages:

" f000:5054: 01 ILLEGAL EXTENDED X86 OPCODE!
" XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
" after 0 requests (0 known processed) with 0 events remaining.


-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                             <http://www.debath.co.uk/>

[Xorg.0.log (text/plain, attachment)]

Message #25 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Brice Goglin <Brice.Goglin@ens-lyon.org>

To: Robert de Bath <"robert$"@debath.co.uk>, 404885@bugs.debian.org

Subject: Re: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Fri, 04 May 2007 21:42:24 +0200

Robert de Bath wrote:
> On Sun, 29 Apr 2007, Brice Goglin wrote:
>
>> Hi Robert,
>>
>> A couple months ago, you reported a bug to the Debian BTS regarding the
>> X server being very slow with the vesa driver. Does this problem still
>> happen today? There has not been many changes upstream in the vesa
>> driver, but the X server core changed at lot. Could you try with
>> xserver-xorg-core 1.3 currently in unstable (and possibly a recent
>> kernel too)?
>
> Well, looks like I was wrong, the current unstable (1:7.2-3) locks up

xserver-xorg does not matter actually, this package is basically empty.
xserver-xorg-core is the important one, and you have 1.3.0.0 from what I
see in the log.

> with 100% cpu. The process can be kill -9'd and the attached log is what
> remains. In addition after resetting the console I can see the messages:
>
> " f000:5054: 01 ILLEGAL EXTENDED X86 OPCODE!

Looks like a problem in x86emu. I am not familiar with this at all.
Maybe somebody else will have an idea.

Brice

Message #36 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: Robert de Bath <robert$@debath.co.uk>, 404885@bugs.debian.org

Subject: Re: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Wed, 25 Jul 2007 00:52:23 +0200

On Fri, May  4, 2007 at 19:27:03 +0100, Robert de Bath wrote:

> Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
> with 100% cpu. The process can be kill -9'd and the attached log is what
> remains. In addition after resetting the console I can see the messages:
>
> " f000:5054: 01 ILLEGAL EXTENDED X86 OPCODE!
> " XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
> " after 0 requests (0 known processed) with 0 events remaining.
>
This is either a bug in the x86 emulator included in the X server, or a
bug in your vbios.  In either case, it'd probably work if you didn't use
the vesa driver.  Is there any particular reason you use it instead of
an appropriate driver for your video card?

Cheers,
Julien

Message #41 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Robert de Bath <robert$@debath.co.uk>

To: Julien Cristau <jcristau@debian.org>

Cc: 404885@bugs.debian.org

Subject: Re: Bug#404885: xserver-xorg-video-vesa VERY SLOW

Date: Fri, 27 Jul 2007 09:41:39 +0100 (BST)

On Wed, 25 Jul 2007, Julien Cristau wrote:

> On Fri, May  4, 2007 at 19:27:03 +0100, Robert de Bath wrote:
>
>> Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
>> with 100% cpu. The process can be kill -9'd and the attached log is what
>> remains. In addition after resetting the console I can see the messages:
>>
>> " f000:5054: 01 ILLEGAL EXTENDED X86 OPCODE!
>> " XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
>> " after 0 requests (0 known processed) with 0 events remaining.
>>
> This is either a bug in the x86 emulator included in the X server, or a
> bug in your vbios.  In either case, it'd probably work if you didn't use
> the vesa driver.  Is there any particular reason you use it instead of
> an appropriate driver for your video card?

To some extent you're right, the kernel frame buffer works, the svgalib
driver (chipset VESA) works and debian stable xserver-xorg-video-vesa
driver works. The current card specific driver also works (and it uses
vesa) but bugs 402673 and 407620 make it a pain to use, especially as
402673 understates the problem somewhat. All those except the older
xserver work in linear mode.

One thing I've noticed in the log is this:

...
*Mode: 118 (1024x768)
   ModeAttributes: 0x9b
   WinAAttributes: 0x7
   WinBAttributes: 0x0
   WinGranularity: 64
...
   DirectColorModeInfo: 0
   PhysBasePtr: 0x0
Mode: 117 (1024x768)
...

What does the X server do when that PhysBasePtr is zero ? Why is it zero
and not 0xf0000000 ? Google seems to say that you need to ask for the
linear mode to get the specs for it but the int(10,4f01) table looks like
it doesn't need to change. The kernel seems to do it that way, it looks
like X asks for the specs to paged mode, but it's very confused, does it?

This is what vesafb says ...

vesafb: framebuffer at 0xf0000000, mapped to 0xe0880000, using 6144k, total 32768k
vesafb: mode is 1024x768x32, linelength=4096, pages=9
vesafb: protected mode interface info at c000:85ba
vesafb: pmi: set display start = c00c85e9, set palette = c00c8652
vesafb: scrolling: redraw
vesafb: Truecolor: size=0:8:8:8, shift=0:16:8:0
fb0: VESA VGA frame buffer device

I am reminded about how these BIOSs have probably been tested, and with
which (single) driver, that driver just tries the mode and if the user
doesn't respond in a few seconds switches back to one that was working.
So shouldn't the vesa driver use the same sequence of calls it does, with
the mode sniffing of course but also an "I don't care what you smell,
just jump" option too.

So how easy would a 'paranoid but under orders mode' be :-)

Anyway in the short term that machine is back on stable using the slow
X vesa driver and "mplayer -vo svga" for fullscreen video.

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                             <http://www.debath.co.uk/>

Message #46 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Robert de Bath <robert$@debath.co.uk>

To: Julien Cristau <jcristau@debian.org>

Cc: 404885@bugs.debian.org

Subject: Re: Bug#404885: FOUND IT

Date: Sat, 28 Jul 2007 20:24:16 +0100 (BST)

It's in hw/xfree86/int10/xf86int10.c
Function
int1A_handler(xf86Int10InfoPtr pInt)

For AX values 0xb108, 0xb109, 0xb10a, 0xb10b, 0xb10c and 0xb10d

The entire contents of edi is used as a pci register number, only DI 
should be used.

For this specific bios

< X86_ECX = pciReadLong(tag, X86_EDI);
--
> X86_ECX = pciReadLong(tag, X86_DI);

in case 0xb10a: fixes my problem.

Now I have a driver that's both stable and not too slow. :-)

-- 
Rob.                          (Robert de Bath <robert$ @ debath.co.uk>)
                                             <http://www.debath.co.uk/>

On Wed, 25 Jul 2007, Julien Cristau wrote:

> On Fri, May  4, 2007 at 19:27:03 +0100, Robert de Bath wrote:
>
>> Well, looks like I was wrong, the current unstable (1:7.2-3) locks up
>> with 100% cpu. The process can be kill -9'd and the attached log is what
>> remains. In addition after resetting the console I can see the messages:
>>
>> " f000:5054: 01 ILLEGAL EXTENDED X86 OPCODE!
>> " XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
>> " after 0 requests (0 known processed) with 0 events remaining.
>>
> This is either a bug in the x86 emulator included in the X server, or a
> bug in your vbios.  In either case, it'd probably work if you didn't use
> the vesa driver.  Is there any particular reason you use it instead of
> an appropriate driver for your video card?
>
> Cheers,
> Julien
>
>

Message #53 received at 404885@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: control@bugs.debian.org

Cc: 404885@bugs.debian.org

Subject: setting package to xdmx-tools xvfb xnest xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xprint xdmx xprint-common xorg-server xserver-xephyr ...

Date: Tue, 24 Jun 2008 20:40:37 +0200

# Automatically generated email from bts, devscripts version 2.10.30
# via tagpending 
#
# xorg-server (2:1.4.2-1) UNRELEASED; urgency=low
#
#  * Backport patch from upstream git to fix emulation of int1A PCI BIOS
#    services (closes: #404885).  Thanks, Robert de Bath!
#

package xdmx-tools xvfb xnest xserver-xorg-core xserver-xorg-core-dbg xserver-xorg-dev xprint xdmx xprint-common xorg-server xserver-xephyr
tags 404885 + pending

Message #60 received at 404885-close@bugs.debian.org (full text, mbox, reply):

From: Julien Cristau <jcristau@debian.org>

To: 404885-close@bugs.debian.org

Subject: Bug#404885: fixed in xorg-server 2:1.4.2-1

Date: Thu, 26 Jun 2008 01:02:06 +0000

Source: xorg-server
Source-Version: 2:1.4.2-1

We believe that the bug you reported is fixed in the latest version of
xorg-server, which is due to be installed in the Debian FTP archive:

xdmx-tools_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xdmx-tools_1.4.2-1_i386.deb
xdmx_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xdmx_1.4.2-1_i386.deb
xnest_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xnest_1.4.2-1_i386.deb
xorg-server_1.4.2-1.diff.gz
  to pool/main/x/xorg-server/xorg-server_1.4.2-1.diff.gz
xorg-server_1.4.2-1.dsc
  to pool/main/x/xorg-server/xorg-server_1.4.2-1.dsc
xorg-server_1.4.2.orig.tar.gz
  to pool/main/x/xorg-server/xorg-server_1.4.2.orig.tar.gz
xprint-common_1.4.2-1_all.deb
  to pool/main/x/xorg-server/xprint-common_1.4.2-1_all.deb
xprint_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xprint_1.4.2-1_i386.deb
xserver-xephyr_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xserver-xephyr_1.4.2-1_i386.deb
xserver-xorg-core-dbg_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xserver-xorg-core-dbg_1.4.2-1_i386.deb
xserver-xorg-core_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xserver-xorg-core_1.4.2-1_i386.deb
xserver-xorg-dev_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xserver-xorg-dev_1.4.2-1_i386.deb
xvfb_1.4.2-1_i386.deb
  to pool/main/x/xorg-server/xvfb_1.4.2-1_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 404885@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Julien Cristau <jcristau@debian.org> (supplier of updated xorg-server package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Thu, 26 Jun 2008 01:57:18 +0200
Source: xorg-server
Binary: xserver-xorg-core xserver-xorg-dev xdmx xdmx-tools xnest xvfb xserver-xephyr xprint xprint-common xserver-xorg-core-dbg
Architecture: source all i386
Version: 2:1.4.2-1
Distribution: unstable
Urgency: low
Maintainer: Debian X Strike Force <debian-x@lists.debian.org>
Changed-By: Julien Cristau <jcristau@debian.org>
Description: 
 xdmx       - distributed multihead X server
 xdmx-tools - Distributed Multihead X tools
 xnest      - Nested X server
 xprint     - X11 print system (binary)
 xprint-common - Xprint - the X11 print system (configuration files)
 xserver-xephyr - nested X server
 xserver-xorg-core - Xorg X server - core server
 xserver-xorg-core-dbg - Xorg - the X.Org X server (debugging symbols)
 xserver-xorg-dev - Xorg X server - development files
 xvfb       - Virtual Framebuffer 'fake' X server
Closes: 404885 433331 466526 473260 478277 485185
Changes: 
 xorg-server (2:1.4.2-1) unstable; urgency=low
 .
   [ Julien Cristau ]
   * New upstream release.
   * Security fixes from the previous upload are included upstream.
   * Cherry-pick patches from upstream git to make the LeftOf and Above options
     in xorg.conf actually work (closes: #466526).
   * 48_xaa_nooffscreenpixmaps.diff: disable XAA offscreen pixmaps by default;
     they can be enabled with Option "XaaOffscreenPixmaps" (closes: #478277,
     #433331).
   * Cherry-pick various patches from upstream for Xorg's modes code:
     - add quirks for monitors with broken EDID (closes: #473260)
     - fix max clock computation
     - inherit the preferred mode from the global configuration (so if you have
       Modes "800x600" in the Display subsection the server will honor it
       instead of ignoring it)
   * Backport patch from upstream git to fix emulation of int1A PCI BIOS
     services (closes: #404885).  Thanks, Robert de Bath!
 .
   [ Brice Goglin ]
   * Update patches to not require -p0, closes: #485185.
Checksums-Sha1: 
 a4455c8bd943b3da065f1f8a2b0abdb85da32483 2867 xorg-server_1.4.2-1.dsc
 8032716600b649a0c6ca9383af0613614e5cedc2 8246561 xorg-server_1.4.2.orig.tar.gz
 7b3f8a80fd7ae092fb61aabbd5d6fd7188585056 655070 xorg-server_1.4.2-1.diff.gz
 964c772ca33e34fae869eddd5cb0c120970f32c8 644484 xprint-common_1.4.2-1_all.deb
 42ce8beabc601b1aeac54bd3a5a865e1f28aff3b 4113290 xserver-xorg-core_1.4.2-1_i386.deb
 91b6f022c500e40925b6495d186c14c2a99b55c9 692016 xserver-xorg-dev_1.4.2-1_i386.deb
 053ce34870f201366da653b94deb76814b3387c6 1150412 xdmx_1.4.2-1_i386.deb
 f08308082147f09c61e6bb7727539e82716116f0 465694 xdmx-tools_1.4.2-1_i386.deb
 1f7cbb7d6509f4e948b35ddd6c3b1a547a0fcb9b 1774238 xnest_1.4.2-1_i386.deb
 a3eca4e5e3b0946c8b2084a8a8920724b6b28c4b 1889608 xvfb_1.4.2-1_i386.deb
 b5a2eb34a314044faddd4501c00949a3bf0232e9 1926352 xserver-xephyr_1.4.2-1_i386.deb
 bd6ef234fe1580f5175874cd0307d3b300d2399d 1570938 xprint_1.4.2-1_i386.deb
 6568faab838d27b9601cb32f7b3f0ed5f5998425 12559840 xserver-xorg-core-dbg_1.4.2-1_i386.deb
Checksums-Sha256: 
 4c33f7b9c7229ab8e6c0d3d03c446637bcf9c5c2166e6dee093b0ae1bad8f182 2867 xorg-server_1.4.2-1.dsc
 632df2c8d9a4f9fe3183beda736d2381af6feb861d5df077edea94002f96eeec 8246561 xorg-server_1.4.2.orig.tar.gz
 17480a3d80077bd666176dfbdfe3429ce348b0c380ae8e45218f8a1780c287a0 655070 xorg-server_1.4.2-1.diff.gz
 3eae8a4e190b6d596ee0f83fc7c9b20bd04a057aa5fcdc211e9e56c7e272e4c1 644484 xprint-common_1.4.2-1_all.deb
 6ad689c3b54ae228d40ac9289907cd0e94f34d8299a082b05c9c7aa102f0fbf5 4113290 xserver-xorg-core_1.4.2-1_i386.deb
 9ba426c087313d8efabb1dea25c6a18c3bc8f40143492c1abb7c20512b11b321 692016 xserver-xorg-dev_1.4.2-1_i386.deb
 15930012b9e0fb60de7345f7938c287b6cbeae132dc423fb782e30cfcf7621a9 1150412 xdmx_1.4.2-1_i386.deb
 633ca4e69f6302917a00634033c5adbf1deba323a94eb81a3679e41d37fc851b 465694 xdmx-tools_1.4.2-1_i386.deb
 ef5da7fd1ea89673241742b029476b8d801416ec5dbd5d9294241c984e2f6008 1774238 xnest_1.4.2-1_i386.deb
 ff0805823513d2032f137bc77a5a46ea8ebb8f817269e3edd34c93a721958536 1889608 xvfb_1.4.2-1_i386.deb
 458d4ae48d1af8d854ef358abd6425e875e75952de32623bf2fa7cd93d9906ee 1926352 xserver-xephyr_1.4.2-1_i386.deb
 199161220e869611c1d1e218ad602c9b21e5101fb41723261cd6512fb104d6c4 1570938 xprint_1.4.2-1_i386.deb
 3550e5ddf36bf5a6ea1374e75afa6caa2135b0d9b84608351ed051033a038b58 12559840 xserver-xorg-core-dbg_1.4.2-1_i386.deb
Files: 
 f31aafd1b808cf6f84ffd07e7e2bb367 2867 x11 optional xorg-server_1.4.2-1.dsc
 5f2f5e23bac5b8a1dfd9462768618021 8246561 x11 optional xorg-server_1.4.2.orig.tar.gz
 a11731fea0e22e51ea90a87be99e1358 655070 x11 optional xorg-server_1.4.2-1.diff.gz
 b51034865db06c55a8c1dfb952065250 644484 x11 optional xprint-common_1.4.2-1_all.deb
 8ea8e621aed13b790e6966fc67d455b0 4113290 x11 optional xserver-xorg-core_1.4.2-1_i386.deb
 c6c710ddda7984044fa652f309ba29a3 692016 x11 optional xserver-xorg-dev_1.4.2-1_i386.deb
 7f07571ac292503abf77b4b81d97623a 1150412 x11 optional xdmx_1.4.2-1_i386.deb
 d89add36e467568c73d8272442f2bc44 465694 x11 optional xdmx-tools_1.4.2-1_i386.deb
 f85416ad7a4724604852ab6a953737dd 1774238 x11 optional xnest_1.4.2-1_i386.deb
 23c10cceb7cfbbaf6e37f659c7a4cbba 1889608 x11 optional xvfb_1.4.2-1_i386.deb
 874bf75ef03e2eb8920774494436d089 1926352 x11 optional xserver-xephyr_1.4.2-1_i386.deb
 33a26332ef87d8063354b76ed53217cc 1570938 x11 optional xprint_1.4.2-1_i386.deb
 db104157fc5512d04e142981e5886ecc 12559840 x11 extra xserver-xorg-core-dbg_1.4.2-1_i386.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhi44kACgkQmEvTgKxfcAymiACcDXmQR8/LXyeNfplm7FVHivPi
JXwAnRRYB4jgh2NkwHPly+vWqi6LDYKJ
=o+TL
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.