|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Xen is not booting with updated kernel 4.13 rc3 from UEFI shell
Hi All,
I have tried to find the dom0 kernel source file/line related to this crash
address using addr2line. But there is no useful information and output is like
below,
root@Minnowboard:/boot# addr2line -fe vmlinuz-4.12.4 ffff82d080345f28
addr2line: vmlinuz-4.12.4: Warning: Ignoring section flag
IMAGE_SCN_MEM_NOT_PAGED in section .bss
??
??:0
then I have enabled debug in xen and taken xen boot log when xen fail to boot
with updated kernel.
It show an error when kernel start booting..
0.247142] ------------[ cut here ]------------
[ 0.252208] kernel BUG at drivers/xen/events/events_base.c:521!
[ 0.258916] invalid opcode: 0000 [#1] SMP
[ 0.263472] Modules linked in:
[ 0.266971] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G W
4.11.12 #1
[ 0.275126] Hardware name: ADI Minnowboard Turbot D0
PLATFORM/MinnowBoard Turbot, BIOS MNW2MAX1.X64.0095.R01.1703281124 03/28/2017
[ 0.288334] task: ffff88001880bfc0 task.stack: ffffc90040328000
[ 0.295040] RIP: e030:__startup_pirq+0x128/0x160
[ 0.300277] RSP: e02b:ffffc9004032b790 EFLAGS: 00010096
[ 0.306202] RAX: 0000000000000000 RBX: 0000000000000031 RCX:
0000000000000000
[ 0.314263] RDX: 0000000000000000 RSI: 0000000000000031 RDI:
ffff880018c021a0
[ 0.322322] RBP: ffffc9004032b7c0 R08: ffff88001894f000 R09:
ffff880018c01ff0
[ 0.330383] R10: 0000000000000000 R11: 0000000000000040 R12:
0000000000000000
[ 0.338443] R13: ffff88001894e218 R14: ffff88001894e218 R15:
000000002003cc00
[ 0.346520] FS: 0000000000000000(0000) GS:ffff88001f680000(0000)
knlGS:0000000000000000
[ 0.355632] CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.362138] CR2: 0000000000000000 CR3: 0000000002209000 CR4:
0000000000002660
[ 0.370201] Call Trace:
[ 0.373021] ? acpi_ut_evaluate_object+0x193/0x1a1
[ 0.378461] startup_pirq+0x11/0x20
[ 0.382439] irq_startup+0x4a/0x80
[ 0.386322] ? byt_gpio_runtime_suspend+0x10/0x10
[ 0.391664] __irq_do_set_handler+0xbd/0x190
[ 0.396518] ? byt_gpio_runtime_suspend+0x10/0x10
[ 0.401860] ? byt_gpio_runtime_suspend+0x10/0x10
[ 0.407201] irq_set_chained_handler_and_data+0x57/0x90
[ 0.413126] gpiochip_set_chained_irqchip+0x38/0x90
[ 0.418660] byt_pinctrl_probe+0x510/0x660
[ 0.423325] platform_drv_probe+0x3c/0xa0
[ 0.427885] driver_probe_device+0x2c0/0x460
[ 0.432742] __device_attach_driver+0x91/0x100
[ 0.437791] ? __driver_attach+0xf0/0xf0
[ 0.442258] bus_for_each_drv+0x69/0xb0
[ 0.446629] __device_attach+0xe4/0x160
[ 0.450998] device_initial_probe+0x13/0x20
[ 0.455757] bus_probe_device+0x8b/0xa0
[ 0.460127] device_add+0x406/0x690
[ 0.464114] ? __insert_resource+0x1d/0x120
[ 0.468867] platform_device_add+0x107/0x270
[ 0.473723] platform_device_register_full+0x105/0x140
[ 0.479551] acpi_create_platform_device+0x21c/0x2e0
[ 0.485183] acpi_lpss_create_device+0x362/0x460
[ 0.490427] ? acpi_evaluate_object+0x232/0x258
[ 0.495574] ? acpi_evaluate_integer+0x54/0x90
[ 0.500623] acpi_bus_attach+0x116/0x200
[ 0.505090] acpi_bus_attach+0x9b/0x200
[ 0.509460] acpi_bus_attach+0x9b/0x200
[ 0.513830] acpi_bus_scan+0x48/0xa0
[ 0.517910] acpi_scan_init+0xfb/0x259
[ 0.522185] acpi_init+0x2f2/0x353
[ 0.526067] ? acpi_sleep_proc_init+0x28/0x28
[ 0.531020] do_one_initcall+0x54/0x1c0
[ 0.535389] ? parse_args+0x2b5/0x4c0
[ 0.539566] kernel_init_freeable+0x1bc/0x256
[ 0.544519] ? rest_init+0x80/0x80
[ 0.548401] kernel_init+0xe/0x100
[ 0.552291] ret_from_fork+0x25/0x30
[ 0.556363] Code: 75 46 48 8d 64 24 18 5b 41 5c 41 5d 5d c3 48 8d 75
d4 bf 02 00 00 00 e8 17 bd ff ff 8d 10 e9 63 ff ff ff 45 31 ed e9 12 ff ff ff
<0f> 0b 8d 10 8d 33 48 c7 c7 70 14 fb 81 e8 29 58 c4 ff 41 8d 3c
[ 0.577536] RIP: __startup_pirq+0x128/0x160 RSP: ffffc9004032b790
[ 0.584435] ---[ end trace 4a018094abbba7e7 ]---
[ 0.589715] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[ 0.589715]
(XEN) Debugging connection not set up.
(XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
Complete log is attached for your reference.
Request your support to resolve this issue.
Regards
Asharaf P.
________________________________________
From: Juergen Gross [jgross@xxxxxxxx]
Sent: Tuesday, August 08, 2017 8:09 PM
To: Asharaf Perinchikkal; Jan Beulich; xen-devel@xxxxxxxxxxxxxxxxxxxx
Cc: Anoop Babu
Subject: Re: [Xen-devel] Xen is not booting with updated kernel 4.13 rc3 from
UEFI shell
On 08/08/17 16:26, Asharaf Perinchikkal wrote:
> Hi All,
>
> I am attaching xen boot log when xen fail to boot with updated kernel
> from UEFI shell.
> It show an error when kernel start booting..
>
> N) ***************************************************
> (XEN) WARNING: CONSOLE OUTPUT IS SYNCHRONOUS
> (XEN) This option is intended to aid debugging of Xen by ensuring
> (XEN) that all output is synchronously delivered on the serial line.
> (XEN) However it can introduce SIGNIFICANT latencies and affect
> (XEN) timekeeping. It is NOT recommended for production use!
> (XEN) ***************************************************
> (XEN) 3... 2... 1...
> (XEN*) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
> input to Xen)
> (XEN) Freed 2048kB init memory
> mapping kernel into physical memory
> about to get started...
> (XEN) d0v0 Unhandled invalid opcode fault/trap [#6, ec=ffffffff]
> (XEN) domain_crash_sync called from entry.S: fault at ffff82d080345f28
> entry.o#create_bounce_frame+0x135/0x14d
> (XEN) Domain 0 (vcpu#0) crashed on cpu#0:
> (XEN) ----[ Xen-4.9.0 x86_64 debug=n Tainted: C ]----
> (XEN) CPU: 0
> (XEN) RIP: e033:[<ffffffff8251f06a>]
Can you please try to find the dom0 kernel source file/line related to
this address? addr2line should be able to help.
Juergen
---Disclaimer------------------------------ This e-mail contains PRIVILEGED AND
CONFIDENTIAL INFORMATION intended solely for the use of the addressee(s). If
you are not the intended recipient, please notify the sender by e-mail and
delete the original message. Opinions, conclusions and other information in
this transmission that do not relate to the official business of QuEST Global
and/or its subsidiaries, shall be understood as neither given nor endorsed by
it. Any statements made herein that are tantamount to contractual obligations,
promises, claims or commitments shall not be binding on the Company unless
followed by written confirmation by an authorized signatory of the Company.
-----------------------------------------------------------------------------------
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |