Bug 1520265 - acpi: unable to handle kernel paging request at ffffc1b9c0376000
Summary: acpi: unable to handle kernel paging request at ffffc1b9c0376000
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-04 07:15 UTC by xiaoli feng
Modified: 2026-07-24 14:54 UTC (History)
24 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description xiaoli feng 2017-12-04 07:15:53 UTC
Description of problem:
Happen once when boot.

[    0.238333] BUG: unable to handle kernel paging request at ffffc1b9c0376000 
[    0.239000] IP: acpi_ex_system_memory_space_handler+0x20b/0x285 
[    0.239000] PGD 7794a067 P4D 7794a067 PUD 7794b067 PMD 77b74067 PTE 0 
[    0.239000] Oops: 0000 [#1] SMP 
[    0.239000] Modules linked in: 
[    0.239000] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 4.15.0-0.rc1.git1.1.fc28.x86_64 #1 
[    0.239000] Hardware name: Hewlett-Packard  /2820h, BIOS 786F2 v01.53 08/27/2008 
[    0.239000] task: ffff9f7e370a8000 task.stack: ffffc1b9c0328000 
[    0.239000] RIP: 0010:acpi_ex_system_memory_space_handler+0x20b/0x285 
[    0.239000] RSP: 0000:ffffc1b9c032b6f0 EFLAGS: 00010246 
[    0.239000] RAX: ffffc1b9c0375ffe RBX: 00000000000fdffe RCX: 0000000000000000 
[    0.239000] RDX: 0000000000000000 RSI: 0000000000000002 RDI: 0000000000000246 
[    0.239000] RBP: 0000000000000020 R08: 0000000000000001 R09: 0000000000000001 
[    0.239000] R10: 0000000000000000 R11: 0000000000000000 R12: ffffc1b9c0375ffe 
[    0.239000] R13: 0000000000000000 R14: ffffc1b9c032b830 R15: ffff9f7e36c261c0 
[    0.239000] FS:  0000000000000000(0000) GS:ffff9f7e39e00000(0000) knlGS:0000000000000000 
[    0.239000] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033 
[    0.239000] CR2: ffffc1b9c0376000 CR3: 0000000035012000 CR4: 00000000000006e0 
[    0.239000] Call Trace: 
[    0.239000]  acpi_ev_address_space_dispatch+0x2d8/0x357 
[    0.239000]  ? acpi_ex_prep_field_value+0x4ce/0x4ce 
[    0.239000]  acpi_ex_access_region+0x439/0x4d8 
[    0.239000]  acpi_ex_field_datum_io+0x181/0x41b 
[    0.239000]  ? acpi_ut_trace+0x22/0x5e 
[    0.239000]  acpi_ex_extract_from_field+0x248/0x30a 
[    0.239000]  acpi_ex_read_data_from_field+0x36d/0x3b7 
[    0.239000]  acpi_ex_resolve_node_to_value+0x335/0x46a 
[    0.239000]  ? kfree+0xfe/0x2e0 
[    0.239000]  acpi_ex_resolve_to_value+0x375/0x422 
[    0.239000]  acpi_ds_evaluate_name_path+0xad/0x166 
[    0.239000]  ? acpi_ut_trace_ptr+0x26/0x68 
[    0.239000]  acpi_ds_exec_end_op+0xcc/0x6ac 
[    0.239000]  acpi_ps_parse_loop+0x926/0x9d3 
[    0.239000]  ? rcu_read_lock_sched_held+0x6b/0x80 
[    0.239000]  ? kmem_cache_alloc+0x289/0x2f0 
[    0.239000]  acpi_ps_parse_aml+0x1a2/0x4af 
[    0.239000]  acpi_ps_execute_method+0x1e9/0x2a5 
[    0.239000]  acpi_ns_evaluate+0x2e4/0x41d 
[    0.239000]  acpi_ut_evaluate_object+0xb1/0x241 
[    0.239000]  ? acpi_dma_deconfigure+0x10/0x10 
[    0.239000]  acpi_rs_get_method_data+0x56/0xd0 
[    0.239000]  ? acpi_ut_trace+0x22/0x5e 
[    0.239000]  ? acpi_res_consumer_cb+0x110/0x110 
[    0.239000]  acpi_walk_resources+0xc4/0x143 
[    0.239000]  __acpi_dev_get_resources+0xad/0xe0 
[    0.239000]  ? acpi_dma_deconfigure+0x10/0x10 
[    0.239000]  acpi_init_device_object+0x342/0x810 
[    0.239000]  acpi_add_single_object+0x72/0x6b0 
[    0.239000]  ? acpi_evaluate_integer+0xe2/0x110 
[    0.239000]  acpi_bus_check_add+0xc3/0x260 
[    0.239000]  ? trace_hardirqs_on_caller+0xed/0x180 
[    0.239000]  ? acpi_os_signal_semaphore+0x41/0x80 
[    0.239000]  acpi_ns_walk_namespace+0x131/0x280 
[    0.239000]  ? acpi_add_single_object+0x6b0/0x6b0 
[    0.239000]  ? acpi_add_single_object+0x6b0/0x6b0 
[    0.239000]  acpi_walk_namespace+0xf5/0x13d 
[    0.239000]  ? acpi_sleep_proc_init+0x24/0x24 
[    0.239000]  ? set_debug_rodata+0x11/0x11 
[    0.239000]  acpi_bus_scan+0x78/0x90 
[    0.239000]  acpi_scan_init+0xee/0x234 
[    0.239000]  ? acpi_sleep_proc_init+0x24/0x24 
[    0.239000]  acpi_init+0x302/0x362 
[    0.239000]  do_one_initcall+0x4b/0x18c 
[    0.239000]  kernel_init_freeable+0x207/0x2a8 
[    0.239000]  ? rest_init+0xd0/0xd0 
[    0.239000]  kernel_init+0xa/0xfc 
[    0.239000]  ret_from_fork+0x24/0x30 
[    0.239000] Code: 00 00 00 00 74 1e 77 0c 83 fd 08 75 50 41 0f b6 04 24 eb 1b 83 fd 20 74 12 83 fd 40 75 3f 49 8b 04 24 eb 0b 41 0f b7 04 24 eb 04 <41> 8b 04 24 49 89 06 eb 29 83 fd 10 74 1c 77 0e 83 fd 08 75 1d  
[    0.239000] RIP: acpi_ex_system_memory_space_handler+0x20b/0x285 RSP: ffffc1b9c032b6f0 
[    0.239000] CR2: ffffc1b9c0376000 
[    0.239000] ---[ end trace 2d4613bdc838c0ab ]--- 
[    0.239000] BUG: sleeping function called from invalid context at ./include/linux/percpu-rwsem.h:34 
[    0.239000] in_atomic(): 0, irqs_disabled(): 1, pid: 1, name: swapper/0 
[    0.239000] INFO: lockdep is turned off. 
[    0.239000] irq event stamp: 167320 
[    0.239000] hardirqs last  enabled at (167319): [<ffffffffb59ae272>] _raw_spin_unlock_irqrestore+0x32/0x60 
[    0.239000] hardirqs last disabled at (167320): [<ffffffffb59b00f3>] error_entry+0x73/0xd0 
[    0.239000] softirqs last  enabled at (166518): [<ffffffffb59b2e04>] __do_softirq+0x3b4/0x524 
[    0.239000] softirqs last disabled at (166513): [<ffffffffb50b9d80>] irq_exit+0x110/0x120 
[    0.239000] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G      D          4.15.0-0.rc1.git1.1.fc28.x86_64 #1 
[    0.239000] Hardware name: Hewlett-Packard  /2820h, BIOS 786F2 v01.53 08/27/2008 
[    0.239000] Call Trace: 
[    0.239000]  dump_stack+0x85/0xbf 
[    0.239000]  ___might_sleep+0x15b/0x240 
[    0.239000]  exit_signals+0x30/0x240 
[    0.239000]  do_exit+0xb8/0xd70 
[    0.239000]  rewind_stack_do_exit+0x17/0x20 
[    0.691016] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 
[    0.691016]  
[    0.692000] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000009 


Version-Release number of selected component (if applicable):
4.15.0-0.rc1.git1.1.fc28.x86_64

How reproducible:
once

Steps to Reproduce:
1. install kernel and boot.
2.
3.

Actual results:
kernel  panic

Expected results:
kernel doesn't panic

Additional info:

Comment 1 John Pilkington 2017-12-18 15:52:12 UTC
I have reported a similar panic on the Fedora users' list.  My BIOS is HP 786F2 version 1.04.   Instructions and a download are given here:

https://h30434.www3.hp.com/t5/Desktop-Hardware-and-Upgrade-Questions/Trying-to-update-the-bios-on-dc-5800-mt/m-p/5745831

... but my previous attempts to save BIOS settings have been unsuccessful. I do not know if an update would fix the problem and the 4.13 series still works.  I will await developments...

Comment 2 John Pilkington 2018-01-01 14:10:14 UTC
After following the BIOS-update instructions from the URL given in Comment 1 above I am now running 4.14.8-200.fc26.x86_64 on that box. 

HP Compaq dc5800 Microtower/2820h 

The new BIOS is 786F2 v01.60 10/26/2015 

Before that I had tried reversion to factory settings, which had no obvious effect, and writing the extracted files to a DOS-format CD, which apparently could not be read at the appropriate time.

Comment 3 Jeffrey C. Ollie 2018-03-16 02:10:02 UTC
Updating to BIOS v01.60 solved my problems with booting any kernel newer than 4.13.X as well.

Comment 4 Mo 2018-04-03 14:58:11 UTC
The same happened to me with a DC5800. runs 4.13.16.202 ok  but failed on start up
on 4.15.12 error  "acpi_ex_system_memory_space_handler" .  Upgrading BIOS on device to 1.6 from the HP website ( The BIOS upgrade appears in the Windows OS selection ) has fixed the problem . now OK .

Comment 5 mahis4799 2020-12-30 09:06:06 UTC Comment hidden (spam)
Comment 6 edin 2025-08-07 06:29:05 UTC Comment hidden (spam)
Comment 7 Charles Haithcock 2026-07-24 14:54:17 UTC
This report has not received an update in over 90 days. If this issue is still relevant to you, please do not hesitate to update this report with any relevant details on recent investigative steps or changes and we will absolutely work to understand how to best move forward. Otherwise, this bug report will need to be closed in 30 days. No worries, however; should you need still assistance after the report is closed, please do not hesitate to create a new bug report referencing this report and with any new details on the matter. 

NOTE: This is an automated mass update.


Note You need to log in before you can comment on or make changes to this bug.