search for: do_nanosleep

...x86_64 #1 Call Trace: [<ffffffff81069997>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff810699ea>] ? warn_slowpath_null+0x1a/0x20 [<ffffffff814eccc5>] ? thread_return+0x232/0x79d [<ffffffff810958e3>] ? __hrtimer_start_range_ns+0x1a3/0x460 [<ffffffff814ee5db>] ? do_nanosleep+0x8b/0xc0 [<ffffffff81095da4>] ? hrtimer_nanosleep+0xc4/0x180 [<ffffffff81094b70>] ? hrtimer_wakeup+0x0/0x30 [<ffffffff81095bd4>] ? hrtimer_start_range_ns+0x14/0x20 [<ffffffff81095ed4>] ? sys_nanosleep+0x74/0x80 [<ffffffff8100b0f2>] ? system_call_fastpath+...

...shed >- this is why I finally needed to find time to look into the problem. I shall >note though that the kernel we use does not disable CONFIG_GENERIC_TIME >and makes use of a Xen clocksource as posted by Jeremy among the >paravirt ops patches. >What happens when the hang occurs (in do_nanosleep context) is that the >time read/interpolated from the Xen provided values is in the past compared >to the last value read (and cached inside the kernel), resulting in a huge >timeout value rather than the intended 50ms one. >Without having collected data proving this (will do later toda...

https://bugs.freedesktop.org/show_bug.cgi?id=91738 Bug ID: 91738 Summary: xf86-video-nouveau 1.0.11 will not allow X to start Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Driver/nouveau

HI: I run glusterfs with four nodes, 2x2 Distributed-Replicate. I mounted it via fuse and did some test, it was ok. However when I mounted it via nfs, a problem was found: When I copied 200G files to the glusterfs, the glusterfs process in the server node(mounted by client) was killed because of OOM, and all terminals of the client were hung. Trying to test for many times, I got the