From: Jay Lan <jlan@engr.sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: A regression in IA64 kexec/kdump patch for 2.6.18?
Date: Tue, 17 Oct 2006 01:51:56 +0000 [thread overview]
Message-ID: <4534373C.10407@engr.sgi.com> (raw)
In-Reply-To: <4533F2BE.3070300@engr.sgi.com>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Jay Lan wrote:
<snip>
>
> Well, i built 2.6.18 kernel and 2.6.18rc5 kernels.
> I also built 2 kexec-tools based on kdump10 patch. I have been
> associating the kexec-tools tree that i built at the rc5 time with
> the rc5 kernel and the newer kexec-tools tree with the 2.6.18
> kernel.
>
> I just ran a few tests with different combination of kexec-tools
> and kernels. Well, it showed that the rc5 version of kexec-tools
> worked correctly with both kernels, but the newer version of
> kexec-tools displayed the system restart problem with both kernels.
>
> So, it was the kexec-tools that caused the problem. Not the kernel
> side. I will diff the patches i applied to both trees...
Nan-hai,
OK, the '-noio' option patch you posted on 9/20 was the cause of
my system restart.
http://lists.osdl.org/pipermail/fastboot/2006-September/004062.html
If instead, if i make every inline functions in
purgatory/arch/ia64/io.h null functions, it would then work.
I will attach the patch i used (based on your suggestion) here for
your reference. It was in rough form.
Thanks,
- jay
>
> Later,
> - jay
>
>
>
>> Zou Nan hai
>>> Thanks,
>>> - jay
>> -
>> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
[-- Attachment #2: kexec-ia64-reset-vga --]
[-- Type: text/plain, Size: 1676 bytes --]
Index: kexec-tools-1.101/purgatory/arch/ia64/io.h
===================================================================
--- kexec-tools-1.101.orig/purgatory/arch/ia64/io.h 2006-10-16 18:19:07.346416494 -0700
+++ kexec-tools-1.101/purgatory/arch/ia64/io.h 2006-10-16 18:47:14.742913628 -0700
@@ -4,6 +4,7 @@
#define MF() asm volatile ("mf.a" ::: "memory")
#define IO_SPACE_ENCODING(p) ((((p) >> 2) << 12) | (p & 0xfff))
+#ifdef DO_VGA_IO
static inline void *io_addr (unsigned long port)
{
unsigned long offset;
@@ -91,4 +92,46 @@ static inline void writel(unsigned int b
{
*(volatile unsigned int *) addr = b;
}
+#else
+static inline void *io_addr (unsigned long port)
+{ return (void*)0; }
+
+static inline unsigned int inb (unsigned long port)
+{ return 0; }
+
+static inline unsigned int inw (unsigned long port)
+{ return 0; }
+
+static inline unsigned int ia64_inl (unsigned long port)
+{ return 0; }
+
+static inline void outb (unsigned char val, unsigned long port)
+{ return; }
+
+static inline void outw (unsigned short val, unsigned long port)
+{ return; }
+
+static inline void outl (unsigned int val, unsigned long port)
+{ return; }
+
+
+static inline unsigned char readb(const volatile void *addr)
+{ return 0; }
+
+static inline unsigned short readw(const volatile void *addr)
+{ return 0; }
+
+static inline unsigned int readl(const volatile void *addr)
+{ return 0; }
+
+static inline void writeb(unsigned char b, volatile void *addr)
+{ return; }
+
+static inline void writew(unsigned short b, volatile void *addr)
+{ return; }
+
+static inline void writel(unsigned int b, volatile void *addr)
+{ return; }
+
+#endif
#endif
next prev parent reply other threads:[~2006-10-17 1:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:59 A regression in IA64 kexec/kdump patch for 2.6.18? Jay Lan
2006-10-16 21:21 ` Jay Lan
2006-10-16 21:39 ` Zou Nan hai
2006-10-17 0:21 ` Jay Lan
2006-10-17 1:51 ` Jay Lan [this message]
2006-10-17 2:50 ` Zou Nan hai
2006-10-17 15:55 ` Jay Lan
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=4534373C.10407@engr.sgi.com \
--to=jlan@engr.sgi.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