From: "Steve Lord" <lord@xfs.org>
To: "Andrew Morton" <akpm@osdl.org>
Cc: <pozsy@uhulinux.hu>, <linux-kernel@vger.kernel.org>,
<rusty@rustcorp.com.au>
Subject: Re: Race condition in module load causing undefined symbols
Date: Sat, 11 Jun 2005 15:09:08 -0500 [thread overview]
Message-ID: <000a01c56ec1$75f437d0$6401a8c0@adic.com> (raw)
In-Reply-To: 20050611120040.084942ed.akpm@osdl.org
Well, the bizarre part is that I think this has been around for a while, but
it
does not exhibit itself in redhat kernels which postdate the earliest
recolloction of me seeing it. 2.6.11-rc1 is the earliest I remember,
but I am not religious about updating the kernel on this box so
my samples are spotty.
The difference between the two may be that I recompile for a P4
while redhat uses a lowest common denominator cpu type.
If I get a chance this weekend I will try some other kernels and
report back. Maybe just start out by dumbing down my cpu
type.
Steve
> Stephen Lord <lord@xfs.org> wrote:
>>
>> I disabled hyperthreading and things started working, so are there any
>> HT related scheduling bugs right now?
>
> There haven't been any scheduler changes for some time. There have been a
> few low-level SMT changes I think.
>
> Are you able to identify which kernel version broke it?
>
>
next prev parent reply other threads:[~2005-06-11 20:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 14:03 Race condition in module load causing undefined symbols Stephen Lord
2005-06-10 18:25 ` Andrew Morton
2005-06-10 19:06 ` Steve Lord
2005-06-11 3:30 ` Stephen Lord
2005-06-11 8:26 ` Pozsár Balázs
2005-06-11 13:23 ` Steve Lord
2005-06-11 15:05 ` Pozsár Balázs
2005-06-11 17:56 ` Stephen Lord
2005-06-11 19:00 ` Andrew Morton
2005-06-11 19:08 ` Pozsár Balázs
2005-06-11 20:09 ` Steve Lord [this message]
2005-06-11 20:18 ` Pozsár Balázs
2005-06-14 13:34 ` Steve Lord
2005-06-14 15:33 ` K.R. Foley
2005-06-14 15:36 ` K.R. Foley
2005-06-14 16:38 ` Steve Lord
2005-06-14 16:56 ` Andi Kleen
2005-06-14 17:16 ` Steve Lord
2005-06-14 20:56 ` Pozsár Balázs
2005-06-14 17:10 ` K.R. Foley
2005-06-14 17:39 ` Steve Lord
2005-06-14 18:23 ` Prarit Bhargava
2005-06-14 19:27 ` Steve Lord
2005-06-14 19:32 ` Christoph Hellwig
2005-06-14 20:59 ` Pozsár Balázs
2005-06-15 11:28 ` Prarit Bhargava
2005-06-15 11:34 ` Pozsár Balázs
2005-06-15 11:35 ` Prarit Bhargava
2005-06-15 11:43 ` Pozsár Balázs
2005-06-15 12:33 ` Stephen Lord
2005-07-28 19:42 ` David Howells
2005-06-12 6:49 ` Rusty Russell
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='000a01c56ec1$75f437d0$6401a8c0@adic.com' \
--to=lord@xfs.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pozsy@uhulinux.hu \
--cc=rusty@rustcorp.com.au \
/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