EFI kdump without acpi_rsdp
by Dave Young
Vivek
I tried kdump without acpi_rsdp on your reserved machine. It can not
boot similar with the initial report here:
http://lists.infradead.org/pipermail/kexec/2010-March/003889.html
Below is the detail kmsg, tried noacpi, noapic, nox2apic, they all does
not help on this problem.
[root@intel-canoepass-02 ~]# echo c >/proc/sysrq-trigger
[ 288.091055] SysRq : Trigger a crash
[ 288.094991] BUG: unable to handle kernel NULL pointer dereference at
(null)
[ 288.103755] IP: [<ffffffff813aee06>] sysrq_handle_crash+0x16/0x20
[ 288.110574] PGD 41ed3a067 PUD 41ef11067 PMD 0
[ 288.115573] Oops: 0002 [#1] SMP
[ 288.119191] Modules linked in: nf_conntrack_netbios_ns
nf_conntrack_broadcast ipt_MASQUERADE ip6table_nat nf_nat_ipv6
ip6table_mangle ip6t_REJECT nf_conntrack_ipv6 nf_defrag_ipv6 iptable_nat
nf_nat_ipv4 nf_nat iptable_mangle nf_conntrack_ipv4 nf_defrag_ipv4
xt_conntrack nf_conntrack ebtable_filter ebtables ip6table_filter
ip6_tables vfat fat acpi_cpufreq mperf coretemp kvm_intel kvm
crc32_pclmul crc32c_intel ghash_clmulni_intel iTCO_wdt igb
iTCO_vendor_support ptp microcode lpc_ich pps_core mfd_core ioatdma
i2c_i801 dca mgag200 i2c_algo_bit drm_kms_helper ttm isci drm libsas
i2c_core scsi_transport_sas wmi
[ 288.179797] CPU 3
[ 288.181854] Pid: 1443, comm: bash Not tainted 3.9.8-300.fc19.x86_64
#1 Intel Corporation S2600CP/S2600CP
[ 288.192633] RIP: 0010:[<ffffffff813aee06>] [<ffffffff813aee06>]
sysrq_handle_crash+0x16/0x20
[ 288.202158] RSP: 0018:ffff880420bd5e70 EFLAGS: 00010096
[ 288.208083] RAX: 000000000000000f RBX: ffffffff81c9a100 RCX:
ffff88042f66fb90
[ 288.216046] RDX: 0000000000000000 RSI: ffff88042f66df48 RDI:
0000000000000063
[ 288.224007] RBP: ffff880420bd5e70 R08: ffffffff81e97ddc R09:
000000000000084e
[ 288.231967] R10: 000000000000084d R11: 0000000000000003 R12:
0000000000000063
[ 288.239927] R13: 0000000000000246 R14: 0000000000000007 R15:
0000000000000000
[ 288.247888] FS: 00007f2458bb7740(0000) GS:ffff88042f660000(0000)
knlGS:0000000000000000
[ 288.256917] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 288.263329] CR2: 0000000000000000 CR3: 0000000425752000 CR4:
00000000001407e0
[ 288.271282] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 288.279244] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 288.287205] Process bash (pid: 1443, threadinfo ffff880420bd4000,
task ffff880423811770)
[ 288.296231] Stack:
[ 288.298475] ffff880420bd5ea8 ffffffff813af4c2 0000000000000002
ffff8804246dc900
[ 288.306782] 00007f2458bbe000 0000000000000002 ffff880420bd5f50
ffff880420bd5ec8
[ 288.315091] ffffffff813af93a 00007f2458bbe000 ffff8804258ea600
ffff880420bd5f08
[ 288.323398] Call Trace:
[ 288.326135] [<ffffffff813af4c2>] __handle_sysrq+0xa2/0x170
[ 288.332357] [<ffffffff813af93a>] write_sysrq_trigger+0x4a/0x50
[ 288.338968] [<ffffffff811fe809>] proc_reg_write+0x69/0xa0
[ 288.345096] [<ffffffff81199fcf>] vfs_write+0x9f/0x170
[ 288.350831] [<ffffffff8119a2c9>] sys_write+0x49/0xa0
[ 288.356473] [<ffffffff8164efd9>] system_call_fastpath+0x16/0x1b
[ 288.363175] Code: e8 20 f8 ff ff eb c3 66 2e 0f 1f 84 00 00 00 00 00
0f 1f 40 00 0f 1f 44 00 00 55 c7 05 04 7f ae 00 01 00 00 00 48 89 e5 0f
ae f8 <c6> 04 25 00 00 00 00 01 5d c3 0f 1f 44 00 00 55 31 c0 c7 05 6e
[ 288.385035] RIP [<ffffffff813aee06>] sysrq_handle_crash+0x16/0x20
[ 288.391944] RSP <ffff880420bd5e70>
[ 288.395836] CR2: 0000000000000000
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 3.9.8-300.fc19.x86_64 (mockbuild@bkernel02)
(gcc version 4.8.1 20130603 (Red Hat 4.8.1-1) (GCC) ) #1 SMP Thu Jun 27
19:24:23 UTC 2013
[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-3.9.8-300.fc19.x86_64
root=/dev/mapper/fedora_intel--canoepass--02-root ro rd.md=0 rd.dm=0
rd.lvm.lv=fedora_intel-canoepass-02/root console=ttyS0,115200n81
vconsole.keymap=us rd.lvm.lv=fedora_intel-canoepass-02/swap rd.luks=0
vconsole.font=latarcyrheb-sun16 irqpoll nr_cpus=1 reset_devices
cgroup_disable=memory mce=off numa=off udev.children-max=2 rd.memdebug=1
rd.break=cmdline earlyprintk=ttyS0,115200n8 memmap=exactmap
memmap=636K@4K memmap=130412K@786432K elfcorehdr=916844K
memmap=3076K#3060380K memmap=2048K#3106140K memmap=280K#3110812K
memmap=848K#3111092K memmap=4K#3111940K memmap=120K#3111944K
memmap=564K#3112064K
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000100-0x000000000009ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000000a0000-0x00000000000fffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000b9f83fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000b9f84000-0x00000000b9f9efff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000b9f9f000-0x00000000ba556fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000ba557000-0x00000000ba558fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ba559000-0x00000000ba8aefff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000ba8af000-0x00000000ba8d6fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ba8d7000-0x00000000baa7ffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000baa80000-0x00000000baa8ffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000baa90000-0x00000000baaa8fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000baaa9000-0x00000000baadffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000baae0000-0x00000000bab57fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bab58000-0x00000000bab5bfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bab5c000-0x00000000bab67fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bab68000-0x00000000bab6bfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bab6c000-0x00000000bab9bfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bab9c000-0x00000000bababfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000babac000-0x00000000babb1fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000babb2000-0x00000000babddfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000babde000-0x00000000bac39fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bac3a000-0x00000000bac40fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bac41000-0x00000000baca6fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000baca7000-0x00000000bafa7fff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bafa8000-0x00000000bb04afff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb04b000-0x00000000bb04efff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb04f000-0x00000000bb06cfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb06d000-0x00000000bb070fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb071000-0x00000000bb085fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb086000-0x00000000bb089fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb08a000-0x00000000bb163fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb164000-0x00000000bb176fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb177000-0x00000000bb187fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb188000-0x00000000bb18bfff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb18c000-0x00000000bb1f6fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bb1f7000-0x00000000bb1fefff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bb1ff000-0x00000000bd8d5fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bd8d6000-0x00000000bd8d9fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bd8da000-0x00000000bd956fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bd957000-0x00000000bdb56fff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bdb57000-0x00000000bdb5bfff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bdb5c000-0x00000000bdb5efff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bdb5f000-0x00000000bdcd5fff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000bdcd6000-0x00000000bdde6fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000bdde7000-0x00000000bde2cfff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bde2d000-0x00000000bdf00fff]
ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bdf01000-0x00000000bdf01fff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bdf02000-0x00000000bdf1ffff]
ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000bdf20000-0x00000000bdfacfff]
ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000bdfad000-0x00000000bdffffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000be000000-0x00000000cfffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed19000-0x00000000fed19fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff]
reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffc00000-0x00000000ffffffff]
reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000083fffffff] usable
[ 0.000000] bootconsole [earlyser0] enabled
[ 0.000000] e820: last_pfn = 0x840000 max_arch_pfn = 0x400000000
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] e820: user-defined physical RAM map:
[ 0.000000] user: [mem 0x0000000000001000-0x000000000009ffff] usable
[ 0.000000] user: [mem 0x0000000030000000-0x0000000037f5afff] usable
[ 0.000000] user: [mem 0x00000000baca7000-0x00000000bafa7fff] ACPI data
[ 0.000000] user: [mem 0x00000000bd957000-0x00000000bdb56fff] ACPI data
[ 0.000000] user: [mem 0x00000000bdde7000-0x00000000bdfacfff] ACPI data
[ 0.000000] DMI not present or invalid.
[ 0.000000] No AGP bridge found
[ 0.000000] e820: last_pfn = 0x37f5b max_arch_pfn = 0x400000000
[ 0.000000] x86 PAT enabled: cpu 0, old 0x7010600070106, new
0x7010600070106
[ 0.000000] x2apic enabled by BIOS, switching to x2apic ops
[ 0.000000] found SMP MP-table at [mem 0x000fcaf0-0x000fcaff] mapped
at [ffff8800000fcaf0]
[ 0.000000] Using GB pages for direct mapping
[ 0.000000] init_memory_mapping: [mem 0x00000000-0x000fffff]
[ 0.000000] init_memory_mapping: [mem 0x37400000-0x375fffff]
[ 0.000000] init_memory_mapping: [mem 0x34000000-0x373fffff]
[ 0.000000] init_memory_mapping: [mem 0x30000000-0x33ffffff]
[ 0.000000] init_memory_mapping: [mem 0x37600000-0x37f5afff]
[ 0.000000] RAMDISK: [mem 0x377ac000-0x37f48fff]
[ 0.000000] ACPI BIOS Bug: Error: A valid RSDP was not found
(20130117/tbxfroot-218)
[ 0.000000] NUMA turned off
[ 0.000000] Faking a node at [mem 0x0000000000000000-0x0000000037f5afff]
[ 0.000000] Initmem setup node 0 [mem 0x00000000-0x37f5afff]
[ 0.000000] NODE_DATA [mem 0x37798000-0x377abfff]
[ 0.000000] Zone ranges:
[ 0.000000] DMA [mem 0x00001000-0x00ffffff]
[ 0.000000] DMA32 [mem 0x01000000-0xffffffff]
[ 0.000000] Normal empty
[ 0.000000] Movable zone start for each node
[ 0.000000] Early memory node ranges
[ 0.000000] node 0: [mem 0x00001000-0x0009ffff]
[ 0.000000] node 0: [mem 0x30000000-0x37f5afff]
[ 0.000000] SFI: Simple Firmware Interface v0.81
http://simplefirmware.org
[ 0.000000] Intel MultiProcessor Specification v1.4
[ 0.000000] MPTABLE: OEM ID: INTEL
[ 0.000000] MPTABLE: Product ID: ROMLEY
[ 0.000000] MPTABLE: APIC at: 0xFEE00000
[ 0.000000] BUG: unable to handle kernel paging request at
ffffffffff5f8020
[ 0.000000] IP: [<ffffffff8103c5a3>] native_apic_mem_read+0x3/0x10
[ 0.000000] PGD 36c0f067 PUD 36c11067 PMD 36e4b067 PTE 0
[ 0.000000] Oops: 0000 [#1] SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU 0
[ 0.000000] Pid: 0, comm: swapper Not tainted 3.9.8-300.fc19.x86_64 #1
[ 0.000000] RIP: 0010:[<ffffffff8103c5a3>] [<ffffffff8103c5a3>]
native_apic_mem_read+0x3/0x10
[ 0.000000] RSP: 0000:ffffffff81c01e38 EFLAGS: 00010046
[ 0.000000] RAX: ffffffff81c20d40 RBX: ffff8800000fcaf0 RCX:
0000000000000025
[ 0.000000] RDX: 00000000000000ca RSI: 0000000000000046 RDI:
0000000000000020
[ 0.000000] RBP: ffffffff81c01e48 R08: 3a454c424154504d R09:
000000000000008b
[ 0.000000] R10: 7830203a74612043 R11: 3030303030454546 R12:
0000000000000000
[ 0.000000] R13: 000000000079c9ba R14: 00000000000004d4 R15:
ffffffffff475510
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffff81cef000(0000)
knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: ffffffffff5f8020 CR3: 0000000036c0c000 CR4:
00000000000000b0
[ 0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 0.000000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 0.000000] Process swapper (pid: 0, threadinfo ffffffff81c00000,
task ffffffff81c13440)
[ 0.000000] Stack:
[ 0.000000] ffffffff81c01e48 ffffffff81037116 ffffffff81c01e60
ffffffff81d15bde
[ 0.000000] ffff8800000fcaf0 ffffffff81c01ed8 ffffffff81d14e9b
ffffffffff475000
[ 0.000000] ffffffff81c01e88 ffffffff8162ecf3 4e49ffff81c01ed8
ff000000004c4554
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81037116>] ? read_apic_id+0x16/0x30
[ 0.000000] [<ffffffff81d15bde>] register_lapic_address+0x60/0x89
[ 0.000000] [<ffffffff81d14e9b>] default_get_smp_config+0x24b/0x3e9
[ 0.000000] [<ffffffff8162ecf3>] ? sfi_unmap_memory+0x23/0x40
[ 0.000000] [<ffffffff81d0b001>] setup_arch+0xc51/0xd11
[ 0.000000] [<ffffffff8163c832>] ? printk+0x67/0x69
[ 0.000000] [<ffffffff81d04ba6>] start_kernel+0xd4/0x3fe
[ 0.000000] [<ffffffff81d04120>] ? early_idt_handlers+0x120/0x120
[ 0.000000] [<ffffffff81d045da>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff81d046cf>] x86_64_start_kernel+0xf3/0x100
[ 0.000000] Code: 81 f0 0f ab 01 eb 91 90 48 83 c4 10 5b 41 5c 41 5d
41 5e 41 5f 5d c3 90 55 89 ff 48 89 e5 89 b7 00 80 5f ff 5d c3 66 90 55
89 ff <8b> 87 00 80 5f ff 48 89 e5 5d c3 66 90 55 48 8b 05 d0 a6 7c 00
[ 0.000000] RIP [<ffffffff8103c5a3>] native_apic_mem_read+0x3/0x10
[ 0.000000] RSP <ffffffff81c01e38>
[ 0.000000] CR2: ffffffffff5f8020
[ 0.000000] ---[ end trace a7919e7f17c0a725 ]---
[ 0.000000] Kernel panic - not syncing: Attempted to kill the idle task!
[ 0.000000] BUG: unable to handle kernel paging request at
ffffffffff5f8030
[ 0.000000] IP: [<ffffffff8103c5a3>] native_apic_mem_read+0x3/0x10
[ 0.000000] PGD 36c0f067 PUD 36c11067 PMD 36e4b067 PTE 0
[ 0.000000] Oops: 0000 [#2] SMP
[ 0.000000] Modules linked in:
[ 0.000000] CPU 0
[ 0.000000] Pid: 0, comm: swapper Tainted: G D
3.9.8-300.fc19.x86_64 #1
[ 0.000000] RIP: 0010:[<ffffffff8103c5a3>] [<ffffffff8103c5a3>]
native_apic_mem_read+0x3/0x10
[ 0.000000] RSP: 0000:ffffffff81c01a58 EFLAGS: 00010002
[ 0.000000] RAX: ffffffff81c20d40 RBX: 0000000000000046 RCX:
0000000000000002
[ 0.000000] RDX: 0000000000000002 RSI: 0000000000000001 RDI:
0000000000000030
[ 0.000000] RBP: ffffffff81c01a70 R08: 0000000000000001 R09:
0000000000000002
[ 0.000000] R10: ffffffff81ce2b70 R11: 216b73617420656c R12:
0000000000000000
[ 0.000000] R13: ffffffff81ce2b70 R14: 0000000000000000 R15:
ffffffff81c13440
[ 0.000000] FS: 0000000000000000(0000) GS:ffffffff81cef000(0000)
knlGS:0000000000000000
[ 0.000000] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 0.000000] CR2: ffffffffff5f8030 CR3: 0000000036c0c000 CR4:
00000000000000b0
[ 0.000000] DR0: 0000000000000000 DR1: 0000000000000000 DR2:
0000000000000000
[ 0.000000] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7:
0000000000000400
[ 0.000000] Process swapper (pid: 0, threadinfo ffffffff81c00000,
task ffffffff81c13440)
[ 0.000000] Stack:
[ 0.000000] ffffffff81c01a70 ffffffff81037664 0000000000000046
ffffffff81c01a80
[ 0.000000] ffffffff810378f2 ffffffff81c01aa8 ffffffff8103692e
ffffffff819e7c78
[ 0.000000] 0000000000000000 0000000000000046 ffffffff81c01b20
ffffffff8163c695
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff81037664>] ? clear_local_APIC+0x34/0x2a0
[ 0.000000] [<ffffffff810378f2>] disable_local_APIC+0x22/0x50
[ 0.000000] [<ffffffff8103692e>] native_stop_other_cpus+0xde/0x160
[ 0.000000] [<ffffffff8163c695>] panic+0xd7/0x1d7
[ 0.000000] [<ffffffff81062c89>] do_exit+0x939/0xa20
[ 0.000000] [<ffffffff8163c832>] ? printk+0x67/0x69
[ 0.000000] [<ffffffff81647ce3>] oops_end+0xa3/0xe0
[ 0.000000] [<ffffffff8163c168>] no_context+0x263/0x270
[ 0.000000] [<ffffffff8163c1e8>] __bad_area_nosemaphore+0x73/0x1cc
[ 0.000000] [<ffffffff8163c354>] bad_area_nosemaphore+0x13/0x15
[ 0.000000] [<ffffffff8164a8ae>] __do_page_fault+0x31e/0x510
[ 0.000000] [<ffffffff8105d73c>] ? print_time.part.4+0x6c/0x90
[ 0.000000] [<ffffffff8105d7cf>] ? print_prefix+0x6f/0xb0
[ 0.000000] [<ffffffff8105d8fa>] ? msg_print_text+0xea/0x1d0
[ 0.000000] [<ffffffff8103fb7c>] ? early_serial_write+0x2c/0x60
[ 0.000000] [<ffffffff81646826>] ? _raw_spin_unlock_irqrestore+0x16/0x20
[ 0.000000] [<ffffffff81646826>] ? _raw_spin_unlock_irqrestore+0x16/0x20
[ 0.000000] [<ffffffff8105ea75>] ? wake_up_klogd+0x5/0x50
[ 0.000000] [<ffffffff8164aaae>] do_page_fault+0xe/0x10
[ 0.000000] [<ffffffff81647158>] page_fault+0x28/0x30
[ 0.000000] [<ffffffff8103c5a3>] ? native_apic_mem_read+0x3/0x10
[ 0.000000] [<ffffffff81037116>] ? read_apic_id+0x16/0x30
[ 0.000000] [<ffffffff81d15bde>] register_lapic_address+0x60/0x89
[ 0.000000] [<ffffffff81d14e9b>] default_get_smp_config+0x24b/0x3e9
[ 0.000000] [<ffffffff8162ecf3>] ? sfi_unmap_memory+0x23/0x40
[ 0.000000] [<ffffffff81d0b001>] setup_arch+0xc51/0xd11
[ 0.000000] [<ffffffff8163c832>] ? printk+0x67/0x69
[ 0.000000] [<ffffffff81d04ba6>] start_kernel+0xd4/0x3fe
[ 0.000000] [<ffffffff81d04120>] ? early_idt_handlers+0x120/0x120
[ 0.000000] [<ffffffff81d045da>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff81d046cf>] x86_64_start_kernel+0xf3/0x100
[ 0.000000] Code: 81 f0 0f ab 01 eb 91 90 48 83 c4 10 5b 41 5c 41 5d
41 5e 41 5f 5d c3 90 55 89 ff 48 89 e5 89 b7 00 80 5f ff 5d c3 66 90 55
89 ff <8b> 87 00 80 5f ff 48 89 e5 5d c3 66 90 55 48 8b 05 d0 a6 7c 00
[ 0.000000] RIP [<ffffffff8103c5a3>] native_apic_mem_read+0x3/0x10
[ 0.000000] RSP <ffffffff81c01a58>
[ 0.000000] CR2: ffffffffff5f8030
[ 0.000000] ---[ end trace a7919e7f17c0a726 ]---
--
Thanks
Dave
10 years, 1 month
There is no message displayed if dump was not saved successfully
by Vivek Goyal
Hi Chao,
Recently you put a commit to output various messages related to dump.
Today I was saving dump and it failed but there is no message on console
saying dump failed.
I think we should display a message on console if dump saving failed. Can
you please look into it.
Thanks
Vivek
10 years, 2 months
Re: [Fwd: Re: F20 System Wide Change: Enable kdump on secureboot machines]
by Vivek Goyal
Adam,
I am forwarding this discussion to kexec list. Right now, I don't have time
to try it. I am hoping somebody on the list will have enthusiasm to
give kdump on on live images a try and see what are the issues.
Thanks
Vivek
On Thu, Jul 25, 2013 at 09:13:14AM -0700, Adam Williamson wrote:
> Hi, dedo. I realized I forgot to pass this onto you. I forwarded your
> concerns about kdump on live images to our kdump person (hi Vivek!), he
> had some comments - see attached. Vivek, what is it you'd like dedo or
> me to 'play with'?
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> Date: Fri, 12 Jul 2013 11:55:59 -0400
> From: Vivek Goyal <vgoyal(a)redhat.com>
> To: Adam Williamson <awilliam(a)redhat.com>
> Subject: Re: F20 System Wide Change: Enable kdump on secureboot machines
> User-Agent: Mutt/1.5.21 (2010-09-15)
> Message-ID: <20130712155559.GF2272(a)redhat.com>
>
> On Fri, Jul 12, 2013 at 08:29:21AM -0700, Adam Williamson wrote:
> > On Fri, 2013-07-12 at 10:55 -0400, Vivek Goyal wrote:
> > > On Thu, Jul 11, 2013 at 02:09:54PM -0700, Adam Williamson wrote:
> > > > On Thu, 2013-07-11 at 14:13 -0400, Vivek Goyal wrote:
> > > >
> > > > > I think this is a wrong impression. Kdump should work in Fedora. For a
> > > > > long time I got the feedback that fedora users don't care about kdump
> > > > > working. But I think kdump is an important debugging facility and is
> > > > > very useful for enterprise distro. So at times it should be useful for
> > > > > fedora users too.
> > > > >
> > > > > So now I am trying to make sure things work well in Fedora.
> > > >
> > > > FWIW, dedoimedo (a notoriously tough distro reviewer) mentioned to me in
> > > > private correspondence that he's been hitting a kernel crash with F19
> > > > with one of his test systems and he'd want to use kdump to try and
> > > > diagnose it, only it doesn't work on live images, he says. Is that
> > > > accurate? If so, can it be made to work on live images?
> > >
> > > I have never tested kdump on live images. What's the problem he is facing?
> >
> > Taking off list since it's a bit OT, here's what I got from him:
> >
> > "I was not able to install the server because of this. I also don't have
> > a kdump core, cause it's not enable in the live session."
>
> Ok, I think he might be facing multiple issues here.
>
> - kexec-tools rpm is not available in live media.
> - crashkernel=128M is not enabled on kernel command line.
>
> I suspect it could be rpm thing.
>
> >
> > "P.S. I would recommend setting up live beta editions with kdump enabled
> > and ask user just to configure the dump storage, because this can allow
> > you to collect cores and sort them out."
> >
> > "... the best thing would be to configure kdump really.
> > Have the crash offset configured,
>
> Not sure what he means by crash core offset configured. Most likely he
> is referring to crashkernel= parameter which needs to be specified on
> kernel command line. That one can do by editing grub command line
> when live media boots.
>
> > just leave the last stage for
> > destination. That would be useful, maybe for v20."
>
> Will you be interested in playing with it a bit.
>
> Thanks
> Vivek
>
10 years, 2 months
[Fedora Patch] dracut-module-setup.sh: setup correct system time and time zone in 2nd kernel.
by WANG Chao
Currently in initrd, hardware clock is always considered to use UTC time
format and system time zone is also UTC. Thus system time isn't correct
if hw clock is localtime or we're using other time zone in real root.
To fix this, install /etc/adjtime and /etc/localtime to initrd.
Previously, this functionality was implemented in dracut base module:
commit 77364fd
Author: WANG Chao <chaowang(a)redhat.com>
base: setup correct system time and time zone in initrd
But some people complains about a normal boot initrd needs to rebuild
every time if time zone is changed. So let's fix it on our side.
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
---
dracut-module-setup.sh | 1 +
1 file changed, 1 insertion(+)
diff --git a/dracut-module-setup.sh b/dracut-module-setup.sh
index 725eecf..3c64d00 100755
--- a/dracut-module-setup.sh
+++ b/dracut-module-setup.sh
@@ -403,6 +403,7 @@ install() {
if is_ssh_dump_target; then
dracut_install /var/lib/random-seed || exit $?
fi
+ dracut_install -o /etc/adjtime /etc/localtime
inst "$moddir/monitor_dd_progress" "/kdumpscripts/monitor_dd_progress"
chmod +x ${initdir}/kdumpscripts/monitor_dd_progress
inst "/bin/dd" "/bin/dd"
--
1.8.3.1
10 years, 2 months
[Fedora Patch v3] kernel cmdline: Remove hugepage allocations
by WANG Chao
2nd kernel has very limited memory. Allocating huge pages will probably
trigger OOM. So let's remove hugepages and hugepagesz kernel parameters
for 2nd kernel when 1st kernel are using them.
If user wants huge pages cmdline in 2nd kernel, he/she can still specify
it through KERNEL_COMMANDLINE_APPEND in /etc/sysconfig/kdump.
This patch adds a new function remove_cmdline_param(). It takes a list
of kernel parameters as its arguments and remove them from given kernel
cmdline.
update:
1. Add description of remove_cmdline_param() per Vivek.
2. Remove_cmdline_param() will take kernel cmdline as $1, then strip it
and print the result.
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
---
kdumpctl | 19 ++++++++++++++++++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/kdumpctl b/kdumpctl
index 36e969f..aba1e3c 100755
--- a/kdumpctl
+++ b/kdumpctl
@@ -16,6 +16,23 @@ if [ -f /etc/sysconfig/kdump ]; then
. /etc/sysconfig/kdump
fi
+# remove_cmdline_param <kernel cmdline> <param1> [<param2>] ... [<paramN>]
+# Remove a list of kernel parameters from a given kernel cmdline and print the result.
+# For each "arg" in the removing params list, "arg" and "arg=xxx" will be removed if exists.
+function remove_cmdline_param()
+{
+ local cmdline=$1
+ shift
+
+ for arg in $@; do
+ cmdline=`echo $cmdline | \
+ sed -e "s/\b$arg=[^ ]*\b//g" \
+ -e "s/\b$arg\b//g" \
+ -e "s/\s\+/ /g"`
+ done
+ echo $cmdline
+}
+
function save_core()
{
coredir="/var/crash/`date +"%Y-%m-%d-%H:%M"`"
@@ -221,8 +238,8 @@ function load_kdump()
then
KDUMP_COMMANDLINE=`cat /proc/cmdline`
fi
+ KDUMP_COMMANDLINE=`remove_cmdline_param "$KDUMP_COMMANDLINE" crashkernel hugepages hugepagesz`
- KDUMP_COMMANDLINE=`echo $KDUMP_COMMANDLINE | sed -e 's/crashkernel=[^ ]*//'`
KDUMP_COMMANDLINE="${KDUMP_COMMANDLINE} ${KDUMP_COMMANDLINE_APPEND}"
$KEXEC $KEXEC_ARGS $standard_kexec_args \
--
1.8.3.1
10 years, 2 months
[Fedora Patch v2] kernel cmdline: Remove hugepage allocations
by WANG Chao
2nd kernel has very limited memory. Allocating huge pages will probably
trigger OOM. So let's remove hugepages and hugepagesz kernel parameters
for 2nd kernel when 1st kernel are using them.
If user wants huge pages cmdline in 2nd kernel, he/she can still specify
it through KERNEL_COMMANDLINE_APPEND in /etc/sysconfig/kdump.
This patch adds a new function remove_cmdline_param(). It takes a list
of kernel parameters as its arguments and remove them from
1st kernel cmdline or KERNEL_COMMANDLINE if set in /etc/sysconfig/kdump.
However It wouldn't touch user specified KDUMP_COMMANDLINE_APPEND in
/etc/sysconfig/kdump.
update: Add description of remove_cmdline_param() per Vivek.
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
---
kdumpctl | 15 ++++++++++++++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/kdumpctl b/kdumpctl
index 36e969f..8b2e746 100755
--- a/kdumpctl
+++ b/kdumpctl
@@ -16,6 +16,19 @@ if [ -f /etc/sysconfig/kdump ]; then
. /etc/sysconfig/kdump
fi
+# Removes a list of kernel parameters from KDUMP_COMMANDLINE
+# $@ takes a list of arguments, but can not be empty.
+# For each arg in $@, kernel param "arg" and "arg=xxx" will be removed if exists.
+function remove_cmdline_param()
+{
+ for arg in $@; do
+ KDUMP_COMMANDLINE=`echo $KDUMP_COMMANDLINE | \
+ sed -e "s/\b$arg=[^ ]*\b//g" \
+ -e "s/\b$arg\b//g" \
+ -e "s/\s\+/ /g"`
+ done
+}
+
function save_core()
{
coredir="/var/crash/`date +"%Y-%m-%d-%H:%M"`"
@@ -221,8 +234,8 @@ function load_kdump()
then
KDUMP_COMMANDLINE=`cat /proc/cmdline`
fi
+ remove_cmdline_param crashkernel hugepages hugepagesz
- KDUMP_COMMANDLINE=`echo $KDUMP_COMMANDLINE | sed -e 's/crashkernel=[^ ]*//'`
KDUMP_COMMANDLINE="${KDUMP_COMMANDLINE} ${KDUMP_COMMANDLINE_APPEND}"
$KEXEC $KEXEC_ARGS $standard_kexec_args \
--
1.8.3.1
10 years, 2 months
[Fedora Patch] kernel cmdline: Remove hugepage allocations
by WANG Chao
2nd kernel has very limited memory. Allocating huge pages will probably
trigger OOM. So let's remove hugepages and hugepagesz kernel parameters
for 2nd kernel when 1st kernel are using them.
If user wants huge pages cmdline in 2nd kernel, he/she can still specify
it through KERNEL_COMMANDLINE_APPEND in /etc/sysconfig/kdump.
This patch adds a new function remove_cmdline(). It takes a list of
kernel parameters as its arguments and remove them from
1st kernel cmdline or KERNEL_COMMANDLINE if set in /etc/sysconfig/kdump.
However It wouldn't touch user specified KDUMP_COMMANDLINE_APPEND in
/etc/sysconfig/kdump.
Signed-off-by: WANG Chao <chaowang(a)redhat.com>
---
kdumpctl | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/kdumpctl b/kdumpctl
index 36e969f..8aaeb97 100755
--- a/kdumpctl
+++ b/kdumpctl
@@ -16,6 +16,16 @@ if [ -f /etc/sysconfig/kdump ]; then
. /etc/sysconfig/kdump
fi
+function remove_cmdline()
+{
+ for arg in $@; do
+ KDUMP_COMMANDLINE=`echo $KDUMP_COMMANDLINE | \
+ sed -e "s/\b$arg=[^ ]*\b//g" \
+ -e "s/\b$arg\b//g" \
+ -e "s/\s\+/ /g"`
+ done
+}
+
function save_core()
{
coredir="/var/crash/`date +"%Y-%m-%d-%H:%M"`"
@@ -221,8 +231,8 @@ function load_kdump()
then
KDUMP_COMMANDLINE=`cat /proc/cmdline`
fi
+ remove_cmdline crashkernel hugepages hugepagesz
- KDUMP_COMMANDLINE=`echo $KDUMP_COMMANDLINE | sed -e 's/crashkernel=[^ ]*//'`
KDUMP_COMMANDLINE="${KDUMP_COMMANDLINE} ${KDUMP_COMMANDLINE_APPEND}"
$KEXEC $KEXEC_ARGS $standard_kexec_args \
--
1.8.3.1
10 years, 2 months