public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank van Maarseveen <frankvm@frankvm.com>
To: linux-kernel@vger.kernel.org
Subject: 2.6.17.13 on i386: tg3 related slab corruption
Date: Tue, 24 Oct 2006 16:31:44 +0200	[thread overview]
Message-ID: <20061024143144.GB12781@janus> (raw)

On three different machine I catched this:

2.6.17.13:
Oct 24 08:26:41 lahti kernel: Slab corruption: start=c2750ef8, len=2048
Oct 24 08:26:41 lahti kernel: Redzone: 0x5a2cf071/0x5a2cf071.
Oct 24 08:26:41 lahti kernel: Last user: [release_mem+232/496](release_mem+0xe8/0x1f0)
Oct 24 08:26:41 lahti kernel: 0b0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ff ff ff ff
Oct 24 08:26:41 lahti kernel: 0c0: 00 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Oct 24 08:26:41 lahti kernel: Prev obj: start=c27506ec, len=2048
Oct 24 08:26:41 lahti kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Oct 24 08:26:41 lahti kernel: Last user: [tg3_alloc_rx_skb+123/368](tg3_alloc_rx_skb+0x7b/0x170)
Oct 24 08:26:41 lahti kernel: 000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct 24 08:26:41 lahti kernel: 010: 5a 5a 00 13 72 ad 5b ba 00 50 56 00 02 d6 08 06
Oct 24 08:26:41 lahti kernel: Next obj: start=c2751704, len=2048
Oct 24 08:26:41 lahti kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Oct 24 08:26:41 lahti kernel: Last user: [tg3_alloc_rx_skb+123/368](tg3_alloc_rx_skb+0x7b/0x170)
Oct 24 08:26:41 lahti kernel: 000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct 24 08:26:41 lahti kernel: 010: 5a 5a 00 13 72 ad 5b ba 00 0e 0c bc 74 a5 08 00

2.6.17.8:
Oct 24 16:06:20 jaala kernel: Slab corruption: start=e582d0c4, len=2048
Oct 24 16:06:20 jaala kernel: Redzone: 0x5a2cf071/0x5a2cf071.
Oct 24 16:06:20 jaala kernel: Last user: [release_mem+232/496](release_mem+0xe8/0x1f0)
Oct 24 16:06:20 jaala kernel: 0b0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ff ff ff ff
Oct 24 16:06:20 jaala kernel: 0c0: 00 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Oct 24 16:06:20 jaala kernel: Prev obj: start=e582c8b8, len=2048
Oct 24 16:06:20 jaala kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Oct 24 16:06:20 jaala kernel: Last user: [tg3_alloc_rx_skb+123/368](tg3_alloc_rx_skb+0x7b/0x170)
Oct 24 16:06:20 jaala kernel: 000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct 24 16:06:20 jaala kernel: 010: 5a 5a 00 14 22 4c b1 01 00 12 3f 84 84 fe 08 00

2.6.17.13:
Oct  5 18:02:28 espoo kernel: Slab corruption: start=c221cb78, len=2048
Oct  5 18:02:28 espoo kernel: Redzone: 0x5a2cf071/0x5a2cf071.
Oct  5 18:02:28 espoo kernel: Last user: [release_mem+232/496](release_mem+0xe8/0x1f0)
Oct  5 18:02:28 espoo kernel: 0b0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b ff ff ff ff
Oct  5 18:02:28 espoo kernel: 0c0: 00 00 00 00 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
Oct  5 18:02:28 espoo kernel: Prev obj: start=c221c36c, len=2048
Oct  5 18:02:28 espoo kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Oct  5 18:02:28 espoo kernel: Last user: [tg3_alloc_rx_skb+123/368](tg3_alloc_rx_skb+0x7b/0x170)
Oct  5 18:02:28 espoo kernel: 000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct  5 18:02:28 espoo kernel: 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct  5 18:02:28 espoo kernel: Next obj: start=c221d384, len=2048
Oct  5 18:02:28 espoo kernel: Redzone: 0x170fc2a5/0x170fc2a5.
Oct  5 18:02:28 espoo kernel: Last user: [tg3_alloc_rx_skb+123/368](tg3_alloc_rx_skb+0x7b/0x170)
Oct  5 18:02:28 espoo kernel: 000: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a
Oct  5 18:02:28 espoo kernel: 010: 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a


Since I saw some other discussions regarding TSO: According to ethtool it is off.

-- 
Frank

                 reply	other threads:[~2006-10-24 14:31 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20061024143144.GB12781@janus \
    --to=frankvm@frankvm.com \
    --cc=linux-kernel@vger.kernel.org \
    /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