Hi,
Using ELF format to construct dump information (registers, physical adress
range, and physical memory etc.) is OK. It's not bad idea.
But it is not necessary to indend to use a particular analysis tool.
Do simple.
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from thi
Hi,
Using ELF format to construct dump information (registers, physical adress
range, and physical memory etc.) is OK. It's not bad idea.
But it is not necessary to indend to use a particular analysis tool.
Do simple.
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list
om this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubsc
://www.tux.org/lkml/
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
of the kexec code. So while many times I can see what needs to be
> done it is hard for me to justify doing it. So a lot of times
> where I will weigh in with code is when I see a particular blind spot
> on the part of the implementors.
I see. I would like to contribute as possible I can
code. So while many times I can see what needs to be
done it is hard for me to justify doing it. So a lot of times
where I will weigh in with code is when I see a particular blind spot
on the part of the implementors.
I see. I would like to contribute as possible I can.
Thanks.
--
Itsuro ODA
Hi,
> I thought efi related data structures are of type __initdata and will be gone
> after initilization. (efi.c)
oops. certainly.
and, devmem_is_allowed does same mistake :-)
(I don't know who made it.)
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from thi
(3)
+ enable_NMI_through_LVT0 (4)
-
check_nmi_watchdog(2) runs before enabling NMI(4).
(where cpu_callin_map is already set)
console log is attached.
(line marked "<= debuging" are my debugging printk)
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]&g
gt; code altogether in this code path. I threw it in there to
> ease the transition from the old code base to the new, but
> if that code is causing issues So this is probably a good time
> to start testing that.
How about this ?
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsub
-rc3-mm2 ?
How do I get and examine the latest kexec/kdump ?
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
---
--- linux-2.6.11-rc3-mm2/drivers/char/mem.c 2005-02-16 15:36:31.0
+0900
+++ linux-2.6.11-rc3-mm2-test/drivers/char/mem.c2005-02-16
23:32:15.244876816 +0900
@@
-rc3-mm2 ?
How do I get and examine the latest kexec/kdump ?
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
---
--- linux-2.6.11-rc3-mm2/drivers/char/mem.c 2005-02-16 15:36:31.0
+0900
+++ linux-2.6.11-rc3-mm2-test/drivers/char/mem.c2005-02-16
23:32:15.244876816 +0900
@@ -25,6 +25,9
the transition from the old code base to the new, but
if that code is causing issues So this is probably a good time
to start testing that.
How about this ?
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
(3)
+ enable_NMI_through_LVT0 (4)
-
check_nmi_watchdog(2) runs before enabling NMI(4).
(where cpu_callin_map is already set)
console log is attached.
(line marked = debuging are my debugging printk)
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
---
Bootdata ok
Hi,
I thought efi related data structures are of type __initdata and will be gone
after initilization. (efi.c)
oops. certainly.
and, devmem_is_allowed does same mistake :-)
(I don't know who made it.)
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line
> as the kernel knows enough to completely setup the apics.
I see. Thank you for your explanation.
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo inf
Hi,
On Fri, 04 Feb 2005 08:18:56 +0900
Itsuro Oda <[EMAIL PROTECTED]> wrote:
>
> > > 5) dump kernel: export all valid physical memory (and saved register
> > >information) to the user. (as /dev/oldmem /proc/vmcore ?)
> >
> > Or in user space,
Hi,
On 02 Feb 2005 07:45:11 -0700
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
>
> And the feedback begins :)
>
> Itsuro Oda <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > I don't like calling crash_kexec() directly in (ex.) panic().
> > It
Hi,
On 03 Feb 2005 02:58:02 -0700
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
> Itsuro Oda <[EMAIL PROTECTED]> writes:
>
> > Hi,
> >
> > This is not for kdump but an experience of our project(mkdump).
> > The du
ents to the dump kernel is that:
* supply a method to access whole (valid) physical memory.
* supply a method to access the saved register information.
Does the kdump meet this requirment ?
(I am not interesting to /proc/vmcore. Constructing the vmcore
image is area of analysis tools. not kernel's
:12:32 +0530
Vivek Goyal <[EMAIL PROTECTED]> wrote:
> On Thu, 2005-02-03 at 10:42, Itsuro Oda wrote:
> > Hi,
> >
> > I found the following in an old mail:
> >
> > >From vgoyal at in.ibm.com Thu Jan 6 07:20:43 2005
> > ...
> > >2. Kdump c
+0530
Vivek Goyal [EMAIL PROTECTED] wrote:
On Thu, 2005-02-03 at 10:42, Itsuro Oda wrote:
Hi,
I found the following in an old mail:
From vgoyal at in.ibm.com Thu Jan 6 07:20:43 2005
...
2. Kdump can possibly fail on SMP machines if crash occurs on non-boot
cpu. Hari
to access the saved register information.
Does the kdump meet this requirment ?
(I am not interesting to /proc/vmcore. Constructing the vmcore
image is area of analysis tools. not kernel's task.)
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe
Hi,
On 03 Feb 2005 02:58:02 -0700
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
Itsuro Oda [EMAIL PROTECTED] writes:
Hi,
This is not for kdump but an experience of our project(mkdump).
The dump kernel(not SMP config) boot hangs if machine_kexec()
Hi,
On 02 Feb 2005 07:45:11 -0700
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
And the feedback begins :)
Itsuro Oda [EMAIL PROTECTED] writes:
Hi,
I don't like calling crash_kexec() directly in (ex.) panic().
It should be call_dump_hook() (or something like this).
I think
Hi,
On Fri, 04 Feb 2005 08:18:56 +0900
Itsuro Oda [EMAIL PROTECTED] wrote:
5) dump kernel: export all valid physical memory (and saved register
information) to the user. (as /dev/oldmem /proc/vmcore ?)
Or in user space, by just mmaping /dev/mem. That is part of the
current
. Thank you for your explanation.
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
40K backup area is.
Please let me know why it is necessary.
Thanks.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.ht
.6.11-rc2-mm1.)
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.)
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
is.
Please let me know why it is necessary.
Thanks.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe lin
nice to me.
--
Itsuro ODA <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
.
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
the FAQ at http://www.tux.org/lkml/
--
Itsuro ODA [EMAIL PROTECTED]
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
34 matches
Mail list logo