[i915] xorg intel driver reports Couldn't find PLL settings

Bug #312133 reported by Andrew Whalan
38
This bug affects 4 people
Affects Status Importance Assigned to Milestone
xf86-video-intel
Fix Released
High
xserver-xorg-video-intel (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: xserver-xorg-video-intel

Release: Ubuntu 8.10
Package: xserver-xorg-video-intel 2:2.4.1-1ubuntu10

I recently installed 8.10 on an ASUS R2H UMPC I bought. It will boot into X with the VESA driver, however, the intel driver fails to start up correctly. The chipset is detected (as shown in attached logs) but X exits with:

Fatal server error:
Couldn't find PLL settings for mode!

The i810 driver doesn't detect the hardware at all. The guides I've read for my PC suggest using it, however after reading some bug reports that mentioned that the use of i810 is no longer supported, i focused my efforts on the intel driver which has gotten the most progress thus far.

I've tried running X from the commandline using "X" and "startx" but neither work.

Output from lspci -v -s 00:02.0:
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
 Subsystem: ASUSTeK Computer Inc. Device 12f7
 Flags: bus master, fast devsel, latency 0, IRQ 16
 Memory at feb80000 (32-bit, non-prefetchable) [size=512K]
 I/O ports at ec00 [size=8]
 Memory at d0000000 (32-bit, prefetchable) [size=256M]
 Memory at feb40000 (32-bit, non-prefetchable) [size=256K]
 Capabilities: [d0] Power Management version 2
 Kernel modules: intelfb

Revision history for this message
Andrew Whalan (skozombie) wrote :
Revision history for this message
Andrew Whalan (skozombie) wrote :
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

Hi skozombie,

Please attach the output of `lspci -vvnn` too.

Changed in xserver-xorg-video-intel:
status: New → Incomplete
Revision history for this message
Andrew Whalan (skozombie) wrote :
Revision history for this message
In , Vzorvat (vzorvat) wrote :
Download full text (42.2 KiB)

after starting x server it fails with error:
"Couldn't find PLL settings for mode!"

here is my Xorg log:
//////////////////////////////////////////////////////////////////////////////
X.Org X Server 1.5.3
Release Date: 5 November 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.28-gentoo i686
Current Operating System: Linux R2H 2.6.28-gentoo #4 Thu Jan 8 14:06:15 MSK 2009 i686
Build Date: 08 January 2009 06:20:31PM

        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Fri Jan 9 12:50:18 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "Simple Layout"
(**) |-->Screen "Screen 1" (0)
(**) | |-->Monitor "display"
(**) | |-->Device "videocard"
(**) |-->Input Device "Mouse1"
(**) |-->Input Device "touchscreen0"
(**) |-->Input Device "Keyboard1"
(==) Automatically adding devices
(==) Automatically enabling devices
(WW) The directory "/usr/lib/X11/fonts/local/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/misc/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/75dpi/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/100dpi/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/Type1/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/TrueType/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/freefont/" does not exist.
        Entry deleted from font path.
(WW) The directory "/usr/lib/X11/fonts/75d...

Revision history for this message
In , Gordon Jin (gordon-jin) wrote :

reassign to Jesse as the error info is like #17310.

Revision history for this message
In , Vzorvat (vzorvat) wrote :

patch from bug #17310 didn't help,because i use 2.5-r1 version of video driver,wich already includes that patch
test's show that 2.5* versons causes this error,and 2.4 versons show one big full-screen artefact

Revision history for this message
In , Rofmeister (rofmeister) wrote :

have same problem with that driver

asus r2h

Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller

configs in attachment

another one report: http://bugs.gentoo.org/show_bug.cgi?&id=208358

ps work fine with vesa

Revision history for this message
In , Rofmeister (rofmeister) wrote :

Created an attachment (id=21981)
xorg.conf

Revision history for this message
In , Rofmeister (rofmeister) wrote :

Created an attachment (id=21983)
xorg.0.log

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22011)
Xorg log with 2.6.0 driver

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22012)
Xorg conf i used to start with 2.6.0 driver

Revision history for this message
In , Vzorvat (vzorvat) wrote :

I have tested 2.6.0 driver,it didn't work too

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

pls get rid of your xorg.conf and retest.

Revision history for this message
In , Ling-ma (ling-ma) wrote :

(In reply to comment #9)
> pls get rid of your xorg.conf and retest.

hi Nuzhdin Urii,

when you test comment #9, please paste Xorg log file with Modedebug option.

Thanks
Ma Ling

Revision history for this message
jaxxed (jaxxed) wrote :

I have the same device and have the same problem.

Another forum suggest trying Jaunty-aplha 3, however there is a usb keyboard recognition problem there that prevents install

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22244)
Here Xorg.log with ModeDebug enabled

Sorry for so long whait,here is log of Xorg server
i tryed remove Xorg.conf,Xorg didn't started with same error
how to enable modedebug without xorg.conf i don't know (am i stupid?)

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Hi Nuzhdin Urii,

Could you describe what 's your evironment configuration, such as external displays and output ports, I find driver detect TV output. If your laptop actually doesn't connect TV, please use the following option to ignore it, then restart your Xorg ,and paste log file.

Section "Device"
        Identifier "videocard"
        Option "monitor-TV" "TV"
        ...
EndSection
        ...
Section "Monitor"
 Identifier "TV"
 Option "Ignore" "True"
EndSection

Thanks
Ma Ling

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22511)
xorg log with tv output configured

videocard installed into ASUS R2H umpc
it have video out port via additional device
i made recommended changes to Xorg,log attached

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Hi Nuzhdin Urii,

From the log file, I find the reasone may be from too high pixel clock, 388.04MHZ of initial mode 2048x1536 exceed our scope.

please try use lower resolution and pixel rate, then paste your log file, which are configured in xorg.conf as follow.

Section "Device"
        Identifier "videocard"
        Option "monitor-TV" "TV"
        Option "monitor-LVDS" "LVDS"

        ...
EndSection

Section "Monitor"
        Identifier "LVDS"
        Modeline "1280x1024_60.00" 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
        Option "PreferredMode" "1280x1024_60.00"
EndSection

Thanks
Ma Ling

Revision history for this message
jaxxed (jaxxed) wrote :

I have tried with yesterday's jaunty daily (2008/02/02) and got an install, but still have the exact same PLL Settings problem.

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22660)
xorg log

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22661)
xorg conf

here my conf ang log
by the way,R2H has 800x480 screen,may be this is a problem?

Revision history for this message
Geir Ove Myhr (gomyhr) wrote :

Thank you for supplying the necessary information and testing on a recent Jaunty (there has been significant updates since alpha-3, but most that made it into alpha-4 is in the daily image you tested). It would be useful if you could also supply the Xorg.0.log from Jaunty, since that may have more up-to-date information than the Intrepid version.

Changed in xserver-xorg-video-intel:
status: Incomplete → Confirmed
Revision history for this message
jaxxed (jaxxed) wrote :

Here's the log file you requested. The xorg.conf file is the default, without even any changes made for the evtouch touchscreen device which I am leaving to work on after the intel problems are sorted out.

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

(In reply to comment #14)
> Hi Nuzhdin Urii,
>
> From the log file, I find the reasone may be from too high pixel clock,
> 388.04MHZ of initial mode 2048x1536 exceed our scope.
>
> please try use lower resolution and pixel rate, then paste your log file, which
> are configured in xorg.conf as follow.
>
> Section "Device"
> Identifier "videocard"
> Option "monitor-TV" "TV"
> Option "monitor-LVDS" "LVDS"
>
> ...
> EndSection
>
> Section "Monitor"
> Identifier "LVDS"
> Modeline "1280x1024_60.00" 108.00 1280 1328 1440 1688 1024 1025 1028
> 1066 +hsync +vsync
> Option "PreferredMode" "1280x1024_60.00"
> EndSection
>
>
> Thanks
> Ma Ling
>

ling, for LVDS, timging info for all modes are "fixed up" to the fixed modes in fixup func, so chaning modeline may not help...maybe we can try to dump out more info about the fixed mode the device use (it must be a broken modeline I think )

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Created an attachment (id=22746)
please try the patch on your machine, thanks.

Hi Nuzhdin Urii,
Could you try the patch which can help us narrow down the issue, and paste log info again?

thanks
Ma Ling

Revision history for this message
jaxxed (jaxxed) wrote :

Jaunty updated the xserver-xorg-video-intel driver yesterday, so I though I'd mention that this update had no effect on the problem.

Revision history for this message
ehroure (ehroure) wrote :

I have the same problem, but when i connect the r2h to a external monitor it works OK. I have tested Jaunty and intrepid and have the PLL error in the 2 versions.

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22870)
with extra debug info

seems like there is no modline for 800x480
i will try to start with other resolutions later,but it is not sollution of problem

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Created an attachment (id=22890)
please try the patch on your machine, thanks.

Hi Nuzhdin Urii,
the log shows the clock of fixed mode is 0! It can't work, based on your mode list from Xorg, I re-construct another fixed mode, please try.

Thanks
Ma Ling

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22908)
it started

xorg started but image very bad

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Created an attachment (id=22932)
please try it on your machine, thanks

Hi Nuzhdin Urii,

In order not to impact your work, the new patch intends to make better image.

Thanks
Ma Ling

Revision history for this message
In , Ling-ma (ling-ma) wrote :

Created an attachment (id=22972)
please try the patch on your machine, thanks.

Hi Nuzhdin Urii,
The patch is our latest one, because we have no corresponding HW, could you try it besides that on comment #22

Thanks
Ma Ling

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=22980)
working patch

still bad in cause of wrong resolution
i changed your patch to this one,it works good

Revision history for this message
In , Vzorvat (vzorvat) wrote :

Created an attachment (id=23000)
working patch

still bad in cause of wrong resolution
i changed your patch to this one,it works good

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

(In reply to comment #25)
> Created an attachment (id=23000) [details]
> working patch
>
> still bad in cause of wrong resolution
> i changed your patch to this one,it works good
>

have you tried ma ling's patch in comment# 23? we are looking for a generic fix, though I agree this bug is because your HW is broken...

where do you get those parameters in your patch?

Revision history for this message
In , Ling-ma (ling-ma) wrote :

(In reply to comment #26)
> (In reply to comment #25)
> > Created an attachment (id=23000) [details] [details]
> > working patch
> >
> > still bad in cause of wrong resolution
> > i changed your patch to this one,it works good
> >
> have you tried ma ling's patch in comment# 23? we are looking for a generic
> fix, though I agree this bug is because your HW is broken...
> where do you get those parameters in your patch?

ping Nuzhdin Urii ~
Thanks
Ma Ling

Revision history for this message
In , Vzorvat (vzorvat) wrote :

(In reply to comment #27)
> (In reply to comment #26)
> > (In reply to comment #25)
> > > Created an attachment (id=23000) [details] [details] [details]
> > > working patch
> > >
> > > still bad in cause of wrong resolution
> > > i changed your patch to this one,it works good
> > >
> > have you tried ma ling's patch in comment# 23? we are looking for a generic
> > fix, though I agree this bug is because your HW is broken...
> > where do you get those parameters in your patch?
>
> ping Nuzhdin Urii ~
> Thanks
> Ma Ling
>

sorry :)

patch from comment# 23 didn't work
parameters was found in google

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

(In reply to comment #28)
> (In reply to comment #27)
> > (In reply to comment #26)
> > > (In reply to comment #25)
> > > > Created an attachment (id=23000) [details] [details] [details] [details]
> > > > working patch
> > > >
> > > > still bad in cause of wrong resolution
> > > > i changed your patch to this one,it works good
> > > >
> > > have you tried ma ling's patch in comment# 23? we are looking for a generic
> > > fix, though I agree this bug is because your HW is broken...
> > > where do you get those parameters in your patch?
> >
> > ping Nuzhdin Urii ~
> > Thanks
> > Ma Ling
> >
>
> sorry :)
>
> patch from comment# 23 didn't work
> parameters was found in google
>

There are only two ways we can find the correct fixed timing that is suitable for the panel this device use - either from the BIOS, or from the EDID. DDC fails, and no EDID returns. Apparently the modes read from BIOS is also broken..

I think the patch in general is ok for sanity check purpose, so should send to mailing list for RFC.

Nuzhdin Urii, you need to report this to the HW vendor of your device...

Revision history for this message
In , Rofmeister (rofmeister) wrote :

>There are only two ways we can find the correct fixed timing that is suitable
>for the panel this device use - either from the BIOS, or from the EDID. DDC
>fails, and no EDID returns. Apparently the modes read from BIOS is also
>broken..

but why i810 worked fine with that device ?

http://www.xs4all.nl/~sozonko/asus_r2h_howto/index.html#32

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

please provide the vbios dump via:

# cd /sys/devices/pci0000\:00/0000\:00\:02.0/
# echo 1 > rom
# cat rom > /tmp/rom.bin
# echo 0 > rom

then submit the rom.bin here. thanks.

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

also, pls try if Option "NoDDC" "True" will help, without the patch. Pls attach xorg log as well.

Revision history for this message
In , Rofmeister (rofmeister) wrote :

Created an attachment (id=23145)
rom dump

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks for testing jaunty; this should go upstream. Setting to Triaged for now.

Changed in xserver-xorg-video-intel:
importance: Undecided → High
status: Confirmed → Triaged
Revision history for this message
In , Ling-ma (ling-ma) wrote :

(In reply to comment #33)
> Created an attachment (id=23145) [details]
> rom dump

Thanks for you help, whould you please append option LVDSFixedMode "true" into xorg.conf as follow
Section "Device"
        Identifier "MY Video Device"
        driver "intel"
        ...
        Option "LVDSFixedMode" "true"
EndSection

Thanks
Ma Ling

Revision history for this message
Bryce Harrington (bryce) wrote :

Hi, I've forwarded this bug upstream to https://bugs.freedesktop.org/show_bug.cgi?id=20327 - please subscribe to this bug in case upstream needs further information or has something they need you to test. Thanks ahead of time.

skozombie, upstream may ask you to test against a newer xserver and driver. While jaxxed confirmed the issue still exists with the newer stuff, upstream tends to prefer that the original reporter do the testing. ISOs of new Ubuntu alphas can be had at http://cdimages.ubuntu.com/releases/jaunty/ and bleeding edge versions of drivers can be had at https://launchpad.net/~xorg-edgers/+archive/ppa

Changed in xserver-xorg-video-intel:
status: Unknown → Confirmed
Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

*** Bug 20327 has been marked as a duplicate of this bug. ***

Changed in xserver-xorg-video-intel:
status: Confirmed → Invalid
Revision history for this message
Andrew Whalan (skozombie) wrote :

I'm now downloading Jaunty-alpha5. I'll install it + bleeding edge xorg drivers as soon as I get a chance. Thanks for your help Bryce.

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

root cause of this is a HW issue that the panel report modes that it can't support at all. I think NoDDC option should fix this, if it works in console mode.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel:
status: Invalid → Unknown
Revision history for this message
Bryce Harrington (bryce) wrote :

Upstream has suggested several tests to try to see if it eliminates the problem:

Section "Device"
        Identifier "MY Video Device"
        driver "intel"
        ...
        Option "LVDSFixedMode" "true"
EndSection

-or-

        Option "NoDDC" "True"

Changed in xserver-xorg-video-intel:
status: Unknown → Invalid
Revision history for this message
jaxxed (jaxxed) wrote :

My R2H went down last week. I can't even get it to POST. I'll try to take it in for repairs if I can scrape together some cash for it, and then see if the recommendations work.

Revision history for this message
In , Rofmeister (rofmeister) wrote :

not working with

Option "NoDCC" "true"

and

 Option "LVDSFixedMode" "true"

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Are we sure this isn't our bug? It looks like the rom Dmitry posted has a mostly correct modeline:
* panel type 02: 800x480 clock 27000000
                info:
                  LVDS: 0x40000300
                  PP_ON_DELAYS: 0x025907d1
                  PP_OFF_DELAYS: 0x01f507d1
                  PP_DIVISOR: 0x00270f05
                  PFIT: 0x00000668
                timings: 800 808 904 900 480 482 484 500 27000.00 (BAD!)
only the vtotal vs vsyncend is broken (as we've seen before). The mode pointer table is busted though:
LVDS timing pointer data:
  Number of entries: 3
        panel type 02: 0x3072

It sounds like the EDID might be broken, but we're trying to use it anyway? What happens if we just use the VBT mode unconditionally, rather than assuming the EDID data is right?

Maybe once we get more VBIOS info we'll be able to figure out what data to trust better...

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

(In reply to comment #38)
> It sounds like the EDID might be broken, but we're trying to use it anyway?
> What happens if we just use the VBT mode unconditionally, rather than assuming
> the EDID data is right?
>
> Maybe once we get more VBIOS info we'll be able to figure out what data to
> trust better...
>

if we can get a mode from vbt, it actually override any mode from EDID via fix_up call in LVDS. It seems even though the VBT has a mode that is correct, the VBT didn't point it to us, and rather point us a wrong one. Apparently this is wrong. that's why I say it's notourbug.

unfortunately, any modeline setting in conf will also be overrided by the fixed mode as well, thus we don't have a way to correct this. My wild guess is windows driver has a way to override it maybe using a inf file, but that's just my guess..

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

But one of the VBT modes looked ok, which is why I thought it's probably our bug. There's some versioning magic we're missing in our VBT parsing; on some platforms we need to use the BDB_LVDS_LFP_DATA block, while on others we need to use the BDB_LVDS_LFP_DATA_PTRS block. Apparently on this platform needs to use the former. I don't know how we can tell which one will be accurate though...

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

actually could this bug just a dup of bug# 17292? so, even bios indicator 800x480 is the preferred, and we use it to override EDID modes, but since its DTD is "wrong", the screen is still blank...

we didn't notice the HTotal vs Hsync issue before and didn't double check with the bug reporter about this..

Changed in xserver-xorg-video-intel:
status: Invalid → Confirmed
Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

Jesse, I think the BDB_LVDS_LFP_DATA and BDB_LVDS_LFP_DATA_PTRS should be the same thing, while one is pointers and the other is datum. Driver is preferred to use BDB_LVDS_LFP_DATA_PTRS , rather than visit BDB_LVDS_LFP_DATA directly, even though we can...But,

I did some Hex editing and noticed that all pointers in BDB_LVDS_LFP_DATA_PTRS are busted, as you said, and are set 4 bytes ahead of the correct value. Not only DVO_Timing, but also LFP_PARAMs, PnPIDs. I further checked out and noticed that BDB_LVDS_OPTIONS is unexpected 4 bytes longer than it should be of its BDB version ...The correct size is 4 ( excluding bdb header/size ) , but in this rom, it's 8. From a document I have, it is valid to have this size but it's only in later version, not 1.26.

It looks like someone tucked 4 extra bytes of information to block BDB_LVDS_OPTIONS and just updated its size ( thus each block can still be parsed out correctly ), while forget the offset values in following blocks..

Googling around of this platform, it seems i810 or vesa driver need the hint of 800x480 to pick up the correct timing as well. I guess they use BDB_LVDS_LFP_DATA directly...

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

(In reply to comment #42)
> Jesse, I think the BDB_LVDS_LFP_DATA and BDB_LVDS_LFP_DATA_PTRS should be the
> same thing, while one is pointers and the other is datum. Driver is preferred
> to use BDB_LVDS_LFP_DATA_PTRS , rather than visit BDB_LVDS_LFP_DATA directly,
> even though we can...But,
>
> I did some Hex editing and noticed that all pointers in BDB_LVDS_LFP_DATA_PTRS
> are busted, as you said, and are set 4 bytes ahead of the correct value. Not
> only DVO_Timing, but also LFP_PARAMs, PnPIDs. I further checked out and noticed
> that BDB_LVDS_OPTIONS is unexpected 4 bytes longer than it should be of its BDB
> version ...The correct size is 4 ( excluding bdb header/size ) , but in this
> rom, it's 8. From a document I have, it is valid to have this size but it's
> only in later version, not 1.26.

Oh, nice debugging Michael, thanks for checking it out. So do you think it's possible to add a version check that accounts for this in our VBT parsing code? Sounds like 1.26 wouldn't work but maybe something earlier? Or we could check the BDB_LVDS_OPTIONS size instead since that seems correct, and use that to determine how to handle the DATA_PTRS offsets.

Revision history for this message
Popolon (popolon) wrote :

Seen today in dmesg (after last driver update) (Hope it will help):

[ 207.896089] ------------[ cut here ]------------
[ 207.896097] WARNING: at /build/buildd/linux-2.6.28/drivers/gpu/drm/i915/i915_gem.c:2475 i915_gem_idle+0x2ec/0x310 [i915]()
[ 207.896103] Modules linked in: nls_iso8859_1 nls_cp437 binfmt_misc i915 drm ppdev bridge stp bnep vboxnetflt vboxdrv input_polldev video output vfat fat lp parport joydev snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm usbhid snd_seq_dummy psmouse serio_raw pcspkr iTCO_wdt iTCO_vendor_support usblp snd_seq_oss snd_seq_midi wacom snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd intel_agp soundcore snd_page_alloc r8169 mii usb_storage fbcon tileblit font bitblit softcursor
[ 207.896186] Pid: 3066, comm: Xorg Not tainted 2.6.28-11-generic #40-Ubuntu
[ 207.896191] Call Trace:
[ 207.896207] [<ffffffff802509bf>] warn_on_slowpath+0x5f/0x90
[ 207.896222] [<ffffffffa0459fe4>] ? i915_gem_retire_requests+0x114/0x170 [i915]
[ 207.896234] [<ffffffffa045c11c>] i915_gem_idle+0x2ec/0x310 [i915]
[ 207.896246] [<ffffffffa045c193>] i915_gem_leavevt_ioctl+0x23/0x50 [i915]
[ 207.896265] [<ffffffffa04377fa>] drm_ioctl+0x10a/0x330 [drm]
[ 207.896274] [<ffffffff8021bb70>] ? restore_i387_xstate+0x120/0x150
[ 207.896287] [<ffffffffa045c170>] ? i915_gem_leavevt_ioctl+0x0/0x50 [i915]
[ 207.896296] [<ffffffff802f631d>] vfs_ioctl+0x7d/0xa0
[ 207.896303] [<ffffffff802f6685>] do_vfs_ioctl+0x75/0x230
[ 207.896310] [<ffffffff802f68d9>] sys_ioctl+0x99/0xa0
[ 207.896317] [<ffffffff8021253a>] system_call_fastpath+0x16/0x1b
[ 207.896322] ---[ end trace 8091fc89fedda383 ]---

Revision history for this message
Andrew Whalan (skozombie) wrote :

Bryce,

I've finally had a chance to update my system to the latest jaunty w/ xorg-edgers packages ... it's still broken. None of the driver options suggested help.

Based on what I've read on the upstream bug all we can do unfortunately is sit back and wait. Thank you for your efforts.

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Created an attachment (id=25420)
Add LVDS LFP data quirk

Can you give this patch a try? I'll need the output from lspci -vn on your machine to make it more specific.

Andrew Ash (ash211)
tags: added: edid error-exit
Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Created an attachment (id=25750)
LVDS data fetch fix

Here's another one to try too. It uses the goofy offset calculation used by the Windows driver, so it seems to pick up the size on your panel correctly at least.

Revision history for this message
In , Michael Fu (michael-fu-intel) wrote :

*** Bug 21641 has been marked as a duplicate of this bug. ***

Revision history for this message
Bryce Harrington (bryce) wrote :

heya skozombie, jbarnes posted a patch upstream; are you able to do a rebuild of the driver to test it? If not I may be able to build a package for you later.

Revision history for this message
Andrew Whalan (skozombie) wrote :

If you could build a package when you find time, that'd be awesome.

Revision history for this message
Bryce Harrington (bryce) wrote :

Yeah, I can do that when I get back home, in the next week or so.

Changed in xserver-xorg-video-intel (Ubuntu):
assignee: nobody → Bryce Harrington (bryceharrington)
Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Fix pushed, putting together the kernel side now.

commit 15af8ea6ab6998bbab9f4eeda227565c409da229
Author: Jesse Barnes <email address hidden>
Date: Mon Jun 22 11:11:06 2009 -0700

    Fix LFP data block fetch

Changed in xserver-xorg-video-intel:
status: Confirmed → Fix Released
Revision history for this message
Bryce Harrington (bryce) wrote :

Andrew, I've set up a PPA here:

https://edge.launchpad.net/~bryceharrington/+archive/red

I'm uncertain though that just updating the -intel driver is sufficient. Based on Jesse's last comment it sounds like there might be a kernel patch needed as well. Give it a try and let us know.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
assignee: Bryce Harrington (bryceharrington) → nobody
Revision history for this message
thieme (thieme-reis) wrote :

I have the same problem with kubuntu 9.04 with all updates and repository:
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main
enabled.

Attached intel.tar.gz with:
xorg.conf
lspci.txt
Xorg.0.log

Revision history for this message
Bryce Harrington (bryce) wrote :

[Awaiting reply from Andrew Whalan]

Changed in xserver-xorg-video-intel (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
thieme (thieme-reis) wrote :

Solved after the last update from repository:
deb http://ppa.launchpad.net/xorg-edgers/ppa/ubuntu jaunty main

Revision history for this message
thieme (thieme-reis) wrote :

but .....
xorg crash on logout!
I need add

[X-*-Core]
TerminateServer=true

to kdmrc.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Andrew Whalan (skozombie) wrote :

I can confirm it now works perfectly using the latest packages from the xorg-edgers PPA.

I don't get a crash on logout as reported by thieme, but i'm using GDM not KDM.

Video acceleration also works great.

Revision history for this message
Bryce Harrington (bryce) wrote :

Thanks Andrew, that's very good news. I'll try to make sure this gets included in the -intel update for Alpha-3

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → In Progress
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-intel - 2:2.7.99.902+git20090720.bb300738-0ubuntu1

---------------
xserver-xorg-video-intel (2:2.7.99.902+git20090720.bb300738-0ubuntu1) karmic; urgency=low

  * Update to git 20090720 (master branch) up to commit bb300738
    - Fix intel driver reports Couldn't find PLL settings on i915
      (LP: #312133)
    - Fix X freezing on intel 855GM
      (LP: #370292)
    - Implement vblank sync'd GL buffer swap
      (LP: #377090)

 -- Bryce Harrington <email address hidden> Mon, 20 Jul 2009 22:05:31 -0700

Changed in xserver-xorg-video-intel (Ubuntu):
status: In Progress → Fix Released
Changed in xserver-xorg-video-intel:
importance: Unknown → High
Changed in xserver-xorg-video-intel:
importance: High → Unknown
Changed in xserver-xorg-video-intel:
importance: Unknown → High
Revision history for this message
Eugene Lipchansky (nsky) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.