search for: kernel_init

...smp_prepare_cpus. This is done in start_kernel and at this point in time, there is no change to the pv_lock_ops and they point to the ticket versions. Later in start_kernel, check_bugs is called and part of that takes the pv_lock_ops and patches the kernel with the correct jumps. _After_ that, the kernel_init is called and that in turn does the smp_prepare_cpus which now changes the pv_lock_ops again, *but not* run any patching again. So the _raw_spin_*lock calls still use the ticket calls. start_kernel setup_arch -> xen_hvm_smp_init (set smp_ops) ... check_bugs -> alternative_instructions...

Hi, I''m having some problems with getting the latest linux kernel and xen build working on ARM''s Fast Model simulator ( Cortex A15 ). I tried a lot of different configurations and I''m having trouble with all of them. I got all my information from the wiki pages at http://wiki.xen.org/wiki/Xen_ARMv7_with_Virtualization_Extensions#Building_Xen_on_ARM . I was hoping

Hey all, Just downloaded the new Xen 4.0 and ran Make xen Make tools Make stubdom Copied the new files from dist/install Im already running pv_ops 2.6.31.6 kernel. When I boot i get (XEN) Panic on CPU 0: (XEN) IO-APIC + timer doesn''t work! I have tried booting with noapic boot option but makes no difference. The system worked fine on 3.4.2 CPU is AMD.

...0] [<ffffffff813a4252>] dump_stack+0x5c/0x7a [ 0.680369] [<ffffffff8118e3fa>] panic+0xd5/0x217 [ 0.682169] [<ffffffff81f56419>] mount_block_root+0x1fe/0x2c0 [ 0.684285] [<ffffffff81f56668>] prepare_namespace+0x12b/0x161 [ 0.686439] [<ffffffff81f56103>] kernel_init_freeable+0x1f6/0x20a [ 0.688675] [<ffffffff816c727a>] kernel_init+0xa/0x100 [ 0.690623] [<ffffffff816d485f>] ret_from_fork+0x1f/0x40 [ 0.696659] DWARF2 unwinder stuck at ret_from_fork+0x1f/0x40 [ 0.698858] [ 0.699533] Leftover inexact backtrace: [ 0.699533] [ 0.70...

...; > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, we can simply rip out the explicit cleanup that the devm > > infrastructure will do for us when our probe function returns an error > &g...

...; > [ 3.740249] bus_add_driver+0x26c/0x5b8 > > [ 3.752248] driver_register+0x16c/0x398 > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > [ 3.782671] do_one_initcall+0xe0/0x398 > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > [ 3.798514] kernel_init+0x18/0x190 > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > To fix this, we can simply rip out the explicit cleanup that the devm > > infrastructure will do for us when our probe function returns an error > &g...

..._dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe function returns an error code. We only need to ensure that we call put_device() if...

..._dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe function returns an error code. We only need to ensure that we call put_device() if...

..._dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe function returns an error code, or when our remove function returns. We only need...

..._dev+0x14c/0x1f0 [ 3.728633] driver_attach+0x48/0x78 [ 3.740249] bus_add_driver+0x26c/0x5b8 [ 3.752248] driver_register+0x16c/0x398 [ 3.757211] __platform_driver_register+0xd8/0x128 [ 3.770860] virtio_mmio_init+0x1c/0x24 [ 3.782671] do_one_initcall+0xe0/0x398 [ 3.791890] kernel_init_freeable+0x594/0x660 [ 3.798514] kernel_init+0x18/0x190 [ 3.810220] ret_from_fork+0x10/0x18 To fix this, we can simply rip out the explicit cleanup that the devm infrastructure will do for us when our probe function returns an error code, or when our remove function returns. We only need...

...driver_register+0x72/0x170 [<ffffffff81308671>] platform_driver_register+0x41/0x50 [<ffffffff81308696>] platform_driver_probe+0x16/0xa0 [<ffffffff81ac2ece>] efifb_init+0x273/0x292 [<ffffffff810002da>] do_one_initcall+0x11a/0x170 [<ffffffff8154187c>] kernel_init+0x11c/0x290 [<ffffffff8155acac>] ret_from_fork+0x7c/0xb0 -> #0 ((fb_notifier_list).rwsem){++++.+}: [<ffffffff8108ff10>] validate_chain.isra.33+0x1000/0x10d0 [<ffffffff81090a61>] __lock_acquire+0x3a1/0xb60 [<ffffffff810916ea>] lock_acquire+0x5a/0x70 [&...

...ffffff81b1766d>] ? mon_bin_init+0xb5/0xb5 [ 0.706755] [<ffffffff8132bb36>] __pci_register_driver+0x56/0xd0 [ 0.706755] [<ffffffff81b176d7>] ehci_hcd_init+0x6a/0x78 [ 0.706755] [<ffffffff81002164>] do_one_initcall+0x44/0x190 [ 0.706755] [<ffffffff81ae5ccb>] kernel_init+0xc8/0x14d [ 0.706755] [<ffffffff8162e474>] kernel_thread_helper+0x4/0x10 [ 0.706755] [<ffffffff8162c523>] ? int_ret_from_sys_call+0x7/0x1b [ 0.706755] [<ffffffff8162bafc>] ? retint_restore_args+0x5/0x6 [ 0.706755] [<ffffffff8162e470>] ? gs_change+0x13/0x13 [...

I am getting the following on my 'new box' for my DNS server: Date: Wed, 20 Feb 2013 13:58:04 -0500 From: To: Subject: [abrt] full crash report User-Agent: Heirloom mailx 12.4 7/29/08 abrt_version: 2.0.8 cmdline: ro root=/dev/mapper/vg_onlo3-root_01 rd_NO_LUKS rd_LVM_LV=vg_onlo3/root_01 LANG=en_US.UTF-8 +rd_NO_MD SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us

...ffff80083a20dc>] __pci_register_driver+0x3c/0x48 [ 2.898809] [<ffffff8008468eb4>] drm_pci_init+0xf4/0x120 [ 2.898818] [<ffffff8008c56fc0>] nouveau_drm_init+0x21c/0x230 [ 2.898825] [<ffffff80080829d4>] do_one_initcall+0x8c/0x190 [ 2.898832] [<ffffff8008c31af4>] kernel_init_freeable+0x14c/0x1f0 [ 2.898839] [<ffffff80088a0c20>] kernel_init+0x10/0x100 [ 2.898845] [<ffffff8008085e10>] ret_from_fork+0x10/0x40 [ 2.898853] Code: a88120c7 a8c12027 a88120c7 a8c12027 (a88120c7) [ 2.898871] ---[ end trace d5713dcad023ee04 ]--- [ 2.898888] Kernel panic...

...ffff80083a20dc>] __pci_register_driver+0x3c/0x48 [ 2.898809] [<ffffff8008468eb4>] drm_pci_init+0xf4/0x120 [ 2.898818] [<ffffff8008c56fc0>] nouveau_drm_init+0x21c/0x230 [ 2.898825] [<ffffff80080829d4>] do_one_initcall+0x8c/0x190 [ 2.898832] [<ffffff8008c31af4>] kernel_init_freeable+0x14c/0x1f0 [ 2.898839] [<ffffff80088a0c20>] kernel_init+0x10/0x100 [ 2.898845] [<ffffff8008085e10>] ret_from_fork+0x10/0x40 [ 2.898853] Code: a88120c7 a8c12027 a88120c7 a8c12027 (a88120c7) [ 2.898871] ---[ end trace d5713dcad023ee04 ]--- [ 2.898888] Kernel panic...

...21cf6>] ? ttm_init+0x62/0x62 > [ 0.633730] [<ffffffff81b21cf6>] ? ttm_init+0x62/0x62 > [ 0.633731] [<ffffffff81b21d43>] nouveau_drm_init+0x4d/0x4f > [ 0.633732] [<ffffffff81000312>] do_one_initcall+0x122/0x170 > [ 0.633734] [<ffffffff81af6f49>] kernel_init_freeable+0x108/0x197 > [ 0.633735] [<ffffffff81af681c>] ? do_early_param+0x8c/0x8c > [ 0.633737] [<ffffffff815d4d20>] ? rest_init+0xe0/0xe0 > [ 0.633738] [<ffffffff815d4d2e>] kernel_init+0xe/0xf0 > [ 0.633740] [<ffffffff815f6b1c>] ret_from_fork+0x...

...0x88/0xf0 [ 0.000000] [<c102fb12>] xen_setup_cpu_clockevents+0x22/0x40 [ 0.000000] [<c16bba3a>] xen_time_init+0xb7/0xbf [ 0.000000] [<c16bcf1c>] x86_late_time_init+0x9/0x10 [ 0.000000] [<c16b7a7f>] start_kernel+0x286/0x317 [ 0.000000] [<c16b766a>] ? kernel_init+0x1cd/0x1cd [ 0.000000] [<c16b72e6>] i386_start_kernel+0xa9/0xb0 [ 0.000000] [<c16ba609>] xen_start_kernel+0x5c9/0x5d1 [ 0.000000] ---[ end trace 4eaa2a86a8e2da22 ]--- [ 0.000000] Detected 2899.988 MHz processor. [1266874889.140126] Calibrating delay loop (skipped), value...

...] driver_attach+0x48/0x78 > [ 3.740249] bus_add_driver+0x26c/0x5b8 > [ 3.752248] driver_register+0x16c/0x398 > [ 3.757211] __platform_driver_register+0xd8/0x128 > [ 3.770860] virtio_mmio_init+0x1c/0x24 > [ 3.782671] do_one_initcall+0xe0/0x398 > [ 3.791890] kernel_init_freeable+0x594/0x660 > [ 3.798514] kernel_init+0x18/0x190 > [ 3.810220] ret_from_fork+0x10/0x18 > > To fix this, we can simply rip out the explicit cleanup that the devm > infrastructure will do for us when our probe function returns an error > code, or when our remove fu...

It appears the attachment did not go through. The errors look something like: ... ... [<ffffffff8100969d>] ? __switch_to+0x7d/0x2f7 [<ffffffff8100c28a>] ? child_rip+0x0/0x20 [<ffffffff81c3a7dc>] ? kernel_init+0x0/0x2f7 [<ffffffff8100c280>] ? child_rip+0x0/0x20 On 12/9/2016 12:30 PM, Emma M Birath wrote: > Dear all, > > I'm having trouble installing Centos 6.8, in a VM using VirtualBox, > and hoping that someone on this distribution can help. > > I'm running VirtualBox...

...s_add_driver+0x26c/0x5b8 > > > [ 3.752248] driver_register+0x16c/0x398 > > > [ 3.757211] __platform_driver_register+0xd8/0x128 > > > [ 3.770860] virtio_mmio_init+0x1c/0x24 > > > [ 3.782671] do_one_initcall+0xe0/0x398 > > > [ 3.791890] kernel_init_freeable+0x594/0x660 > > > [ 3.798514] kernel_init+0x18/0x190 > > > [ 3.810220] ret_from_fork+0x10/0x18 > > > > > > To fix this, we can simply rip out the explicit cleanup that the devm > > > infrastructure will do for us when our probe function...