Re: Tiger oops in ia64_sal_physical_id_info (was [RFC] regression: 113134fcbca83619be4c68d0ca66db6093777b5d)

From: Alex Chiang <achiang_at_hp.com>
Date: 2008-02-26 18:15:25
* Shaohua Li <shaohua.li@intel.com>:
> 
> 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 but SAL_PHYSICAL_ID_INFO is.
> > 
> > I think the more interesting question is, why is that SAL
> > call hanging / oops'ing your machine rather than returning
> > with an error code?
> > 
> > In other words, why doesn't the error path work?
>
> Yes, this is strange. But other SAL calls are ok, maybe
> firmware bug or something I don't know. I'm not familiar with
> this area, if you need further info, let me know.

Do you get anything useful (like the oops message) printed on the
console or in your syslog?

That might be a good first step.

Thanks.

/ac

-
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
Received on Tue Feb 26 18:15:56 2008

This archive was generated by hypermail 2.1.8 : 2008-02-26 18:16:12 EST