Displaying 20 results from an estimated 10000 matches similar to: "Console Auto-Completion Lockup"
2013 Nov 07
8
[Bug 71362] New: [NVC1] X hang with drop to console after some time / GPU lockup
https://bugs.freedesktop.org/show_bug.cgi?id=71362
Priority: medium
Bug ID: 71362
Assignee: nouveau at lists.freedesktop.org
Summary: [NVC1] X hang with drop to console after some time /
GPU lockup
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: krah.tm at gmail.com
2004 Sep 10
1
[bodrato@gulp.linux.it: Bug#174609: flac: option "-E, --escape-coding" in man page, but not accepted]
I assume this option was intentionally removed, and the man page should
simply be updated...is this correct?
----- Forwarded message from Marco Bodrato <bodrato@gulp.linux.it> -----
Date: Sat, 28 Dec 2002 13:31:35 +0100
From: Marco Bodrato <bodrato@gulp.linux.it>
Resent-From: Marco Bodrato <bodrato@gulp.linux.it>
To: Debian Bug Tracking System <maintonly@bugs.debian.org>
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Hey,
op 04-08-14 13:57, Christian K?nig schreef:
> Am 04.08.2014 um 10:55 schrieb Maarten Lankhorst:
>> op 04-08-14 10:36, Christian K?nig schreef:
>>> Hi Maarten,
>>>
>>> Sorry for the delay. I've got way to much todo recently.
>>>
>>> Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst:
>>>> On 01-08-14 18:35, Christian K?nig
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
> It'a pain to deal with gpu reset.
Yeah, well that's nothing new.
> I've now tried other solutions but that would mean reverting to the old style during gpu lockup recovery, and only running the delayed work when !lockup.
> But this meant that the timeout was useless to add. I think the cleanest is keeping the v2 patch, because potentially any waiting code can be called
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
op 04-08-14 10:36, Christian K?nig schreef:
> Hi Maarten,
>
> Sorry for the delay. I've got way to much todo recently.
>
> Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst:
>>
>> On 01-08-14 18:35, Christian K?nig wrote:
>>> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
>>>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
op 04-08-14 16:37, Christian K?nig schreef:
>> It'a pain to deal with gpu reset.
>
> Yeah, well that's nothing new.
>
>> I've now tried other solutions but that would mean reverting to the old style during gpu lockup recovery, and only running the delayed work when !lockup.
>> But this meant that the timeout was useless to add. I think the cleanest is keeping
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
op 04-08-14 16:45, Christian K?nig schreef:
> Am 04.08.2014 um 16:40 schrieb Maarten Lankhorst:
>> op 04-08-14 16:37, Christian K?nig schreef:
>>>> It'a pain to deal with gpu reset.
>>> Yeah, well that's nothing new.
>>>
>>>> I've now tried other solutions but that would mean reverting to the old style during gpu lockup recovery, and
2014 Aug 04
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
op 04-08-14 17:04, Christian K?nig schreef:
> Am 04.08.2014 um 16:58 schrieb Maarten Lankhorst:
>> op 04-08-14 16:45, Christian K?nig schreef:
>>> Am 04.08.2014 um 16:40 schrieb Maarten Lankhorst:
>>>> op 04-08-14 16:37, Christian K?nig schreef:
>>>>>> It'a pain to deal with gpu reset.
>>>>> Yeah, well that's nothing new.
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Am 04.08.2014 um 16:40 schrieb Maarten Lankhorst:
> op 04-08-14 16:37, Christian K?nig schreef:
>>> It'a pain to deal with gpu reset.
>> Yeah, well that's nothing new.
>>
>>> I've now tried other solutions but that would mean reverting to the old style during gpu lockup recovery, and only running the delayed work when !lockup.
>>> But this
2014 Jul 31
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
---
V1 had a nasty bug breaking gpu lockup recovery. The fix is not
allowing radeon_fence_driver_check_lockup to take exclusive_lock,
and kill it during lockup recovery instead.
---
drivers/gpu/drm/radeon/radeon.h | 3 +
drivers/gpu/drm/radeon/radeon_device.c | 5 +
drivers/gpu/drm/radeon/radeon_fence.c |
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Hi Maarten,
Sorry for the delay. I've got way to much todo recently.
Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst:
>
> On 01-08-14 18:35, Christian K?nig wrote:
>> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
>>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
>>> ---
>>> V1 had a nasty bug breaking gpu lockup
2008 Oct 21
0
Lockup problem, watchdog, other ways to debug?
Hi,
I have been trying to figure out why my Supermicro X7DWA-N with dual
Xeon E5420''s locks up occasionally when running Xen, I''ve tried 3.2.1
and 3.3 with the Xensource 2.6.18 kernel, with gentoo 2.6.21, and
2.6.25 and 2.6.27 kernels patched with suse xen patches, every single
combination suffers from occasional lockups :(, I am reasonably
confident that the hardware is ok
2009 Dec 27
1
[PATCH] drm/nouveau: create function for "dealing" with gpu lockup
It's mostly a cleanup, but in nv50_fbcon_accel_init gpu lockup
message was printed, but HWACCEL_DISBALED flag was not set.
Signed-off-by: Marcin Slusarz <marcin.slusarz at gmail.com>
---
drivers/gpu/drm/nouveau/nouveau_fbcon.c | 15 +++++++++++----
drivers/gpu/drm/nouveau/nouveau_fbcon.h | 2 ++
drivers/gpu/drm/nouveau/nv04_fbcon.c | 15 +++++----------
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Am 04.08.2014 um 10:55 schrieb Maarten Lankhorst:
> op 04-08-14 10:36, Christian K?nig schreef:
>> Hi Maarten,
>>
>> Sorry for the delay. I've got way to much todo recently.
>>
>> Am 01.08.2014 um 19:46 schrieb Maarten Lankhorst:
>>> On 01-08-14 18:35, Christian K?nig wrote:
>>>> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
2014 Aug 04
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Am 04.08.2014 um 16:58 schrieb Maarten Lankhorst:
> op 04-08-14 16:45, Christian K?nig schreef:
>> Am 04.08.2014 um 16:40 schrieb Maarten Lankhorst:
>>> op 04-08-14 16:37, Christian K?nig schreef:
>>>>> It'a pain to deal with gpu reset.
>>>> Yeah, well that's nothing new.
>>>>
>>>>> I've now tried other solutions
2012 Apr 16
1
kldload uhci lockup
I observed that following could cause
machine lockup since at least 8-CURRENT.
Now I'm on 9-STABLE
No usb in kernel, attached mouse pointer.
# kldload usb ums ehci
# kldload uhci
or
# kldload uhci usb ums ehci
uhci is required for working mouse.
Can anyone confirm? Please
test few different iterations, as
it's probably not easily reproducible.
Most times nothing happens, if
2005 Dec 31
2
Resend: setting breakpoints around hypercalls in a domU causes dom0 to lockup
Any thoughts on setting breakpoints around hypercalls?
---------- Forwarded message ----------
From: Kip Macy <kip.macy@gmail.com>
Date: Dec 26, 2005 12:14 AM
Subject: setting breakpoints around hypercalls in a domU causes dom0 to
lockup
To: xen-devel <xen-devel@lists.xensource.com>, Keir Fraser <
Keir.Fraser@cl.cam.ac.uk>
Stepping through hypercalls (at the source level, not
2014 Aug 01
2
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
> ---
> V1 had a nasty bug breaking gpu lockup recovery. The fix is not
> allowing radeon_fence_driver_check_lockup to take exclusive_lock,
> and kill it during lockup recovery instead.
That looks like the delayed work starts running as soon as we submit a
2014 Aug 01
0
[PATCH 09/19] drm/radeon: handle lockup in delayed work, v2
On 01-08-14 18:35, Christian K?nig wrote:
> Am 31.07.2014 um 17:33 schrieb Maarten Lankhorst:
>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com>
>> ---
>> V1 had a nasty bug breaking gpu lockup recovery. The fix is not
>> allowing radeon_fence_driver_check_lockup to take exclusive_lock,
>> and kill it during lockup recovery instead.
>
2013 Oct 23
0
Soft lockup btrfs-transacti:680
When I try to umount btrfs filesystem I get always this error with
kernel 3.11.4 and 3.11.3, but I can mount and umount without error on
kernel 3.11.2.
Exact error messages are:
BUG: soft lockup - CPU#0 stuck for 23s! [btrfs-transacti:680]
BUG: soft lockup - CPU#1 stuck for 23s! [umount:1575]
I''m on Fedora 19
I have run scrub and there are no errors:
# btrfs scrub status /home
scrub