Displaying 6 results from an estimated 6 matches for "vprintk_default".
2018 Jan 05
4
Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode
...rly) [<ffffffff81006b9e>] ? xen_extend_mmu_update+0xde/0x1b0
(early) [<ffffffff81006fcd>] ? xen_set_pmd_hyper+0x9d/0xc0
(early) [<ffffffff81c5e8ac>] ? early_ioremap_init+0x98/0x133
(early) [<ffffffff81c45221>] ? setup_arch+0x40/0xca6
(early) [<ffffffff8107e0ee>] ? vprintk_default+0xe/0x10
(early) [<ffffffff8154b0cd>] ? printk+0x4f/0x52
(early) [<ffffffff81c3fdda>] ? start_kernel+0xdc/0x43b
(early) [<ffffffff81c47eb0>] ? reserve_early+0x30/0x39
(early) [<ffffffff81c3f33a>] ? x86_64_start_reservations+0x125/0x129
(early) [<ffffffff81c4309c>]...
2018 Jan 05
0
Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode
...Call Trace:
[<ffffffff812b7872>] __memcpy_fromio+0x12 <--
[<ffffffff812b7872>] __memcpy_fromio+0x12
[<ffffffff812b7869>] __memcpy_fromio+0x9
[<ffffffff81c80153>] dmi_scan_machine+0x139
[<ffffffff81c45605>] setup_arch+0x424
[<ffffffff8107e0ee>] vprintk_default+0xe
[<ffffffff8154b0cd>] printk+0x4f
[<ffffffff81c3fdda>] start_kernel+0xdc
[<ffffffff81c3f33a>] x86_64_start_reservations+0x125
[<ffffffff81c4309c>] xen_start_kernel+0x4fe
And my domU has similar boot messages as Sarah Newman's:
(early) Initializing cgro...
2018 Jan 06
0
Centos 6 2.6.32-696.18.7.el6.x86_64 does not boot in Xen PV mode
...fff81006b9e>] ? xen_extend_mmu_update+0xde/0x1b0
>(early) [<ffffffff81006fcd>] ? xen_set_pmd_hyper+0x9d/0xc0
>(early) [<ffffffff81c5e8ac>] ? early_ioremap_init+0x98/0x133
>(early) [<ffffffff81c45221>] ? setup_arch+0x40/0xca6
>(early) [<ffffffff8107e0ee>] ? vprintk_default+0xe/0x10
>(early) [<ffffffff8154b0cd>] ? printk+0x4f/0x52
>(early) [<ffffffff81c3fdda>] ? start_kernel+0xdc/0x43b
>(early) [<ffffffff81c47eb0>] ? reserve_early+0x30/0x39
>(early) [<ffffffff81c3f33a>] ? x86_64_start_reservations+0x125/0x129
>(early) [<f...
2016 Feb 02
2
[Bug 93968] New: BUG in nouveau_fbcon_sync()
...vt_console_print+0x2a7/0x3e0
[ 37.438739] [<ffffffff810e89c4>]
call_console_drivers.constprop.24+0x144/0x1d0
[ 37.438741] [<ffffffff810e9783>] console_unlock+0x463/0x540
[ 37.438742] [<ffffffff810e9bba>] vprintk_emit+0x35a/0x620
[ 37.438744] [<ffffffff810e9fd9>] vprintk_default+0x29/0x40
[ 37.438748] [<ffffffff8119f71a>] printk+0x4d/0x4f
[ 37.438750] [<ffffffff81137ad2>] audit_printk_skb+0x62/0x70
[ 37.438751] [<ffffffff81137e84>] audit_log_end+0x1d4/0x2d0
[ 37.438752] [<ffffffff81137ce0>] ? audit_log_end+0x30/0x2d0
[ 37.438754] [<...
2016 Nov 07
3
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Hi,
I can relatively easily reproduce this bug:
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
------------[ cut here ]------------
kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 355 Comm: kworker/1:2 Not tainted 4.9.0-rc2-next-20161028+ #32
Hardware name: QEMU Standard PC (i440FX
2016 Nov 07
3
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
Hi,
I can relatively easily reproduce this bug:
BUG: 'list_empty(&vgdev->free_vbufs)' is true!
------------[ cut here ]------------
kernel BUG at /home/latest/linux/drivers/gpu/drm/virtio/virtgpu_vq.c:130!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 1 PID: 355 Comm: kworker/1:2 Not tainted 4.9.0-rc2-next-20161028+ #32
Hardware name: QEMU Standard PC (i440FX