mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: Martin Braun <mbraun@uni-hd.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: xfs kernel BUG again in 2.6.17.11
Date: Tue, 14 Nov 2006 11:21:52 +0000	[thread overview]
Message-ID: <20061114112152.GA11492@flower.upol.cz> (raw)
In-Reply-To: <45599B0E.8050505@uni-hd.de>

On Tue, Nov 14, 2006 at 11:31:42AM +0100, Martin Braun wrote:
> 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

2.6.18 have many XFS fixes, that were not backported to 2.6.17
(and will not, i think).

> 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
 
(And not mixing too much here, try to search last 3 months for "ntp".
 There are people, who can actually help with that. 2.6.19-rc have even
 more timekeeping fixes, maybe something will work for you).
____

      reply	other threads:[~2006-11-14 11:14 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
2006-11-14 11:21                 ` Oleg Verych [this message]

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=20061114112152.GA11492@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbraun@uni-hd.de \
    /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

all inboxes | Powered by JetHome®