From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [PATCH] (was RE: IA64 test report:Umount cdrom oops : 2.6.6 /Lion 2004-5-13: 8/10 pass)
Date: Thu, 20 May 2004 03:22:30 +0000 [thread overview]
Message-ID: <16556.9334.359144.203181@napali.hpl.hp.com> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F840462309C@PDSMSX403.ccr.corp.intel.com>
>>>>> On Thu, 20 May 2004 10:30:09 +0800, "Yu, Luming" <luming.yu@intel.com> said:
Luming> Hmm, maybe its memory ordering issue here.
>> How interesting. Do you have CONFIG_PREEMPT enabled?
Luming> grep -i preempt include/linux/autoconf.h
Luming> #undef CONFIG_PREEMPT
It can't be a memory-ordering issue then. Memory certainly is guaranteed
to be coherent...
I agree with Matthew then: most likely a compiler issue. Especially
since nobody else has reported a similar problem.
--david
next prev parent reply other threads:[~2004-05-20 3:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 13:45 [PATCH] (was RE: IA64 test report:Umount cdrom oops : 2.6.6 /Lion 2004-5-13: 8/10 pass) Yu, Luming
2004-05-19 14:22 ` Matthew Wilcox
2004-05-19 18:33 ` David Mosberger
2004-05-20 2:30 ` Yu, Luming
2004-05-20 2:31 ` Yu, Luming
2004-05-20 3:22 ` David Mosberger [this message]
2004-05-20 3:45 ` Yu, Luming
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=16556.9334.359144.203181@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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