Just a reminder: the following fix should (IMO) be considered for
2.6.24. The first patch does indeed fix the OOPS on MTU however
subsequent MTU changes still OOPS. The below fixes that. I've been
using both patches for over a week and they work just great. I noticed
that the first fix made 2.6.24
On 11/16/07, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> On Fri, 16 Nov 2007 10:21:25 -0600
> "Jon Nelson" <[EMAIL PROTECTED]> wrote:
>
> > I get a segmentation fault.
> >
> > Should this patch be in addition to the one from bug 9382?
>
I get a segmentation fault.
Should this patch be in addition to the one from bug 9382?
http://bugzilla.kernel.org/attachment.cgi?id=13555&action=view
--
Jon
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at h
On 11/16/07, Jarek Poplawski <[EMAIL PROTECTED]> wrote:
> On 16-11-2007 03:18, Andrew Morton wrote:
> > On Thu, 15 Nov 2007 18:04:19 -0800 (PST) [EMAIL PROTECTED] wrote:
> >
> >> http://bugzilla.kernel.org/show_bug.cgi?id=9391
> >>
> >>Summary: Netgear GA320T(tg3) strange errors and non
On 11/15/07, Jarek Poplawski <[EMAIL PROTECTED]> wrote:
..
> Sure! I was only worried velocity_open() treats dev->mtu
> a bit different than velocity_change_mtu(), so eg. after:
>
> velocity_change_mtu() // dev is down
> velocity_open()
> velocity_change_mtu() // dev is up
>
> with the same mtu, v
I have created bug 9391 on bugzilla.kernel.org containing pretty much
everything.
--
Jon
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
On 11/15/07, Michael Chan <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-11-15 at 13:17 -0600, Jon Nelson wrote:
>
> > Is this what you mean? I pulled this from the quoted text:
> >
> > Nov 10 22:45:52 frank kernel: NETDEV WATCHDOG: eth0: transmit timed out
> >
>
On 11/15/07, Michael Chan <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-11-15 at 10:47 +0100, Jarek Poplawski wrote:
> > On 13-11-2007 19:57, Jon Nelson wrote:
> > > The best info I've got is this:
>
> It looks like the card is being reset periodically. Every tim
I'm not sure if this is the right place, but I've got a pair of GiG-E
cards that do not work correctly. Everything appears to come up just
fine, but sooner or later (typically fairly quickly) the cards weird
out and never really come back.
The best info I've got is this:
Nov 10 22:21:19 frank ker
On 11/7/07, Evgeniy Polyakov <[EMAIL PROTECTED]> wrote:
> Hi Jon.
>
> On Tue, Nov 06, 2007 at 02:23:03PM -0600, Jon Nelson ([EMAIL PROTECTED])
> wrote:
> > I was testing some network throughput today and ran into this.
> > I should note that I've this mother
[linux-raid was also emailed this same information]
I was testing some network throughput today and ran into this.
I should note that I've this motherboard has 2x MCP55 Ethernet and one
of them works fine and the other one gives lots and lots of frame
errors under load.
The following is only an h
[linux-raid was also emailed this same information]
I was testing some network throughput today and ran into this.
I should note that I've this motherboard has 2x MCP55 Ethernet and one
of them works fine and the other one gives lots and lots of frame
errors under load.
The following is only an h
12 matches
Mail list logo
