Re: 2.6.23: x86_64 oops caused by hotplug running before vdso initialized

2007-12-06 Thread Chuck Ebbert
On 12/06/2007 03:51 PM, Andi Kleen wrote: > On Thursday 06 December 2007 20:44:46 Chuck Ebbert wrote: >> pages is NULL here, implying vma->vm_private_data was NULL. This is >> apparently >> because init_vdso_vars() is __initcall and runs after the rootfs gets >> populated. >> An experimental init

Re: 2.6.23: x86_64 oops caused by hotplug running before vdso initialized

2007-12-06 Thread Andi Kleen
On Thursday 06 December 2007 20:44:46 Chuck Ebbert wrote: > pages is NULL here, implying vma->vm_private_data was NULL. This is apparently > because init_vdso_vars() is __initcall and runs after the rootfs gets > populated. > An experimental initrd containing an /sbin/hotplug binary caused this.

2.6.23: x86_64 oops caused by hotplug running before vdso initialized

2007-12-06 Thread Chuck Ebbert
pages is NULL here, implying vma->vm_private_data was NULL. This is apparently because init_vdso_vars() is __initcall and runs after the rootfs gets populated. An experimental initrd containing an /sbin/hotplug binary caused this. Normally we don't have that file in the initrd. Should vdso init be