From: Andrew Morton <akpm@digeo.com>
To: John Stoffel <stoffel@lucent.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Zwane Mwaikambo <zwane@holomorphy.com>,
Manfred Spraul <manfred@colorfullife.com>,
William Lee Irwin III <wli@holomorphy.com>
Subject: Re: 2.5.70-mm3 - Oops and hang
Date: Tue, 10 Jun 2003 12:37:32 -0700 [thread overview]
Message-ID: <20030610123732.562e7b22.akpm@digeo.com> (raw)
In-Reply-To: <16101.55819.768909.143767@gargle.gargle.HOWL>
"John Stoffel" <stoffel@lucent.com> wrote:
>
>
> Here's an oops and hang from /var/log/messages that happened the other
> evening. It kicked in at 4am or so. This was running 2.5.70-mm3 SMP,
> PREEMPT, no ACPI, RAID1 on one pair of disks, not root or /boot.
>
> Here's the messages I got in the messages file. The system was
> completely hung and needed to be reset to recover:
>
> Unable to handle kernel paging request at virtual
> address 6b6b6b6b
> printing eip:
> c0133477
> *pde = 00000000
> Oops: 0000 [#1]
> PREEMPTSMP DEBUG_PAGEALLOC
> CPU: 1
> EIP: 0060:[detach_pid+23/304] Not tainted VLI
> EIP: 0060:[<c0133477>] Not tainted VLI
> EFLAGS: 00010046
> EIP is at detach_pid+0x17/0x130
> eax: dfd30050 ebx: 6b6b6b6b ecx: dfd30100 edx: 6b6b6b6b
> esi: e3cc6000 edi: 00000000 ebp: 00000000 esp: e3cc7f08
> ds: 007b es: 007b ss: 0068
> Process makewhatis (pid: 2446, threadinfo=e3cc6000 task=e4117000)
> Stack: dfd30000 e3cc6000 00000000 c0123a79 dfd30000 c0123bb3 dfd30000 dfd30000
> dfd305c4 dfd30000 00000a07 bffff5c8 c01258cd dfd30000 ea854a74 bffff350
> dfd300a4 dfd30000 e4117000 00000000 c0125075 dfd30000 bffff5c8 00000000
> Call Trace:
> [__unhash_process+57/176] __unhash_process+0x39/0xb0
> [<c0123a79>] __unhash_process+0x39/0xb0
> [release_task+195/560] release_task+0xc3/0x230
> [<c0123bb3>] release_task+0xc3/0x230
> [wait_task_zombie+397/432] wait_task_zombie+0x18d/0x1b0
> [<c01258cd>] wait_task_zombie+0x18d/0x1b0
> [sys_wait4+357/640] sys_wait4+0x165/0x280
> [<c0125c75>] sys_wait4+0x165/0x280
> [default_wake_function+0/32] default_wake_function+0x0/0x20
> [<c011da40>] default_wake_function+0x0/0x20
> [default_wake_function+0/32] default_wake_function+0x0/0x20
> [<c011da40>] default_wake_function+0x0/0x20
> [syscall_call+7/11] syscall_call+0x7/0xb
> [<c010af1f>] syscall_call+0x7/0xb
>
> Code: 51 08 52 e8 8c cd fe ff 58 5b c3 89 f6 8d bc 27 00 00 00 00 57 56 53 89 d3 8d 14 9b 8d 04 d0 8d 88 b0 00 00 00 8b 59 08 8b 51 04 <39> 0a 74 08 0f 0b 8c 00 c8 8f 3a c0 8b 80 b0 00 00 00 39 48 04
This appears to be a visitation from the Great Unsolved Bug of the 2.5
series. Someone playing with a freed task_struct.
Correct me if I'm wrong, but this has only ever been seen with
CONFIG_PREEMPT=y?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-06-10 19:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 13:15 John Stoffel
2003-06-10 19:37 ` Andrew Morton [this message]
2003-06-10 20:10 ` John Stoffel
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=20030610123732.562e7b22.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=manfred@colorfullife.com \
--cc=stoffel@lucent.com \
--cc=wli@holomorphy.com \
--cc=zwane@holomorphy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox