RE: Linus' tree broken?

> > Could be, but it sounds like there's something
fishy in the current
> > tree - Doug Chapman is having problems as well,
presumably on zx1 boxes.
>
> I am seeing the panic on HP zx1 and zx2 systems. 
Currently doing a git
> bisect to narrow it down.

2.6.23-rc1 booted OK on my rx2620.  On the zx2000 too
(though X is currently
behaving weirdly, I think that might be some other issue
though).

-Tony
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony wrote:
> > > Could be, but it sounds like there's
something fishy in the current
> > > tree - Doug Chapman is having problems as
well, presumably on zx1 boxes.
> >
> > I am seeing the panic on HP zx1 and zx2 systems. 
Currently doing a git
> > bisect to narrow it down.
> 
> 2.6.23-rc1 booted OK on my rx2620.  On the zx2000 too
(though X is currently
> behaving weirdly, I think that might be some other
issue though).
> 
> -Tony

Odd,

I am hitting this on my rx2620, rx6600 and rx2600 (i.e.
everywhere I
have tried it) and the bisection is showing that it appears
to have been
broken before -rc1.


It appears to have something to do with grabbing the kernel
args.  The
panic happens here:

0xa0000001007f1511 is in setup_arch
(arch/ia64/kernel/setup.c:570).
565
566             /* enable IA-64 Machine Check Abort Handling
unless disabled
*/
567             if (!nomca)
568                     ia64_mca_init();
569
570             platform_setup(cmdline_p);
571             paging_init();
572     }


If it is working for others I am wondering if the version of
elilo makes
a difference.  I am using RHEL5 as my base system.  I might
try grabbing
elilo from upstream or from another release and see if that
makes a
difference.

Bisection almost done, should know what commit triggered
this soon.  I
tried reverting a couple seemingly obvious patches but
didn't find it
that way.

- Doug


-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony wrote:
> > > Could be, but it sounds like there's
something fishy in the current
> > > tree - Doug Chapman is having problems as
well, presumably on zx1 boxes.
> >
> > I am seeing the panic on HP zx1 and zx2 systems. 
Currently doing a git
> > bisect to narrow it down.
> 
> 2.6.23-rc1 booted OK on my rx2620.  On the zx2000 too
(though X is currently
> behaving weirdly, I think that might be some other
issue though).
> 
> -Tony

Through the magic of git-bisect I have narrowed it down to
this commit
(although I don't know why):

commit 4994be1b3fe9120c88022ff5c0c33f6312b17adb
Author: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>
Date:   Tue Jul 17 21:22:33 2007 +0900

    [IA64] Add support for vector domain
    
    Add fundamental support for multiple vector domain.
There still exists
    only one vector domain even with this patch. IRQ
migration across
    domain is not supported yet by this patch.
    
    Signed-off-by: Kenji Kaneshige <kaneshige.kenjijp.fujitsu.com>
    Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>
    Signed-off-by: Tony Luck <tony.luckintel.com>



As far as why I see this and so far others have not I have 2
guesses.
It could be related to firmware version (I have all my
systems with 
the latest available version) or, it could be the version of
elilo
(perhaps more of a longshot).

Or, could be my .config file (ok, now that I think of it
that may be
more likely).  Attaching my .config here.  This is a custom
config
that started out as the fedora 7 .config but I have made
some changes
over time.

- Doug

On Mon, 2007-07-23 at 21:07 -0400, Doug Chapman wrote:
> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony wrote:
> > > > Could be, but it sounds like there's
something fishy in the current
> > > > tree - Doug Chapman is having problems
as well, presumably on zx1 boxes.
> > >
> > > I am seeing the panic on HP zx1 and zx2
systems.  Currently doing a git
> > > bisect to narrow it down.
> > 
> > 2.6.23-rc1 booted OK on my rx2620.  On the zx2000
too (though X is currently
> > behaving weirdly, I think that might be some other
issue though).
> > 
> > -Tony
> 
> Through the magic of git-bisect I have narrowed it down
to this commit
> (although I don't know why):
> 
> commit 4994be1b3fe9120c88022ff5c0c33f6312b17adb
> Author: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>
> Date:   Tue Jul 17 21:22:33 2007 +0900
> 
>     [IA64] Add support for vector domain
>     
>     Add fundamental support for multiple vector domain.
There still exists
>     only one vector domain even with this patch. IRQ
migration across
>     domain is not supported yet by this patch.
>     
>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
>     Signed-off-by: Tony Luck <tony.luckintel.com>
> 
> 

I have confirmed that it was my .config.  The panic is seen
if the
kernel is compiled with CONFIG_IA64_GENERIC.  When I
compiled with 
CONFIG_IA64_HP_ZX1 it worked OK.

- Doug


-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Hi Doug,

Doug Chapman wrote:
> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony wrote:
>>>> Could be, but it sounds like there's
something fishy in the current
>>>> tree - Doug Chapman is having problems as
well, presumably on zx1 boxes.
>>> I am seeing the panic on HP zx1 and zx2
systems.  Currently doing a git
>>> bisect to narrow it down.
>> 2.6.23-rc1 booted OK on my rx2620.  On the zx2000
too (though X is currently
>> behaving weirdly, I think that might be some other
issue though).
>>
>> -Tony
>
> Through the magic of git-bisect I have narrowed it down
to this commit
> (although I don't know why):
>
> commit 4994be1b3fe9120c88022ff5c0c33f6312b17adb
> Author: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>
> Date:   Tue Jul 17 21:22:33 2007 +0900
>
>     [IA64] Add support for vector domain
>
>     Add fundamental support for multiple vector domain.
There still exists
>     only one vector domain even with this patch. IRQ
migration across
>     domain is not supported yet by this patch.
>
>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
>     Signed-off-by: Tony Luck <tony.luckintel.com>
>
>
>
> As far as why I see this and so far others have not I
have 2 guesses.
> It could be related to firmware version (I have all my
systems with
> the latest available version) or, it could be the
version of elilo
> (perhaps more of a longshot).
>
> Or, could be my .config file (ok, now that I think of
it that may be
> more likely).  Attaching my .config here.  This is a
custom config
> that started out as the fedora 7 .config but I have
made some changes
> over time.

Oops, I forgot to consider assign_irq_vector(AUTO_ASSIGN)
case.
I'm writing bug fix patch now. Wait a moment.

Thanks,
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Hi Doug,

Yasuaki Ishimatsu wrote:
> Hi Doug,
>
> Doug Chapman wrote:
>> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony
wrote:
>>>>> Could be, but it sounds like there's
something fishy in the current
>>>>> tree - Doug Chapman is having problems
as well, presumably on zx1 boxes.
>>>> I am seeing the panic on HP zx1 and zx2
systems.  Currently doing a git
>>>> bisect to narrow it down.
>>> 2.6.23-rc1 booted OK on my rx2620.  On the
zx2000 too (though X is currently
>>> behaving weirdly, I think that might be some
other issue though).
>>>
>>> -Tony
>> Through the magic of git-bisect I have narrowed it
down to this commit
>> (although I don't know why):
>>
>> commit 4994be1b3fe9120c88022ff5c0c33f6312b17adb
>> Author: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>
>> Date:   Tue Jul 17 21:22:33 2007 +0900
>>
>>     [IA64] Add support for vector domain
>>
>>     Add fundamental support for multiple vector
domain. There still exists
>>     only one vector domain even with this patch.
IRQ migration across
>>     domain is not supported yet by this patch.
>>
>>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
>>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
>>     Signed-off-by: Tony Luck <tony.luckintel.com>
>>
>>
>>
>> As far as why I see this and so far others have not
I have 2 guesses.
>> It could be related to firmware version (I have all
my systems with
>> the latest available version) or, it could be the
version of elilo
>> (perhaps more of a longshot).
>>
>> Or, could be my .config file (ok, now that I think
of it that may be
>> more likely).  Attaching my .config here.  This is
a custom config
>> that started out as the fedora 7 .config but I have
made some changes
>> over time.
>
> Oops, I forgot to consider
assign_irq_vector(AUTO_ASSIGN) case.
> I'm writing bug fix patch now. Wait a moment.

Unfortunately, I don't have any ski simulator environment. I
attached
the bug fix patch. Could you try this patch?

Thanks,
Yasuaki Ishimatsu



This change fixes a panic when assign_irq_vector(irq) is
called with
irq = AUTO_ASSIGN.

Signed-off-by: Yasuaki Ishimatsu <isimatu.yasuakijp.fujitsu.com>

 arch/ia64/kernel/irq_ia64.c |    5 ++---
 1 files changed, 2 insertions(+), 3 deletions(-)

Index: linux-2.6.23-rc1/arch/ia64/kernel/irq_ia64.c
============================================================
=======
---
linux-2.6.23-rc1.orig/arch/ia64/kernel/irq_ia64.c	2007-07-24
16:08:32.000000000 +0900
+++ linux-2.6.23-rc1/arch/ia64/kernel/irq_ia64.c	2007-07-24
16:19:46.000000000 +0900
 -212,9
+212,6 
 	vector = -ENOSPC;

 	spin_lock_irqsave(&vector_lock, flags);
-	if (irq < 0) {
-		goto out;
-	}
 	for_each_online_cpu(cpu) {
 		domain = vector_allocation_domain(cpu);
 		vector = find_unassigned_vector(domain);
 -223,6
+220,8 
 	}
 	if (vector < 0)
 		goto out;
+	if (irq == AUTO_ASSIGN)
+		irq = vector;
 	BUG_ON(__bind_irq_vector(irq, vector, domain));
  out:
 	spin_unlock_irqrestore(&vector_lock, flags);
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

On Tue, 2007-07-24 at 22:09 +0900, Yasuaki Ishimatsu wrote:
> Hi Doug,
> 
> Yasuaki Ishimatsu wrote:
> > Hi Doug,
> >
> > Doug Chapman wrote:
> >> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony
wrote:
> >>>>> Could be, but it sounds like
there's something fishy in the current
> >>>>> tree - Doug Chapman is having
problems as well, presumably on zx1 boxes.
> >>>> I am seeing the panic on HP zx1 and
zx2 systems.  Currently doing a git
> >>>> bisect to narrow it down.
> >>> 2.6.23-rc1 booted OK on my rx2620.  On the
zx2000 too (though X is currently
> >>> behaving weirdly, I think that might be
some other issue though).
> >>>
> >>> -Tony
> >> Through the magic of git-bisect I have
narrowed it down to this commit
> >> (although I don't know why):
> >>
> >> commit
4994be1b3fe9120c88022ff5c0c33f6312b17adb
> >> Author: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
> >> Date:   Tue Jul 17 21:22:33 2007 +0900
> >>
> >>     [IA64] Add support for vector domain
> >>
> >>     Add fundamental support for multiple
vector domain. There still exists
> >>     only one vector domain even with this
patch. IRQ migration across
> >>     domain is not supported yet by this
patch.
> >>
> >>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
> >>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
> >>     Signed-off-by: Tony Luck <tony.luckintel.com>
> >>
> >>
> >>
> >> As far as why I see this and so far others
have not I have 2 guesses.
> >> It could be related to firmware version (I
have all my systems with
> >> the latest available version) or, it could be
the version of elilo
> >> (perhaps more of a longshot).
> >>
> >> Or, could be my .config file (ok, now that I
think of it that may be
> >> more likely).  Attaching my .config here. 
This is a custom config
> >> that started out as the fedora 7 .config but I
have made some changes
> >> over time.
> >
> > Oops, I forgot to consider
assign_irq_vector(AUTO_ASSIGN) case.
> > I'm writing bug fix patch now. Wait a moment.
> 
> Unfortunately, I don't have any ski simulator
environment. I attached
> the bug fix patch. Could you try this patch?
> 
> Thanks,
> Yasuaki Ishimatsu
> 
> 

Yasuaki,

With this patch it still panics in the same way.  I am
building with
CONFIG_IA64_GENERIC and booting on an HP rx6600.  I do not
have the ski
simulator either.

- Doug


-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Yasuaki,

> > Oops, I forgot to consider
assign_irq_vector(AUTO_ASSIGN) case.
> > I'm writing bug fix patch now. Wait a moment.
> 
> Unfortunately, I don't have any ski simulator
environment. I attached
> the bug fix patch. Could you try this patch?
> 

I tried your patch on my ski environment, and I confirmed it
fixes
the "Out of interrupt vectors" problem reported by
Peter Chubb.

Thanks,
Kenji Kaneshige


2007-07-24 (火) の 22:09 +0900 に Yasuaki
Ishimatsu さんは書きました:
> Hi Doug,
> 
> Yasuaki Ishimatsu wrote:
> > Hi Doug,
> >
> > Doug Chapman wrote:
> >> On Mon, 2007-07-23 at 13:42 -0700, Luck, Tony
wrote:
> >>>>> Could be, but it sounds like
there's something fishy in the current
> >>>>> tree - Doug Chapman is having
problems as well, presumably on zx1 boxes.
> >>>> I am seeing the panic on HP zx1 and
zx2 systems.  Currently doing a git
> >>>> bisect to narrow it down.
> >>> 2.6.23-rc1 booted OK on my rx2620.  On the
zx2000 too (though X is currently
> >>> behaving weirdly, I think that might be
some other issue though).
> >>>
> >>> -Tony
> >> Through the magic of git-bisect I have
narrowed it down to this commit
> >> (although I don't know why):
> >>
> >> commit
4994be1b3fe9120c88022ff5c0c33f6312b17adb
> >> Author: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
> >> Date:   Tue Jul 17 21:22:33 2007 +0900
> >>
> >>     [IA64] Add support for vector domain
> >>
> >>     Add fundamental support for multiple
vector domain. There still exists
> >>     only one vector domain even with this
patch. IRQ migration across
> >>     domain is not supported yet by this
patch.
> >>
> >>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
> >>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
> >>     Signed-off-by: Tony Luck <tony.luckintel.com>
> >>
> >>
> >>
> >> As far as why I see this and so far others
have not I have 2 guesses.
> >> It could be related to firmware version (I
have all my systems with
> >> the latest available version) or, it could be
the version of elilo
> >> (perhaps more of a longshot).
> >>
> >> Or, could be my .config file (ok, now that I
think of it that may be
> >> more likely).  Attaching my .config here. 
This is a custom config
> >> that started out as the fedora 7 .config but I
have made some changes
> >> over time.
> >
> > Oops, I forgot to consider
assign_irq_vector(AUTO_ASSIGN) case.
> > I'm writing bug fix patch now. Wait a moment.
> 
> Unfortunately, I don't have any ski simulator
environment. I attached
> the bug fix patch. Could you try this patch?
> 
> Thanks,
> Yasuaki Ishimatsu
> 
> 
> 
> This change fixes a panic when assign_irq_vector(irq)
is called with
> irq = AUTO_ASSIGN.
> 
> Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
> 
>  arch/ia64/kernel/irq_ia64.c |    5 ++---
>  1 files changed, 2 insertions(+), 3 deletions(-)
> 
> Index: linux-2.6.23-rc1/arch/ia64/kernel/irq_ia64.c
>
============================================================
=======
> ---
linux-2.6.23-rc1.orig/arch/ia64/kernel/irq_ia64.c	2007-07-24
16:08:32.000000000 +0900
> +++
linux-2.6.23-rc1/arch/ia64/kernel/irq_ia64.c	2007-07-24
16:19:46.000000000 +0900
>  -212,9 +212,6 
>  	vector = -ENOSPC;
> 
>  	spin_lock_irqsave(&vector_lock, flags);
> -	if (irq < 0) {
> -		goto out;
> -	}
>  	for_each_online_cpu(cpu) {
>  		domain = vector_allocation_domain(cpu);
>  		vector = find_unassigned_vector(domain);
>  -223,6 +220,8 
>  	}
>  	if (vector < 0)
>  		goto out;
> +	if (irq == AUTO_ASSIGN)
> +		irq = vector;
>  	BUG_ON(__bind_irq_vector(irq, vector, domain));
>   out:
>  	spin_unlock_irqrestore(&vector_lock, flags);

-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

Hi Doug,

Doug Chapman wrote:
> On Tue, 2007-07-24 at 22:09 +0900, Yasuaki Ishimatsu
wrote:
>> Hi Doug,
>>
>> Yasuaki Ishimatsu wrote:
>>> Hi Doug,
>>>
>>> Doug Chapman wrote:
>>>> On Mon, 2007-07-23 at 13:42 -0700, Luck,
Tony wrote:
>>>>>>> Could be, but it sounds like
there's something fishy in the current
>>>>>>> tree - Doug Chapman is having
problems as well, presumably on zx1 boxes.
>>>>>> I am seeing the panic on HP zx1 and
zx2 systems.  Currently doing a git
>>>>>> bisect to narrow it down.
>>>>> 2.6.23-rc1 booted OK on my rx2620.  On
the zx2000 too (though X is currently
>>>>> behaving weirdly, I think that might be
some other issue though).
>>>>>
>>>>> -Tony
>>>> Through the magic of git-bisect I have
narrowed it down to this commit
>>>> (although I don't know why):
>>>>
>>>> commit
4994be1b3fe9120c88022ff5c0c33f6312b17adb
>>>> Author: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
>>>> Date:   Tue Jul 17 21:22:33 2007 +0900
>>>>
>>>>     [IA64] Add support for vector domain
>>>>
>>>>     Add fundamental support for multiple
vector domain. There still exists
>>>>     only one vector domain even with this
patch. IRQ migration across
>>>>     domain is not supported yet by this
patch.
>>>>
>>>>     Signed-off-by: Kenji Kaneshige
<kaneshige.kenjijp.fujitsu.com>
>>>>     Signed-off-by: Yasuaki Ishimatsu
<isimatu.yasuakijp.fujitsu.com>
>>>>     Signed-off-by: Tony Luck
<tony.luckintel.com>
>>>>
>>>>
>>>>
>>>> As far as why I see this and so far others
have not I have 2 guesses.
>>>> It could be related to firmware version (I
have all my systems with
>>>> the latest available version) or, it could
be the version of elilo
>>>> (perhaps more of a longshot).
>>>>
>>>> Or, could be my .config file (ok, now that
I think of it that may be
>>>> more likely).  Attaching my .config here. 
This is a custom config
>>>> that started out as the fedora 7 .config
but I have made some changes
>>>> over time.
>>> Oops, I forgot to consider
assign_irq_vector(AUTO_ASSIGN) case.
>>> I'm writing bug fix patch now. Wait a moment.
>> Unfortunately, I don't have any ski simulator
environment. I attached
>> the bug fix patch. Could you try this patch?
>>
>> Thanks,
>> Yasuaki Ishimatsu
>>
>>
> 
> Yasuaki,
> 
> With this patch it still panics in the same way.  I am
building with
> CONFIG_IA64_GENERIC and booting on an HP rx6600.  I do
not have the ski
> simulator either.
> 

I don't know what happen on your machine. Could you send me
your entire
stack trace?

Thanks,
Yasuaki Ishimatsu
-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html

On Wed, 2007-07-25 at 09:19 +0900, Yasuaki Ishimatsu wrote:
> Hi Doug,
> > 
> > Yasuaki,
> > 
> > With this patch it still panics in the same way. 
I am building with
> > CONFIG_IA64_GENERIC and booting on an HP rx6600. 
I do not have the ski
> > simulator either.
> > 
> 
> I don't know what happen on your machine. Could you
send me your entire
> stack trace?
> 
> Thanks,
> Yasuaki Ishimatsu

Here is the panic with a few lines from before to show some
context as
to when it happens (fairly early in boot).  I have to admit
I have no
clue as to why your patch causes this.  I don't see anything
that
appears to be related.  I will see if I can get a little
more data.  If
you have suggestions for what might be helpful please let me
know.


SAL Platform features: None
SAL: AP wakeup using external interrupt vector 0xff
cpu package is Multi-Core capable: number of cores=2
cpu package is Multi-Threading capable: number of
siblings=2
ACPI: Local APIC address c0000000fee00000
GSI 25 (level, low) -> CPU 0 (0x0000) vector 48
16 CPUs available, 16 CPUs total
MCA related initialization done
kernel unaligned access to 0xffffffffffffffff,
ip=0xa000000100815491
swapper[0]: error during unaligned kernel access
 -1 [1]
Modules linked in:

Pid: 0, CPU 0, comm:              swapper
psr : 00001210084a2010 ifs : 800000000000030a ip  :
[<a000000100815491>]    Not tainted
ip is at setup_arch+0x671/0x720
unat: 0000000000000000 pfs : 000000000000030a rsc :
0000000000000003
rnat: 89543ffffe403fc4 bsps: 0000000000010017 pr  :
656960155aa66599
ldrs: 0000000000000000 ccv : 0000000000000000 fpsr:
0009804c8a70433f
csd : 0000000000000000 ssd : 0000000000000000
b0  : a000000100815470 b6  : a000000100304a80 b7  :
a0000001000132e0
f6  : 1003e0000000000000000 f7  : 1003e0000000000000000
f8  : 1003e0000000000000000 f9  : 1003e0000000000000001
f10 : 10004c7ffffffff380000 f11 : 1003e0000000000000032
r1  : a000000100d2f000 r2  : a000000100b49248 r3  :
a000000100a4f220
r8  : 0000000000000023 r9  : 0000000000004000 r10 :
a000000100b536a8
r11 : a000000100b3a8a0 r12 : a0000001008b7d60 r13 :
a0000001008b0000
r14 : 0000000000000000 r15 : a000000100a4f220 r16 :
ffffffffdead4ead
r17 : 00000000dead4ead r18 : a0000001009e13fc r19 :
a000000100b3a870
r20 : 000000000001ffff r21 : a000000100b47840 r22 :
0000000000000000
r23 : a000000100b49218 r24 : a000000100b34058 r25 :
000000000001ffff
r26 : 0000000000020000 r27 : a000000100b47828 r28 :
a000000100b47820
r29 : a0000001009e1400 r30 : 0000000000000000 r31 :
a0000001009e1408



Here is the bit of code showing where the ip points to:

(gdb) list *setup_arch+0x671
0xa000000100815491 is in setup_arch
(arch/ia64/kernel/setup.c:570).
565
566             /* enable IA-64 Machine Check Abort Handling
unless disabled */
567             if (!nomca)
568                     ia64_mca_init();
569
570             platform_setup(cmdline_p);
571             paging_init();
572     }
573
574     /*




-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html