I came to the same conclusion as Daniel Povey in Message #56.
RestartSec in systemd-journal-flush does not help in this case. it is a
one-shot service and it will not be restarted.
Note that in my case systemd-journald is killed due to a watchdog timeout when
the server is under heavy load.
As
Jonathan Nieder wrote :
> found 592497 linux-2.6/2.6.32-35
> quit
>
> Joseph Landry wrote:
>
>> I made a short test with squeeze's 2.6.32-35 and it crashed 2 hours
>> later. Unfortunately kdump didn't work and switched to
>> squeeze-backport 2.6.38
> Thanks. FWIW the kernels installed in the past are listed in
> /var/log/dpkg.log*.
Yes, I actually did install squeeze's 2.6.32-35 but I didn't use it
immediately, I kept using lenny-backport 2.6.32 by mistake.
I made a short test with squeeze's 2.6.32-35 and it crashed 2 hours later.
Unfortu
I dont use lenny anymore, and I don't remember if we tested 2.6.32-31 on our
server.
I will test squeeze's 2.6.32-35 (linux-image-2.6.32-5-686-bigmem) and keep you
informed if the bug is still there.
Joseph.
> Hi,
>
> Joseph Landry wrote:
>
>> I'm using the
>> Hi,
>> I'm using the latest lenny-backport kernel on a new dell poweredge R710.
>> every few days I have a kernel panic similar to : Kernel panic - not
>> syncing: CRED: put_cred_rcu() sees f640ad80 with usage -163535872"
>
> Do you see the same message (apart from the numbers) or different
>
Package: linux-2.6
Version: 2.6.32-15~bpo50+1
Severity: important
Hi,
I'm using the latest lenny-backport kernel on a new dell poweredge R710.
every few days I have a kernel panic similar to : Kernel panic - not syncing:
CRED: put_cred_rcu() sees f640ad80 with usage -163535872"
I automated a vmco
6 matches
Mail list logo
