Bug 16837 - E7221 DRI problem
Summary: E7221 DRI problem
Status: RESOLVED DUPLICATE of bug 14395
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Wang Zhenyu
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-24 12:28 UTC by Jay Barrett
Modified: 2008-11-18 21:48 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Xorg.log during server startup (autodetecting and enabling DRI) (28.56 KB, text/plain)
2008-07-24 12:28 UTC, Jay Barrett
no flags Details
Xorg.log file from a server crash during a neverending crash-restart loop (23.76 KB, text/plain)
2008-07-24 12:30 UTC, Jay Barrett
no flags Details

Description Jay Barrett 2008-07-24 12:28:51 UTC
Created attachment 17859 [details]
Xorg.log during server startup (autodetecting and enabling DRI)

Hi, I had a problem with a recent update to the xorg Intel driver.  I restarted my machine (Fedora 9, i386) after a few weeks of uptime and 3-4 sets of yum system updates and after the restart the desktop came up basically in gibberish.  The various windows on the screen were discernable, but the text and icons were tiled repeatedly in random patterns in the windows.  Also, after a few minutes of playing around with the desktop the X server started an unending crash-and-reboot cycle (caused by a "lockup" error).

Not to belabor the details, I backtracked through all of the updates on the system and found that an updated xorg-x11-drv-i810 RPM package had recently been installed.  I also found some evidence in this bug tracker that the driver had been recently changed to add/fix some DRI support to certain Intel cards.  It turns out that this was the problem.

My system has an on-board E7221 video card.  The Xorg.log file (attached) indicates that it autodetects DRI capability and tries to use it on the card - and my guess is that the card has buggy DRI support.  I was able to fix the problem by adding an option line to the Device section of the xorg.conf file like:

Option     "DRI"    "false"

The fact that this was not a problem before and it is a problem now suggests that either the driver was not attempting to use DRI on my card before and the more recent version is, or that DRI used to work and now it doesn't.  I have no way of knowing if the old driver was trying to use DRI since I had to restart the X server so many times that all of the old log files were blown away.

For your information:

> lspci


00:00.0 Host bridge: Intel Corporation E7220/E7221 Memory Controller Hub (rev 04)
00:01.0 PCI bridge: Intel Corporation E7220/E7221 PCI Express Root Port (rev 04)
00:02.0 VGA compatible controller: Intel Corporation E7221 Integrated Graphics Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev d3)
00:1f.0 ISA bridge: Intel Corporation 82801FB/FR (ICH6/ICH6R) LPC Interface Bridge (rev 03)
00:1f.1 IDE interface: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) IDE Controller (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FR/FRW (ICH6R/ICH6RW) SATA Controller (rev 03)
00:1f.3 SMBus: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01)



> lsmod

Module                  Size  Used by
ipt_MASQUERADE          6528  1 
iptable_nat             9224  1 
nf_nat                 18072  2 ipt_MASQUERADE,iptable_nat
bridge                 46104  0 
bnep                   14592  2 
rfcomm                 34576  4 
l2cap                  22272  16 bnep,rfcomm
bluetooth              47588  5 bnep,rfcomm,l2cap
ib_iser                30136  0 
rdma_cm                26112  1 ib_iser
ib_cm                  32080  1 rdma_cm
iw_cm                  10884  1 rdma_cm
ib_sa                  20296  2 rdma_cm,ib_cm
ib_mad                 33432  2 ib_cm,ib_sa
ib_core                43648  6 ib_iser,rdma_cm,ib_cm,iw_cm,ib_sa,ib_mad
ib_addr                 9476  1 rdma_cm
iscsi_tcp              18820  0 
libiscsi               24576  2 ib_iser,iscsi_tcp
scsi_transport_iscsi    28184  4 ib_iser,iscsi_tcp,libiscsi
fuse                   41116  3 
sunrpc                151412  3 
ipt_REJECT              6784  4 
nf_conntrack_ipv4      11396  20 iptable_nat,nf_nat
iptable_filter          6528  1 
ip_tables              13840  2 iptable_nat,iptable_filter
nf_conntrack_netbios_ns     6144  0 
nf_conntrack_ftp       10660  0 
ip6t_REJECT             7552  2 
xt_tcpudp               6656  34 
nf_conntrack_ipv6      15992  16 
xt_state                5888  33 
nf_conntrack           49748  8 ipt_MASQUERADE,iptable_nat,nf_nat,nf_conntrack_ipv4,nf_conntrack_netbios_ns,nf_conntrack_ftp,nf_conntrack_ipv6,xt_state
ip6table_filter         6400  1 
ip6_tables             14736  1 ip6table_filter
x_tables               15236  8 ipt_MASQUERADE,iptable_nat,ipt_REJECT,ip_tables,ip6t_REJECT,xt_tcpudp,xt_state,ip6_tables
ipv6                  221660  34 ip6t_REJECT,nf_conntrack_ipv6
loop                   16772  0 
dm_multipath           18056  0 
ppdev                  10244  0 
dcdbas                 10272  0 
parport_pc             25364  0 
parport                32084  2 ppdev,parport_pc
serio_raw               8708  0 
i2c_i801               11920  0 
pcspkr                  6272  0 
iTCO_wdt               13476  0 
iTCO_vendor_support     6916  1 iTCO_wdt
sg                     31028  0 
i915                   85636  2 
button                 10000  0 
tg3                   103812  0 
drm                   145508  3 i915
sr_mod                 17064  1 
i2c_algo_bit            8964  1 i915
cdrom                  32796  1 sr_mod
i2c_core               20628  4 i2c_i801,i915,drm,i2c_algo_bit
dm_snapshot            18468  0 
dm_zero                 5632  0 
dm_mirror              26116  0 
dm_mod                 48980  9 dm_multipath,dm_snapshot,dm_zero,dm_mirror
pata_acpi               8320  0 
ata_generic             8964  0 
ata_piix               20100  1 
ahci                   26760  2 
libata                127328  4 pata_acpi,ata_generic,ata_piix,ahci
sd_mod                 25624  3 
scsi_mod              120948  8 ib_iser,iscsi_tcp,libiscsi,scsi_transport_iscsi,sg,sr_mod,libata,sd_mod
ext3                  108552  2 
jbd                    40852  1 ext3
mbcache                10116  1 ext3
uhci_hcd               22928  0 
ohci_hcd               22404  0 
ehci_hcd               32268  0 


I've attached the log file from server startup as well.

As stated, I was able to work around this problem, but it should be noted that the driver either has a buggy implementation of DRI support for the E7221 card or it does not support DRI and is erroneously attempting to use it.
Comment 1 Jay Barrett 2008-07-24 12:30:55 UTC
Created attachment 17860 [details]
Xorg.log file from a server crash during a neverending crash-restart loop
Comment 2 Gordon Jin 2008-07-24 23:06:12 UTC
This seems related to http://bugs.freedesktop.org/show_bug.cgi?id=14395.
Comment 3 Jay Barrett 2008-07-25 05:13:34 UTC
(In reply to comment #2)
> This seems related to http://bugs.freedesktop.org/show_bug.cgi?id=14395.
> 

I would agree that it seems related.  This bug is on a similar system to mine (mine is a Dell Poweredge SC420) with the same card.  This is actually one of the bug reports that lead me to believe that changes in the driver related to DRI were in fact causing my problem - I just couldn't find it again when I was created this bug report yesterday.

I still contend that some set of changes to the Intel driver (or in re-reading the reference bug report, the mesa driver) have broken my system which was working in the past (though perhaps without DRI).  And although the work around was as simple as manually disabling DRI, the root cause of the problem should still be noted and hopefully resolved.
Comment 4 Wang Zhenyu 2008-07-27 23:30:43 UTC
What's your mesa version? What application caused the crash you saw? You may disable gdm or kdm and start X by hand, not letting them restart X after crash.
Comment 5 Jay Barrett 2008-07-30 04:56:00 UTC
(In reply to comment #4)
> What's your mesa version? What application caused the crash you saw? You may
> disable gdm or kdm and start X by hand, not letting them restart X after crash.
> 

Mesa version (package): 7.1-0.37.fc9
The crash was caused by gdm - nothing else was open except for maybe a gnome-terminal window.  I tried starting gdm by hand, as well as reverting to xdm - both suffered the same problems.
Comment 6 Wang Zhenyu 2008-08-04 17:57:40 UTC
First just try to run X or xinit from console, ignore gdm. Does that crash for you?
Comment 7 Jeremy Huddleston Sequoia 2008-10-13 15:57:17 UTC
Yeah, I'm betting that this is actually a dupe of bug #14395 ... It was working for you in the past probably because you had DRI disabled.  Try this configuration which is working for my E7221 box:

linux-2.6.25
libdrm-2.3.1
xorg-server-1.4.2
mesa-7.0.4
xf86-video-i810-2.4.2

Note that I actually have mesa-7.0.3 with this patch: http://gitweb.freedesktop.org/?p=mesa/mesa.git;a=commit;h=44f6a6f9c4195727e8819007ac4e3aeac898838a

but that patch is included in 7.0.4
Comment 8 Michael Fu 2008-11-18 21:48:01 UTC

*** This bug has been marked as a duplicate of bug 14395 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.