: 0
netfinity5000:~$ free
total used free sharedbuffers cached
Mem: 20748041340228 734576 0 294672 805404
-/+ buffers/cache: 2401521834652
Swap: 1943860 01943860
Best regards,
Hans-Juergen Mauser
Hello,
Ben Hutchings wrote:
[...]
I think it's fine and has nothing to do with the problem.
Since you say it has taken 1-8 days for any problem to appear, I suppose
you will have to wait a few weeks to have some confidence that
'nowatchdog' makes a difference.
well, even if you think
Hello,
currently the system starts reaching an amount of uptime that was hardly
possible before setting nowatchdog:
netfinity5000:~# uptime
13:43:12 up 10 days, 20:43, 2 users, load average: 0,01, 0,08, 0,07
When we reach 14 days or more, we know that it's really the watchdog/NMI
feature
Hello,
Ben Hutchings wrote:
On Thu, 2012-06-21 at 21:25 +0200, Hans-Juergen Mauser wrote:
[...]
Here we see
again how bad the documentation of open-source projects sometimes is
cared about... even when configuring a kernel, the config help says that
the nmi watchdog had to be enabled
Package: linux-2.6
Version: 2.6.38-5
Hello!
(Backgrund information: the motivation for this bug report comes from
bug 639331 which already seems to have dug more deeply into the version
introducing this berhaviour)
The NMI watchdog mechanism (as I know today it is the probable source)
has
Hello!
I am very happy having found this bug report as it is possible that the
NMI watchdog mechanism has given me serious headaches since Debian
kernel 2.6.38 was released! I cannot tell it definitely yet as it is an
intermittent error in my case which may take up to a week to appear
once,
6 matches
Mail list logo
