Displaying 4 results from an estimated 4 matches for "unreponsiveness".
Did you mean:
unresponsiveness
2017 Jul 03
3
[Bug 101676] New: kmail hangs or causes desktop to hang when used with Nouveau graphics driver
https://bugs.freedesktop.org/show_bug.cgi?id=101676
Bug ID: 101676
Summary: kmail hangs or causes desktop to hang when used with
Nouveau graphics driver
Product: Mesa
Version: unspecified
Hardware: Other
OS: Linux (All)
Status: NEW
Severity: critical
Priority: medium
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'
https://bugs.freedesktop.org/show_bug.cgi?id=80627
Priority: medium
Bug ID: 80627
Assignee: nouveau at lists.freedesktop.org
Summary: [NVE6] 'HUB_INIT timed out' 'Watchdog detected hard
LOCKUP on cpu 7'
QA Contact: xorg-team at lists.x.org
Severity: normal
Classification: Unclassified
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