Hello,

I've been hit by more or less periodical stuck of system response including graphics animation  (even stuck of mouse cursor).

 The problem tooks c. 1 second a then system for bolow 1 second is interactive and visual running. The stuck occurs under the
specific level of graphical loads (during scrooling of text, in Opera browser, in some 2D game e.g. Asylum, in  glxgears...)

The workaround of this problem is unistall firmware-linux, which are recomend to install. This action is due to disable DRI and
IMHO no 2D acceleration (like VESA driver).

with regards

M.Kovarik

Hi,

merlin <v.merlin@seznam.cz> (18/06/2010):

does the machine goes done entirely, or is it still reachable through
the network? If the X server crashed, getting a backtrace would be
nice; as well as kernel logs. See this doc for example:
http://pkg-xorg.alioth.debian.org/howto/use-gdb.html

It would be nice to tell us how it goes with an up-to-date X stack, be
it in squeeze or in sid. Also, I think you want to install both
firmware-linux-free and firmware-linux-nonfree.

KiBi.

Hi,

the problem missed sometime in the past. (I've been using fglrx)  X
server didn't crash - I can normally work after closing the issue 3D
application.

I'm using Debian "testing" now. There are this version of xorg
installed:

        aptitude show xserver-xorg-core | grep Verze
                Verze: 2:1.7.7-11
        aptitude show xserver-xorg-video-radeon | grep Verze
                Verze: 1:6.13.1-2+squeeze1

To enable Kernel Modesetting active in Xorg.0.log I have to add string
"radeon" to /etc/modules. In this case it seems 3D acceleration works
all  right (fgrlx is still better) Xorg.0.log says :
 (II) [KMS] Kernel modesetting enabled.

If I'll don't write "radeon" in /etc/modules I can see this in
Xorg.0.log:

(EE) RADEON(0): [dri] RADEONDRIGetVersion failed because of a version
mismatch.
[dri] This chipset requires a kernel module version of 1.17.0,
[dri] but the kernel reports a version of 2.0.0.[dri] If using legacy
modesetting, upgrade your kernel.
[dri] If using kernel modesetting, make sure your module is
[dri] loaded prior to starting X, and that this driver was built
[dri] with support for KMS.
[dri] Disabling DRI
Of course, in this case acceleration is off.
On http://www.x.org/wiki/radeonBuildHowTo#Kernel-basedModeSetting this
is explained like as KMS is not enabled before X started. So I don't
know if my solution is all right.

Hi,

the problem with circular 1 or 0.5 second jamming of system sometime is again present.

I don't know what trigger this one. Is it very infrequently.  I had Opera browser
 runnig with last stable Adobe flash through nspluginwrapper, but I had not been browsing just.

When the bug is activated, the systems give following report.

Message from syslogd@martin at Mar 10 23:29:02 ...
 kernel:[ 9052.018792] Disabling IRQ #24

Mar 10 23:29:02 martin kernel: [ 9052.018661] Pid: 2767, comm: yiff Not tainted 2.6.32-5-amd64 #1
Mar 10 23:29:02 martin kernel: [ 9052.018666] Call Trace:
Mar 10 23:29:02 martin kernel: [ 9052.018670]  <IRQ>  [<ffffffff81095855>] ? __report_bad_irq+0x30/0x7d
Mar 10 23:29:02 martin kernel: [ 9052.018690]  [<ffffffff810959a7>] ? note_interrupt+0x105/0x16e
Mar 10 23:29:02 martin kernel: [ 9052.018698]  [<ffffffff8109600c>] ? handle_fasteoi_irq+0x93/0xb5
Mar 10 23:29:02 martin kernel: [ 9052.018707]  [<ffffffff8101327f>] ? handle_irq+0x17/0x1d
Mar 10 23:29:02 martin kernel: [ 9052.018713]  [<ffffffff810128d9>] ? do_IRQ+0x57/0xb6
Mar 10 23:29:02 martin kernel: [ 9052.018720]  [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11
Mar 10 23:29:02 martin kernel: [ 9052.018723]  <EOI>  [<ffffffff810fc736>] ? sys_select+0x5a/0xbb
Mar 10 23:29:02 martin kernel: [ 9052.018738]  [<ffffffff810fc710>] ? sys_select+0x34/0xbb
Mar 10 23:29:02 martin kernel: [ 9052.018744]  [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b

Hi,

it's from syslog.

Mar 10 23:29:02 martin kernel: [ 9052.018650] irq 24: nobody cared (try booting with the "irqpoll" option)
Mar 10 23:29:02 martin kernel: [ 9052.018661] Pid: 2767, comm: yiff Not tainted 2.6.32-5-amd64 #1
Mar 10 23:29:02 martin kernel: [ 9052.018666] Call Trace:
Mar 10 23:29:02 martin kernel: [ 9052.018670]  <IRQ>  [<ffffffff81095855>] ? __report_bad_irq+0x30/0x7d
Mar 10 23:29:02 martin kernel: [ 9052.018690]  [<ffffffff810959a7>] ? note_interrupt+0x105/0x16e
Mar 10 23:29:02 martin kernel: [ 9052.018698]  [<ffffffff8109600c>] ? handle_fasteoi_irq+0x93/0xb5
Mar 10 23:29:02 martin kernel: [ 9052.018707]  [<ffffffff8101327f>] ? handle_irq+0x17/0x1d
Mar 10 23:29:02 martin kernel: [ 9052.018713]  [<ffffffff810128d9>] ? do_IRQ+0x57/0xb6
Mar 10 23:29:02 martin kernel: [ 9052.018720]  [<ffffffff810114d3>] ? ret_from_intr+0x0/0x11
Mar 10 23:29:02 martin kernel: [ 9052.018723]  <EOI>  [<ffffffff810fc736>] ? sys_select+0x5a/0xbb
Mar 10 23:29:02 martin kernel: [ 9052.018738]  [<ffffffff810fc710>] ? sys_select+0x34/0xbb
Mar 10 23:29:02 martin kernel: [ 9052.018744]  [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
Mar 10 23:29:02 martin kernel: [ 9052.018749] handlers:
Mar 10 23:29:02 martin kernel: [ 9052.018751] [<ffffffffa04e7a68>] (radeon_driver_irq_handler_kms+0x0/0x18 [radeon])
Mar 10 23:29:02 martin kernel: [ 9052.018792] Disabling IRQ #24

Hi,

same problem here:

[    2.669272] irq 18: nobody cared (try booting with the "irqpoll" option)
[    2.669278] Pid: 191, comm: modprobe Not tainted 2.6.38-8-server #42-Ubuntu
[    2.669281] Call Trace:
[    2.669283]  <IRQ>  [<ffffffff810d478b>] ? __report_bad_irq.clone.2+0x2b/0xa0
[    2.669299]  [<ffffffff810d4b8a>] ? note_interrupt+0x19a/0x1e0
[    2.669304]  [<ffffffff8106d3e9>] ? __do_softirq+0xf9/0x1c0
[    2.669308]  [<ffffffff810d5a7d>] ? handle_fasteoi_irq+0xdd/0x110
[    2.669313]  [<ffffffff8100e982>] ? handle_irq+0x22/0x40
[    2.669318]  [<ffffffff815df97d>] ? do_IRQ+0x5d/0xe0
[    2.669323]  [<ffffffff815d7cd3>] ? ret_from_intr+0x0/0x15
[    2.669325]  <EOI>  [<ffffffff812e4add>] ? delay_tsc+0x3d/0x80
[    2.669334]  [<ffffffff812e4aea>] ? delay_tsc+0x4a/0x80
[    2.669338]  [<ffffffff812e4a3e>] ? __const_udelay+0x2e/0x30
[    2.669379]  [<ffffffffa015ccee>] ? radeon_set_pll.clone.4+0x52e/0xb20 [radeon]
[    2.669410]  [<ffffffffa015da3c>] ? radeon_crtc_mode_set+0x3c/0x160 [radeon]
[    2.669419]  [<ffffffffa00b05c3>] ? drm_crtc_helper_set_mode+0x343/0x4e0 [drm_kms_helper]
[    2.669423]  [<ffffffff815d7cce>] ? common_interrupt+0xe/0x13
[    2.669430]  [<ffffffffa00b147d>] ? drm_crtc_helper_set_config+0x84d/0xa10 [drm_kms_helper]
[    2.669435]  [<ffffffff815d5f01>] ? mutex_lock+0x1/0x50
[    2.669440]  [<ffffffffa00af22c>] ? drm_fb_helper_set_par+0x7c/0xf0 [drm_kms_helper]
[    2.669444]  [<ffffffff8132ebd0>] ? fbcon_init+0x650/0x6c0
[    2.669449]  [<ffffffff8139810f>] ? visual_init+0xcf/0x180
[    2.669453]  [<ffffffff813987bc>] ? bind_con_driver+0x1cc/0x410
[    2.669456]  [<ffffffff81398b81>] ? take_over_console+0x61/0x70
[    2.669460]  [<ffffffff81329a73>] ? fbcon_takeover+0x63/0xc0
[    2.669463]  [<ffffffff8132f3bd>] ? fbcon_event_notify+0x4dd/0x550
[    2.669468]  [<ffffffff815db8ed>] ? notifier_call_chain+0x4d/0x70
[    2.669473]  [<ffffffff8108d588>] ? __blocking_notifier_call_chain+0x58/0x80
[    2.669478]  [<ffffffff813246f9>] ? fb_add_videomode+0x89/0xf0
[    2.669482]  [<ffffffff8108d5c6>] ? blocking_notifier_call_chain+0x16/0x20
[    2.669486]  [<ffffffff8131e00b>] ? fb_notifier_call_chain+0x1b/0x20
[    2.669490]  [<ffffffff8131f5d8>] ? register_framebuffer+0x1d8/0x2b0
[    2.669495]  [<ffffffffa00af4f2>] ? drm_fb_helper_single_fb_probe+0x252/0x2f0 [drm_kms_helper]
[    2.669501]  [<ffffffffa00af684>] ? drm_fb_helper_initial_config+0xf4/0x120 [drm_kms_helper]
[    2.669533]  [<ffffffffa0170e8a>] ? radeon_fbdev_init+0xca/0x120 [radeon]
[    2.669564]  [<ffffffffa016a746>] ? radeon_modeset_init+0x226/0x250 [radeon]
[    2.669591]  [<ffffffffa0143048>] ? radeon_driver_load_kms+0x118/0x1a0 [radeon]
[    2.669610]  [<ffffffffa004ea3e>] ? drm_get_pci_dev+0x18e/0x300 [drm]
[    2.669615]  [<ffffffff81154e8f>] ? kmem_cache_alloc_trace+0xef/0x110
[    2.669645]  [<ffffffffa01d36be>] ? radeon_pci_probe+0xb2/0xba [radeon]
[    2.669649]  [<ffffffff812ff26f>] ? local_pci_probe+0x5f/0xd0
[    2.669653]  [<ffffffff81300b69>] ? pci_device_probe+0x129/0x130
[    2.669659]  [<ffffffff813bab9a>] ? driver_sysfs_add+0x7a/0xb0
[    2.669662]  [<ffffffff813bacc8>] ? really_probe+0x68/0x190
[    2.669666]  [<ffffffff813bafd5>] ? driver_probe_device+0x45/0x70
[    2.669670]  [<ffffffff813bb0ab>] ? __driver_attach+0xab/0xb0
[    2.669673]  [<ffffffff813bb000>] ? __driver_attach+0x0/0xb0
[    2.669677]  [<ffffffff813b9e4e>] ? bus_for_each_dev+0x5e/0x90
[    2.669681]  [<ffffffff813bab1e>] ? driver_attach+0x1e/0x20
[    2.669684]  [<ffffffff813ba685>] ? bus_add_driver+0xc5/0x280
[    2.669707]  [<ffffffffa0219000>] ? radeon_init+0x0/0x1000 [radeon]
[    2.669711]  [<ffffffff813bb346>] ? driver_register+0x76/0x140
[    2.669733]  [<ffffffffa0219000>] ? radeon_init+0x0/0x1000 [radeon]
[    2.669736]  [<ffffffff812ff916>] ? __pci_register_driver+0x56/0xd0
[    2.669748]  [<ffffffffa004ef54>] ? drm_pci_init+0xe4/0xf0 [drm]
[    2.669770]  [<ffffffffa0219000>] ? radeon_init+0x0/0x1000 [radeon]
[    2.669780]  [<ffffffffa00465f8>] ? drm_init+0x58/0x70 [drm]
[    2.669802]  [<ffffffffa02190c4>] ? radeon_init+0xc4/0x1000 [radeon]
[    2.669807]  [<ffffffff81002175>] ? do_one_initcall+0x45/0x190
[    2.669812]  [<ffffffff810a472b>] ? sys_init_module+0xfb/0x250
[    2.669816]  [<ffffffff8100bfc2>] ? system_call_fastpath+0x16/0x1b
[    2.669818] handlers:
[    2.669820] [<ffffffff81449f30>] (usb_hcd_irq+0x0/0x80)
[    2.669826] [<ffffffffa0172ae0>] (radeon_driver_irq_handler_kms+0x0/0x20 [radeon])
[    2.669858] Disabling IRQ #18

I found a maybe related post at the LKML:
https://lkml.org/lkml/2011/5/2/271

Seems all to be quite recent (2011), so I assume it's quite a new
problem with the radeon driver.