From: Dave Jones <davej@redhat.com>
To: Dave Peterson <dsp@llnl.gov>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
norsk5@xmission.com, dthompson@linuxnetworx.com
Subject: Re: edac slab corruption.
Date: Mon, 6 Mar 2006 12:53:32 -0500 [thread overview]
Message-ID: <20060306175332.GB15971@redhat.com> (raw)
In-Reply-To: <200603060944.53601.dsp@llnl.gov>
On Mon, Mar 06, 2006 at 09:44:53AM -0800, Dave Peterson wrote:
> On Saturday 04 March 2006 23:43, Dave Jones wrote:
> > rmmod e752x_edac edac_mc
> > Wait a few seconds...
> >
> > EDAC MC0: Removed device 0 for "e752x_edac" E7525: PCI 0000:00:00.0
> > Slab corruption: start=ffff81003fc5a000, len=4096
> >
> > Call Trace: <ffffffff8017bcab>{check_poison_obj+121}
> > <ffffffff802028a8>{kobject_uevent+676}
> > <ffffffff8017be34>{cache_alloc_debugcheck_after+48}
> > <ffffffff802028a8>{kobject_uevent+676}
> > <ffffffff8017dd52>{__kmalloc_track_caller+301}
> > <ffffffff802db731>{__alloc_skb+97} <ffffffff80202701>{kobject_uevent+253}
> > <ffffffff802028a8>{kobject_uevent+676}
> > <ffffffff80201fd6>{kobject_unregister+14}
> > <ffffffff8026f273>{bus_remove_driver+126}
> > <ffffffff8027004a>{driver_unregister+9}
> > <ffffffff8020f4a8>{pci_unregister_driver+16}
> > <ffffffff8014ec37>{sys_delete_module+551}
> > <ffffffff8010dbdc>{syscall_trace_enter+156}
> > <ffffffff8010a91c>{tracesys+209} 0f0: 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b
> > 6a 6b 6b 6b
> >
> > Dave
>
> Which version of the EDAC code was this observed with?
2.6.16rc5-gitX (I forget the exact -git release, but it's
not relevant as edac hasn't changed recently).
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-06 17:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-05 7:43 edac slab corruption Dave Jones
2006-03-06 17:44 ` Dave Peterson
2006-03-06 17:53 ` Dave Jones [this message]
2006-03-07 16:53 ` Dave Peterson
2006-03-07 16:57 ` Dave Jones
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=20060306175332.GB15971@redhat.com \
--to=davej@redhat.com \
--cc=dsp@llnl.gov \
--cc=dthompson@linuxnetworx.com \
--cc=linux-kernel@vger.kernel.org \
--cc=norsk5@xmission.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.