Re: 1352 NUL bytes at the end of a page?

From: Steven Cole (elenstev_at_mesatop.com)
Date: 05/14/04

  • Next message: Theodore Ts'o: "Re: [Ext2-devel] Re: [RFC/RFT] [PATCH] EXT3: Retry allocation after journal commit" 
    To: Andrew Morton <akpm@osdl.org>
Date:	Thu, 13 May 2004 22:32:01 -0600

    Andrew Morton wrote:
    >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.

    Hi Andrew,

    The user is me. The machine is a 450 Mhz P-III, about five years old now.
    Andy mentioned ethernet, but I don't have that here, just 56k dialup. The
    extra information he requested was sent a couple of hours ago, and in the
    meantime I ran two full passes of memtest86 3.1 with zero errors.

    <slight detour>
    I do occasionally have problems with pppd, and the following message always
    appears in /var/log/messages:

    May 13 18:09:30 spc kernel: serial8250: too much work for irq10
    May 13 18:09:30 spc kernel: serial8250: too much work for irq10

    The message is always doubled as above. This has never yet occurred
    at the same time as the bk failure, so the two seem unrelated. I have
    to kill -9 the pppd process and reconnect when the above happens.
    This problem never happened with a 2.4.x kernel, and was first detected
    during the middle of 2.5.x development.
    </slight detour>

    The only reason the above was at all possibly relevant to the bk failtures,
    is that I've only noticed the failures when pulling over the net via ppp.
    I've never gotten the failure when pulling from another repository
    on the same disk (I've only got one).

    If you have any ideas about narrowing down the potentially rotted
    component, please let me know.

    I cut and pasted the above from a lkml archive, so sorry if this
    messes up your mail thread. I'm not on lkml here at home, so
    please cc me on any replies.

    Steven
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  • Next message: Theodore Ts'o: "Re: [Ext2-devel] Re: [RFC/RFT] [PATCH] EXT3: Retry allocation after journal commit"

    Relevant Pages

    • Re: [Lit.] Buffer overruns
      ... percent of failures/exploits for the specific environment that are ... detailed study of the reported types of failures and the failure ... occurances of a specific failure cause to a single failure reporting ... and/or using pointers after the related operations had all be ...
      (sci.crypt)
    • Re: dts Logging
      ... errorFlag is True and package is reporting a failure to the GUI. ... DTSPackageLog.WriteStringToLog errMsg ... > www.SQLDTS.com - The site for all your DTS needs. ...
      (microsoft.public.sqlserver.dts)
    • Re: hard lockup, followed by ext4_lookup: deleted inode referenced: 524788
      ... The host ran memtest86+ for 8 hours with no errors and the disk isn't ... reporting any problems via SMART. ... I'm going to try to reproduce the failure today. ... the dumpe2fs output looks OK around group 48. ...
      (Linux-Kernel)
    • aio_sgi_init: dlopen failed, cannot map soname libdba.so
      ... I have an application using ffio that is reporting a failure in aio_sgi_init: ... aio_sgi_init: dlopen failed: Fatal Error: Cannot Successfully map soname 'libdba.so' under any of the filenames. ...
      (comp.sys.sgi.admin)
    • Re: electric gyro options
      ... in a club 182. ... haven't needed to use it in a vacum failure yet it makes me feel ... Also I had an alternator failure when IMC once and the little red flag ... the ol VOR 1 hole, which puts it just two holes away from the primary ...
      (rec.aviation.ifr)