Bug 12106 - i810 modules cause drm to print *Errors* when X startups
Summary: i810 modules cause drm to print *Errors* when X startups
Status: CLOSED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-08-22 21:41 UTC by kjb
Modified: 2017-07-24 23:11 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description kjb 2007-08-22 21:41:41 UTC
Hello every, it seems some bug in i810 or drm 
kernel modules (linux version 2.6.22.3).
    When X startup, the drm module prints follow message:

8<------------------------------------------------------------
[drm] Initialized i810 1.4.0 20030605 on minor 0
mtrr: base(0xe0000000) is not aligned on a size(0x180000) boundary
[drm] Using v1.4 init.
[drm:drm_release] *ERROR* reclaim_buffers_locked() deadlock. Please rework this
        driver to use reclaim_buffers_idlelocked() instead.
        I will go on reclaiming the buffers anyway.
8<--------------------------------------------------------------
     
       My kernel configuration file is:
CONFIG_AGP=m
CONFIG_AGP_INTEL=m
CONFIG_DRM=m
CONFIG_DRM_I810=m

     My xorg.conf is:
Section "Module"
        Load    "bitmap"
        Load    "dbe"
        Load    "dri"
        Load    "extmod"
        Load    "freetype"
        Load    "glx"
EndSection

Section "Device"
        Identifier      "Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller]"
        Driver          "intel"
        BusID           "PCI:0:1:0"
        VideoRam        16384
EndSection

Section "Monitor"
        Identifier      "LG"
        Option          "DPMS"
        HorizSync       40-70
        VertRefresh     80-90
EndSection

Section "Screen"
        Identifier      "Default Screen"
        Device          "Intel Corporation 82810E DC-133 CGC [Chipset Graphics Controller]"
        Monitor         "LG"
        DefaultDepth    16
                SubSection "Display"
                Depth           16
                Modes           "1024x768"
        EndSubSection
EndSection

Section "DRI"
        Mode    0666
EndSection

      These configurations work fine on linux-2.6.21.
Comment 1 Adam Jackson 2007-08-27 07:35:38 UTC
Not a sitewranglers bug.
Comment 2 Heikki Repo 2010-01-15 16:23:41 UTC
Same problem here, even though the bug seems to be quite old. I'm running a Dell Optiplex GX150 which has Intel 82815 graphics. Gives errors and the 2D acceleration feels slow i.e. screen is updated slowly [Slowness might also have something to do with the screen resolution -- my lcd screen is 1600x1200 in native resolution, and xorg doesn't allow me to start up in smaller resolution -- but might be caused by mtrr problems as well?] I'm running fluxbox.

I have the same kernel options as the first writer but built-in, not as modules.

Here's the lspci output:
00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 
Chipset Graphics Controller (CGC) [8086:1132] (rev 02) (prog-if 00 [VGA 
controller])
	Subsystem: Dell Device [1028:00be]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- 
ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- 
<TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 9
	Region 0: Memory at f8000000 (32-bit, prefetchable) [size=64M]
	Region 1: Memory at ff000000 (32-bit, non-prefetchable) 
[size=512K]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: [dc] Power Management version 2
		Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
		Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

DMESG:
[ 1994.615736] [drm] DMA Cleanup
[ 1994.696757] mtrr: no MTRR for f8000000,3000000 found
[ 2076.292607] mtrr: base(0xf8000000) is not aligned on a size(0x3aa000) 
boundary
[ 2076.595558] [drm] Using v1.4 init.
[ 2079.757013] [drm:drm_reclaim_locked_buffers] *ERROR* 
reclaim_buffers_locked() deadlock. Please rework this
[ 2079.757020] 	driver to use reclaim_buffers_idlelocked() instead.
[ 2079.757024] 	I will go on reclaiming the buffers anyway.

cat /proc/mtrr:
reg00: base=0x000000000 (    0MB), size=  256MB, count=1: write-back
reg01: base=0x00ff00000 (  255MB), size=    1MB, count=1: uncachable
reg02: base=0x00fe80000 (  254MB), size=  512KB, count=1: uncachable
reg03: base=0x0f8000000 ( 3968MB), size=   64MB, count=1: write-combining

Comment 3 Matt Turner 2010-12-02 20:16:21 UTC
Closing due to inactivity. Reopen if this is still a problem. (You probably didn't get any feedback, as you filed the bug in the wrong category.)


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.