On Sunday 28 September 2014 at 15:01:21 +0100, Ben Hutchings wrote:
> On Sat, 2014-09-27 at 19:41 +0100, Mike Crowe wrote:
> > I compiled my own version of the Debian 3.2.60-1+deb7u3 kernel with
> > CONFIG_LOCKDEP and panic on hung task enabled.
> >
>
I compiled my own version of the Debian 3.2.60-1+deb7u3 kernel with
CONFIG_LOCKDEP and panic on hung task enabled.
>From the crash dump:
[25202.156175] INFO: task nfsd:3247 blocked for more than 900 seconds.
[25202.162565] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
On Thursday 31 July 2014 at 10:56:39 +0100, Simon McVittie wrote:
> On Sun, 18 May 2014 at 20:36:42 +0100, Mike Crowe wrote:
> > gnome-settings-daemon, nm-applet and (my) i3-gnome are launched correctly
> > yet gnome-screensaver is not. This appears to be due to the following l
On Monday 21 July 2014 at 15:01:31 +0100, Mike Crowe wrote:
> It is possible that I'm seeing the same problem. Our AMD Opteron 4386 (16
> cores) machine is also getting stuck with lots of hung tasks.
[snip]
> PID: 4087 TASK: 88040ea63840 CPU: 2 COMMAND: "nfsd"
It is possible that I'm seeing the same problem. Our AMD Opteron 4386 (16
cores) machine is also getting stuck with lots of hung tasks.
Although it responds to ping, and even a KVM virtual machine running on it
appears to continue working correctly, the host itself is locked up. This
happens once
I'm not absolutely sure that this is what the original reporter meant but
I've just run into this problem when using gnome-session to launch my own
"i3-gnome" session. My session file contains:
[GNOME Session]
Name=i3 Gnome session
RequiredComponents=gnome-settings-daemon;gnome-screensaver;nm-a
On Feb 14, Mike Crowe <[EMAIL PROTECTED]> wrote:
>> I don't think this issue is limited to network devices.
On Tue, Feb 14, 2006 at 01:46:30PM +0100, Marco d'Itri wrote:
> You are showing some totally unrelated issue which is obviously a
> bug in lvm2.
I admit that th
On Feb 14, Mike Crowe <[EMAIL PROTECTED]> wrote:
>> This means that on some boots the boot disk on megaraid is sda and
>> on others it's sdb.
On Tue, Feb 14, 2006 at 10:12:09PM +0100, Marco d'Itri wrote:
> It will happen among devices handled by different driver
chines
ii udev 0.081-0bpo1 /dev/ and hotplug management
daemon
--
Mike Crowe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
9 matches
Mail list logo