On Wednesday 07 March 2007 01:47, Thomas Gleixner wrote: > On Wed, 2007-03-07 at 00:24 +1100, Con Kolivas wrote: > > > printk(KERN_INFO "Time: %s clocksource has been installed.\n", > > > clock->name); > > > } > > > > > > So clock seems to be NULL, but was accessed before > > > clocksource_calculate_interval() as well. > > > > It seems to be specifically tripping at c->mult after reading c->shift if > > I'm reading it correctly. > > > > Note again, this is qemu, not real hardware and it will likely be giving > > very unrealistic values for timer calibrations. > > I know, but this does not really explain why the > > tmp += c->mult/2; > > results in a NULL pointer access after > > tmp <<= c->shift;
/me shrugs No idea. > Does disassembling the code in question give some info ? You might also > try to look with GDB at it. Alas it wouldn't mean anything to me, sorry. And qemu doesn't work with gdb on 64bit processes in 32bit userspace even with a 64bit gdb. -- -ck - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
