April 2010 - Radeon HD - openSUSE Mailing Lists

[Bug 21716] New: Detected (native) modes not available for external monitor
by bugzilla-daemon＠freedesktop.org 16 Oct '11

16 Oct '11

http://bugs.freedesktop.org/show_bug.cgi?id=21716 Summary: Detected (native) modes not available for external monitor Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: sparkybluefang(a)gmail.com QAContact: xorg-team(a)lists.x.org Created an attachment (id=25817) --> (http://bugs.freedesktop.org/attachment.cgi?id=25817) Xorg.0.log When connecting to an external monitor (IBM L200p) I use at work, radeonhd appears to correctly detect the available modes, however, they are not available via xrandr. However, I can manually create and add the mode via xrandr and they work just fine. This is a bit odd, as last summer I'm pretty sure I was also using the same model monitor. So I guess this particular one is a bit quirky or something got changed in the driver. I was able to get the xf86-video-ati driver to make the detected modes available, but IIRC I had to have the monitor attached when I started the xserver. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 5

[Bug 25734] New: radeonhd not working
by bugzilla-daemon＠freedesktop.org 16 Oct '11

16 Oct '11

http://bugs.freedesktop.org/show_bug.cgi?id=25734 Summary: radeonhd not working Product: xorg Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: eich(a)pdx.freedesktop.org ReportedBy: john.ettedgui(a)gmail.com QAContact: xorg-team(a)lists.x.org Created an attachment (id=32212) --> (http://bugs.freedesktop.org/attachment.cgi?id=32212) xorg.0.log Hello, I have been trying to get the git version of radeonhd to work with a radeonhd 4670 but I always end up with a black screen when starting Xorg. when I switch back to the terminal the screen flashes green a bit, and then goes back to black and I cannot see anything but the computer is still alive... I have a 2.6.32 linux kernel, with a git mesa. Maybe related but when I modprobe the radeon module, the resolution on screen is wacky, ie I do not see everythin, some part of the screen are outside my monitor. Thanks, John -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 8

[Bug 21043] New: second radeon card uses atombios of primary radeon card in multiseat configuration
by bugzilla-daemon＠freedesktop.org 16 Oct '11

16 Oct '11

http://bugs.freedesktop.org/show_bug.cgi?id=21043 Summary: second radeon card uses atombios of primary radeon card in multiseat configuration Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: kl(a)stat.phys.spbu.ru QAContact: xorg-team(a)lists.x.org Created an attachment (id=24521) --> (http://bugs.freedesktop.org/attachment.cgi?id=24521) multi-seat Xorg configuration file I have two radeonhd cards: primary (integrated rs780) and secondary (rv710). I can get both cards working in the same time with the single Xserver configuration, but when i use multiseat configuration (each card have their own Xserver) the secondary card is failing to initialize. >From the corresponding Xorg.log file i see: (--) RADEONHD(0): Detected an RV710 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfe7f0000 to 0x7fc05337f000 (size 0x00010000) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1002 SubsystemID: 0x1002 IOBaseAddress: 0xb000 Filename: M3A78T_D_1.b BIOS Bootup Message: B27722 RS780D DDR2 200e/500m i.e. radeonhd use atombios of primary vidocard for secondary one and later we get: Backtrace: 0: /usr/local/bin/X1(xf86SigHandler+0x6a) [0x47898a] 1: /lib/libc.so.6 [0x7fc0518e5190] 2: /usr/lib/xorg/modules/drivers//radeonhd_drv.so(RHDAudioUnregisterHdmi+0x4d) [0x7fc04fe243ed] 3: /usr/lib/xorg/modules/drivers//radeonhd_drv.so(RHDHdmiDestroy+0x42) [0x7fc04fe3ae92] 4: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0x7fc04fe229b2] 5: /usr/lib/xorg/modules/drivers//radeonhd_drv.so(RHDOutputsDestroy+0x5c) [0x7fc04fe4a12c] 6: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0x7fc04fe35762] 7: /usr/lib/xorg/modules/drivers//radeonhd_drv.so [0x7fc04fe37c2e] 8: /usr/local/bin/X1(InitOutput+0x9eb) [0x46b29b] 9: /usr/local/bin/X1(main+0x2c6) [0x4369f6] 10: /lib/libc.so.6(__libc_start_main+0xe6) [0x7fc0518d15a6] 11: /usr/local/bin/X1 [0x435e99] Fatal server error: Caught signal 11. Server aborting -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 9

[Bug 20146] New: r6xx-r7xx-support: second radeonhd card initialization failed
by bugzilla-daemon＠freedesktop.org 16 Oct '11

16 Oct '11

http://bugs.freedesktop.org/show_bug.cgi?id=20146 Summary: r6xx-r7xx-support: second radeonhd card initialization failed Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: kl(a)stat.phys.spbu.ru QAContact: xorg-team(a)lists.x.org Created an attachment (id=22995) --> (http://bugs.freedesktop.org/attachment.cgi?id=22995) Xorg.0.log I have a multiseat configuration based on two pci/e radeonhd cards (primary:RS780, secondary:rv710). Both cards are working fine with radeonhd-1.2.4, but when i try r6xx-r7xx-support radeonhd brunch to get 2D hardware acceleration only primary videocard was initialized. I try to initialize videocards separately, but this does not help also. The initialization of secondary chip(rv710) finished with the messages ===================================================================== (--) RADEONHD(0): Detected an RV710 on an unidentified card (II) RADEONHD(0): Mapped IO @ 0xfe7f0000 to 0x7fc084b5c000 (size 0x00010000) (II) RADEONHD(0): PCIE Card Detected (II) RADEONHD(0): Getting BIOS copy from legacy VBIOS location (II) RADEONHD(0): ATOM BIOS Rom: SubsystemVendorID: 0x1002 SubsystemID: 0x1002 IOBaseAddress: 0xb000 Filename: M3A78T_D_1.b BIOS Bootup Message: B27722 RS780D DDR2 200e/500m (II) RADEONHD(0): Analog TV Default Mode: 4294967040 (EE) RADEONHD(0): No Video RAM detected. (II) UnloadModule: "radeonhd" (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ===================================================================== As i can see radeonhd driver try to use ATOM BIOS of primary videochip to boot secondary videochip. As result it did not find videoram and failed. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 5

[Bug 20593] New: radeonhd driver generates unaligned traps on Alpha
by bugzilla-daemon＠freedesktop.org 16 May '11

16 May '11

http://bugs.freedesktop.org/show_bug.cgi?id=20593 Summary: radeonhd driver generates unaligned traps on Alpha Product: xorg Version: git Platform: Alpha OS/Version: Linux (All) Status: NEW Severity: minor Priority: low Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: mcree(a)orcon.net.nz QAContact: xorg-team(a)lists.x.org CC: mcree(a)orcon.net.nz The radeonhd driver generates unaligned traps on Alpha architecture. These are not a show stopper, but do incur very inefficient memory accesses via kernel traps, and pollute the kernel logs with annoying messages. Using radeonhd at git df71658688e47614a3f660c28ac1dc77970eb491 But the version is irrelevant as the misaligned memory accesses have been there for a long time - I have been too lazy to report them until now. >From dmesg: X(2015): unaligned trap at 0000020000903088: 000002000098c5d7 28 1 X(2015): unaligned trap at 0000020000903088: 000002000098c5df 28 1 X(2015): unaligned trap at 0000020000903088: 000002000098c5e7 28 1 X(2015): unaligned trap at 0000020000903088: 0000020000989771 28 1 Connecting gdb to the running X process reveals the culprit: (gdb) list *0x0000020000903088 0x20000903088 is in GetParametersDirect32 (AtomBios/CD_Operations.c:441). 436 } 437 438 UINT32 GetParametersDirect32(PARSER_TEMP_DATA STACK_BASED * pParserTempData) 439 { 440 pParserTempData->CD_Mask.SrcAlignment=alignmentDword; 441 pParserTempData->Index=*(UINT32*)pParserTempData->pWorkingTableData->IP; 442 pParserTempData->pWorkingTableData->IP+=sizeof(UINT32); 443 return pParserTempData->Index; 444 } 445 Line 441 is a 32bit (long word) access. The address dereferenced is not aligned to a 32bit boundary for an unaligned trap to occur. The ati driver is worse. It coughs up unaligned traps from GetParametersDirect16() and GetParametersRegister() too, but I haven't seen these from radeonhd. Cheers Michael. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 10

[Bug 25309] New: OpenGL corruption with radeonhd on HD 4850
by bugzilla-daemon＠freedesktop.org 09 Mar '11

09 Mar '11

http://bugs.freedesktop.org/show_bug.cgi?id=25309 Summary: OpenGL corruption with radeonhd on HD 4850 Product: xorg Version: 7.5 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/radeonhd AssignedTo: eich(a)pdx.freedesktop.org ReportedBy: dawitbro(a)sbcglobal.net QAContact: xorg-team(a)lists.x.org Created an attachment (id=31493) --> (http://bugs.freedesktop.org/attachment.cgi?id=31493) xorg.conf Overview: Enabling OpenGL support in apps while using combination of radeonhd with RV770 GPU leads to massive screen corruption. It's likely that this is a very hardware-specific issue -- see reference to fdo bug #24301 in "Additional information" section below. Originally this bug was shared by radeon as well as radeonhd, but has been fixed in xf86-video-ati by Alex Deucher (commit 5f84636...), so it now is present in radeonhd only. Steps to reproduce: I've been using two apps to test OpenGL: 'prboom' and 'dosbox'. (I believe that running any app using OpenGL would result in the same massive rendering corruption.) prboom: running 'prboom -vidmode gl' enables OpenGL support, resulting in corruption. (Running 'prboom' without "-vidmode gl" option disables OpenGL, and rendering is fine.) dosbox: graphics output mode is controlled by ~/.dosboxrc, in the section called "[sdl]", and using the option "output=opengl" enables OpenGL support. (Setting this to other output modes, such as "output=overlay", disables OpenGL in DOSBox and results in perfect rendering.) Actual results: prboom: running prboom with OpenGL enabled results in massive screen corruption. The game does not crash, but all surfaces and enemies are rendered in a garbled fashion. Essentially unplayable, unless you want to take an "acid trip" without the LSD. dosbox: Running an old DOS game (I've been using Warlords 2) with OpenGL enabled results in worse corruption than with 'prboom', and is totally unusable. DOSBox is not crashed, and the game's keyboard shortcuts are working, but you cannot see anything at all except the unchanging, corrupt graphics. Both test apps spam my dmesg and kern.log files with this message when running with OpenGL enabled: [drm:r600_cp_dispatch_texture] *ERROR* Invalid destination offset Expected results: both apps should render the games without corrupting the graphics and with all of the benefits OpenGL has to offer (acceleration, superior rendering quality, etc.). System info: GPU: GIGABYTE GV-R485MC-1GI Radeon HD 4850 (RV770) 1GB VRAM, 256-bit GDDR3 PCI Express 2.0 x16 Kernel + architecture: [uname -r -m] 2.6.32-rc8-0git091120.desktop.uvesafb x86_64 Linux distribution: Debian unstable Machine: self-built MSI 790FX-GD70 motherboard socket AM3 AMD 790FX and SB750 Chipset OCZ OCZ3P1600EB4GK 2x2GB DDR3 1600 AMD Phenom II X4 955 Software versions: xf86-video-radeonhd: git commit 6387ab4..., dated 11-12-2009 Mesa-7.7-devel: git commit 37676b3..., dated 11-15-2009 libdrm: release 2.4.15 tarball XOrg Server: 1.7.0 from Debian experimental, dated 10-04-2009 prboom: v2.5.0 DOSBox: v0.72 Additional versions: radeonhd: initially was using 1.2.5 from Debian unstable; built radeon 1.3.0 from official release tarball in early November before upgrading to the version mention above on Nov. 12 Mesa: initially using Mesa-7.7-devel from tarball, dated 11-05-2009 X Server: initially using 1.6.5 from Debian unstable (Other software -- libdrm, prboom, and DOSBox -- remained unchanged.) Symptoms with OpenGL enabled did not change (on radeonhd) with any of the mentioned version changes. Additional Information: This problem was discovered in the process of experimenting with 2D/3D acceration support for my RV770 GPU. Debian did not include support for Radeon 'r600' in their Mesa-7.6 packages, so I had to build upstream versions of libdrm, Mesa-7.7-devel, and xf86-video-radeonhd to get the necessary support for 'r600'. I also have experimented with xf86-video-ati. The "xserver-xorg-video-radeon" package in Debian unstable (from xf86-video-ati) was version 6.12.3 when I began experimenting. It also produced the same graphics corruption I am seeing with "radeonhd", including the "r600_cp_dispatch_texture" error spam in my logs. However, it was discovered by Alex Deucher that a problem in the "radeon" DDX driver having to do with large amounts of VRAM was the cause of the problem with that driver. (See fdo bug #24301.) Matthias Hopf believes that the root cause of this identical corruption (and log spam) I am experiencing with "radeonhd" is not the same as for "radeon", however. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 6

[Bug 22114] New: monitor sometimes stays flashing black
by bugzilla-daemon＠freedesktop.org 21 Jan '11

21 Jan '11

http://bugs.freedesktop.org/show_bug.cgi?id=22114 Summary: monitor sometimes stays flashing black Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/radeonhd AssignedTo: lverhaegen(a)suse.de ReportedBy: estellnb(a)gmail.com QAContact: xorg-team(a)lists.x.org Using the new xorg-x11-driver-video-radeonhd-1.2.5_20090506_4be5f71-3.1 driver with kernel2.6.30-rc5-git1-master_20090515173431_9c6d4c14-default as recommended a very strange error annoys me from time to time: The screen suddenly turns black for about a second; then it continues to view everything as usual. This happens multiple times in sequence and may not stop at all; very annoying. using a FS Scaleoview Q26W-1 1920x1200 monitor. Singleton turn-blacks have occured with previous versions but they did not annoy. Now they occur multiple times in sequence and may not stop at all. May be related with bug 21896, since it sometimes occurs more often on scrolling. Very likely related to the new radeonhd driver since the rest of the system has stayed the same; i.e. I have not updated Xorg or any other relevant component than the 2.6.30 kernel required for the new radeonhd. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team(a)lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 28

Re: [radeonhd] no compositing (gnome/kwin) with FireGL v5200
by Egbert Eich 31 May '10

31 May '10

Antenore Gatta writes: > Hello, > > I'm quite sure I did some mistake in the configuration, so before to > open a bug I'd be really glad if someone can help me to troubleshoot > my issue. > > I've an ATI mobility Firegl v5200 (lenovo T60p) > > I pastebin some info at http://pastebin.com/m40597c37 > > I've first moved from using the fglrx to radeonhd 1.2.4, as I was > quite happy with it (just really slow), I've upgraded to the last > versions of radeonhd (from mesa 7.7.2) and kernel 2.6.32 > > 2D works perfectly, 3D works with OpenGL applications (I tried > glxgears), but not the compositing with Gnome and/or kwin (AIGLX, glx, > dri and composite are enabled). What problems are you seeing actually? Cheers, Egbert. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 3

rv505 crash
by Thomas Drillich 05 May '10

05 May '10

Hi, I'm using debian linux kernel 2.6.32-trunk-amd64 smp with a ATI Technologies Inc RV505 [Radeon X1550 64-bit] when after a while (some hours) after I turned composite on the display crashes I'm able to connect to the host, but radeon wants reboot ;-(... do you knew the reason ? -- mit freundlichem Gruss -- regards Thomas Drillich ---- start of syslog entry ---- Apr 27 08:47:03 mzpc kernel: [50002.238091] BUG: unable to handle kernel NULL pointer dereference at (null) Apr 27 08:47:03 mzpc kernel: [50002.238101] IP: [<ffffffffa0506102>] radeon_read_ring_rptr+0x26/0x29 [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238124] PGD 0 Apr 27 08:47:03 mzpc kernel: [50002.238127] Oops: 0000 [#1] SMP Apr 27 08:47:03 mzpc kernel: [50002.238130] last sysfs file: /sys/devices/pci0000:00/0000:00:18.3/temp3_input Apr 27 08:47:03 mzpc kernel: [50002.238134] CPU 1 Apr 27 08:47:03 mzpc kernel: [50002.238136] Modules linked in: nls_utf8 nls_cp437 vfat fat ppdev lp cpufreq_stats cpufreq_conservative cpufreq_userspace cpufreq_powersave binfmt_misc deflate zlib_deflate ctr twofish twofish_common camellia serpent blowfish cast5 des_generic cbc cryptd aes_x86_64 aes_generic xcbc rmd160 sha256_generic sha1_generic hmac crypto_null af_key fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc powernow_k8 radeon ttm drm_kms_helper drm agpgart i2c_algo_bit hwmon_vid firewire_sbp2 loop snd_hda_codec_realtek dvb_usb_dib0700 dib7000p uvcvideo videodev v4l1_compat v4l2_compat_ioctl32 dib7000m snd_hda_intel dib0070 dvb_usb dib3000mc dib8000 dibx000_common dvb_core snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi joydev snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device i2c_ali15x3 snd i2c_ali1535 soundcore snd_page_alloc shpchp i2c_core edac_core edac_mce_amd k8temp parport_pc pci_hotplug evdev parport serio_raw pcspkr processor ext3 jbd mbca Apr 27 08:47:03 mzpc kernel: che dm_mod hid_microsoft sd_mod crc_t10dif ata_generic usbhid hid usb_storage ide_pci_generic ohci_hcd sata_uli alim15x3 firewire_ohci libata tg3 button firewire_core crc_itu_t ide_core ehci_hcd scsi_mod libphy usbcore nls_base thermal fan thermal_sys [last unloaded: scsi_wait_scan] Apr 27 08:47:03 mzpc kernel: [50002.238226] Pid: 3464, comm: Xorg Not tainted 2.6.32-trunk-amd64 #1 ST20V10 Apr 27 08:47:03 mzpc kernel: [50002.238229] RIP: 0010:[<ffffffffa0506102>] [<ffffffffa0506102>] radeon_read_ring_rptr+0x26/0x29 [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238241] RSP: 0018:ffff8800798c9c20 EFLAGS: 00010246 Apr 27 08:47:03 mzpc kernel: [50002.238243] RAX: 0000000000000000 RBX: ffff8800379b7000 RCX: 000000000000000a Apr 27 08:47:03 mzpc kernel: [50002.238246] RDX: ffff880079f0e940 RSI: 0000000000000000 RDI: ffff8800379b7000 Apr 27 08:47:03 mzpc kernel: [50002.238249] RBP: 0000000000000040 R08: ffff8800798c8000 R09: ffff88007d0038b8 Apr 27 08:47:03 mzpc kernel: [50002.238251] R10: ffff8800136f8000 R11: 0000000000000206 R12: ffff88007f52e0c0 Apr 27 08:47:03 mzpc kernel: [50002.238254] R13: ffff88003742a970 R14: ffff88003742a970 R15: ffff88007d36a200 Apr 27 08:47:03 mzpc kernel: [50002.238257] FS: 00007f37134c36f0(0000) GS:ffff880001900000(0000) knlGS:0000000000000000 Apr 27 08:47:03 mzpc kernel: [50002.238260] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b Apr 27 08:47:03 mzpc kernel: [50002.238263] CR2: 0000000000000000 CR3: 00000000794a3000 CR4: 00000000000006e0 Apr 27 08:47:03 mzpc kernel: [50002.238265] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 Apr 27 08:47:03 mzpc kernel: [50002.238268] DR3: 0000000000000000 DR6: 00000000ffff4ff0 DR7: 0000000000000400 Apr 27 08:47:03 mzpc kernel: [50002.238271] Process Xorg (pid: 3464, threadinfo ffff8800798c8000, task ffff88007d003880) Apr 27 08:47:03 mzpc kernel: [50002.238273] Stack: Apr 27 08:47:03 mzpc kernel: [50002.238275] ffffffffa050685e ffff8800379b7000 ffffffffa0507a2d ffff88003742a970 Apr 27 08:47:03 mzpc kernel: [50002.238279] <0> ffff8800379b7000 ffff8800379b5000 ffffffffa05096a9 ffff8800379b5000 Apr 27 08:47:03 mzpc kernel: [50002.238283] <0> 0000000000000008 ffff8800379b5000 ffffffffa04b81a2 ffff8800798d6300 Apr 27 08:47:03 mzpc kernel: [50002.238288] Call Trace: Apr 27 08:47:03 mzpc kernel: [50002.238299] [<ffffffffa050685e>] ? radeon_commit_ring+0x48/0x9c [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238310] [<ffffffffa0507a2d>] ? radeon_do_cp_idle+0x13a/0x145 [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238321] [<ffffffffa05096a9>] ? radeon_do_release+0x97/0x1aa [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238331] [<ffffffffa04b81a2>] ? drm_lastclose+0x43/0x295 [drm] Apr 27 08:47:03 mzpc kernel: [50002.238338] [<ffffffff810ed022>] ? __fput+0x100/0x1ae Apr 27 08:47:03 mzpc kernel: [50002.238342] [<ffffffff810ea4a6>] ? filp_close+0x5b/0x62 Apr 27 08:47:03 mzpc kernel: [50002.238347] [<ffffffff8104f768>] ? put_files_struct+0x64/0xc1 Apr 27 08:47:03 mzpc kernel: [50002.238351] [<ffffffff8105100a>] ? do_exit+0x225/0x6b5 Apr 27 08:47:03 mzpc kernel: [50002.238361] [<ffffffffa0506fe4>] ? radeon_do_wait_for_idle+0x20/0xf5 [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238365] [<ffffffff81051510>] ? do_group_exit+0x76/0x9d Apr 27 08:47:03 mzpc kernel: [50002.238369] [<ffffffff8105dca8>] ? get_signal_to_deliver+0x310/0x33c Apr 27 08:47:03 mzpc kernel: [50002.238375] [<ffffffff8101000f>] ? do_notify_resume+0x87/0x73f Apr 27 08:47:03 mzpc kernel: [50002.238381] [<ffffffff812e57ec>] ? thread_return+0x79/0xe0 Apr 27 08:47:03 mzpc kernel: [50002.238386] [<ffffffff810f7af2>] ? vfs_ioctl+0x5d/0x6c Apr 27 08:47:03 mzpc kernel: [50002.238389] [<ffffffff81010dce>] ? int_signal+0x12/0x17 Apr 27 08:47:03 mzpc kernel: [50002.238392] Code: fb ff 90 90 90 f6 87 d6 03 00 00 08 48 8b 97 10 01 00 00 74 09 89 f0 48 03 42 18 8b 00 c3 c1 ee 02 89 f0 48 c1 e0 02 48 03 42 18 <8b> 00 c3 83 7f 74 00 74 07 31 f6 e9 ca ff ff ff 66 83 bf d4 03 Apr 27 08:47:03 mzpc kernel: [50002.238421] RIP [<ffffffffa0506102>] radeon_read_ring_rptr+0x26/0x29 [radeon] Apr 27 08:47:03 mzpc kernel: [50002.238432] RSP <ffff8800798c9c20> Apr 27 08:47:03 mzpc kernel: [50002.238433] CR2: 0000000000000000 Apr 27 08:47:03 mzpc kernel: [50002.238436] ---[ end trace 036c8fb36e4f8706 ]--- Apr 27 08:47:03 mzpc kernel: [50002.238439] Fixing recursive fault but reboot is needed! -- end of syslog --- root@mzpc>modinfo radeon filename: /lib/modules/2.6.32-trunk-amd64/kernel/drivers/gpu/drm/radeon/radeon.ko license: GPL and additional rights description: ATI Radeon author: Gareth Hughes, Keith Whitwell, others. firmware: radeon/R520_cp.bin firmware: radeon/RS600_cp.bin firmware: radeon/RS690_cp.bin firmware: radeon/R420_cp.bin firmware: radeon/R300_cp.bin firmware: radeon/R200_cp.bin firmware: radeon/R100_cp.bin firmware: radeon/RV710_me.bin firmware: radeon/RV710_pfp.bin firmware: radeon/RV730_me.bin firmware: radeon/RV730_pfp.bin firmware: radeon/RV770_me.bin firmware: radeon/RV770_pfp.bin firmware: radeon/RS780_me.bin firmware: radeon/RS780_pfp.bin firmware: radeon/RV670_me.bin firmware: radeon/RV670_pfp.bin firmware: radeon/RV635_me.bin firmware: radeon/RV635_pfp.bin firmware: radeon/RV620_me.bin firmware: radeon/RV620_pfp.bin firmware: radeon/RV630_me.bin firmware: radeon/RV630_pfp.bin firmware: radeon/RV610_me.bin firmware: radeon/RV610_pfp.bin firmware: radeon/R600_me.bin firmware: radeon/R600_pfp.bin license: GPL firmware: radeon/R520_cp.bin firmware: radeon/RS600_cp.bin firmware: radeon/RS690_cp.bin firmware: radeon/R420_cp.bin firmware: radeon/R300_cp.bin firmware: radeon/R200_cp.bin firmware: radeon/R100_cp.bin firmware: radeon/RV710_me.bin firmware: radeon/RV710_pfp.bin firmware: radeon/RV730_me.bin firmware: radeon/RV730_pfp.bin firmware: radeon/RV770_me.bin firmware: radeon/RV770_pfp.bin firmware: radeon/RS780_me.bin firmware: radeon/RS780_pfp.bin firmware: radeon/RV670_me.bin firmware: radeon/RV670_pfp.bin firmware: radeon/RV635_me.bin firmware: radeon/RV635_pfp.bin firmware: radeon/RV620_me.bin firmware: radeon/RV620_pfp.bin firmware: radeon/RV630_me.bin firmware: radeon/RV630_pfp.bin firmware: radeon/RV610_me.bin firmware: radeon/RV610_pfp.bin firmware: radeon/R600_me.bin firmware: radeon/R600_pfp.bin depends: drm,drm_kms_helper,ttm,i2c-core,i2c-algo-bit vermagic: 2.6.32-trunk-amd64 SMP mod_unload modversions parm: no_wb:Disable AGP writeback for scratch registers (int) parm: modeset:Disable/Enable modesetting (int) parm: dynclks:Disable/Enable dynamic clocks (int) parm: r4xx_atom:Enable ATOMBIOS modesetting for R4xx (int) parm: vramlimit:Restrict VRAM for testing (int) parm: agpmode:AGP Mode (-1 == PCI) (int) parm: gartsize:Size of PCIE/IGP gart to setup in megabytes (32,64, etc) (int) parm: benchmark:Run benchmark (int) parm: test:Run tests (int) parm: connector_table:Force connector table (int) parm: tv:TV enable (0 = disable) (int) -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

3 3

0x791E:0x1002:0x791E: Biostart TA690G integrated video (ATI XPress 1200)
by Mauro Ziliani 27 Apr '10

27 Apr '10

Goodmorning. My name's Mauro from Parma, Italy. As shown by xorg driver my integrated board is unknown. In subject I put the name. -- To unsubscribe, e-mail: radeonhd+unsubscribe(a)opensuse.org For additional commands, e-mail: radeonhd+help(a)opensuse.org

1 0