* 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 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
