[Bug 59904] 3DMark2000 crashes: radeon: mmap failed, errno: 12

https://bugs.freedesktop.org/show_bug.cgi?id=59904 --- Comment #3 from Anton Petrov m...@sibnet.ru --- I started to get regular OOM-kills after that commit when i try to play minecraft. Memory usage with openarena was increased too. Looks like everything is ok with just compositing desktop

[Bug 52491] radeon massive screen corruption BARTS HD6870

https://bugzilla.kernel.org/show_bug.cgi?id=52491 --- Comment #17 from Bruno Jacquet maxi...@free.fr 2013-01-27 14:04:31 --- Indeed, linux 3.8-rc5 with no patch applied is working now, I see no corruption. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ---

[PATCH] drm/fb-helper: don't disable everything in initial_config

This should be done in the drivers for two reasons: - it gets in the way of fastboot efforts - it links the fb helpers with the crtc helpers instead of going through the real interface vfuncs, forcing i915 to fake all the -disable callbacks used by the crtc helper to avoid ugly Oopsen v2:

[PATCH] drm/fb-helper: improve kerneldoc

Now that the fbdev helper interface for drivers is trimmed down, update the kerneldoc for all the remaining exported functions. I've tried to beat the DocBook a bit by reordering the function references a bit into a more sensible ordering. But that didn't work out at all. Hence just extend the

[PATCH] drm/fb-helper: don't sleep for screen unblank when an oopps is in progress

Otherwise the system will burn even brighter and worse, leave the user wondering what's going on exactly. Since we already have a panic handler which will (try) to restore the entire fbdev console mode, we can just bail out. Inspired by a patch from Konstantin Khlebnikov. The callchain leading to

[RFC v1] drm: new VESA BIOS Extension DRM driver

Driver, + .date = 20130127, + .major = 0, + .minor = 0, + .patchlevel = 1, +}; + +#ifdef CONFIG_PM_SLEEP +static int dvbe_platform_suspend(struct device *dev) +{ + return 0; +} + +static int dvbe_platform_resume(struct device *dev) +{ + return 0; +} +#endif

[PATCH v3 11/22] PCI, drm: Kill pci_root_buses in alpha hose setting

Replace that with hotplug-safe version. Signed-off-by: Yinghai Lu ying...@kernel.org Cc: David Airlie airl...@linux.ie Cc: dri-devel@lists.freedesktop.org --- drivers/gpu/drm/drm_fops.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/drm_fops.c

[Bug 59945] New: Launching weston fails with error radeon 0000:01:00.0: forbidden register 0x00008040 at 558

https://bugs.freedesktop.org/show_bug.cgi?id=59945 Priority: medium Bug ID: 59945 Assignee: dri-devel@lists.freedesktop.org Summary: Launching weston fails with error radeon :01:00.0: forbidden register 0x8040 at 558

[Bug 59945] Launching weston fails with error radeon 0000:01:00.0: forbidden register 0x00008040 at 558

https://bugs.freedesktop.org/show_bug.cgi?id=59945 --- Comment #1 from Martin Andersson g02ma...@gmail.com --- Created attachment 73743 -- https://bugs.freedesktop.org/attachment.cgi?id=73743action=edit dmesg -- You are receiving this mail because: You are the assignee for the bug.

[Bug 59945] Launching weston fails with error radeon 0000:01:00.0: forbidden register 0x00008040 at 558

https://bugs.freedesktop.org/show_bug.cgi?id=59945 --- Comment #2 from Martin Andersson g02ma...@gmail.com --- Created attachment 73744 -- https://bugs.freedesktop.org/attachment.cgi?id=73744action=edit weston -- You are receiving this mail because: You are the assignee for the bug.

[Bug 58033] [r300g][r600g] Black gap artifacts when playing WoW

https://bugs.freedesktop.org/show_bug.cgi?id=58033 --- Comment #17 from Chris Rankin ranki...@googlemail.com --- My RV790 (HD4890) is also unaffected by this bug. And this box is 64 bit too. Could it just be a coincidence that both of my affected boxes are 32 bit? -- You are receiving this mail

[Bug 59946] New: [r600g] WoW crashed with page allocation failure

https://bugs.freedesktop.org/show_bug.cgi?id=59946 Priority: medium Bug ID: 59946 Assignee: dri-devel@lists.freedesktop.org Summary: [r600g] WoW crashed with page allocation failure Severity: normal Classification: Unclassified

[Bug 59904] 3DMark2000 crashes: radeon: mmap failed, errno: 12

https://bugs.freedesktop.org/show_bug.cgi?id=59904 --- Comment #4 from Paul Heldens pheld...@planet.nl --- Also OOM kills here, bisected: 68a097596efdf314ec60487a1761cac789ae2367 is the first bad commit in Xonotic 64 bit and Spring 64 bit games after several minutes of play I run out of my 8GB

Re: [git pull] fbcon locking fixes.

On Fri, Jan 25, 2013 at 1:50 AM, Andrew Morton a...@linux-foundation.org wrote: On Fri, 25 Jan 2013 00:42:37 + (GMT) Dave Airlie airl...@linux.ie wrote: These patches have been sailing around long enough, waiting for a maintainer to reappear, so I've decided enough is enough, lockdep is

[Bug 59945] Launching weston fails with error radeon 0000:01:00.0: forbidden register 0x00008040 at 558

https://bugs.freedesktop.org/show_bug.cgi?id=59945 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Product|DRI |Mesa

[Bug 59945] Launching weston fails with error radeon 0000:01:00.0: forbidden register 0x00008040 at 558

https://bugs.freedesktop.org/show_bug.cgi?id=59945 --- Comment #4 from Alex Deucher ag...@yahoo.com --- Created attachment 73753 -- https://bugs.freedesktop.org/attachment.cgi?id=73753action=edit possible fix The attached mesa patch should fix the issue. -- You are receiving this mail

Re: [PATCH v3 11/22] PCI, drm: Kill pci_root_buses in alpha hose setting

On Sun, Jan 27, 2013 at 7:21 PM, Yijing Wang wangyij...@huawei.com wrote: On 2013/1/28 3:23, Yinghai Lu wrote: Replace that with hotplug-safe version. Signed-off-by: Yinghai Lu ying...@kernel.org Cc: David Airlie airl...@linux.ie Cc: dri-devel@lists.freedesktop.org ---

[PATCH v3 02/22] PCI: Add dummy bus_type for pci_host_bridge

Need to use it for looping registered host_bridge, and kill pci_root_buses list. Signed-off-by: Yinghai Lu ying...@kernel.org Cc: Mauro Carvalho Chehab mche...@redhat.com Cc: Doug Thompson dougthomp...@xmission.com Cc: linux-e...@vger.kernel.org Cc: x...@kernel.org Cc: David Airlie

[PATCH v3 05/22] PCI: Add for_each_pci_host_bridge() and pci_get_next_host_bridge

Now we have pci_root_buses list, and there is lots of iteration with list_of_each of it, that is not safe after we add pci root bus hotplug support after booting stage. Also pci_find_next_bus is pretty misleading name, and it is only finding next root bus instead of regular pci bus. Add

[PATCH v3 00/22] PCI: Iterate pci host bridge instead of pci root bus

Now we have pci_root_buses list, and there is lots of iteration with list_of_each of it, that is not safe after we add pci root bus hotplug support after booting stage. Add pci_get_next_host_bridge and use bus_find_device in driver core to iterate host bridge and the same time get root bus. We

[PATCH v3 22/22] PCI: Kill pci_root_buses

No user now, remove it. Signed-off-by: Yinghai Lu ying...@kernel.org Cc: Mauro Carvalho Chehab mche...@redhat.com Cc: Doug Thompson dougthomp...@xmission.com Cc: linux-e...@vger.kernel.org Cc: x...@kernel.org Cc: David Airlie airl...@linux.ie Cc: dri-devel@lists.freedesktop.org Cc: David S.

[PATCH v3 21/22] PCI: Kill pci_find_next_bus

No user now, remove it. That name is misleading as it only for root buses. Signed-off-by: Yinghai Lu ying...@kernel.org Cc: Mauro Carvalho Chehab mche...@redhat.com Cc: Doug Thompson dougthomp...@xmission.com Cc: linux-e...@vger.kernel.org Cc: x...@kernel.org Cc: David Airlie airl...@linux.ie

Adding a i915 quirk (here: pipe A force quirk for testing purposes)?

Hi, From [1]: ... static struct intel_quirk intel_quirks[] = { /* HP Mini needs pipe A force quirk (LP: #322104) */ { 0x27ae, 0x103c, 0x361a, quirk_pipea_force }, ... } Triple - which value is what? 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core

Re: Adding a i915 quirk (here: pipe A force quirk for testing purposes)?

On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek sedat.di...@gmail.com wrote: Hi, From [1]: ... static struct intel_quirk intel_quirks[] = { /* HP Mini needs pipe A force quirk (LP: #322104) */ { 0x27ae, 0x103c, 0x361a, quirk_pipea_force }, ... } Triple - which value is

Re: Adding a i915 quirk (here: pipe A force quirk for testing purposes)?

On Mon, Jan 28, 2013 at 1:16 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Mon, Jan 28, 2013 at 12:52 AM, Sedat Dilek sedat.di...@gmail.com wrote: Hi, From [1]: ... static struct intel_quirk intel_quirks[] = { /* HP Mini needs pipe A force quirk (LP: #322104) */ { 0x27ae,

[PATCH] Adds display-timing node parsing to exynos drm fimd as per

This patch adds display-timing node parsing to drm fimd, this depends on the display helper patchset at http://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg33354.html It also adds pinctrl support for drm fimd. patch is based on branch exynos-drm-next at

[PATCH] video: drm: exynos: Adds display-timing node parsing using video helper function

This patch adds display-timing node parsing using video helper function Signed-off-by: Leela Krishna Amudala l.kris...@samsung.com Signed-off-by: Vikas Sajjan vikas.saj...@linaro.org --- drivers/gpu/drm/exynos/exynos_drm_fimd.c | 35 -- 1 file changed, 33

[Bug 59904] 3DMark2000 crashes: radeon: mmap failed, errno: 12

other 3d apps. I have hd4330 (rv710) -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/2b19ff89/attachment.html>

[Bug 59332] Problems building 32bit Mesa

be causing some of the issues I'm seeing -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/c0cc10b9/attachment.html>

[Bug 52491] radeon massive screen corruption BARTS HD6870

https://bugzilla.kernel.org/show_bug.cgi?id=52491 --- Comment #17 from Bruno Jacquet 2013-01-27 14:04:31 --- Indeed, linux 3.8-rc5 with no patch applied is working now, I see no corruption. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving

[PATCH] drm/fb-helper: don't disable everything in initial_config

This should be done in the drivers for two reasons: - it gets in the way of fastboot efforts - it links the fb helpers with the crtc helpers instead of going through the real interface vfuncs, forcing i915 to fake all the ->disable callbacks used by the crtc helper to avoid ugly Oopsen v2:

[PATCH] drm/fb-helper: improve kerneldoc

Now that the fbdev helper interface for drivers is trimmed down, update the kerneldoc for all the remaining exported functions. I've tried to beat the DocBook a bit by reordering the function references a bit into a more sensible ordering. But that didn't work out at all. Hence just extend the

[PATCH] drm/fb-helper: don't sleep for screen unblank when an oopps is in progress

Otherwise the system will burn even brighter and worse, leave the user wondering what's going on exactly. Since we already have a panic handler which will (try) to restore the entire fbdev console mode, we can just bail out. Inspired by a patch from Konstantin Khlebnikov. The callchain leading to

[RFC v1] drm: new VESA BIOS Extension DRM driver

umb_map_offset = dvbe_dumb_map_offset, + .dumb_destroy = dvbe_dumb_destroy, + + .name = "dvbe", + .desc = "DRM VESA BIOS Extension Driver", + .date = "20130127", + .major = 0, + .minor = 0, + .patchlevel = 1, +}; + +#ifd

[PATCH v3 11/22] PCI, drm: Kill pci_root_buses in alpha hose setting

Replace that with hotplug-safe version. Signed-off-by: Yinghai Lu Cc: David Airlie Cc: dri-devel at lists.freedesktop.org --- drivers/gpu/drm/drm_fops.c | 10 +++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/drm_fops.c b/drivers/gpu/drm/drm_fops.c

[Bug 59945] New: Launching weston fails with error "radeon 0000:01:00.0: forbidden register 0x00008040 at 558"

ML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/1ef78fe9/attachment.html>

[Bug 59945] Launching weston fails with error "radeon 0000:01:00.0: forbidden register 0x00008040 at 558"

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/9e8cdbeb/attachment.html>

[Bug 59945] Launching weston fails with error "radeon 0000:01:00.0: forbidden register 0x00008040 at 558"

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/c9ecde40/attachment.html>

[Bug 58033] [r300g][r600g] Black gap artifacts when playing WoW

are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/4b52ac00/attachment.html>

[Bug 59946] New: [r600g] WoW crashed with "page allocation failure"

e assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/53441eb9/attachment-0001.html>

[Bug 59904] 3DMark2000 crashes: radeon: mmap failed, errno: 12

are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130127/5d34f426/attachment.html>

[git pull] fbcon locking fixes.

On Fri, Jan 25, 2013 at 1:50 AM, Andrew Morton wrote: > On Fri, 25 Jan 2013 00:42:37 + (GMT) > Dave Airlie wrote: > >> These patches have been sailing around long enough, waiting for a maintainer >> to reappear, so I've decided enough is enough, lockdep is kinda useful to >> have. >> >>

[PATCH v3 11/22] PCI, drm: Kill pci_root_buses in alpha hose setting

On Sun, Jan 27, 2013 at 7:21 PM, Yijing Wang wrote: > On 2013/1/28 3:23, Yinghai Lu wrote: >> Replace that with hotplug-safe version. >> >> Signed-off-by: Yinghai Lu >> Cc: David Airlie >> Cc: dri-devel at lists.freedesktop.org >> --- >> drivers/gpu/drm/drm_fops.c | 10 +++--- >> 1 file

[pull] radeon drm-fixes-3.8

From: Alex Deucher Hi Dave, A couple of small fixes I picked up over the weekend. The following changes since commit 483674325f64a37c7696edb12ce6ad3e535421bc: Merge branch 'drm-intel-fixes' of git://people.freedesktop.org/~danvet/drm-intel (2013-01-26

[PATCH v3 05/22] PCI: Add for_each_pci_host_bridge() and pci_get_next_host_bridge

Now we have pci_root_buses list, and there is lots of iteration with list_of_each of it, that is not safe after we add pci root bus hotplug support after booting stage. Also pci_find_next_bus is pretty misleading name, and it is only finding next root bus instead of regular pci bus. Add

[PATCH v3 00/22] PCI: Iterate pci host bridge instead of pci root bus

Now we have pci_root_buses list, and there is lots of iteration with list_of_each of it, that is not safe after we add pci root bus hotplug support after booting stage. Add pci_get_next_host_bridge and use bus_find_device in driver core to iterate host bridge and the same time get root bus. We

[PATCH v3 22/22] PCI: Kill pci_root_buses

No user now, remove it. Signed-off-by: Yinghai Lu Cc: Mauro Carvalho Chehab Cc: Doug Thompson Cc: linux-edac at vger.kernel.org Cc: x86 at kernel.org Cc: David Airlie Cc: dri-devel at lists.freedesktop.org Cc: "David S. Miller" Cc: sparclinux at vger.kernel.org Cc: Tony Luck Cc: Fenghua Yu

[PATCH v3 02/22] PCI: Add dummy bus_type for pci_host_bridge

Need to use it for looping registered host_bridge, and kill pci_root_buses list. Signed-off-by: Yinghai Lu Cc: Mauro Carvalho Chehab Cc: Doug Thompson Cc: linux-edac at vger.kernel.org Cc: x86 at kernel.org Cc: David Airlie Cc: dri-devel at lists.freedesktop.org Cc: "David S. Miller" Cc:

[PATCH v3 21/22] PCI: Kill pci_find_next_bus

No user now, remove it. That name is misleading as it only for root buses. Signed-off-by: Yinghai Lu Cc: Mauro Carvalho Chehab Cc: Doug Thompson Cc: linux-edac at vger.kernel.org Cc: x86 at kernel.org Cc: David Airlie Cc: dri-devel at lists.freedesktop.org Cc: "David S. Miller" Cc: