[Bug 34252] Unexpected behaviour when switching video cards with vga_switcheroo
https://bugzilla.kernel.org/show_bug.cgi?id=34252 --- Comment #13 from Florian Mickler 2011-05-19 07:21:09 --- A patch referencing this bug report has been merged in v2.6.39: commit a67b8887ced9d54cab7759bdb19deafed37481eb Author: Florian Mickler Date: Sun May 15 16:32:50 2011 +0200 vga_switcheroo: don't toggle-switch devices -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34252] Unexpected behaviour when switching video cards with vga_switcheroo
https://bugzilla.kernel.org/show_bug.cgi?id=34252 Florian Mickler changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALREADY_AVAILABLE |CODE_FIX -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: PROBLEM: i915 regression between 2.6.39-rc6 and 2.6.39-rc7
On Wed, 18 May 2011 20:15:05 +0200, Eric Leblond wrote: > I confirm that it is working fine when enabling semaphore. Thanks a lot > for the workaround, it is a pleasure to have a real laptop again ;) And, we'll keep trying to make it work without per-laptop configuration... -- keith.pack...@intel.com pgpBxyb6YkmzT.pgp Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #7 from sh...@bitspin.org 2011-05-19 03:30:41 PDT --- (In reply to comment #3) > I'm booting an imac12,2 in UEFI mode (need a "Run EFI in physical mode" patch > before doing so), > here's how : > 1) boot from latest ubuntu live CD (hold alt, or c, at boot) > 2) dump the bios >dd if=/dev/mem of=vbios.bin bs=65536 skip=12 count=1 > 3) move it to your partition's /lib/firmware/radeon/vbios.bin > 4) use your patch, but move the radeon_read_bios_from_firmware >call before all other calls to get the bios (force using vbios.bin) > Thats exactly what I did on my MBP however the screen flicker remains.. I'm pretty sure the BIOS is valid (dmesg identifies it as ATOM BIOS: Apple) and strings revealed data like "Whistler Pro" which IIRC is the type code used by the Radeon HD 6xxx series. Since Jérémy has a working setup with GPU acceleration I can only suspect a problem in the microcode. iMac12,2 has a Radeon HD 6970M which utilizes the CAYMAN microcode while my Radeon HD6750M is using TURKS. So I'm stuck with working but non-accelerated radeondrmfb. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #13 from Karesz L. 2011-05-19 03:39:03 PDT --- Any news on this? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #14 from Karesz L. 2011-05-19 03:49:36 PDT --- I'm a little confused, https://bugs.freedesktop.org/attachment.cgi?id=45729";>this Xorg.0.log is marked as a patch, but I'm not really sure, if it is. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 Michel Dänzer changed: What|Removed |Added Attachment #45729|1 |0 is patch|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: Summary of the V4L2 discussions during LDS - was: Re: Embedded Linux memory management interest group list
Em 18-05-2011 16:46, Sakari Ailus escreveu: > Hans Verkuil wrote: >> Note that many video receivers cannot stall. You can't tell them to wait >> until >> the last buffer finished processing. This is different from some/most? >> sensors. > > Not even image sensors. They just output the frame data; if the receiver > runs out of buffers the data is just lost. And if any part of the frame > is lost, there's no use for other parts of it either. But that's > something the receiver must handle, i.e. discard the data and increment > frame number (field_count in v4l2_buffer). > > The interfaces used by image sensors, be they parallel or serial, do not > provide means to inform the sensor that the receiver has run out of > buffer space. These interfaces are just unidirectional. Well, it depends on how the hardware works, really. On most (all?) designs, the IP block responsible to receive data from a sensor (or to transmit data, on an output device) is capable of generating an IRQ to notify the OS that a framebuffer was filled. So, the V4L driver can mark that buffer as finished and remove it from the list of the queued buffers. Although the current API's don't allow to create a new buffer if the list is empty, it may actually make sense to allow kernel to dynamically create a new buffer, warranting that the sensor (or receiver) will never run out of buffers under normal usage. Of course, the maximum number of buffers should be specified, to avoid having an unacceptable delay. On such case, the frame will end by being discarded. It makes sense to provide a way to report userspace if this happens. Mauro. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #8 from Jérémy Lal 2011-05-19 05:34:40 PDT --- (In reply to comment #7) > Since Jérémy has a working setup with GPU acceleration I can only suspect a > problem in the microcode. iMac12,2 has a Radeon HD 6970M which utilizes the > CAYMAN microcode while my Radeon HD6750M is using TURKS. Mine is [1002:6740] : [9.285052] [drm] Loading TURKS Microcode which kernel version are you using ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 Stuart Foster changed: What|Removed |Added CC||smf.li...@ntlworld.com Kernel Version|2.6.38.2|2.6.39 --- Comment #13 from Stuart Foster 2011-05-19 13:04:45 --- Just a quick update to report that the fault is also present in the 2.6.39 kernel. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #9 from sh...@bitspin.org 2011-05-19 06:22:52 PDT --- (In reply to comment #8) > Mine is [1002:6740] : > [9.285052] [drm] Loading TURKS Microcode > > which kernel version are you using ? 2.6.39-rc7-00215-g194a526 git head with local patches applied (phys-efi, radeon-firmware hack) I'm running Gentoo linux amd64. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #15 from Евгений М. 2011-05-19 07:00:19 PDT --- No Karesz, it is not a patch. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
https://bugzilla.kernel.org/show_bug.cgi?id=35192 Jérôme Glisse changed: What|Removed |Added CC||gli...@freedesktop.org --- Comment #5 from Jérôme Glisse 2011-05-19 14:05:02 --- So is the bug still revealent ? If so what is the bt now ? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] agp/uninorth: Fix lockups with radeon KMS and >1x.
From: Michel Dänzer
This was based on a description by Ben Herrenschmidt:
> I've removed that SBA reset from the normal TLB invalidation path and
> left it only once after turning AGP on.
About six months ago, he said:
> I did it a bit differently, but yeah, you get the idea. I'm doing a
> patch series so don't bother pushing things too hard yet.
But I haven't seen anything from him about this since then, and people are
regularly hitting these lockups, so here we are...
Signed-off-by: Michel Dänzer
---
drivers/char/agp/uninorth-agp.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/char/agp/uninorth-agp.c b/drivers/char/agp/uninorth-agp.c
index 47c2218..55af723 100644
--- a/drivers/char/agp/uninorth-agp.c
+++ b/drivers/char/agp/uninorth-agp.c
@@ -80,7 +80,7 @@ static void uninorth_tlbflush(struct agp_memory *mem)
ctrl | UNI_N_CFG_GART_INVAL);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL, ctrl);
- if (uninorth_rev <= 0x30) {
+ if (!mem && uninorth_rev <= 0x30) {
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
ctrl | UNI_N_CFG_GART_2xRESET);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
--
1.7.5.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37368] New: Server crashes with "failed to map pixmap: -12"
https://bugs.freedesktop.org/show_bug.cgi?id=37368 Summary: Server crashes with "failed to map pixmap: -12" Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel@lists.freedesktop.org ReportedBy: gt...@spearhead.de Created an attachment (id=46907) --> (https://bugs.freedesktop.org/attachment.cgi?id=46907) Server log with crash info Every now and then, the X server will crash on my machine and restart to kdm. I have never seen it happen live so far, it always happened when I was away from the machine for some time. System is Debian unstable, xserver-xorg-core package version is 1.10.1-2, but the problem has been occuring for some months now. In the server log, I find: == failed to map pixmap: -12 Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a38b8] 1: /usr/bin/X (0x40+0x646e9) [0x4646e9] 2: /lib/libpthread.so.0 (0x7f45b8dd2000+0xf020) [0x7f45b8de1020] 3: /lib/libc.so.6 (0x7f45b7aed000+0x84b30) [0x7f45b7b71b30] 4: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x6436) [0x7f45b5611436] 5: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x8f92) [0x7f45b5613f92] 6: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x12355) [0x7f45b561d355] 7: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x9b31) [0x7f45b5614b31] 8: /usr/bin/X (0x40+0xe0034) [0x4e0034] 9: /usr/bin/X (0x40+0x2e283) [0x42e283] 10: /usr/bin/X (0x40+0x31731) [0x431731] 11: /usr/bin/X (0x40+0x257de) [0x4257de] 12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f45b7b0bead] 13: /usr/bin/X (0x40+0x25389) [0x425389] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. == A full server log is attached. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[PATCH] drm/radeon/evergreen/btc/fusion: setup hdp to invalidate and flush when asked
This needs to be explicitly set on btc. It's set by default
on evergreen/fusion, so it fine to just unconditionally enable it for
all chips.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/evergreen.c |6 +-
drivers/gpu/drm/radeon/evergreend.h |2 ++
2 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/radeon/evergreen.c
b/drivers/gpu/drm/radeon/evergreen.c
index c98abd5..9f907f7 100644
--- a/drivers/gpu/drm/radeon/evergreen.c
+++ b/drivers/gpu/drm/radeon/evergreen.c
@@ -1582,7 +1582,7 @@ static void evergreen_gpu_init(struct radeon_device *rdev)
u32 sq_stack_resource_mgmt_2;
u32 sq_stack_resource_mgmt_3;
u32 vgt_cache_invalidation;
- u32 hdp_host_path_cntl;
+ u32 hdp_host_path_cntl, tmp;
int i, j, num_shader_engines, ps_thread_count;
switch (rdev->family) {
@@ -2199,6 +2199,10 @@ static void evergreen_gpu_init(struct radeon_device
*rdev)
for (i = SQ_ALU_CONST_BUFFER_SIZE_HS_0; i < 0x29000; i += 4)
WREG32(i, 0);
+ tmp = RREG32(HDP_MISC_CNTL);
+ tmp |= HDP_FLUSH_INVALIDATE_CACHE;
+ WREG32(HDP_MISC_CNTL, tmp);
+
hdp_host_path_cntl = RREG32(HDP_HOST_PATH_CNTL);
WREG32(HDP_HOST_PATH_CNTL, hdp_host_path_cntl);
diff --git a/drivers/gpu/drm/radeon/evergreend.h
b/drivers/gpu/drm/radeon/evergreend.h
index fc40e0c..f37e91e 100644
--- a/drivers/gpu/drm/radeon/evergreend.h
+++ b/drivers/gpu/drm/radeon/evergreend.h
@@ -64,6 +64,8 @@
#define GB_BACKEND_MAP 0x98FC
#define DMIF_ADDR_CONFIG 0xBD4
#define HDP_ADDR_CONFIG0x2F48
+#define HDP_MISC_CNTL 0x2F4C
+#defineHDP_FLUSH_INVALIDATE_CACHE (1 << 0)
#defineCC_SYS_RB_BACKEND_DISABLE 0x3F88
#defineGC_USER_RB_BACKEND_DISABLE 0x9B7C
--
1.7.1.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 37368] Server crashes with "failed to map pixmap: -12"
https://bugs.freedesktop.org/show_bug.cgi?id=37368 Nicos Gollan changed: What|Removed |Added Attachment #46907|application/x-trash |text/plain mime type|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36812] GPU lockup in Team Fortress 2
https://bugs.freedesktop.org/show_bug.cgi?id=36812 --- Comment #5 from Sven Arvidsson 2011-05-19 11:16:03 PDT --- With nopt it's even worse, I get a GPU hang and this error on the terminal "EE r600_pipe.c:429 r600_get_param - r600: unknown param 45" when I try to start the game. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
https://bugzilla.kernel.org/show_bug.cgi?id=35192 --- Comment #6 from Stratos Psomadakis 2011-05-19 18:15:57 --- The only problem now seems to be with commit 737a3b, which should be reverted, as it breaks radeon with a non-modular kernel (because of __init_or_module). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote: > (add LKML) > > On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote: > > Hi > > > > Last known good: 2.6.38 > > Failing kernel: 2.6.39-rc3 > > Subsystem: Intel graphics driver. > > > > Description: > > PC should work with 1440x900 resolution. But console (and after) X Window > > start work with 1024x768. > > > > I attach dmesg and Xorg.0.log with drm.debug=14 log_buf_len=16M options: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/ > > > > seems that driver cannot detect resolution higher than 1024x768. > > > > Also I boot kernel replace "i915.modeset=1" with "nomodeset" option: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/ > > > > But then X Window fails to start and got message: "(EE) No devices > > detected." > > > > Config for 2.6.39-rc3: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3 > > > > Best regards > > Device: > 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express > Integrated Graphics Controller (rev 02) Reported on: https://bugzilla.kernel.org/show_bug.cgi?id=34002 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic developers might be interested in the problem? -- Maciej Rutecki http://www.maciek.unixy.pl ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #1 from Rogério Brito 2011-05-19 20:34:40 --- Just for the record, I can provide further messages of these: this is as reproducible as I like. In fact, I am now able to reproduce it with kernel 2.6.38 if I boot the iBook G4 with the options: "video=radeonfb:off radeon.agpmode=-1 radeon.modeset=1" and play a video with mplayer. If, OTOH, I leave off the KMS, then I don't get the GPU lockups that I reported. Anyway, things are *way* better with 2.6.38 than with 2.6.39, as with 2.6.39 the kernel doesn't even get the colors correctly---everything that should be red becomes blue and so forth (any kind of endianness problem?). I am attaching here another stacktrace, in case it helps. Regards, Rogério Brito. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #2 from Rogério Brito 2011-05-19 20:36:24 --- Created an attachment (id=58602) --> (https://bugzilla.kernel.org/attachment.cgi?id=58602) A dmesg log from 2.6.39-rc7 showing problems. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #3 from Rogério Brito 2011-05-19 20:37:08 --- Created an attachment (id=58612) --> (https://bugzilla.kernel.org/attachment.cgi?id=58612) The log of X with the 2.6.39-rc7 kernel -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #4 from Rogério Brito 2011-05-19 20:38:14 --- Created an attachment (id=58622) --> (https://bugzilla.kernel.org/attachment.cgi?id=58622) A dmesg log with 2.6.38 kernel Please, notice the GPU hang with kernel 2.6.38. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #5 from Rogério Brito 2011-05-19 20:38:56 --- Created an attachment (id=58632) --> (https://bugzilla.kernel.org/attachment.cgi?id=58632) Log from X with the kernel 2.6.38 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] agp/uninorth: Fix lockups with radeon KMS and >1x.
On Thu, 2011-05-19 at 16:08 +0200, Michel Dänzer wrote:
> From: Michel Dänzer
>
> This was based on a description by Ben Herrenschmidt:
>
> > I've removed that SBA reset from the normal TLB invalidation path and
> > left it only once after turning AGP on.
>
> About six months ago, he said:
>
> > I did it a bit differently, but yeah, you get the idea. I'm doing a
> > patch series so don't bother pushing things too hard yet.
>
> But I haven't seen anything from him about this since then, and people are
> regularly hitting these lockups, so here we are...
>
> Signed-off-by: Michel Dänzer
Oops. I do have a pile of patches, but I never got something "stable"
enough and got distracted by more important stuff. Dave, please merge
this for now.
Acked-by: Benjamin Herrenschmidt
Thanks !
Cheers,
Ben.
> ---
> drivers/char/agp/uninorth-agp.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/char/agp/uninorth-agp.c b/drivers/char/agp/uninorth-agp.c
> index 47c2218..55af723 100644
> --- a/drivers/char/agp/uninorth-agp.c
> +++ b/drivers/char/agp/uninorth-agp.c
> @@ -80,7 +80,7 @@ static void uninorth_tlbflush(struct agp_memory *mem)
> ctrl | UNI_N_CFG_GART_INVAL);
> pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL, ctrl);
>
> - if (uninorth_rev <= 0x30) {
> + if (!mem && uninorth_rev <= 0x30) {
> pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
> ctrl | UNI_N_CFG_GART_2xRESET);
> pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35472] New: [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 Summary: [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730) Product: Drivers Version: 2.5 Kernel Version: 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-...@kernel-bugs.osdl.org ReportedBy: virtuous...@gmail.com Regression: Yes with 2.6.37 it's all OK but since 2.6.38 from very framebuffer initialization screen is filled with dense grey lines looking like ugly grid. also per every 3cm on my 1920x1080/23' screen there is a distinctive whitish vertical line. when X try to startup i can see cursor and can move it around for a while (that grey grid is there too) but kdm does not starting up and GPU locks up. it is the same with 2.6.39. here is `dmesg|grep drm` for 2.6.39: [0.462282] [drm] Initialized drm 1.1.0 20060810 [0.462315] [drm] radeon defaulting to kernel modesetting. [0.462337] [drm] radeon kernel modesetting enabled. [0.462575] [drm] initializing kernel modesetting (RV770 0x1002:0x944E). [0.462608] [drm] register mmio base: 0xFDFE [0.462630] [drm] register mmio size: 65536 [0.463313] [drm] Detected VRAM RAM=512M, BAR=256M [0.463343] [drm] RAM width 128bits DDR [0.463526] [drm] radeon: 512M of VRAM memory ready [0.463549] [drm] radeon: 512M of GTT memory ready. [0.463571] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [0.463594] [drm] Driver supports precise vblank timestamp query. [0.463708] [drm] radeon: irq initialized. [0.463733] [drm] GART: num cpu pages 131072, num gpu pages 131072 [0.465260] [drm] Loading RV770 Microcode [0.512429] [drm] ring test succeeded in 1 usecs [0.512544] [drm] radeon: ib pool ready. [0.512584] [drm] ib test succeeded in 0 usecs [0.512609] [drm] Enabling audio support [0.512805] [drm] Radeon Display Connectors [0.512827] [drm] Connector 0: [0.512847] [drm] DVI-I [0.512868] [drm] HPD2 [0.512889] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [0.512915] [drm] Encoders: [0.512936] [drm] DFP1: INTERNAL_UNIPHY [0.512957] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [0.512979] [drm] Connector 1: [0.512999] [drm] DIN [0.513028] [drm] Encoders: [0.513049] [drm] TV1: INTERNAL_KLDSCP_DAC2 [0.513070] [drm] Connector 2: [0.513091] [drm] DVI-I [0.513111] [drm] HPD1 [0.513132] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [0.513158] [drm] Encoders: [0.513179] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [0.513201] [drm] DFP2: INTERNAL_KLDSCP_LVTMA [0.577285] [drm] Internal thermal controller without fan control [0.578307] [drm] radeon: power management initialized [0.657478] [drm] fb mappable at 0xD0142000 [0.657500] [drm] vram apper at 0xD000 [0.657521] [drm] size 8294400 [0.657541] [drm] fb depth is 24 [0.657562] [drm]pitch is 7680 [0.657632] fbcon: radeondrmfb (fb0) is primary device [1.073319] fb0: radeondrmfb frame buffer device [1.073349] drm: registered panic notifier [1.073379] [drm] Initialized radeon 2.9.0 20080528 for :01:00.0 on minor 0 [ 252.565034] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 252.565102] [] ? drm_ioctl+0x394/0x450 [ 252.565145] [drm] Disabling audio support [ 252.731618] [drm] ring test succeeded in 1 usecs [ 252.908838] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 252.908841] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 267.523039] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 267.523107] [] ? drm_ioctl+0x394/0x450 [ 268.216464] [drm] ring test succeeded in 1 usecs [ 268.216473] [drm] ib test succeeded in 1 usecs [ 268.216475] [drm] Enabling audio support [ 273.719044] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 273.719114] [] ? drm_ioctl+0x394/0x450 [ 273.719159] [drm] Disabling audio support [ 274.411517] [drm] ring test succeeded in 1 usecs [ 274.588784] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 274.588787] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 290.090036] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 290.090103] [] ? drm_ioctl+0x394/0x450 [ 290.779828] [drm] ring test succeeded in 1 usecs [ 290.957091] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 290.957094] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 306.459037] WARNING: at drivers/gpu/drm/radeon/radeo
[Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 --- Comment #1 from Sergey Kondakov 2011-05-20 04:05:41 --- Created an attachment (id=58692) --> (https://bugzilla.kernel.org/attachment.cgi?id=58692) full dmesg from 2.6.39 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 --- Comment #2 from Sergey Kondakov 2011-05-20 04:08:40 --- Created an attachment (id=58702) --> (https://bugzilla.kernel.org/attachment.cgi?id=58702) .config from 2.6.39 created via `make oldconfig` and based on .config from working 2.6.37 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 Alex Deucher changed: What|Removed |Added CC||alexdeuc...@gmail.com --- Comment #3 from Alex Deucher 2011-05-20 04:12:58 --- Can you bisect? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 --- Comment #4 from Sergey Kondakov 2011-05-20 04:15:58 --- Created an attachment (id=58712) --> (https://bugzilla.kernel.org/attachment.cgi?id=58712) full dmesg from 2.6.37 dmesg from working kernel -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
https://bugzilla.kernel.org/show_bug.cgi?id=35472 --- Comment #5 from Sergey Kondakov 2011-05-20 05:01:00 --- you mean like taking kernel's git and bisecting entire commit range between 2.6.37 and 2.6.38 (or, more likely, 2.6.37.4 and 2.6.38-rc4 which i think i've tested) while rebooting every time ? i'm not sure if i up for it but if i am then it may take quite a while. meanwhile i will also try to get a photograph of the screen. but also not today, probably. any easily gathered info, however, i can drop anytime. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list dri-de...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #16 from Karesz L. 2011-05-19 23:11:47 PDT --- Created an attachment (id=46931) --> (https://bugs.freedesktop.org/attachment.cgi?id=46931) A failed resume's recurring log- Fedora 15 beta I've made a bootable live Fedora 15 beta USB, booted, and noticed, that gnome3 had only a suspend in it's "live user options" menu, so I clicked it. It suspended correctly, as expected. Then I pressed the power button, to see whether it resumes, or not. It doesn't, but the screen got backlit, and this message kept running on the screen. Pressing ctrl+alt+F3 stopped it, and I was able to take a photo of it (don't know how to get this message in text form), and I enhanced it a little. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. ___ dri-devel mailing list dri-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver.
>>>
>>> Description:
>>> PC should work with 1440x900 resolution. But console (and after) X Window
>>> start work with 1024x768.
>>>
>>> I attach dmesg and Xorg.0.log with drm.debug=14 log_buf_len=16M options:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/
>>>
>>> seems that driver cannot detect resolution higher than 1024x768.
>>>
>>> Also I boot kernel replace "i915.modeset=1" with "nomodeset" option:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/
>>>
>>> But then X Window fails to start and got message: "(EE) No devices
>>> detected."
>>>
>>> Config for 2.6.39-rc3:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3
>>>
>>> Best regards
>>
>> Device:
>> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
>> Integrated Graphics Controller (rev 02)
>
> Reported on:
> https://bugzilla.kernel.org/show_bug.cgi?id=34002
>
> 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic
> developers might be interested in the problem?
I had a problem similar to this, beginning with 2.6.37 (2.6.36 was okay).
It turned out to be that newer kernels were detecting the LVDS (LCD panel)
interface from the chipset, event though nothing was attached to that interface.
So GNOME would come up at 1024x768 (max the LVDS supported, I guess).
I initially worked around it by going into the GNOME -> Preferences -> Monitors,
and disabling the LVDS device there, in favour of the 1920x1200 "VGA" device I
use.
Later, I hacked my kernel to just ignore the LVDS completely:
--- linux/drivers/gpu/drm/i915/intel_lvds.c.orig2011-05-09
22:33:54.0 -0400
+++ linux/drivers/gpu/drm/i915/intel_lvds.c 2011-05-17 23:00:40.829773525
-0400
@@ -841,6 +841,7 @@
*/
bool intel_lvds_init(struct drm_device *dev)
{
+if (0) {
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_lvds *intel_lvds;
struct intel_encoder *intel_encoder;
@@ -1041,5 +1042,6 @@
drm_encoder_cleanup(encoder);
kfree(intel_lvds);
kfree(intel_connector);
+}
return false;
}
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
Commit 7f58aabc36901 causes boot hang
Sorry for the late test; my laptop didn't need rebooting. But when I installed a recent kernel (-rc7, actually; I just missed the .39 release), it hung hard (no caps-lock or Alt-SysRq) partway through boot after printing: Linux agpgart interface v0.103 agpgart-intel :00:00.0: Intel 945GM Chipset agpgart-intel :00:00.0: detected gtt size: 262144K total, 262144K mappable agpgart-intel :00:00.0: detected 8192K stolen memory agpgart-intel :00:00.0: AGP aperture is 256M @ 0xd000 [drm] Initialized drm 1.1.0 20060810 i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 i915 :00:02.0: setting latency timer to 64 [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [drm] Driver supports precise vblank timestamp query. composite sync not supported vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [drm] initialized overlay support composite sync not supported fbcon: inteldrmfb (fb0) is primary device Console: switching to colour frame buffer device 180x56 fb0: inteldrmfb frame buffer device drm: registered panic notifier [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 loop: module loaded [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 4 [i915 gmbus dpc] After some bisecting, I found that reverting 7f58aabc36901 (drm/i915: Reset GMBUS controller after NAK) resulted in a successful boot, which replaced the above hang with: [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 loop: module loaded [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled] ata_piix :00:1f.2: version 2.13 ata_piix :00:1f.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17 ata_piix :00:1f.2: MAP [ P0 P2 IDE IDE ] ata_piix :00:1f.2: setting latency timer to 64 scsi0 : ata_piix scsi1 : ata_piix ata1: SATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xbfa0 irq 14 ata2: PATA max UDMA/100 cmd 0x170 ctl 0x376 bmdma 0xbfa8 irq 15 b44 :02:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 [etc...] The PCI devices on this laptop (Dell Inspirion E1405) are: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 01) 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 01) 00:1c.1 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 2 [8086:27d2] (rev 01) 00:1c.3 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 4 [8086:27d6] (rev 01) 00:1d.0 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 [8086:27c8] (rev 01) 00:1d.1 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 [8086:27c9] (rev 01) 00:1d.2 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 [8086:27ca] (rev 01) 00:1d.3 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 [8086:27cb] (rev 01) 00:1d.7 USB Controller [0c03]: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller [8086:27cc] (rev 01) 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01) 00:1f.2 IDE interface [0101]:
[PATCH 0/4] cayman acceleration fixes so far
These 4 patches allow me to run piglit to ~1460/1660 tests with my port of r600g to cayman. I still have to track down why the DDX composite accel isn't working though. I suspect we'll need a cayman accel is working flag as well. Dave.
[PATCH 1/4] drm/radeon/kms: fix incorrect comparison in cayman setup code.
From: Dave Airlie This was leading to a bogus value being programmed to the backend routing register. Signed-off-by: Dave Airlie --- drivers/gpu/drm/radeon/ni.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/radeon/ni.c b/drivers/gpu/drm/radeon/ni.c index 3d8a763..a38d745 100644 --- a/drivers/gpu/drm/radeon/ni.c +++ b/drivers/gpu/drm/radeon/ni.c @@ -417,7 +417,7 @@ static u32 cayman_get_tile_pipe_to_backend_map(struct radeon_device *rdev, num_shader_engines = 1; if (num_shader_engines > rdev->config.cayman.max_shader_engines) num_shader_engines = rdev->config.cayman.max_shader_engines; - if (num_backends_per_asic > num_shader_engines) + if (num_backends_per_asic < num_shader_engines) num_backends_per_asic = num_shader_engines; if (num_backends_per_asic > (rdev->config.cayman.max_backends_per_se * num_shader_engines)) num_backends_per_asic = rdev->config.cayman.max_backends_per_se * num_shader_engines; -- 1.7.1
[PATCH 2/4] drm/radeon/kms: fix tile_config value reported to userspace on cayman.
From: Dave Airlie cayman is reporting the wrong tile config value to userspace, this causes piglit mipmap generation tests to fail. Signed-off-by: Dave Airlie --- drivers/gpu/drm/radeon/ni.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/radeon/ni.c b/drivers/gpu/drm/radeon/ni.c index a38d745..99f4f40 100644 --- a/drivers/gpu/drm/radeon/ni.c +++ b/drivers/gpu/drm/radeon/ni.c @@ -829,7 +829,7 @@ static void cayman_gpu_init(struct radeon_device *rdev) rdev->config.cayman.tile_config |= ((mc_arb_ramcfg & NOOFBANK_MASK) >> NOOFBANK_SHIFT) << 4; rdev->config.cayman.tile_config |= - (gb_addr_config & PIPE_INTERLEAVE_SIZE_MASK) >> PIPE_INTERLEAVE_SIZE_SHIFT; + ((gb_addr_config & PIPE_INTERLEAVE_SIZE_MASK) >> PIPE_INTERLEAVE_SIZE_SHIFT) << 8; rdev->config.cayman.tile_config |= ((gb_addr_config & ROW_SIZE_MASK) >> ROW_SIZE_SHIFT) << 12; -- 1.7.1
[PATCH 3/4] drm/radeon/cayman: setup hdp to invalidate and flush when asked
From: Dave Airlie On cayman we need to set the bit to cause HDP flushes to invalidate the HDP cache also. Signed-off-by: Dave Airlie --- drivers/gpu/drm/radeon/ni.c |4 drivers/gpu/drm/radeon/nid.h |2 ++ 2 files changed, 6 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/ni.c b/drivers/gpu/drm/radeon/ni.c index 99f4f40..b205ba1 100644 --- a/drivers/gpu/drm/radeon/ni.c +++ b/drivers/gpu/drm/radeon/ni.c @@ -931,6 +931,10 @@ static void cayman_gpu_init(struct radeon_device *rdev) WREG32(CB_PERF_CTR3_SEL_0, 0); WREG32(CB_PERF_CTR3_SEL_1, 0); + tmp = RREG32(HDP_MISC_CNTL); + tmp |= HDP_FLUSH_INVALIDATE_CACHE; + WREG32(HDP_MISC_CNTL, tmp); + hdp_host_path_cntl = RREG32(HDP_HOST_PATH_CNTL); WREG32(HDP_HOST_PATH_CNTL, hdp_host_path_cntl); diff --git a/drivers/gpu/drm/radeon/nid.h b/drivers/gpu/drm/radeon/nid.h index 0f9a08b..b2088c1 100644 --- a/drivers/gpu/drm/radeon/nid.h +++ b/drivers/gpu/drm/radeon/nid.h @@ -136,6 +136,8 @@ #defineHDP_NONSURFACE_INFO 0x2C08 #defineHDP_NONSURFACE_SIZE 0x2C0C #define HDP_ADDR_CONFIG0x2F48 +#define HDP_MISC_CNTL 0x2F4C +#defineHDP_FLUSH_INVALIDATE_CACHE (1 << 0) #defineCC_SYS_RB_BACKEND_DISABLE 0x3F88 #defineGC_USER_SYS_RB_BACKEND_DISABLE 0x3F8C -- 1.7.1
[PATCH 4/4] drm/radeon/kms: add wait idle ioctl for eg->cayman
From: Dave Airlie
None of the latest GPUs had this hooked up, this is necessary for
correct operation in a lot of cases, however we should test this on a few
GPUs in these families as we've had problems in this area before.
Signed-off-by: Dave Airlie
---
drivers/gpu/drm/radeon/radeon_asic.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/gpu/drm/radeon/radeon_asic.c
b/drivers/gpu/drm/radeon/radeon_asic.c
index ca57619..d948265 100644
--- a/drivers/gpu/drm/radeon/radeon_asic.c
+++ b/drivers/gpu/drm/radeon/radeon_asic.c
@@ -782,6 +782,7 @@ static struct radeon_asic evergreen_asic = {
.hpd_fini = &evergreen_hpd_fini,
.hpd_sense = &evergreen_hpd_sense,
.hpd_set_polarity = &evergreen_hpd_set_polarity,
+ .ioctl_wait_idle = r600_ioctl_wait_idle,
.gui_idle = &r600_gui_idle,
.pm_misc = &evergreen_pm_misc,
.pm_prepare = &evergreen_pm_prepare,
@@ -828,6 +829,7 @@ static struct radeon_asic sumo_asic = {
.hpd_fini = &evergreen_hpd_fini,
.hpd_sense = &evergreen_hpd_sense,
.hpd_set_polarity = &evergreen_hpd_set_polarity,
+ .ioctl_wait_idle = r600_ioctl_wait_idle,
.gui_idle = &r600_gui_idle,
.pm_misc = &evergreen_pm_misc,
.pm_prepare = &evergreen_pm_prepare,
@@ -874,6 +876,7 @@ static struct radeon_asic btc_asic = {
.hpd_fini = &evergreen_hpd_fini,
.hpd_sense = &evergreen_hpd_sense,
.hpd_set_polarity = &evergreen_hpd_set_polarity,
+ .ioctl_wait_idle = r600_ioctl_wait_idle,
.gui_idle = &r600_gui_idle,
.pm_misc = &evergreen_pm_misc,
.pm_prepare = &evergreen_pm_prepare,
@@ -920,6 +923,7 @@ static struct radeon_asic cayman_asic = {
.hpd_fini = &evergreen_hpd_fini,
.hpd_sense = &evergreen_hpd_sense,
.hpd_set_polarity = &evergreen_hpd_set_polarity,
+ .ioctl_wait_idle = r600_ioctl_wait_idle,
.gui_idle = &r600_gui_idle,
.pm_misc = &evergreen_pm_misc,
.pm_prepare = &evergreen_pm_prepare,
--
1.7.1
[PATCH 0/4] cayman acceleration fixes so far
On Thu, May 19, 2011 at 12:14 AM, Dave Airlie wrote: > These 4 patches allow me to run piglit to ~1460/1660 tests with my port > of r600g to cayman. I still have to track down why the DDX composite accel > isn't working though. I suspect we'll need a cayman accel is working flag > as well. For the series, Reviewed-by: Alex Deucher > > Dave. > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel >
+ drivers-base-platformc-dont-mark-platform_device_register_resndata-as-__init_or_module.patch added to -mm tree
Hello,
[added some people involved in the thread
http://thread.gmane.org/gmane.linux.ports.ppc.embedded/41996 to Cc:]
On Wed, May 18, 2011 at 02:57:36PM -0700, akpm at linux-foundation.org wrote:
>
> The patch titled
> drivers/base/platform.c: don't mark platform_device_register_resndata()
> as __init_or_module
> has been added to the -mm tree. Its filename is
>
> drivers-base-platformc-dont-mark-platform_device_register_resndata-as-__init_or_module.patch
>
> Before you just go and hit "reply", please:
>a) Consider who else should be cc'ed
>b) Prefer to cc a suitable mailing list as well
>c) Ideally: find the original patch on the mailing list and do a
> reply-to-all to that, adding suitable additional cc's
>
> *** Remember to use Documentation/SubmitChecklist when testing your code ***
>
> See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
> out what to do about this
>
> The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
>
> --
> Subject: drivers/base/platform.c: don't mark
> platform_device_register_resndata() as __init_or_module
> From: Andrew Morton
>
> This reverts 737a3bb9416ce2a7c7a4 ("Driver core: move platform device
> creation helpers to .init.text (if MODULE=n)"). That patch assumed that
> platform_device_register_resndata() is only ever called from __init code
> but that isn't true in the case ioctl->drm_ioctl->radeon_cp_init().
>
> Addresses https://bugzilla.kernel.org/show_bug.cgi?id=35192
I'm not sure that the things that radeon_cp_init does are sane. Maybe
add a comment that it is the only known stopper to make
platform_device_register_resndata __init_or_module and a similar comment
to platform_device_register_resndata itself?
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig|
Industrial Linux Solutions | http://www.pengutronix.de/ |
[Bug 34252] Unexpected behaviour when switching video cards with vga_switcheroo
https://bugzilla.kernel.org/show_bug.cgi?id=34252 --- Comment #13 from Florian Mickler 2011-05-19 07:21:09 --- A patch referencing this bug report has been merged in v2.6.39: commit a67b8887ced9d54cab7759bdb19deafed37481eb Author: Florian Mickler Date: Sun May 15 16:32:50 2011 +0200 vga_switcheroo: don't toggle-switch devices -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34252] Unexpected behaviour when switching video cards with vga_switcheroo
https://bugzilla.kernel.org/show_bug.cgi?id=34252 Florian Mickler changed: What|Removed |Added Status|RESOLVED|CLOSED Resolution|PATCH_ALREADY_AVAILABLE |CODE_FIX -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
PROBLEM: i915 regression between 2.6.39-rc6 and 2.6.39-rc7
On Wed, 18 May 2011 20:15:05 +0200, Eric Leblond wrote: > I confirm that it is working fine when enabling semaphore. Thanks a lot > for the workaround, it is a pleasure to have a real laptop again ;) And, we'll keep trying to make it work without per-laptop configuration... -- keith.packard at intel.com -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20110519/15bc1950/attachment.pgp>
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #7 from shirk at bitspin.org 2011-05-19 03:30:41 PDT --- (In reply to comment #3) > I'm booting an imac12,2 in UEFI mode (need a "Run EFI in physical mode" patch > before doing so), > here's how : > 1) boot from latest ubuntu live CD (hold alt, or c, at boot) > 2) dump the bios >dd if=/dev/mem of=vbios.bin bs=65536 skip=12 count=1 > 3) move it to your partition's /lib/firmware/radeon/vbios.bin > 4) use your patch, but move the radeon_read_bios_from_firmware >call before all other calls to get the bios (force using vbios.bin) > Thats exactly what I did on my MBP however the screen flicker remains.. I'm pretty sure the BIOS is valid (dmesg identifies it as ATOM BIOS: Apple) and strings revealed data like "Whistler Pro" which IIRC is the type code used by the Radeon HD 6xxx series. Since J?r?my has a working setup with GPU acceleration I can only suspect a problem in the microcode. iMac12,2 has a Radeon HD 6970M which utilizes the CAYMAN microcode while my Radeon HD6750M is using TURKS. So I'm stuck with working but non-accelerated radeondrmfb. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #13 from Karesz L. 2011-05-19 03:39:03 PDT --- Any news on this? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #14 from Karesz L. 2011-05-19 03:49:36 PDT --- I'm a little confused, https://bugs.freedesktop.org/attachment.cgi?id=45729";>this Xorg.0.log is marked as a patch, but I'm not really sure, if it is. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 Michel D?nzer changed: What|Removed |Added Attachment #45729|1 |0 is patch|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
Summary of the V4L2 discussions during LDS - was: Re: Embedded Linux memory management interest group list
Em 18-05-2011 16:46, Sakari Ailus escreveu: > Hans Verkuil wrote: >> Note that many video receivers cannot stall. You can't tell them to wait >> until >> the last buffer finished processing. This is different from some/most? >> sensors. > > Not even image sensors. They just output the frame data; if the receiver > runs out of buffers the data is just lost. And if any part of the frame > is lost, there's no use for other parts of it either. But that's > something the receiver must handle, i.e. discard the data and increment > frame number (field_count in v4l2_buffer). > > The interfaces used by image sensors, be they parallel or serial, do not > provide means to inform the sensor that the receiver has run out of > buffer space. These interfaces are just unidirectional. Well, it depends on how the hardware works, really. On most (all?) designs, the IP block responsible to receive data from a sensor (or to transmit data, on an output device) is capable of generating an IRQ to notify the OS that a framebuffer was filled. So, the V4L driver can mark that buffer as finished and remove it from the list of the queued buffers. Although the current API's don't allow to create a new buffer if the list is empty, it may actually make sense to allow kernel to dynamically create a new buffer, warranting that the sensor (or receiver) will never run out of buffers under normal usage. Of course, the maximum number of buffers should be specified, to avoid having an unacceptable delay. On such case, the frame will end by being discarded. It makes sense to provide a way to report userspace if this happens. Mauro.
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #8 from J?r?my Lal 2011-05-19 05:34:40 PDT --- (In reply to comment #7) > Since J?r?my has a working setup with GPU acceleration I can only suspect a > problem in the microcode. iMac12,2 has a Radeon HD 6970M which utilizes the > CAYMAN microcode while my Radeon HD6750M is using TURKS. Mine is [1002:6740] : [9.285052] [drm] Loading TURKS Microcode which kernel version are you using ? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 32402] Oops associated with radeon_unpin_work_func
https://bugzilla.kernel.org/show_bug.cgi?id=32402 Stuart Foster changed: What|Removed |Added CC||smf.linux at ntlworld.com Kernel Version|2.6.38.2|2.6.39 --- Comment #13 from Stuart Foster 2011-05-19 13:04:45 --- Just a quick update to report that the fault is also present in the 2.6.39 kernel. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 26891] Radeon KMS on Macs with EFI boot
https://bugs.freedesktop.org/show_bug.cgi?id=26891 --- Comment #9 from shirk at bitspin.org 2011-05-19 06:22:52 PDT --- (In reply to comment #8) > Mine is [1002:6740] : > [9.285052] [drm] Loading TURKS Microcode > > which kernel version are you using ? 2.6.39-rc7-00215-g194a526 git head with local patches applied (phys-efi, radeon-firmware hack) I'm running Gentoo linux amd64. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #15 from ??? ?. 2011-05-19 07:00:19 PDT --- No Karesz, it is not a patch. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
https://bugzilla.kernel.org/show_bug.cgi?id=35192 J?r?me Glisse changed: What|Removed |Added CC||glisse at freedesktop.org --- Comment #5 from J?r?me Glisse 2011-05-19 14:05:02 --- So is the bug still revealent ? If so what is the bt now ? -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[PATCH] agp/uninorth: Fix lockups with radeon KMS and >1x.
From: Michel D?nzer
This was based on a description by Ben Herrenschmidt:
> I've removed that SBA reset from the normal TLB invalidation path and
> left it only once after turning AGP on.
About six months ago, he said:
> I did it a bit differently, but yeah, you get the idea. I'm doing a
> patch series so don't bother pushing things too hard yet.
But I haven't seen anything from him about this since then, and people are
regularly hitting these lockups, so here we are...
Signed-off-by: Michel D?nzer
---
drivers/char/agp/uninorth-agp.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/char/agp/uninorth-agp.c b/drivers/char/agp/uninorth-agp.c
index 47c2218..55af723 100644
--- a/drivers/char/agp/uninorth-agp.c
+++ b/drivers/char/agp/uninorth-agp.c
@@ -80,7 +80,7 @@ static void uninorth_tlbflush(struct agp_memory *mem)
ctrl | UNI_N_CFG_GART_INVAL);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL, ctrl);
- if (uninorth_rev <= 0x30) {
+ if (!mem && uninorth_rev <= 0x30) {
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
ctrl | UNI_N_CFG_GART_2xRESET);
pci_write_config_dword(agp_bridge->dev, UNI_N_CFG_GART_CTRL,
--
1.7.5.1
[Bug 37368] New: Server crashes with "failed to map pixmap: -12"
https://bugs.freedesktop.org/show_bug.cgi?id=37368 Summary: Server crashes with "failed to map pixmap: -12" Product: DRI Version: XOrg CVS Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: DRM/Radeon AssignedTo: dri-devel at lists.freedesktop.org ReportedBy: gtdev at spearhead.de Created an attachment (id=46907) --> (https://bugs.freedesktop.org/attachment.cgi?id=46907) Server log with crash info Every now and then, the X server will crash on my machine and restart to kdm. I have never seen it happen live so far, it always happened when I was away from the machine for some time. System is Debian unstable, xserver-xorg-core package version is 1.10.1-2, but the problem has been occuring for some months now. In the server log, I find: == failed to map pixmap: -12 Backtrace: 0: /usr/bin/X (xorg_backtrace+0x28) [0x4a38b8] 1: /usr/bin/X (0x40+0x646e9) [0x4646e9] 2: /lib/libpthread.so.0 (0x7f45b8dd2000+0xf020) [0x7f45b8de1020] 3: /lib/libc.so.6 (0x7f45b7aed000+0x84b30) [0x7f45b7b71b30] 4: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x6436) [0x7f45b5611436] 5: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x8f92) [0x7f45b5613f92] 6: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x12355) [0x7f45b561d355] 7: /usr/lib/xorg/modules/libexa.so (0x7f45b560b000+0x9b31) [0x7f45b5614b31] 8: /usr/bin/X (0x40+0xe0034) [0x4e0034] 9: /usr/bin/X (0x40+0x2e283) [0x42e283] 10: /usr/bin/X (0x40+0x31731) [0x431731] 11: /usr/bin/X (0x40+0x257de) [0x4257de] 12: /lib/libc.so.6 (__libc_start_main+0xfd) [0x7f45b7b0bead] 13: /usr/bin/X (0x40+0x25389) [0x425389] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. == A full server log is attached. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[PATCH] drm/radeon/evergreen/btc/fusion: setup hdp to invalidate and flush when asked
This needs to be explicitly set on btc. It's set by default
on evergreen/fusion, so it fine to just unconditionally enable it for
all chips.
Signed-off-by: Alex Deucher
---
drivers/gpu/drm/radeon/evergreen.c |6 +-
drivers/gpu/drm/radeon/evergreend.h |2 ++
2 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/drivers/gpu/drm/radeon/evergreen.c
b/drivers/gpu/drm/radeon/evergreen.c
index c98abd5..9f907f7 100644
--- a/drivers/gpu/drm/radeon/evergreen.c
+++ b/drivers/gpu/drm/radeon/evergreen.c
@@ -1582,7 +1582,7 @@ static void evergreen_gpu_init(struct radeon_device *rdev)
u32 sq_stack_resource_mgmt_2;
u32 sq_stack_resource_mgmt_3;
u32 vgt_cache_invalidation;
- u32 hdp_host_path_cntl;
+ u32 hdp_host_path_cntl, tmp;
int i, j, num_shader_engines, ps_thread_count;
switch (rdev->family) {
@@ -2199,6 +2199,10 @@ static void evergreen_gpu_init(struct radeon_device
*rdev)
for (i = SQ_ALU_CONST_BUFFER_SIZE_HS_0; i < 0x29000; i += 4)
WREG32(i, 0);
+ tmp = RREG32(HDP_MISC_CNTL);
+ tmp |= HDP_FLUSH_INVALIDATE_CACHE;
+ WREG32(HDP_MISC_CNTL, tmp);
+
hdp_host_path_cntl = RREG32(HDP_HOST_PATH_CNTL);
WREG32(HDP_HOST_PATH_CNTL, hdp_host_path_cntl);
diff --git a/drivers/gpu/drm/radeon/evergreend.h
b/drivers/gpu/drm/radeon/evergreend.h
index fc40e0c..f37e91e 100644
--- a/drivers/gpu/drm/radeon/evergreend.h
+++ b/drivers/gpu/drm/radeon/evergreend.h
@@ -64,6 +64,8 @@
#define GB_BACKEND_MAP 0x98FC
#define DMIF_ADDR_CONFIG 0xBD4
#define HDP_ADDR_CONFIG0x2F48
+#define HDP_MISC_CNTL 0x2F4C
+#defineHDP_FLUSH_INVALIDATE_CACHE (1 << 0)
#defineCC_SYS_RB_BACKEND_DISABLE 0x3F88
#defineGC_USER_RB_BACKEND_DISABLE 0x9B7C
--
1.7.1.1
[Bug 37368] Server crashes with "failed to map pixmap: -12"
https://bugs.freedesktop.org/show_bug.cgi?id=37368 Nicos Gollan changed: What|Removed |Added Attachment #46907|application/x-trash |text/plain mime type|| -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 36812] GPU lockup in Team Fortress 2
https://bugs.freedesktop.org/show_bug.cgi?id=36812 --- Comment #5 from Sven Arvidsson 2011-05-19 11:16:03 PDT --- With nopt it's even worse, I get a GPU hang and this error on the terminal "EE r600_pipe.c:429 r600_get_param - r600: unknown param 45" when I try to start the game. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[Bug 35192] BUG() in radeon driver with ATI Technologies Inc RV515 [Radeon X1300]
https://bugzilla.kernel.org/show_bug.cgi?id=35192 --- Comment #6 from Stratos Psomadakis 2011-05-19 18:15:57 --- The only problem now seems to be with commit 737a3b, which should be reverted, as it breaks radeon with a non-modular kernel (because of __init_or_module). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote: > (add LKML) > > On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote: > > Hi > > > > Last known good: 2.6.38 > > Failing kernel: 2.6.39-rc3 > > Subsystem: Intel graphics driver. > > > > Description: > > PC should work with 1440x900 resolution. But console (and after) X Window > > start work with 1024x768. > > > > I attach dmesg and Xorg.0.log with drm.debug=14 log_buf_len=16M options: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/ > > > > seems that driver cannot detect resolution higher than 1024x768. > > > > Also I boot kernel replace "i915.modeset=1" with "nomodeset" option: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/ > > > > But then X Window fails to start and got message: "(EE) No devices > > detected." > > > > Config for 2.6.39-rc3: > > http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3 > > > > Best regards > > Device: > 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express > Integrated Graphics Controller (rev 02) Reported on: https://bugzilla.kernel.org/show_bug.cgi?id=34002 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic developers might be interested in the problem? -- Maciej Rutecki http://www.maciek.unixy.pl
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #1 from Rog?rio Brito 2011-05-19 20:34:40 --- Just for the record, I can provide further messages of these: this is as reproducible as I like. In fact, I am now able to reproduce it with kernel 2.6.38 if I boot the iBook G4 with the options: "video=radeonfb:off radeon.agpmode=-1 radeon.modeset=1" and play a video with mplayer. If, OTOH, I leave off the KMS, then I don't get the GPU lockups that I reported. Anyway, things are *way* better with 2.6.38 than with 2.6.39, as with 2.6.39 the kernel doesn't even get the colors correctly---everything that should be red becomes blue and so forth (any kind of endianness problem?). I am attaching here another stacktrace, in case it helps. Regards, Rog?rio Brito. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #2 from Rog?rio Brito 2011-05-19 20:36:24 --- Created an attachment (id=58602) --> (https://bugzilla.kernel.org/attachment.cgi?id=58602) A dmesg log from 2.6.39-rc7 showing problems. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #3 from Rog?rio Brito 2011-05-19 20:37:08 --- Created an attachment (id=58612) --> (https://bugzilla.kernel.org/attachment.cgi?id=58612) The log of X with the 2.6.39-rc7 kernel -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #4 from Rog?rio Brito 2011-05-19 20:38:14 --- Created an attachment (id=58622) --> (https://bugzilla.kernel.org/attachment.cgi?id=58622) A dmesg log with 2.6.38 kernel Please, notice the GPU hang with kernel 2.6.38. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 34772] [radeon] [R300] GPU lockups with when KMS is enabled
https://bugzilla.kernel.org/show_bug.cgi?id=34772 --- Comment #5 from Rog?rio Brito 2011-05-19 20:38:56 --- Created an attachment (id=58632) --> (https://bugzilla.kernel.org/attachment.cgi?id=58632) Log from X with the kernel 2.6.38 -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are watching the assignee of the bug. -- What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- ___ Dri-devel mailing list Dri-devel at lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 36327] fujitsu siemens amilo li1718: ati radeon x200m does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=36327 --- Comment #16 from Karesz L. 2011-05-19 23:11:47 PDT --- Created an attachment (id=46931) --> (https://bugs.freedesktop.org/attachment.cgi?id=46931) A failed resume's recurring log- Fedora 15 beta I've made a bootable live Fedora 15 beta USB, booted, and noticed, that gnome3 had only a suspend in it's "live user options" menu, so I clicked it. It suspended correctly, as expected. Then I pressed the power button, to see whether it resumes, or not. It doesn't, but the screen got backlit, and this message kept running on the screen. Pressing ctrl+alt+F3 stopped it, and I was able to take a photo of it (don't know how to get this message in text form), and I enhanced it a little. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug.
[REGRESSION] [2.6.39-rc3] Wrong resolution in framebuffer and X Window
On 11-05-19 03:01 PM, Maciej Rutecki wrote:
> On czwartek, 21 kwietnia 2011 o 19:22:05 Maciej Rutecki wrote:
>> (add LKML)
>>
>> On niedziela, 17 kwietnia 2011 o 18:04:04 Maciej Rutecki wrote:
>>> Hi
>>>
>>> Last known good: 2.6.38
>>> Failing kernel: 2.6.39-rc3
>>> Subsystem: Intel graphics driver.
>>>
>>> Description:
>>> PC should work with 1440x900 resolution. But console (and after) X Window
>>> start work with 1024x768.
>>>
>>> I attach dmesg and Xorg.0.log with drm.debug=14 log_buf_len=16M options:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/kms/
>>>
>>> seems that driver cannot detect resolution higher than 1024x768.
>>>
>>> Also I boot kernel replace "i915.modeset=1" with "nomodeset" option:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/nomodeset/
>>>
>>> But then X Window fails to start and got message: "(EE) No devices
>>> detected."
>>>
>>> Config for 2.6.39-rc3:
>>> http://unixy.pl/maciek/download/kernel/2.6.39-rc1/zlom/config-2.6.39-rc3
>>>
>>> Best regards
>>
>> Device:
>> 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express
>> Integrated Graphics Controller (rev 02)
>
> Reported on:
> https://bugzilla.kernel.org/show_bug.cgi?id=34002
>
> 2 weeks ago. Problem STILL exists on 2.6.39. That any of the graphic
> developers might be interested in the problem?
I had a problem similar to this, beginning with 2.6.37 (2.6.36 was okay).
It turned out to be that newer kernels were detecting the LVDS (LCD panel)
interface from the chipset, event though nothing was attached to that interface.
So GNOME would come up at 1024x768 (max the LVDS supported, I guess).
I initially worked around it by going into the GNOME -> Preferences -> Monitors,
and disabling the LVDS device there, in favour of the 1920x1200 "VGA" device I
use.
Later, I hacked my kernel to just ignore the LVDS completely:
--- linux/drivers/gpu/drm/i915/intel_lvds.c.orig2011-05-09
22:33:54.0 -0400
+++ linux/drivers/gpu/drm/i915/intel_lvds.c 2011-05-17 23:00:40.829773525
-0400
@@ -841,6 +841,7 @@
*/
bool intel_lvds_init(struct drm_device *dev)
{
+if (0) {
struct drm_i915_private *dev_priv = dev->dev_private;
struct intel_lvds *intel_lvds;
struct intel_encoder *intel_encoder;
@@ -1041,5 +1042,6 @@
drm_encoder_cleanup(encoder);
kfree(intel_lvds);
kfree(intel_connector);
+}
return false;
}
