From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Grant Coady <Grant.Coady@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via-Rhine NIC, Via SATA or reiserfs broken, how to tell??
Date: Fri, 12 Aug 2005 14:43:42 +0400 [thread overview]
Message-ID: <42FC7D5E.8020604@namesys.com> (raw)
In-Reply-To: <54nnf1tv8722aq6med3mlr4mvg7nli0r09@4ax.com>
Hello
Grant Coady wrote:
> Greetings,
>
> Situation is dataloss with no errors logged.
>
> Test: unpack 2.6.12 tarball from NFS mount source, diff against
> previous attempt:
>
> $ diff -Nrup linux-2.6.12.old linux-2.6.12
> Binary files linux-2.6.12.old/include/asm-sparc/a.out.h and linux-2.6.12/include/asm-sparc/a.out.h differ
> diff -Nrup linux-2.6.12.old/include/asm-sparc/apc.h linux-2.6.12/include/asm-sparc/apc.h
> --- linux-2.6.12.old/include/asm-sparc/apc.h 2005-06-18 05:48:29.000000000 +1000
> +++ linux-2.6.12/include/asm-sparc/apc.h 2005-06-18 05:48:29.000000000 +1000
> @@ -31,7 +31,7 @@
> #define APC_BPORT_REG 0x30
>
> #define APC_REGMASK 0x01
> -define APC_BPMASK 0x03
> +#define APC_BPMASK 0x03
>
> /*
> * IDLE - CPU standby values (set to initiate standby)
> diff -Nrup linux-2.6.12.old/include/asm-sparc/svr4.h linux-2.6.12/include/asm-sparc/svr4.h
> --- linux-2.6.12.old/include/asm-sparc/svr4.h 2005-06-18 05:48:29.000000000 +1000
> +++ linux-2.6.12/include/asm-sparc/svr4.h 2005-06-18 05:48:29.000000000 +1000
> @@ -15,7 +15,7 @@ typedef struct { /* signa
>
> /* Values for siginfo.code */
> #define SVR4_SINOINFO 32767
> -/* Siginfo, sucker expects bunch of information on those paramEters */
> +/* Siginfo, sucker expects bunch of information on those parameters */
> typedef union {
> char total_size [128];
> struct {
>
>
> Seems like three bit errors for source tree. Other times I've noted
> compile failures where unpacking source tree fresh would 'fix' error.
> I'd previously assumed that I accidentally killed source tree with
> 'cp -al ...' copies but I've had a segfault on that operation, hence
> I do not know if this be NIC or filesystem (reiserfs on via SATA).
>
>
> Today disabled onboard via-rhine and used Intel pro/100 + e100 driver,
> several source trees unpacked identically, running 2.6.12.4 or 2.4.31-hf3
>
> The fault occurs on 2.4 latest or 2.6 latest only on particular target
> box, so problem is not the NFS server.
>
> How to test and isolate this error is in NIC driver, SATA driver or
> filesystem?
>
Could it be that tarbal on NFS server changed?
It is not very likely that error in kernel drivers fixed typos in source code.
> Thanks,
> Grant.
>
> -
> 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 prev parent reply other threads:[~2005-08-12 10:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 23:43 Via-Rhine NIC, Via SATA or reiserfs broken, how to tell?? Grant Coady
2005-08-12 10:43 ` Vladimir V. Saveliev [this message]
2005-08-12 12:19 ` Grant Coady
2005-08-12 14:21 ` Masoud Sharbiani
2005-08-12 22:13 ` Grant Coady
2005-08-14 9:12 ` Resolved?: " Grant Coady
2005-08-14 12:12 ` Roger Luethi
2005-08-14 20:13 ` Grant Coady
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=42FC7D5E.8020604@namesys.com \
--to=vs@namesys.com \
--cc=Grant.Coady@gmail.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