Bug 698045 - [Arrandale] i915 module giving error "failed to get supported _DSM functions"
Summary: [Arrandale] i915 module giving error "failed to get supported _DSM functions"
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-intel
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Adam Jackson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: [cat:modesetting]
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-20 03:11 UTC by Jerone Young
Modified: 2018-04-11 19:04 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-07 14:40:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Dmesg output (80.71 KB, application/txt)
2011-04-20 03:13 UTC, Jerone Young
no flags Details
lspci output (14.92 KB, text/plain)
2011-04-20 03:23 UTC, Jerone Young
no flags Details
dmesg output (80.71 KB, text/plain)
2011-04-20 03:25 UTC, Jerone Young
no flags Details
Xorg.0.log (35.37 KB, text/plain)
2011-10-17 20:52 UTC, Jerone Young
no flags Details

Description Jerone Young 2011-04-20 03:11:13 UTC
Description of problem:
When Fedora 15 beta with kernel 2.6.38.2-9.fc15.x86_64 is booting up on any machine with intel Arrandale graphics using i915 module you see plymouth disapear for a second and you see the following message on the screen:

[drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions

This issue looks like it *should* have resolved the issue:
http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.38.y.git;a=commit;h=723bfd707a97fee06eb3ba4d3e8b4714c29a1064

This bug may be related to Bug# 669489

Comment 1 Jerone Young 2011-04-20 03:13:41 UTC
Created attachment 493350 [details]
Dmesg output

Comment 2 Jerone Young 2011-04-20 03:23:32 UTC
Created attachment 493351 [details]
lspci output

Comment 3 Jerone Young 2011-04-20 03:25:01 UTC
Created attachment 493352 [details]
dmesg output

Comment 4 Bryn M. Reeves 2011-05-09 10:03:13 UTC
The _DSM functions are firmware supplied ACPI objects. My first thought was an outdated BIOS (I am hitting this on a Thinkpad T410). Now with fully updated firmware and still see the problem. 

I don't think the patch in comment #0 is supposed to "fix" this - it just extends the driver so it actually asks for the  _DSM functions. The patch adds the error message that's logged but presumably before it was introduced the driver had some other way of coping with this (it worked fine on this machine in f13 way before this was added).

I'm no expert in this area but will do a bit of asking around - I really need this machine to work and would rather avoid VESA and fallback! ;)

Comment 5 Bryn M. Reeves 2011-05-10 09:40:30 UTC
OK, although I am hitting this it's not the cause of the X problem I am having on the t410 - the Live Beta images spit out the same error but X is working fine on this hardware. I'll prod some more but this bug certainly isn't the cause of my problems.

Comment 6 Adam Stokes 2011-05-25 01:49:47 UTC
Since release of F15 GA the livecd boots and logs into X. However, once an install to the hdd is performed and a reboot we see the reported errors and are dumped into a debug shell.

Im running this on a T510 with i915 chipset.

Has anyone on QA been able to reproduce this?

Comment 7 James Rankin 2011-06-03 03:28:46 UTC
I'm having this same issue as well. I am also using a ThinkPad T510 with Intel graphics.

Comment 8 Hajime Taira 2011-06-18 03:49:49 UTC
I'm having this same issue as well. I am using SONY VAIO VGN-Z91DS with Intel Corporation Mobile 4 Series Chipset(i915).

Comment 9 Alex Wajda 2011-08-01 22:31:20 UTC
The same issue. ThinkPad T510 w/ Intel chipset

Comment 10 Matěj Cepl 2011-09-27 20:21:03 UTC
(In reply to comment #0)
> Description of problem:
> When Fedora 15 beta with kernel 2.6.38.2-9.fc15.x86_64 is booting up on any
> machine with intel Arrandale graphics using i915 module you see plymouth
> disapear for a second and you see the following message on the screen:
> 
> [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions

You mean, that's it? There is nothing more from Fedora? Can you install Fedora at all?

If yes, could you start it in the runlevel 3, and then start X after that (by running startx)? If it fails, still /var/log/Xorg.0.log and the output of dmesg program from the failed attempt to start X would be useful.

We will review this issue again once you've had a chance to attach this information.

Thank you very much in advance.

Comment 11 Jerone Young 2011-10-17 20:51:15 UTC
The issue is still happening in Kernel 3.1 in Fedora 16 on my T410. Seems to only effect Arrandale Intel Graphics. 

@Matej 
  The issue is not with Xorg, but with KMS (Kernel Mode settings) drm in the kernel. This is happening way before Xorg is coming up. You can see it during Plymoth. I've attached the Xorg file though.

Comment 12 Jerone Young 2011-10-17 20:52:08 UTC
Created attachment 528652 [details]
Xorg.0.log

Comment 13 Matěj Cepl 2011-10-18 12:18:38 UTC
(In reply to comment #11)
>   The issue is not with Xorg, but with KMS (Kernel Mode settings) drm in the
> kernel. This is happening way before Xorg is coming up. You can see it during
> Plymoth. I've attached the Xorg file though.

I know, I didn't claim otherwise, just that Xorg.0.log gives us a lot of information about the hardware etc. which would be difficult to obtain otherwise.

Comment 14 Michele 2011-12-02 20:43:16 UTC
Same issue: Fedora 16 x86.64 on thinkpad t510 w/ intel chipset
lspci http://pastebin.com/Nt1S1nRU
dmesg http://pastebin.com/7HXp2BkY

I have this error with also this one:
[drm:ironlake_update_pch_refclk] *ERROR* enabling SSC on PCH

Comment 15 Fabiano Franz 2012-01-10 04:44:26 UTC
Exactly the same issue here on a ThinkPad T410, Fedora 16 x86.64 upgraded from 15.

Comment 16 Robert de Rooy 2012-02-09 13:33:56 UTC
Just a me too. kernel-3.2.3-2.fc16.x86_64 on a ThinkPad T410.
BIOS 1.39 with ECP 1.16, which still seems to be the latest.

Does not seem to cause any problems, just some flicker during plymouth because of switching to the text console.

Comment 17 Diego Viola 2012-04-13 01:44:25 UTC
Same issue here on a ThinkPad T510, sometimes I even get some screen display issues after KMS is triggered (resolution change) and I have to reboot or wait for the framebuffer to blank/unblank to get rid of the graphics corruption/issue.

Has this issue already been reported upstream? Are Intel developers aware of this?

Comment 18 Robert de Rooy 2012-04-19 15:43:56 UTC
I just updated the BIOS to 1.41 and the ECP to 1.18 which are the latest right now, and the issue remains the same.

Diego: From what I understood, this is a BIOS bug, so you would need to complain to Lenovo.

Comment 19 Diego Viola 2012-04-19 16:19:36 UTC
Hi Robert,

thanks for letting me know this is a Lenovo issue, and apologies for assuming this was a Intel issue.

Is there a way we could contact Lenovo about this? Last time I tried to contact them they weren't really that helpful.

Anyway, I have upgraded the BIOS in my ThinkPad T510 to BIOS 6MET89WW (1.49 ) 02/23/2012 which is the latest version in their site (lenovo.com). But I still get the same problem nonetheless.

[ 5.458729] [drm:intel_dsm_pci_probe] *ERROR* failed to get supported _DSM functions

Any ideas what we can do about it? Can someone help?

Comment 20 Diego Viola 2012-04-19 16:22:22 UTC
Here is the dmesg I get with the latest BIOS:

http://pastie.org/3817576

Comment 21 Fedora End Of Life 2012-08-07 14:40:41 UTC
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.