linux-kernel - Re: agp/intel: can't ioremap flush page

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]

Message-ID: <CAKMK7uE6Gaq-ghgWJ+6Qyn7hrGzAMOHyGT9KQQJ+ij7omPV2Ew@mail.gmail.com>
Date:	Sat, 8 Feb 2014 20:59:48 +0100
From:	Daniel Vetter <daniel.vetter@...ll.ch>
To:	Paul Bolle <pebolle@...cali.nl>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>,
	Ville Syrjälä <ville.syrjala@...ux.intel.com>,
	Yinghai Lu <yinghai@...nel.org>,
	David Airlie <airlied@...ux.ie>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>
Subject: Re: agp/intel: can't ioremap flush page - no chipset flushing

On Sat, Feb 8, 2014 at 8:06 PM, Paul Bolle <pebolle@...cali.nl> wrote:
> 0) Booting v3.14-rc1 on an (outdated) ThinkPad X41 triggers a kernel
> error:
>     pci 0000:00:02.0: can't ioremap flush page - no chipset flushing
>
> That is this pci device:
>      lspci | grep 00:02.0
>      00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
>
> I can't remember seeing that error before. It is apparently printed by
> drivers/char/agp/intel-gtt.c. (So I've sent this message to the people
> touching that file between v3.13 and v3.14-rc1. No, I haven't yet
> pinpointed a specific commit.)
>
> 1) What am I supposed to do to make this error go away?

Hm, if this is really a regression between 3.13 and 3.14-rc1 then I
don't see any quick candidates - relevant functions in intel-gtt.c
seem unchanged.

So probably a bisect is what we need here. Note that this could also
be due to resource handling changes in the driver/pci core, so you
can't restrict the bisect really. But before going down this route it
would be worth to check out the resource allocations of both kernels.
Can you please attach /proc/iomem for both 3.13 and 3.14-rc1

Adding more mailing lists.
-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/