Displaying 4 results from an estimated 4 matches for "unreponsive".
Did you mean:
unresponsive
2017 Jul 03
3
[Bug 101676] New: kmail hangs or causes desktop to hang when used with Nouveau graphics driver
...uses kmail/desktop to hang
System Config, KDE Neon LTS 5.8.7, Nouveau driver 1:1.0.12-2 as described by
Ubuntu 16.04.1 LTS. Nvidia GeForce GTX570M, kmail 5.5.2.
Kmail will become unresponsive when attempting to scroll or click left on an
email. Sometimes just the controls/buttons in kmail will be unreponsive but
sometimes the whole desktop will become unreponsive and freeze, requiring a
ALT-SYSRq RSEIUB command to reboot system, ALT-F1 not working. If instead I use
the Nvidia 375 driver the problem disappears, so this problem seems to be
related to the use of the Nouveau driver. syslog reports the foll...
2006 Jun 06
1
[Fwd: Persistent "Abort due to systemic unresponsiveness"]
Just adding a few more details to the previous mail so that I can avoid
some trouble for you folks.
1. I have done a /execname != "dtrace"/ to avoid dtrace itself causing
more syscalls to be fired.
2. I have also supressed the printing on the terminal which makes dtrace
slower.
And what happens is this:
dtrace -qn ''syscall::read:entry /execname != "dtrace"/ {
2014 Jun 28
4
[Bug 80627] New: [NVE6] 'HUB_INIT timed out' 'Watchdog detected hard LOCKUP on cpu 7'
...it
Component: Driver/nouveau
Product: xorg
Created attachment 101915
--> https://bugs.freedesktop.org/attachment.cgi?id=101915&action=edit
linux 3.15.1
On kernels after ~3.14, some time after nouveau fails to initialize
(<60 seconds) ~all of userland becomes mostly unreponsive (cpu time
preemption?) [dmesg1]. The 'unresponsive' behavior starts
at around the same time 56.740245 happens.
I bisected, and found the first commit where this happens is
1f1ac3bf2a804911ad46076b10ce15364237a698. Removing this commit causes
the previous behavior: initialization fails as u...
2006 Jan 05
2
can not lvcreate after lvm snapshot and "xm mem-set" and lvremove
I am not sure if it''s a xen bug or lvm bug, or just my bad hardware,
but here''s how to reproduce:
/dev/vg0/centos1 is lvm block used by a domainU, it''s 8G in size.
#lvcreate -L8192M -s -n snap1 vg0
#mount /dev/vg0/snap1 /mnt
do some copying files here
#umount /mnt
#lvremove /dev/vg0/snap1
not removed! it says can''t allocated memory
#xm mem-set 0 512
#lvremove