You are not logged in.
Pages: 1
I have installed linux-rt and nvidia-rt (I guess the problem is reproducible also with the nouveau drivers, as I have experienced it there too). I encounter a system freeze with no update of screen on any input, no reaction on any key on the keyboard (even the caps lock led does not work) and no mouse input recognition. Strange thing, audio output does work. So I looked at the logs found no evidence. Enabled /var/log/messages and the only thing that appears weird is a segfault in a program as last line:
Watchdog[6759]: segfault at 0 ip 00007f2fdba298f6 sp 00007f2fc625e8a0 error 6 in chromium[7f2fd7bf8000+5a92000]
Also, before I upgraded to the nvidia drivers, I have used linux-rt-lts which causes no system freeze at all. So, are there any ideas how to fix the problem? Or how can I provide more information? Or is this not so easy fixable and I just have to go to use linux-rt-lts with nvidia-rt?
Offline
Did you remove card configuration files in /etc/X11/xorg.conf.d/ ?
Offline
Problem still there, also, the same segault message appears last.
Offline
Assuming you're using linux-rt-3.14.12_rt9-1 from AUR, you should test if the same base kernel version works without -rt patches, i.e. linux-lts from [core] repository.
also, I'd try bumping the linux-rt version to 3.14.19, if that works
Last edited by ooo (2014-09-21 17:13:34)
Offline
I had a nvidia entry in the modules list in mkinitcpio.conf and removed that.
- linux-lts starts with low resolution, adding a driver conf for X11 loads the nvidia driver. Nothing bad happened at all.
- linux-rt loads the nvidia driver (with or without x11 conf), the system does not get into an overall freeze, but:
* performance governour cannot be started:
Error setting new values. Common errors:
- Do you have proper administration rights? (super-user?)
- Is the governor you requested available and modprobed?
- Trying to set an invalid policy?
- Trying to set a specific frequency, but userspace governor is not available,
for example because of hardware which cannot be set to a specific frequency
or because the userspace governor isn't loaded?* I do have the impression that the system is hanging sometimes, especially, alt-f2 in kde takes ~20secs to appear.
* And then I get these kernel messages, for firefox
22/09/2014 17:47:02 keksmonster kernel firefox D ffff8801d83ecda0 0 2105 2103 0x00000000
22/09/2014 17:47:02 keksmonster kernel ffff8801e1ff3ab8 0000000000000086 00000000000657c0 ffff8801e1ff3fd8
22/09/2014 17:47:02 keksmonster kernel 00000000000657c0 ffff88020c590000 ffff8801d83ecda0 ffff8801e1ff3a18
22/09/2014 17:47:02 keksmonster kernel ffff8801d83ecda0 ffff8800ab665d04 ffff88020a1f8490 ffff8801e1ff3a20
22/09/2014 17:47:02 keksmonster kernel Call Trace:
22/09/2014 17:47:02 keksmonster kernel [<ffffffff8109cda5>] ? migrate_disable+0x55/0xc0
22/09/2014 17:47:02 keksmonster kernel [<ffffffff8109cfe4>] ? migrate_enable+0x94/0x1b0
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810a78f8>] ? __enqueue_entity+0x78/0x80
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810adbde>] ? enqueue_entity+0x26e/0xb00
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa035e562>] ? _nv008899rm+0x1142/0x5c10 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffff815146f0>] schedule+0x30/0xa0
22/09/2014 17:47:02 keksmonster kernel [<ffffffff815138c9>] schedule_timeout+0x1f9/0x280
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810a0007>] ? check_preempt_curr+0x57/0x90
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810a0059>] ? ttwu_do_wakeup+0x19/0x100
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810a0187>] ? ttwu_do_activate.constprop.84+0x47/0x50
22/09/2014 17:47:02 keksmonster kernel [<ffffffff810a2a4c>] ? try_to_wake_up+0x6c/0x450
22/09/2014 17:47:02 keksmonster kernel [<ffffffff815151af>] wait_for_common+0xff/0x170
22/09/2014 17:47:02 keksmonster kernel [<ffffffff8151523d>] wait_for_completion+0x1d/0x20
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05eb143>] os_acquire_semaphore+0x63/0x70 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa058f178>] _nv015134rm+0x558/0x5e0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa058f26f>] ? _nv015126rm+0x5f/0x6d0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa046747a>] ? _nv003798rm+0xbea/0x20a0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa0464aec>] ? _nv001038rm+0x11bc/0x2200 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa058d597>] ? _nv015087rm+0x197/0x310 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa058e045>] ? _nv016781rm+0x45/0x1b0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa0571ef7>] ? _nv000694rm+0x57/0xe0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05c9e02>] ? _nv000790rm+0x6b2/0x840 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05d3e03>] ? rm_ioctl+0x73/0x100 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05e222b>] ? nvidia_ioctl+0x18b/0x4b0 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05ee18f>] ? nvidia_frontend_ioctl+0x2f/0x70 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffffa05ee1f1>] ? nvidia_frontend_unlocked_ioctl+0x21/0x30 [nvidia]
22/09/2014 17:47:02 keksmonster kernel [<ffffffff811cc9f0>] ? do_vfs_ioctl+0x2d0/0x4c0
22/09/2014 17:47:02 keksmonster kernel [<ffffffff811ccc61>] ? SyS_ioctl+0x81/0xa0
22/09/2014 17:47:02 keksmonster kernel [<ffffffff8151fa29>] ? system_call_fastpath+0x16/0x1bfor amarok:
22/09/2014 17:49:03 keksmonster kernel amarok D ffff8801d80a19e0 0 2015 1 0x00000004
22/09/2014 17:49:03 keksmonster kernel ffff8800c15e9ab8 0000000000000086 00000000000657c0 ffff8800c15e9fd8
22/09/2014 17:49:03 keksmonster kernel 00000000000657c0 ffffffff81a16500 ffff8801d80a19e0 ffff8800c15e9a18
22/09/2014 17:49:03 keksmonster kernel ffff8801d80a19e0 ffff8801eec1dd04 ffff88020a1f8490 ffff8800c15e9a20
22/09/2014 17:49:03 keksmonster kernel Call Trace:
22/09/2014 17:49:03 keksmonster kernel [<ffffffff8109cda5>] ? migrate_disable+0x55/0xc0
22/09/2014 17:49:03 keksmonster kernel [<ffffffff8109cfe4>] ? migrate_enable+0x94/0x1b0
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05ec46b>] ? os_release_spinlock+0x1b/0x20 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffff810bbfa0>] ? cpuacct_charge+0x50/0x60
22/09/2014 17:49:03 keksmonster kernel [<ffffffff815146f0>] schedule+0x30/0xa0
22/09/2014 17:49:03 keksmonster kernel [<ffffffff815138c9>] schedule_timeout+0x1f9/0x280
22/09/2014 17:49:03 keksmonster kernel [<ffffffff810bc4ea>] ? rt_mutex_dequeue+0x2a/0x50
22/09/2014 17:49:03 keksmonster kernel [<ffffffff810bc7a8>] ? __try_to_take_rt_mutex+0xf8/0x150
22/09/2014 17:49:03 keksmonster kernel [<ffffffff815151af>] wait_for_common+0xff/0x170
22/09/2014 17:49:03 keksmonster kernel [<ffffffff8151523d>] wait_for_completion+0x1d/0x20
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05eb143>] os_acquire_semaphore+0x63/0x70 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa058f178>] _nv015134rm+0x558/0x5e0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa058f26f>] ? _nv015126rm+0x5f/0x6d0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa046747a>] ? _nv003798rm+0xbea/0x20a0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa0464aec>] ? _nv001038rm+0x11bc/0x2200 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa058d597>] ? _nv015087rm+0x197/0x310 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa058e045>] ? _nv016781rm+0x45/0x1b0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa0571ef7>] ? _nv000694rm+0x57/0xe0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05c9e02>] ? _nv000790rm+0x6b2/0x840 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05d3e03>] ? rm_ioctl+0x73/0x100 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05e222b>] ? nvidia_ioctl+0x18b/0x4b0 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05ee18f>] ? nvidia_frontend_ioctl+0x2f/0x70 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffffa05ee1f1>] ? nvidia_frontend_unlocked_ioctl+0x21/0x30 [nvidia]
22/09/2014 17:49:03 keksmonster kernel [<ffffffff811cc9f0>] ? do_vfs_ioctl+0x2d0/0x4c0
22/09/2014 17:49:03 keksmonster kernel [<ffffffff811d75be>] ? __fget+0x6e/0xb0
22/09/2014 17:49:03 keksmonster kernel [<ffffffff811ccc61>] ? SyS_ioctl+0x81/0xa0
22/09/2014 17:49:03 keksmonster kernel [<ffffffff8151fa29>] ? system_call_fastpath+0x16/0x1bProcesses are then not killable (SIGKILL or SIGTERM) and after the above messages appear, at some time they repeat, slightly differed in their head (above line schedule+0x30/0xa0 is):
22/09/2014 21:56:22 keksmonster kernel [<ffffffff810abbe9>] ? update_curr+0x79/0x1d0
22/09/2014 21:56:22 keksmonster kernel [<ffffffff810156c1>] ? __switch_to+0x1f1/0x540
22/09/2014 21:56:22 keksmonster kernel [<ffffffff8109cc79>] ? finish_task_switch+0x49/0x100
22/09/2014 21:56:22 keksmonster kernel [<ffffffff81514294>] ? __schedule+0x3b4/0x7e0Offline
Pages: 1