All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: linux-kernel@vger.kernel.org
Subject: oops in do_no_page, 2.6.19-rc4
Date: Tue, 07 Nov 2006 17:34:48 +0100	[thread overview]
Message-ID: <4550B5A8.2050000@cdi.cz> (raw)

Hi,
while hunting >=2.6.18 regression my HW (see my older posts) I was able to get
the hw offline for testing. I'm able to reproduce oops below by taking cpu1
offline, then online and running "top".
More info is at http://luxik.cdi.cz/~devik/files/2618-corrupt/oops2/, I have
also /proc/kcore copy if someone wants it.
In reality there was second recursive BUG, see url above.

I run testsuite now in hope to trigger the original bug (without cpu hotplug
involved) and save crashdump using kexec..
devik

[  337.052000] BUG: unable to handle kernel paging request at virtual address 687475f9
[  337.052000]  printing eip:
[  337.052000] c01654cd
[  337.052000] *pde = 00000000
[  337.052000] Oops: 0000 [#1]
[  337.052000] SMP DEBUG_PAGEALLOC
[  337.052000] Modules linked in:
[  337.052000] CPU:    1
[  337.052000] EIP:    0060:[<c01654cd>]    Not tainted VLI
[  337.052000] EFLAGS: 00010206   (2.6.19-rc4 #7)
[  337.052000] EIP is at do_no_page+0x3e/0x2f8
[  337.052000] eax: 68747541   ebx: 00000000   ecx: c04de420   edx: c04de420
[  337.052000] esi: c6af9b7c   edi: c645254c   ebp: c70f1f30   esp: c70f1ef8
[  337.052000] ds: 007b   es: 007b   ss: 0068
[  337.052000] Process httpd (pid: 1405, ti=c70f1000 task=c70f05c0 task.ti=c70f1000)
[  337.052000] Stack: c70f05c0 c70f0ad0 00000001 cddfb85c 00000002 00000246 00000000 00000000
[  337.052000]        c70f1f40 00000246 00000002 00000000 c6af9b7c c645254c c70f1f64 c01659c4
[  337.052000]        c6af8dc8 c04de420 b7d538b5 c645254c c6af9b7c 00000000 00000001 00000001
[  337.052000] Call Trace:
[  337.052000]  [<c01659c4>] __handle_mm_fault+0xdf/0x25f
[  337.052000]  [<c034cfba>] do_page_fault+0x24a/0x5f0
[  337.052000]  [<c034b691>] error_code+0x39/0x40
[  337.052000]  [<b7f83f58>] 0xb7f83f58
[  337.052000]  =======================
[  337.052000] Code: f6 40 15 04 74 08 0f 0b 6d 08 45 0a 38 c0 c7 45 e0 00 00 00 00 c7 45 e4 
00 00
00 00 8b 55 0c 83 7a 48 00 74 1b 8b 4d 0c 8b 41 48 <8b> 80 b8 00 00 00 89 45 e0 8b 70 5c 89 
75 e4 0
f ae e8 66 66 90
[  337.056000] EIP: [<c01654cd>] do_no_page+0x3e/0x2f8 SS:ESP 0068:c70f1ef8

                 reply	other threads:[~2006-11-07 16:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4550B5A8.2050000@cdi.cz \
    --to=devik@cdi.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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.