From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.7-mm2 oopses and badness
Date: Thu, 24 Jun 2004 12:01:44 -0700 [thread overview]
Message-ID: <27420000.1088103704@flay> (raw)
In-Reply-To: <1968860000.1088089370@[10.10.2.4]>
> During bootup, shortly after CPU init (mm1 was fine):
>
> Only candidate I can see is
> +reduce-tlb-flushing-during-process-migration-2.patch
> Will try backing that out unless you want something else ...
Looks like that's ia64 only ;-(
But the oops seems like we're just calling flush_tlb_mm with a NULL mm.
> Jun 24 06:54:24 larry kernel: c010e98b
> Jun 24 06:54:24 larry kernel: SMP
> Jun 24 06:54:24 larry kernel: c010e98b
> Jun 24 06:54:24 larry kernel: Modules linked in:
> Jun 24 06:54:24 larry kernel: CPU: 12
> Jun 24 06:54:24 larry kernel: EIP: 0060:[flush_tlb_mm+7/120] Not tainted VLI
> Jun 24 06:54:24 larry kernel: EFLAGS: 00010292 (2.6.7-mm2)
> Jun 24 06:54:24 larry kernel: EIP is at flush_tlb_mm+0x7/0x78
> Jun 24 06:54:24 larry kernel: eax: 00000000 ebx: f124bfa8 ecx: 00000000 ed
> x: f124bf94
> Jun 24 06:54:24 larry kernel: esi: c30d3be0 edi: 00000000 ebp: f124bf9c esp: f124bf4c
> Jun 24 06:54:24 larry kernel: ds: 007b es: 007b ss: 0068
> Jun 24 06:54:24 larry kernel: Process kswapd3 (pid: 72, threadinfo=f124a000 task=f1247390)
> Jun 24 06:54:24 larry kernel: Stack: 00200200 c01159e1 00000000 f1247390 f124bfdc f124bff0 f124bfa8 c02bcc40
> Jun 24 06:54:24 larry kernel: 00000000 00000282 f124bf74 f124bf74 00000000 f1247390 0000000c f124a000
> Jun 24 06:54:24 larry kernel: 00000000 00000001 f124bf94 f124bf94 f1a00000 c0138bca f1247390 0000f000
> Jun 24 06:54:24 larry kernel: Call Trace:
> Jun 24 06:54:24 larry kernel: [set_cpus_allowed+225/252] set_cpus_allowed+0xe1/0xfc
> Jun 24 06:54:24 larry kernel: [kswapd+142/224] kswapd+0x8e/0xe0
> Jun 24 06:54:24 larry kernel: [kswapd+0/224] kswapd+0x0/0xe0
> Jun 24 06:54:24 larry kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
> Jun 24 06:54:24 larry kernel: [autoremove_wake_function+0/64] autoremove_wake_function+0x0/0x40
> Jun 24 06:54:24 larry kernel: [kernel_thread_helper+5/12] kernel_thread_helper+0x5/0xc
> Jun 24 06:54:24 larry kernel: Code: 0f 20 d8 0f 22 d8 8b 04 24 85 c0 74 13 6a ff 51 50 e8 0a ff ff ff 83 c4 0c 8d b4 26 00 00 00 00 59 c3 89 f6 83 ec
> 04 8b 4c 24 08 <8b> 81 24 01 00 00 ba 00 e0 ff ff 21 e2 89 04 24 8b 42 10 f0 0f
next prev parent reply other threads:[~2004-06-24 19:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 15:02 2.6.7-mm2 oopses and badness Martin J. Bligh
2004-06-24 19:01 ` Martin J. Bligh [this message]
2004-06-24 19:02 ` Andrew Morton
2004-06-24 20:59 ` Martin J. Bligh
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=27420000.1088103704@flay \
--to=mbligh@aracnet.com \
--cc=akpm@osdl.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox