From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Neil Schemenauer <nas@arctrix.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
Gene Heskett <gene.heskett@verizon.net>
Subject: Re: Possible dcache BUG: debugging patch
Date: Tue, 14 Sep 2004 17:06:03 -0300 [thread overview]
Message-ID: <20040914200603.GL30422@logos.cnet> (raw)
In-Reply-To: <20040914211301.GA18197@mems-exchange.org>
Hi Neil,
IIRC Gene's problem was hardware misconfiguration.
And your trace doesnt seem to look similar to his (different location inside
prune_dcache from what I remember).
Anyway, how hard is for you to reproduce this?
Yes 2.6.9-rc1-mm5 contains the remove_inode_buffers BUGs to catch NULL
list pointers, you can try that, but it might be unrelated.
Ingo was also seeing this oopses he said, but he didnt replied. Ingo?
On Tue, Sep 14, 2004 at 05:13:01PM -0400, Neil Schemenauer wrote:
> Hi Marcelo,
>
> One of our AMD K7 machines seems to be running into the dcache bug.
> I'm attaching the oops trace. Is it possible to apply your BUG
> patch to the 2.6.7 or 2.6.8.1 kernel or should I use 2.6.9-rc1-mm5?
>
> Best regards,
>
> Neil
>
>
> ======================================================================
>
> Unable to handle kernel paging request at virtual address 705f6573
> printing eip:
> c01539c6
> *pde = 00000000
> Oops: 0002 [#1]
> Modules linked in: via_rhine crc32 binfmt_capwrap
> CPU: 0
> EIP: 0060:[prune_dcache+38/288] Not tainted
> EFLAGS: 00010212 (2.6.7)
> EIP is at prune_dcache+0x26/0x120
> eax: c038edd4 ebx: c0601ec4 ecx: c8601e50 edx: 705f6573
> esi: c05e8be0 edi: 00000061 ebp: f7ffea48 esp: f7d92f0c
> ds: 007b es: 007b ss: 0068
> Process kswapd0 (pid: 32, threadinfo=f7d92000 task=f7dc6050)
> Stack: 00000080 00000000 f7d92000 c0153d92 c0131417 02c47800 00000000 00030260
> 000000eb 00000000 000000d0 000000c0 c038dca4 00000001 0000000a c038db80
> c01324b3 00000000 f7d92f9c 000000a0 00000000 000000c0 000000c0 000000c0
> Call Trace:
> [shrink_dcache_memory+18/32] shrink_dcache_memory+0x12/0x20
> [shrink_slab+311/368] shrink_slab+0x137/0x170
> [balance_pgdat+419/496] balance_pgdat+0x1a3/0x1f0
> [kswapd+182/192] kswapd+0xb6/0xc0
> [autoremove_wake_function+0/80] autoremove_wake_function+0x0/0x50
> [autoremove_wake_function+0/80] autoremove_wake_function+0x0/0x50
> [kswapd+0/192] kswapd+0x0/0xc0
> [kernel_thread_helper+5/24] kernel_thread_helper+0x5/0x18
>
> Code: 89 02 89 49 04 89 09 a1 d8 ed 38 c0 0f 18 00 90 ff 0d e0 ed
next prev parent reply other threads:[~2004-09-14 21:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 21:13 Possible dcache BUG: debugging patch Neil Schemenauer
2004-09-14 20:06 ` Marcelo Tosatti [this message]
2004-09-14 22:21 ` Neil Schemenauer
-- strict thread matches above, loose matches on Subject: below --
2004-08-19 22:25 Marcelo Tosatti
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=20040914200603.GL30422@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nas@arctrix.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