From: Richard Fuchs <richard.fuchs@inode.info>
To: Matt Mackall <mpm@selenic.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: slab corruption in skb allocs
Date: Fri, 04 Mar 2005 22:19:21 +0100 [thread overview]
Message-ID: <4228D0D9.9010301@inode.info> (raw)
In-Reply-To: <20050304201153.GR3163@waste.org>
_correction_ to my previous mail, this does _not_ happen with the
eepro100 driver. (sorry for the confusion, i got the kernel images mixed
up with all the testing i've been doing.)
could this affect the e1000 driver as well?
Matt Mackall wrote:
> Send the output of ethtool, please.
box 1, affected:
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Current message level: 0x000020c1 (8385)
Link detected: yes
box 2, affected:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
box 3, not affected:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
Link detected: yes
> This tends to be checksum
> offloading not working as it should or the like. Can you repeat this
> with bulk ssh traffic?
yes, with various strange effects:
Received disconnect from 195.58.172.154: 2: Bad packet length 919251405.
or
Received disconnect from 195.58.172.154: 2: Corrupted MAC on input.
cheers
richard
next prev parent reply other threads:[~2005-03-04 23:43 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 9:55 slab corruption in skb allocs Richard Fuchs
2005-03-04 11:53 ` Andrew Morton
2005-03-04 12:23 ` Richard Fuchs
2005-03-04 20:11 ` Matt Mackall
2005-03-04 21:19 ` Richard Fuchs [this message]
2005-03-04 21:27 ` Matt Mackall
2005-03-04 21:52 ` Richard Fuchs
2005-03-04 22:05 ` Matt Mackall
2005-03-04 22:51 ` Richard Fuchs
2005-03-05 18:25 ` Scott Feldman
2005-03-05 19:10 ` Richard Fuchs
2005-03-06 17:44 ` Scott Feldman
2005-03-06 18:40 ` Richard Fuchs
2005-03-07 5:07 ` Scott Feldman
2005-03-07 8:30 ` Richard Fuchs
2005-03-04 18:10 ` Dave Jones
2005-03-04 18:32 ` Richard Fuchs
2005-03-04 19:29 ` Richard Fuchs
2005-03-21 22:36 ` Andrew Morton
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=4228D0D9.9010301@inode.info \
--to=richard.fuchs@inode.info \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.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