Messages in this thread | | | Date | Mon, 23 Feb 2004 22:56:59 -0800 | From | Andrew Morton <> | Subject | Re: [BUG] 2.6.3 Slab corruption: errors are triggered when memory exceeds 2.5GB (correction) |
| |
Manfred Spraul <manfred@colorfullife.com> wrote: > > From your logs: > > >Feb 23 14:54:24 calypso kernel: Slab corruption: start=e00000017e84ea00, expend=e00000017e84f1ff, problemat=e00000017e84f020 > >Feb 23 14:54:24 calypso kernel: Last user: [<a0000001003c9f30>](kfree_skbmem+0x30/0x80) > >Feb 23 14:54:24 calypso kernel: Data: ************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************! **! > *************************************** > >Feb 23 14:54:28 calypso kernel: **************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************6A *************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************! **! > *************************************** > >Feb 23 14:54:28 calypso kernel: ************************************************************A5 > > > > > "6a" instead of 0x6b. One bit is wrong, this is often an indication of a > hardware problem. Do you use ECC memory and is ECC enabled in the BIOS?
Actually, it's often caused by someone doing atomic_dec_and_test() against something which was already freed. Or spin_lock(). One would need to work out what field is at that offset. If it is an atomic_t or a spinlock_t, there you are.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |