From: "Chen, Kenneth W" <kenneth.w.chen@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [ia64 R&D] CONFIG_IA64_MCA
Date: Fri, 07 May 2004 21:28:12 +0000 [thread overview]
Message-ID: <200405072128.i47LSCF00505@unix-os.sc.intel.com> (raw)
In-Reply-To: <EFC4A8BDEDB4B846BC47F0ED773E812C0734C47C@xsun09.ptp.hp.com>
>>>> Jesse Barnes wrote on Friday, May 07, 2004 12:57 PM
>
> On Tuesday, May 4, 2004 7:51 pm, CURRY,JOHN W (HP-Cupertino,ex1) wrote:
> > Well, once it's working I think this will be okay for our team.
>
> Any chance you could test the patch for me? Anyone else have hw they
> could try it on?
Is there another patch or this is the latest one?
http://www.gelato.unsw.edu.au/linux-ia64/0405/9514.html
If that's the latest one, then it won't boot on any machine with nomca
parameter because once match found, it stuck in the for loop and memcmp
endlessly, cp never gets incremented :-(
How about this one:
diff -Nur linux-2.6.6-rc3/arch/ia64/kernel/setup.c linux-2.6.6-rc3.ken/arch/ia64/kernel/setup.c
--- linux-2.6.6-rc3/arch/ia64/kernel/setup.c 2004-04-27 18:35:09.000000000 -0700
+++ linux-2.6.6-rc3.ken/arch/ia64/kernel/setup.c 2004-05-07 14:22:18.000000000 -0700
@@ -360,8 +360,9 @@
# endif
#endif
- /* enable IA-64 Machine Check Abort Handling */
- ia64_mca_init();
+ /* enable IA-64 Machine Check Abort Handling unless disabled */
+ if (!strstr(saved_command_line, "nomca "))
+ ia64_mca_init();
platform_setup(cmdline_p);
paging_init();
next prev parent reply other threads:[~2004-05-07 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 18:35 FW: [ia64 R&D] CONFIG_IA64_MCA John Curry
2004-05-03 18:41 ` Jesse Barnes
2004-05-04 13:53 ` Luck, Tony
2004-05-04 15:19 ` Jesse Barnes
2004-05-04 16:06 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-04 16:34 ` Jesse Barnes
2004-05-05 2:51 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 19:57 ` Jesse Barnes
2004-05-07 21:19 ` CURRY,JOHN W (HP-Cupertino,ex1)
2004-05-07 21:28 ` Chen, Kenneth W [this message]
2004-05-07 21:32 ` Jesse Barnes
2004-08-03 13:57 ` Sourav Sen
2004-08-03 16:00 ` Jesse Barnes
2004-08-03 16:43 ` Luck, Tony
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=200405072128.i47LSCF00505@unix-os.sc.intel.com \
--to=kenneth.w.chen@intel.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