Bug 11453

Thanks for the bisect, but Xorg.0.log is required on basically all driver bugs.

Created attachment 10570 [details]
xorg.0.log

It's attached. Note that I'm not 100% sure that it's the log of a faulty driver, I can provide one if you need.

Cheers,

I am experiencing this issue as well. I am running Ubuntu 7.10 beta AMD64 (upgraded 9 October 2007) with the Intel 82Q35 chipset (Intel GMA 3100 graphics).

I have a dual-head setup with a 1920x1200 monitor and a 1600x1200 monitor side by side. I configure dual-head with xrandr:
`xrandr --output TMDS-1 --auto --pos 0x0 --left-of VGA`

driverBug1.jpg and driverBug2.jpg images show two sections of a line of pixels that are copied onto each other.

I can't get a screenshot of the garbled scrolling behavior because the window refreshes when I take the screenshot.

Software versions:
Xorg (xserver-xorg) v7.2-5ubuntu13
Xorg Server (xserver-xorg-core) v1.3.0.0.dfsg-12ubuntu8
Intel Driver (xserver-xorg-video-intel) v2.1.1-0ubuntu6

Attachments:
Xorg.0.log
xorg.conf
driverBug1.jpg
driverBug2.jpg

Created attachment 11973 [details]
xorg.0.log

Created attachment 11974 [details]
xorg.conf

Created attachment 11975 [details]
shows right line copied to left line on desktop

Created attachment 11976 [details]
shows left line copied to right line on desktop

CC Hong to see if he has work bandwidth for this.

This is now working for me by updating to the version in Ubuntu 7.10.

I suggest marking this as "FIXED".

Then I'm closing this. Thanks.

I cannot say if this bug is fixed or not, in the last Debian package (2.1.1 driver) it completely fail, and leaves the video card in an inconstant state when I set up my virtual screen to be more than 1280 pixels wide.

Not only I don't believe the issue is fixed, but it has even become worse.

Please attach the Xorg.log with "Modedebug" turned on in your xorg.conf device section.

Thanks,
Hong

Pierre, if you are seeing a different issue than the original report, I'd suggest to file a new bug report and mark this one "depends on" the new one.

It will be good if you could try the current git tip or the 2.2 stable release.

(In reply to comment #13)
> Pierre, if you are seeing a different issue than the original report, I'd
> suggest to file a new bug report and mark this one "depends on" the new one.
> 
> It will be good if you could try the current git tip or the 2.2 stable release.
> 

Debian has 2.2 for 2 days now, I just tried, I now have an error message in the Xorg.log but when it comes to that, the video card is left in an incoherent state and I can only reboot. At least the vts work which wasn't teh case with 2.1.1.

The end of the Xorg.log is:

===========================================================================
(II) intel(0): Kernel reported 238592 total, 1 used
(II) intel(0): I830CheckAvailableMemory: 954364 kB available
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:02.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
(II) [drm] DRM interface version 1.3
(II) [drm] DRM open master succeeded.
(II) intel(0): [drm] Using the DRM lock SAREA also for drawables.
(II) intel(0): [drm] framebuffer mapped by ddx driver
(II) intel(0): [drm] added 1 reserved context for kernel
(II) intel(0): X context handle = 0x1
(II) intel(0): [drm] installed DRM signal handler
(==) intel(0): VideoRam: 262144 KB
(**) intel(0): Framebuffer compression enabled
(**) intel(0): Tiling enabled
(II) intel(0): Attempting memory allocation with tiled buffers.
(II) intel(0): Success.
(II) intel(0): Increasing the scanline pitch to allow tiling mode (2560 -> 4096).
(EE) intel(0): Cannot support DRI with frame buffer width > 2048.
(II) intel(0): adjusting plane->pipe mappings to allow for framebuffer compression
(II) intel(0): Page Flipping disabled
(==) intel(0): Write-combining range (0xc0000000,0x10000000)
(II) intel(0): vgaHWGetIOBase: hwp->IOBase is 0x03d0, hwp->PIOOffset is 0x0000
(II) EXA(0): Offscreen pixmap area of 39321600 bytes
(II) EXA(0): Driver registered support for the following operations:
(II)         Solid
(II)         Copy
(II)         Composite (RENDER acceleration)
(==) intel(0): Backing store disabled
(==) intel(0): Silken mouse enabled
(II) intel(0): Initializing HW Cursor
(II) intel(0): xf86BindGARTMemory: bind key 0 at 0x007bf000 (pgoffset 1983)
(II) intel(0): xf86BindGARTMemory: bind key 1 at 0x02e40000 (pgoffset 11840)
(II) intel(0): Fixed memory allocation layout:
(II) intel(0): 0x00000000-0x0001ffff: ring buffer (128 kB)
(II) intel(0): 0x00020000-0x0061ffff: compressed frame buffer (6144 kB, 0x000000003f820000 physical
)
(II) intel(0): 0x00620000-0x00620fff: compressed ll buffer (4 kB, 0x000000003fe20000 physical
)
(II) intel(0): 0x00621000-0x0062afff: HW cursors (40 kB, 0x000000003fe21000 physical
)
(II) intel(0): 0x0062b000-0x00632fff: logical 3D context (32 kB)
(II) intel(0): 0x00633000-0x00633fff: overlay registers (4 kB, 0x000000003fe33000 physical
)
(II) intel(0): 0x00640000-0x02e3ffff: front buffer (40960 kB)
(II) intel(0): 0x007bf000:            end of stolen memory
(II) intel(0): 0x02e40000-0x053bffff: exa offscreen (38400 kB)
(II) intel(0): 0x10000000:            end of aperture
(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
(WW) intel(0): PRB0_HEAD (0x0200986c) and PRB0_TAIL (0x00009998) indicate ring buffer not flushed
(WW) intel(0): Existing errors found in hardware state.
Error in I830WaitLpRing(), timeout for 2 seconds
pgetbl_ctl: 0x3ffc0001 pgetbl_err: 0x0
ipeir: 0 iphdr: 7d8e0001
LP ring tail: 99a0 head: 986c len: 1f001 start 0
eir: 0 esr: 0 emr: ffff
instdone: 4081 instpm: 0
memmode: 306 instps: 800f00c4
hwstam: ffff ier: 0 imr: ffff iir: 0
Ring at virtual 0x5f798000 head 0x986c tail 0x99a0 count 77
	000097ec: 00000000
	000097f0: 00000720
	000097f4: 00000000
	000097f8: 00000720
	000097fc: 00000000
	00009800: 00000720
	00009804: 00000000
	00009808: 00000720
	0000980c: 00000000
	00009810: 00000720
	00009814: 00000000
	00009818: 00000720
	0000981c: 00000000
	00009820: 00000720
	00009824: 00000000
	00009828: 00000720
	0000982c: 00000000
	00009830: 00000720
	00009834: 00000000
	00009838: 00000720
	0000983c: 00000000
	00009840: 00000720
	00009844: 00000000
	00009848: 00000720
	0000984c: 00000000
	00009850: 00000720
	00009854: 00000000
	00009858: 00000720
	0000985c: 00000000
	00009860: 00000720
	00009864: 00000000
	00009868: 00000720
	0000986c: 00000000
Ring end
space: 130756 wanted 131064

Fatal server error:
lockup

===========================================================================

and I was just asking for a Virtual screen (In the Section "SCreen", Subsection "DIsplay" of my xorg.conf) of size 2560 x 1024 to be able to have my 1280x800 laptop LCD displayed next to my other 1280x1024 external monitor, and not below like I do right now because of the original bug.

and yes, maybe I should open a new bug, feel free to clone it as you wish, the point is, I'm totally unable to test if the original one is fixed or not because of that.

Several other people reported the same failure to start X with Intel 2.2 and Virtual screen exceeding 2048, for instance on http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=451570

Not having DRI because of >2048 was ok for them earlier. Not getting any 2D acceleration is much more annoying now (option NoAccel works around the problem).

Brice/Pierre, please file a new bug report for the new issue in 2.2. We'll treat that as high priority bug to fix, and don't want to mess with this one.

Lockup reported in #13376.