public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Andy Isaacson <adi@bitmover.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 1352 NUL bytes at the end of a page?
Date: Thu, 13 May 2004 19:22:31 -0700	[thread overview]
Message-ID: <20040513192231.73064709.akpm@osdl.org> (raw)
In-Reply-To: <20040513190833.GH17965@bitmover.com>

Andy Isaacson <adi@bitmover.com> wrote:
>
>  We've got a user who's reporting BK problems which we've traced down to
>  the fact that his s.ChangeSet file has a hole, filled with '\0' bytes,
>  that's so far always 1352 bytes long, and the end is page-aligned.  (In
>  fact, the two cases we've seen so far have been 8k-aligned.)  The
>  correct file data picks up again after the hole.

When the reporter has a PIII machine it's often useful to find out the clock
frequency - the lower it is, the older it is and the more likely it is that
some component has rotted.

If this one cannot be reproduced on any other machine I'd say it's a
hardware failure.

  reply	other threads:[~2004-05-14  2:22 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 19:08 1352 NUL bytes at the end of a page? Andy Isaacson
2004-05-14  2:22 ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-14  4:32 Steven Cole
     [not found] <200405131723.15752.elenstev@mesatop.com>
2004-05-14 16:53 ` 1352 NUL bytes at the end of a page? (was Re: Assertion `s && s->tree' failed: The saga continues.) Andy Isaacson
2004-05-15  0:54   ` Steven Cole
2004-05-15  1:55     ` 1352 NUL bytes at the end of a page? Wayne Scott
2004-05-17  3:36 1352 NUL bytes at the end of a page? (was Re: Assertion `s && s->tree' failed: The saga continues.) Steven Cole
2004-05-17  5:17 ` Linus Torvalds
2004-05-17  6:11   ` Andrew Morton
2004-05-17 13:56     ` 1352 NUL bytes at the end of a page? Wayne Scott
2004-05-17 15:17       ` Theodore Ts'o
2004-05-17 15:20         ` Larry McVoy
2004-05-17 15:22         ` Linus Torvalds
2004-05-17 15:25           ` Larry McVoy
2004-05-17 15:37           ` viro
2004-05-17 17:30             ` Steven Cole
2004-05-17 17:40               ` viro
2004-05-17 17:39                 ` Steven Cole
2004-05-17 19:06                   ` viro
2004-05-17 15:40           ` Arjan van de Ven
2004-05-17 15:53             ` Steven Cole
2004-05-17 16:23         ` Davide Libenzi
2004-05-17 16:28           ` Davide Libenzi
2004-05-18 14:38 1352 NUL bytes at the end of a page? (was Re: Assertion `s && s->tree' failed: The saga continues.) Linus Torvalds
2004-05-19 10:53 ` Steven Cole
2004-05-19 12:10   ` Chris Mason
2004-05-19 12:20     ` 1352 NUL bytes at the end of a page? Wayne Scott
2004-05-19 12:42       ` Nick Piggin
2004-05-19 13:28         ` Steven Cole
2004-05-19 13:36           ` Chris Mason
2004-05-19 13:59             ` Steven Cole
2004-05-19 14:03               ` Wayne Scott
2004-05-19 14:08               ` Chris Mason
2004-05-19 14:20                 ` Steven Cole
2004-05-19 14:45                 ` Steven Cole

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=20040513192231.73064709.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=adi@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    /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