edac slab corruption.
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
Signature · 1 line
http://www.codemonkey.org.uk
Quoted 22 lines · Dave Jones
rmmod
e752x_edacedac_mc
Wait a few seconds...EDAC MC0: Removed device 0 for "
e752x_edac" E7525: PCI 0000:00:00.0 Slab corruption: start=ffff81003fc5a000, len=4096Call 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
Quoted 1 line
Dave
Which version of the EDAC code was this observed with?
Quoted 23 lines · Dave Peterson
Quoted 22 lines · Dave Jones
rmmod
e752x_edacedac_mc
Wait a few seconds...EDAC MC0: Removed device 0 for "
e752x_edac" E7525: PCI 0000:00:00.0 Slab corruption: start=ffff81003fc5a000, len=4096Call 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
Quoted 3 lines
Quoted 1 line
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
Signature · 1 line
http://www.codemonkey.org.uk
Quoted 22 lines · Dave Jones
rmmod
e752x_edacedac_mc
Wait a few seconds...EDAC MC0: Removed device 0 for "
e752x_edac" E7525: PCI 0000:00:00.0 Slab corruption: start=ffff81003fc5a000, len=4096Call 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
Quoted 1 line
Dave
Can this behavior be reproduced relatively easily? One thing that may be worth checking is whether this reproduces with a 2.6.16-rc5-mm2 kernel. Some EDAC bug fixes were added to that kernel
Quoted 23 lines · Dave Peterson
Quoted 22 lines · Dave Jones
rmmod
e752x_edacedac_mc
Wait a few seconds...EDAC MC0: Removed device 0 for "
e752x_edac" E7525: PCI 0000:00:00.0 Slab corruption: start=ffff81003fc5a000, len=4096Call 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
Quoted 3 lines
Quoted 1 line
Dave
Can this behavior be reproduced relatively easily?
yep.
Quoted 3 lines
One thing that
may be worth checking is whether this reproduces with a 2.6.16-rc5-mm2 kernel. Some EDAC bug fixes were added to that kernel
I've got zero time to jump on this right now -- trying to get FC5 shippable :-/ I'll try and get back to it at some point.
Dave
Signature · 1 line
http://www.codemonkey.org.uk