From: Manfred Spraul <manfred@colorfullife.com>
To: Nicolas <linux@1g6.biz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oops mm/slab.c:1563 on 2.5.68
Date: Tue, 29 Apr 2003 22:46:06 +0200 [thread overview]
Message-ID: <3EAEE48E.8030307@colorfullife.com> (raw)
Nicolas wrote:
>Apr 29 17:37:00 hal9003 kernel: drivers/usb/media/ov511.c: Invalid channel
>(-1)
>Apr 29 17:37:31 hal9003 last message repeated 123 times
>Apr 29 17:37:52 hal9003 last message repeated 89 times
>Apr 29 17:37:53 hal9003 kernel: ------------[ cut here ]------------
>Apr 29 17:37:53 hal9003 kernel: kernel BUG at mm/slab.c:1563!
>
You are running with slab debugging enabled, and the internal self test
noticed a corrupted object list.
>Apr 29 17:37:53 hal9003 kernel: invalid operand: 0000 [#1]
>Apr 29 17:37:53 hal9003 kernel: CPU: 0
>Apr 29 17:37:53 hal9003 kernel: EIP: 0060:[cache_alloc_refill+533/616]
>
The error is noticed during allocation
>Apr 29 17:37:53 hal9003 kernel: [copy_mm+456/864] copy_mm+0x1c8/0x360
>
>
of an mm_struct object.
It looks like a double-free. It was not detected during free, because
mm_struct's are larger than 512 bytes, and thus not redzoned.
Is this the first oops that occured since reboot, or were there previous
messages?
Could you provide further details about your system?
--
Manfred
next reply other threads:[~2003-04-29 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-29 20:46 Manfred Spraul [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-27 20:44 oops ide-scsi 2.5.68 Nicolas
2003-04-29 16:19 ` oops mm/slab.c:1563 on 2.5.68 Nicolas
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=3EAEE48E.8030307@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@1g6.biz \
/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