* Li, Shaohua <[EMAIL PROTECTED]>:
> >
> >Do you get anything useful (like the oops message) printed on the
> >console or in your syslog?
> >
> >That might be a good first step.
> SAL: AP wakeup using external interrupt vetor 0xf0
> swapper[0]: IA-64 Illegal operation fault 0
> Modules linked in:
>
>-Original Message-
>From: Alex Chiang [mailto:[EMAIL PROTECTED]
>Sent: Tuesday, February 26, 2008 3:15 PM
>To: Li, Shaohua
>Cc: Bjorn Helgaas; Luck, Tony; ia64
>Subject: Re: Tiger oops in ia64_sal_physical_id_info (was [RFC]
>regression:113134fcbca83619be4
* Shaohua Li <[EMAIL PROTECTED]>:
>
> On Mon, 2008-02-25 at 16:08 -0700, Alex Chiang wrote:
> >
> > My original commit relied on fall-through behavior to still
> > try and call ia64_sal_physical_id_info(), because there are
> > cases/platforms where PAL_LOGICAL_TO_PHYSICAL is not
> > implemented
On Mon, 2008-02-25 at 16:08 -0700, Alex Chiang wrote:
> * Bjorn Helgaas <[EMAIL PROTECTED]>:
> > On Friday 22 February 2008 12:28:26 am Shaohua Li wrote:
> > > My tiger machine hangs since 2.6.23 with commit above. I always saw oops
> > > in ia64_sal_physical_id_info(). In 2.6.22, if ia64_pal_logi
* Bjorn Helgaas <[EMAIL PROTECTED]>:
> On Friday 22 February 2008 12:28:26 am Shaohua Li wrote:
> > My tiger machine hangs since 2.6.23 with commit above. I always saw oops
> > in ia64_sal_physical_id_info(). In 2.6.22, if ia64_pal_logical_to_phys
> > returns UNIMPLENTED, ia64_sal_physical_id_info(
On Friday 22 February 2008 12:28:26 am Shaohua Li wrote:
> My tiger machine hangs since 2.6.23 with commit above. I always saw oops
> in ia64_sal_physical_id_info(). In 2.6.22, if ia64_pal_logical_to_phys
> returns UNIMPLENTED, ia64_sal_physical_id_info() isn't called. Below
> patch fixes the issue
