linux-kernel - Re: [Intel-gfx] Intel graphics drm issue?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 14 Oct 2012 16:40:08 +0200
From:	Daniel Vetter <daniel@...ll.ch>
To:	dmarkh@....rr.com
Cc:	markh@...pro.net,
	Bruno Prémont <bonbons@...ux-vserver.org>,
	Intel Graphics Development <intel-gfx@...ts.freedesktop.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [Intel-gfx] Intel graphics drm issue?

On Sun, Oct 14, 2012 at 4:19 PM, Mark Hounschell <dmarkh@....rr.com> wrote:
> OK. Applied to 3.6.2. The dmesg is attached. The message did not show up.
> I'll be here most of the day.

Ok, that at least confirms my suspicion (and yeah, I've mis-remembered
when I've merged the agp removal for gen6+, it's already all done in
3.6). But I have no idea how that could fail this way. New little
debug patch:

diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index a24ffbe..7ec35c5 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -848,6 +848,11 @@ i915_pci_probe(struct pci_dev *pdev, const struct
pci_device_id *ent)
                return -ENODEV;
        }

+       printk("force-disabling agp on gen %i, is_ivybridge %i\n",
+              intel_info->gen, intel_info->is_ivybridge);
+
+       driver.driver_features &=
+               ~(DRIVER_USE_AGP | DRIVER_REQUIRE_AGP);
        return drm_get_pci_dev(pdev, ent, &driver);
 }

Yours, Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/