public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Braun <mbraun@uni-hd.de>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: David Chinner <dgc@sgi.com>, LKML <linux-kernel@vger.kernel.org>,
	xfs@oss.sgi.com
Subject: Re: xfs kernel BUG again in 2.6.17.11
Date: Tue, 14 Nov 2006 11:31:42 +0100	[thread overview]
Message-ID: <45599B0E.8050505@uni-hd.de> (raw)
In-Reply-To: <slrnelj5k3.7lr.olecom@flower.upol.cz>

Hi Oleg,

thanks for your response.
> You can find fixes in .17 stable git tree.
Yes it is a 2.6.17.11 stable kernel. - By the way: we tried to setup
kernel 2.6.18.2 on that machine but we got a weired time error, ntpdate
shows two times: first run correct time, second run time is half an hour
in the future - so we switched back to 2.6.17.11

> If it was really just sparse annotations, they were obviously
> fixed, i think. If not, meybe there are some new bugs.
> +
>> It seems that xfs_repair (2.8.10), did not find all of the errors of the FS.
>> Is there a way to be sure that the FS is clean?
> 
> As in faq:
> |   Update: a fixed xfs_repair is now available; version 2.8.10 or later
> |   of the xfsprogs package contains the fixed version.
> .....      
> |   The xfs_check tool, or xfs_repair -n, should be able to detect any
> |   directory corruption.

However the two Kernel BUGS were _after_ xfs_repair (version 2.8.10).

>> Normally  the Kernel freezes/hangs completely, but I found two new
> 
> Do you mean panic or oops here, or just freeze?

In detail:  a Kernel BUG in /var/log/messages is written and after that
the cpu load average is climbing up to 20-30, any tries to shutdown the
system, kill processes umounts etc. are in vain. Than the system freezes
completely: no keyboard, nothing.

 cheers,
martin


  reply	other threads:[~2006-11-14 10:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 14:27 kernel BUG at <bad filename>:50307! Martin Braun
2006-08-15 14:31 ` Arjan van de Ven
2006-08-16  0:11 ` Nathan Scott
2006-08-16  9:05   ` Martin Braun
     [not found]   ` <44EB228F.6020903@uni-hd.de>
     [not found]     ` <20060823134211.E2968256@wobbly.melbourne.sgi.com>
2006-11-13  9:28       ` xfs kernel BUG again in 2.6.17.11 Martin Braun
2006-11-14  4:00         ` David Chinner
2006-11-14  9:23           ` Martin Braun
2006-11-14 10:12             ` Oleg Verych
2006-11-14 10:31               ` Martin Braun [this message]
2006-11-14 11:21                 ` Oleg Verych

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45599B0E.8050505@uni-hd.de \
    --to=mbraun@uni-hd.de \
    --cc=dgc@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=olecom@flower.upol.cz \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox