On Wed, Feb 24, 2010 at 01:43:59PM +0100, Bernd Zeimetz wrote:
Moritz Muehlenhoff wrote:
Does this error still occur with 2.6.26-21 from the latest point
update, which introduced two patches which might have fixed this error?
We'll give it a try as soon as time permits, the machine is
On 07/30/2011 02:27 PM, Moritz Mühlenhoff wrote:
On Wed, Feb 24, 2010 at 01:43:59PM +0100, Bernd Zeimetz wrote:
Moritz Muehlenhoff wrote:
Does this error still occur with 2.6.26-21 from the latest point
update, which introduced two patches which might have fixed this error?
We'll give it a
Moritz Muehlenhoff wrote:
Does this error still occur with 2.6.26-21 from the latest point
update, which introduced two patches which might have fixed this error?
We'll give it a try as soon as time permits, the machine is turned off right now
and other models are in production and not using
On Wed, Oct 28, 2009 at 10:39:10AM +0100, Bernd Zeimetz wrote:
Package: linux-2.6
Version: 2.6.26-19
Severity: important
We get the following backtrace way too often, it repeats for all CPUs,
but I'm pasting it only once here.
Does this error still occur with 2.6.26-21 from the latest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
found 552706 2.6.26-13lenny2
thanks
I get something similar on our HP Proliant 360DL G5 server. It's a
quad-core Xeon running linux-image-2.6.26-1-openvz-amd64
(2.6.26-13lenny2). This has happened several times during the last few
weeks.
Package: linux-2.6
Version: 2.6.26-19
Severity: important
We get the following backtrace way too often, it repeats for all CPUs,
but I'm pasting it only once here.
[633582.838114] BUG: soft lockup - CPU#0 stuck for 61s! [init:1]
[633582.838114] Modules linked in: nfs lockd nfs_acl sunrpc ipip
6 matches
Mail list logo
