From: Ben Greear <greearb@candelatech.com>
To: Urban Widmark <urban@teststation.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Stephan von Krawczynski <skraw@ithnet.com>
Subject: Re: VIA Rhine problem in 2.4.9-pre4
Date: Sun, 26 Aug 2001 21:41:25 -0700 [thread overview]
Message-ID: <3B89CF75.376CBE5B@candelatech.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10108251909110.13314-100000@ada.teststation.com>
Urban Widmark wrote:
>
> On Fri, 24 Aug 2001, Ben Greear wrote:
>
> > This last time it happened, I noticed this printed to the console:
> >
> > eth0: Oversized Ethernet frame spanned multiple buffers, entry 0x9 length 0 status 00000600
> > eth0: Oversized Ethernet frame c7572090 vs c7572090.
>
> I can't answer what this is, but I can point you to a prevous discussion
> on the subject:
> http://uwsg.iu.edu/hypermail/linux/net/0006.1/0005.html
>
> I assume that this is not a problem that you only get on 2.4.9-pre4, but
> on any kernel version you try?
I believe the problem was that my program that reads information out of
the drivers (IP, mask, MTU, QLEN, and the MII-diag flags) was in a very
tight loop, and so was almost constantly trying to read the information.
I fixed that problem, and haven't seen the NIC lock up since. If I
get a chance, I'm going to make a stand-alone GPL version of that code, and when
I do I'll add an option to stress the kernel/drivers and see if I can
reproduce this NIC lockup.
Thanks,
Ben
>
> Drivers for other cards have also reported this (search on google).
>
> Donald Beckers answer to a question on this subject:
> http://uwsg.iu.edu/hypermail/linux/net/9801.1/0159.html
>
> > I looked at /proc/net/dev and didn't see too many errors (there were a few, though,
> > including carrier errors). I tried replacing the cable but that did not fix
> > the problem. The link does come back up after reboot...
>
> Does unloading the modules and then reloading it help? (assuming you run
> it as a module). ifconfig down/up is another variant some people have
> used for other problems.
ifup/down didn't help, but I didn't try reloading the module.
>
> /Urban
>
> -
> 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/
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2001-08-27 4:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 6:55 VIA Rhine problem in 2.4.9-pre4 Ben Greear
2001-08-25 17:30 ` Urban Widmark
2001-08-27 4:41 ` Ben Greear [this message]
2001-08-27 7:39 ` Urban Widmark
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=3B89CF75.376CBE5B@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
--cc=urban@teststation.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