[Bug 37679] [RS690M] No 3d acceleration in Radeon X1200 with the new Gallium r300 / 3d drivers
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Jun 3 17:22:54 PDT 2011
https://bugs.freedesktop.org/show_bug.cgi?id=37679
--- Comment #29 from Phil Cole <filcole at gmail.com> 2011-06-03 17:22:54 PDT ---
(In reply to comment #28)
> .... Does your system have a bios upgrade available?
I've just applied the latest BIOS for the HP Compaq 6715b laptop. I upgraded
from F.07 (16/07/2007) to F.0E (25/11/2008) from here:
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareIndex.jsp?lang=en&cc=us&prodNameId=3356624&prodTypeId=321957&prodSeriesId=3368540&swLang=13&taskId=135&swEnvOID=1093
After doing this and a vanilla kernel boot (nomodeset not set), and the latest
git radeon driver I get: (NOTE: this is a two core system)
0. GNOME3 hangs immediately on startup (so tried KDE4).
1. Whilst booting KDE4 can monitor /proc/interrupts in non-X console and see
radeon interupts rising for both CPUs.
2. Can use X under KDE4 and notice radeon interrupts rising (when windows moved
etc)
3. Then starting "glxgears" or "vblank_output=0 glxgears" under KDE4 gives a
blank window and causes interrupts to no longer be registered in
/proc/interrupts! At this point moving windows around becomes noticeably
slower. (Sometimes this occurs without needing to run glxgears)
4. Killing X (Ctrl-Alt-Backspace) back to GDM and restarting KDE4 causes
interrupts to start being counted again for radeon in /proc/interrupts. BUT
interrupts only increase on CPU0. CPU1 does not increase past that counted in
step 3.
5. Starting "glxgears" causes all radeon interrupts to stop being counted in
/proc/interrupts.
6. Go to step 4 and repeat!
I also got the following messages in syslog. Note radeon is on irq 19.
Jun 4 00:33:54 f15 kernel: [ 900.986231] irq 19: nobody cared (try booting
with the "irqpoll" option)
Jun 4 00:33:54 f15 kernel: [ 900.986241] Pid: 3410, comm: knotify4 Not
tainted 2.6.38.6-27.fc15.i686 #1
Jun 4 00:33:54 f15 kernel: [ 900.986245] Call Trace:
Jun 4 00:33:54 f15 kernel: [ 900.986256] [<c07ceb2d>] ? printk+0x2d/0x2f
Jun 4 00:33:54 f15 kernel: [ 900.986262] [<c07d00ff>]
__report_bad_irq+0x3e/0x86
Jun 4 00:33:54 f15 kernel: [ 900.986269] [<c048820f>]
note_interrupt+0xfa/0x153
Jun 4 00:33:54 f15 kernel: [ 900.986274] [<c0488b17>]
handle_fasteoi_irq+0x88/0xa6
Jun 4 00:33:54 f15 kernel: [ 900.986279] [<c0488a8f>] ?
handle_fasteoi_irq+0x0/0xa6
Jun 4 00:33:54 f15 kernel: [ 900.986282] <IRQ> [<c0404bbd>] ?
do_IRQ+0x3c/0x92
Jun 4 00:33:54 f15 kernel: [ 900.986292] [<c0403770>] ?
common_interrupt+0x30/0x38
Jun 4 00:33:54 f15 kernel: [ 900.986298] [<c04620fd>] ?
arch_local_irq_restore+0x5/0xb
Jun 4 00:33:54 f15 kernel: [ 900.986305] [<c07d62b3>] ?
_raw_spin_unlock_irqrestore+0x13/0x15
Jun 4 00:33:54 f15 kernel: [ 900.986310] [<c0732fb2>] ?
skb_dequeue+0x48/0x4f
Jun 4 00:33:54 f15 kernel: [ 900.986316] [<c07aa2cf>] ?
unix_stream_recvmsg+0x116/0x408
Jun 4 00:33:54 f15 kernel: [ 900.986323] [<c0592f7b>] ?
selinux_socket_recvmsg+0x1f/0x22
Jun 4 00:33:54 f15 kernel: [ 900.986329] [<c072e303>] ?
sock_aio_read+0xf6/0xfe
Jun 4 00:33:54 f15 kernel: [ 900.986335] [<c043feb7>] ? irq_exit+0x4c/0x70
Jun 4 00:33:54 f15 kernel: [ 900.986342] [<c04e4352>] ?
do_sync_read+0x96/0xcf
Jun 4 00:33:54 f15 kernel: [ 900.986348] [<c04e4672>] ?
rw_verify_area+0xd0/0xf3
Jun 4 00:33:54 f15 kernel: [ 900.986352] [<c042e4e2>] ?
__might_sleep+0x29/0xe4
Jun 4 00:33:54 f15 kernel: [ 900.986357] [<c04e49e6>] ? vfs_read+0x94/0xd5
Jun 4 00:33:54 f15 kernel: [ 900.986362] [<c04e4a69>] ? sys_read+0x42/0x63
Jun 4 00:33:54 f15 kernel: [ 900.986367] [<c07d66b4>] ? syscall_call+0x7/0xb
Jun 4 00:33:54 f15 kernel: [ 900.986370] handlers:
Jun 4 00:33:54 f15 kernel: [ 900.986372] [<f7a15415>]
(radeon_driver_irq_handler_kms+0x0/0x19 [radeon])
Jun 4 00:33:54 f15 kernel: [ 900.986440] Disabling IRQ #19
So I tried rebooting with "irqpoll" in the kernel options. KDE4 and GNOME3
(gnome-shell) both run. glxgears gives 50 FPS !!
So, my guess is the kernel/drm/radeon is wedging on interrupt processing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the xorg-driver-ati
mailing list