Jerry Winegarden wrote:
> On Thu, 23 Mar 2000, Jake Johnson wrote:
>
> > I have a pci dlink 530T and I am using the via-rhine.o module and I keep
> > getting this error message in my sys-log. Everything works but I was
> > hoping to find more info on this error!
> >
> What network services are you trying to provide/use at the time?
>
> They are annoying, but can perhaps be ignored (but of course you'd like
> them to stop, right?), depending on what you are trying to do.
>
> I have gotten this message (I love the message: some wicked happened :-)
> when NFS exporting file system to an old Sun Solaris box. I restored
[...]
Looking at the code to via-rhine.c, it looks like that's suppose to trigger
under the following condition
(intr_status & ~(IntrLinkChange|IntrStatsMax|IntrTxAbort)) && debug
The presense of "debug" in the code indicates it's likely not a serious
error. From the place in the code, it looks like its there to trap
otherwise unhandled events.
I suppose one solution would be to set debug to 0 in the code and recompile
the module. :-)
-W-
> files from backup tapes on the Solaris box to the Linux file systems
> (vrestore). (Linux to the rescue! I just happened to have a PC with
> RedHat that I'd just installed with an 18GB drive (<$130 at that time).
> Where else would we have had the disk space to restore all the huge
> database files in order to look for the right one from which to get all
> their data back (this was a disk emergency on the solaris system and
> involved re-engineering the oracle database).
>
> When I used the Oracle import function to read some
> data back from backup (now copied to the Linux box) to the database on the
> Solaris box, I'd keep getting those error messages, every now and then
> (dealing with files of a GB or so). What counts is that things worked,
> but I got several notices of alleged "wicked" activity on my system! :-)
> In my case, since I was just using this configuration temporarily, and
> things worked.
>
> I suspect the problem came possibly from: different block size of
> ufs (Solaris) and e2fs (Linux) file systems, perhaps something funky
> about the particular records (size?) being read, and perhaps something
> slightly incompatible with (newer) Linux NFS service and (older) Sun NFS
> mount. Of course, I'm curious and would like to know myself. We were
> pushing data along at a pretty good clip (the 10T segment was quiet
> except for this transaction, Pentium III 500 on my end)!
>
> I don't think the problem came from the ethernet drivers (I had via-rhine
> with DLINK PCI), but, then I admittedly didn't read the source code yet
> to see what conditions can cause the error.
>
> The point of my story is to show how it might depend on what you
> are doing with network services. Are you providing nfs mounts of
> partitions to other systems? What else might you be doing?
>
> ***************************************************************************
> Jerry Winegarden OIT/Technical Support Duke University
> [EMAIL PROTECTED] http://www-jerry.oit.duke.edu
> ***************************************************************************
>
>
>
> --
> To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
> as the Subject.
--
Wayne Dyer || Recontextualizing the male myth
[EMAIL PROTECTED] || myth since 1963
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.
