[Bug 9233] Black Borders around Windows w/ Compiz and mesa-6.5.2 X11R7.2 RC 3
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=9233 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |NEEDINFO --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 02:59 --- Please attach the full X server log file and any relevant output from compiz. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 9212] radeon crash when an OpenGL app starts w/o window manager
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=9212 --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 03:32 --- (In reply to comment #3) With latest X server it still crashes. Looks like a different crash though. BTW, any reason for not using direct rendering? -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Sat, 2006-12-02 at 12:14 -0500, Adam K Kirchhoff wrote: So something occurred to me last night... I've seen these same symptoms before when trying to get DRI working on FreeBSD a long time ago... On another machine, if I accidentally had the AGPSize set to a value higher than was set in the BIOS, I saw the exact same problem in FreeBSD (but not in Linux, which didn't have any problem with that particular situation). I don't have any config options set for GARTSize, but could something similar be happening now? I think that's unlikely with PCIe, although my first guess would have been something related to GART as well given that the same configuration seems to run or not depending on the OS. Maybe the OSs set up something differently related to PCIe. I'm having a problem getting direct rendering working on one of my workstations. I'm running FreeBSD -CURRENT from November 17th with Xorg installed from the modular Xorg ports tree yesterday (though I first noticed this a couple weeks back when I built modular Xorg using jhbuild): If you're saying that some previous version worked with the same configuration, could you try isolating the regression with git-bisect? If I boot up with DRI enabled in the config file, the server starts, but the very top of the screen shows some visual corruption. http://www.visualtech.com/screenshot.png I dropped the resolution of the image from 2304x864 to 1600x800, but you can still make out the corruption. What's particularly odd, though, is that the root window is never drawn. The background you see is actually the background from my previous X session (when I had DRI disabled), using windowmaker. This time I launched X and had fvwm2 in my .xinitrc file (you can see the outline of the fvwm pager in the screenshot, though that never finished drawing, either). After that nothing else gets drawn. Sounds like a GPU hang/lockup. I can move the mouse pointer, but that's about it. I can safely kill X and restart it, but the same thing happens unless I disable DRI. That's a relatively graceful way for it to deal with the above though. :} This seems to be a FreeBSD specific problem as the same PCIe x800 works fine with the OSS drivers under Linux, but no on on the freebsd-x11 lists seems to have any ideas, and I'm running out of ideas. I thought some of the great minds on this list might be able to shed some light. Any interesting differences between the server log files, DRM related kernel output etc. between OSs? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 14:42 +0100, Michel Dänzer wrote: On Sat, 2006-12-02 at 12:14 -0500, Adam K Kirchhoff wrote: So something occurred to me last night... I've seen these same symptoms before when trying to get DRI working on FreeBSD a long time ago... On another machine, if I accidentally had the AGPSize set to a value higher than was set in the BIOS, I saw the exact same problem in FreeBSD (but not in Linux, which didn't have any problem with that particular situation). I don't have any config options set for GARTSize, but could something similar be happening now? I think that's unlikely with PCIe, although my first guess would have been something related to GART as well given that the same configuration seems to run or not depending on the OS. Maybe the OSs set up something differently related to PCIe. I'm having a problem getting direct rendering working on one of my workstations. I'm running FreeBSD -CURRENT from November 17th with Xorg installed from the modular Xorg ports tree yesterday (though I first noticed this a couple weeks back when I built modular Xorg using jhbuild): If you're saying that some previous version worked with the same configuration, could you try isolating the regression with git-bisect? If I boot up with DRI enabled in the config file, the server starts, but the very top of the screen shows some visual corruption. http://www.visualtech.com/screenshot.png I dropped the resolution of the image from 2304x864 to 1600x800, but you can still make out the corruption. What's particularly odd, though, is that the root window is never drawn. The background you see is actually the background from my previous X session (when I had DRI disabled), using windowmaker. This time I launched X and had fvwm2 in my .xinitrc file (you can see the outline of the fvwm pager in the screenshot, though that never finished drawing, either). After that nothing else gets drawn. Sounds like a GPU hang/lockup. I can move the mouse pointer, but that's about it. I can safely kill X and restart it, but the same thing happens unless I disable DRI. That's a relatively graceful way for it to deal with the above though. :} This seems to be a FreeBSD specific problem as the same PCIe x800 works fine with the OSS drivers under Linux, but no on on the freebsd-x11 lists seems to have any ideas, and I'm running out of ideas. I thought some of the great minds on this list might be able to shed some light. Any interesting differences between the server log files, DRM related kernel output etc. between OSs? The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 (II) RADEON(0): [drm] created radeon driver at busid pci::07:00.0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xc56df000 (II) RADEON(0): [drm] mapped SAREA 0xc56df000 to 0x28557000 (II) RADEON(0): [drm] framebuffer handle = 0xc000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [pci] 8192 kB allocated with handle 0x (II) RADEON(0): [pci] ring handle = 0xc56e3000 (II) RADEON(0): [pci] Ring mapped at 0x38648000 (II) RADEON(0): [pci] Ring contents 0xfc181616 (II) RADEON(0): [pci] ring read ptr handle = 0xc57e4000 (II) RADEON(0): [pci] Ring read ptr mapped at 0x28559000 (II) RADEON(0): [pci] Ring read ptr contents 0xff3a492d (II) RADEON(0): [pci] vertex/indirect buffers handle = 0xc57e5000 (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0x38749000 (II) RADEON(0): [pci] Vertex/indirect buffers contents 0xff252d1e (II) RADEON(0): [pci] GART texture map handle = 0xc59e5000 (II) RADEON(0): [pci] GART Texture map mapped at 0x38949000 (II) RADEON(0): [drm] register handle = 0xdfbe (II) RADEON(0): [dri] Visual configs initialized And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 (II) RADEON(0): [drm] created radeon driver at busid pci::07:00.0 (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf8dee000 (II) RADEON(0): [drm] mapped SAREA 0xf8dee000 to 0xb7bac000 (II) RADEON(0): [drm] framebuffer handle = 0xc000 (II) RADEON(0): [drm] added 1 reserved context for kernel (II) RADEON(0): [pci] 8192 kB allocated with handle 0xf8f2e000 (II) RADEON(0): [pci] ring handle = 0xf8f2e000 (II) RADEON(0): [pci] Ring mapped at 0xa797 (II) RADEON(0): [pci] Ring contents 0x (II) RADEON(0): [pci] ring read ptr handle = 0xf902f000 (II) RADEON(0): [pci] Ring read ptr mapped at 0xb7bab000 (II) RADEON(0): [pci] Ring read ptr contents 0x (II) RADEON(0): [pci] vertex/indirect buffers handle = 0xf903 (II) RADEON(0): [pci] Vertex/indirect buffers mapped at 0xa777 (II) RADEON(0): [pci] Vertex/indirect buffers contents 0x (II) RADEON(0): [pci] GART texture map handle = 0xf923 (II) RADEON(0): [pci]
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote: The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 [...] And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 So it looks like you're using a newer DRM on Linux but a newer xf86-video-ati on FreeBSD. Does making either of these equal between OSs change anything? -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 9232] crash when AGPFastWrite is true
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=9232 --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 06:49 --- I have the same Motherboard, CPU and a Radeon 9600 card. I also get crash with Fast Write on. It crashes when using Windows as well. I believe this is a known issue with motherboard too. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote: The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 [...] And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 So it looks like you're using a newer DRM on Linux but a newer xf86-video-ati on FreeBSD. Does making either of these equal between OSs change anything? Well, the DRM module itself is the same version as under linux (1.25.0). Are you referring to libdrm? I'll see if I can upgrade that on FreeBSD. Adam - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 12:49 -0500, Adam K Kirchhoff wrote: On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote: The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 [...] And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 So it looks like you're using a newer DRM on Linux but a newer xf86-video-ati on FreeBSD. Does making either of these equal between OSs change anything? Well, the DRM module itself is the same version as under linux (1.25.0). Are you referring to libdrm? No, see the different DRM interface versions (corresponding to the 'drm' kernel module) above. Maybe they're just different between OSs though. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Fwd: Re: i915gm and drmWaitVBlank]
-- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer ---BeginMessage--- - Original Message - From: Michel Dänzer [EMAIL PROTECTED] To: kr992 [EMAIL PROTECTED] Sent: Monday, December 04, 2006 5:40 PM Subject: Re: i915gm and drmWaitVBlank [ Again, please follow up to the list and just me! ] On Mon, 2006-12-04 at 17:38 +0100, kr992 wrote: lsmod |grep drm: drm97336 1 i915 agpgart20912 3 drm,intel_agp its like you wrote its nothing about drm in current log , in older logs i saw that was: Nov 26 23:48:02 vwer kernel: [drm] Initialized drm 1.0.1 20051102 Nov 26 23:48:02 vwer kernel: ACPI: PCI Interrupt :00:02.0[A] - Link [LNKA] - GSI 5 (level, low) - IRQ 5 Nov 26 23:48:02 vwer kernel: [drm] Initialized i915 1.5.0 20060119 on minor 0 Please run modprobe -r i915; modprobe i915 as root and post the output of dmesg. I attach dmesg when i try modprobe -r i915 from console in X i have Naruszenie ochrony pamieci, its like segmentation fault , after that if i run modprobe i915 nothing show , but its wait for something , and I have to ctrl-c to break when i try modprobe i915 before i start X then i have like in kern.log: BUG: warning at mm/vmalloc.c:334/__vunmap() [c0145c16] [c01712c0] [c01033eb] === Trying to vfree() nonexistent vm area (c05fc000) BUG: warning at mm/vmalloc.c:334/__vunmap() [c0145c16] [e041da20] [c01033eb] === so , is problem in kernel? Mike -- Jestes kierowca? To poczytaj! http://link.interia.pl/f199e dmesg Description: Binary data ---End Message--- - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV-- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 19:01 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 12:49 -0500, Adam K Kirchhoff wrote: On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote: The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 [...] And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 So it looks like you're using a newer DRM on Linux but a newer xf86-video-ati on FreeBSD. Does making either of these equal between OSs change anything? Well, the DRM module itself is the same version as under linux (1.25.0). Are you referring to libdrm? No, see the different DRM interface versions (corresponding to the 'drm' kernel module) above. Maybe they're just different between OSs though. Yeah, I think that must be the case. I pulled the latest drm from the git repo and built both a newer libdrm and a newer drm.ko and radeon.ko kernel modules. I get the same results (and the same output in the Xorg log file about the interface version). I've also updated the xf86-video-ati driver on the linux installation to 6.6.3, so it's now the same version as the FreeBSD driver. DRI still works fine on the linux installation. Any other ideas? :-) Adam - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 9233] Black Borders around Windows w/ Compiz and mesa-6.5.2 X11R7.2 RC 3
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=9233 --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 10:46 --- Created an attachment (id=7960) -- (https://bugs.freedesktop.org/attachment.cgi?id=7960action=view) Xorg log w/o compiz This is my xorg.log when i use gdm w/o compiz -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 9233] Black Borders around Windows w/ Compiz and mesa-6.5.2 X11R7.2 RC 3
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=9233 --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 10:48 --- Created an attachment (id=7961) -- (https://bugs.freedesktop.org/attachment.cgi?id=7961action=view) Xorg.log with compiz Xorg log when compiz is enabled. compiz itself does not give any errors. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
[Bug 7697] r300_check_offset fails on PCI-E R420 (5D4F)
Please do not reply to this email: if you want to comment on the bug, go to the URL shown below and enter yourcomments there. https://bugs.freedesktop.org/show_bug.cgi?id=7697 --- Additional Comments From [EMAIL PROTECTED] 2006-12-04 11:51 --- Interesting that the same error code is also shown for a person using AGP Radeon 9200, https://bugs.launchpad.net/distros/ubuntu/+source/xserver-xorg-video-ati/+bug/65605 Not that I'd know if it helps anyone to pinpoint the actual problem, but the problem seems to (in one way or another) to occur also outside of r300_cmdbuf.c. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: DRI on FreeBSD with a PCIe X800
On Mon, 2006-12-04 at 13:17 -0500, Adam K Kirchhoff wrote: On Mon, 2006-12-04 at 19:01 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 12:49 -0500, Adam K Kirchhoff wrote: On Mon, 2006-12-04 at 15:42 +0100, Michel Dänzer wrote: On Mon, 2006-12-04 at 09:26 -0500, Adam K Kirchhoff wrote: The log file on FreeBSD doesn't show the same warning as the log file on linux about the support being experimental. Hmmm... FreeBSD shows: (II) RADEON(0): [drm] DRM interface version 1.2 [...] And linux shows: (II) RADEON(0): [drm] DRM interface version 1.3 So it looks like you're using a newer DRM on Linux but a newer xf86-video-ati on FreeBSD. Does making either of these equal between OSs change anything? Well, the DRM module itself is the same version as under linux (1.25.0). Are you referring to libdrm? No, see the different DRM interface versions (corresponding to the 'drm' kernel module) above. Maybe they're just different between OSs though. Yeah, I think that must be the case. I pulled the latest drm from the git repo and built both a newer libdrm and a newer drm.ko and radeon.ko kernel modules. I get the same results (and the same output in the Xorg log file about the interface version). I've also updated the xf86-video-ati driver on the linux installation to 6.6.3, so it's now the same version as the FreeBSD driver. DRI still works fine on the linux installation. Any other ideas? :-) Adam For what it's worth, I've also heard from a user on the freebsd-x11 mailing list with a PCIe x600 mobility that has fully functional 2D with DRI enabled. Adam - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
