From: Grant Coady <Grant.Coady@gmail.com>
To: "Vladimir V. Saveliev" <vs@namesys.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 22:19:25 +1000 [thread overview]
Message-ID: <mc2pf1tgih72uq4flc3hl6q0897r060ilp@4ax.com> (raw)
In-Reply-To: <42FC7D5E.8020604@namesys.com>
On Fri, 12 Aug 2005 14:43:42 +0400, "Vladimir V. Saveliev" <vs@namesys.com> wrote:
>> 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.
The 'typos' are the observed errors from extracting kernel source tarball,
renaming top level directory and extracting tarball again. Other times
extraction fails with corrupt tarball error. Cached image of tarball is
corrupted as box doesn't go back to server.
Since first report I've changed to using ext2 target filesystem, still get
errors, so not reiserfs specific either.
Am in process of reducing options in kernel config, try to narrow down
what problem is. Nothing in logs, me have no idea ... yet.
Not a memory error as box compiled many hundred kernels last week without
choking. Test just now was with 2.6.13-rc6-git3, very repeatable.
Same test on different box, no errors. Other box has pro/100 NIC,
reiserfs, unpack tarball from same server. Never a problem.
Cheers,
Grant.
next prev parent reply other threads:[~2005-08-12 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 23:43 Grant Coady
2005-08-12 10:43 ` Vladimir V. Saveliev
2005-08-12 12:19 ` Grant Coady [this message]
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=mc2pf1tgih72uq4flc3hl6q0897r060ilp@4ax.com \
--to=grant.coady@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vs@namesys.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
all inboxes | Powered by JetHome®