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.
Joseph Landry wrote:
Jonathan Nieder wrote:
I wonder if the fix cred: Fix get_task_cred() and task_state() to not
resurrect dead credentials included in 2.6.32-31 fixes this. What is
the latest kernel version you've tested, and what was the result?
[...]
I dont use lenny anymore, and I
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 latest lenny-backport kernel on a new
Hi,
Joseph Landry wrote:
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 vmcore backup with kexec in order to collect
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
message?
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
On Tue, 2010-08-10 at 11:49 +0200, Joseph Landry wrote:
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:
7 matches
Mail list logo
