![]() | |||||||||||
Messages in this thread |
On Fri, 24 Aug 2007 09:04:22 -0700 "Luck, Tony" <tony.luck@intel.com> wrote: > It is good to avoid registering two clocksources with the same name, but > the fix might be a bit more fragile than the eariler one that temporarily > marked the drivers/char/hpet.c one as CONFIG_IA64 only. Given that the > hang went away when you applied the earlier patch, I conclude that the > drivers/char/hpet.c code is the one that got selected when you had two > "hpet" entries ... and that there is something wrong with that code that > doesn't work right on x86_64. The fix to prevent registering a duplicate > name is presumably working for you simply because arch/x86_64/kernel/hpet.c > happens to get there first with its "hpet", so the drivers/char/hpet.c one > is dropped. If something changed that reversed the order of these registrations, > then you'd get the "hpet" clocksource that results in a hang. 100% agree -- Paolo Ornati Linux 2.6.23-rc3-g1a8f4610-dirty on x86_64 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2007-08-24 18:15 [from the cache] ©2003-2008 | |||||||||||