Bug 13932 - Run shutdown -P command, kernel occur kernel panic issue.
Summary: Run shutdown -P command, kernel occur kernel panic issue.
Status: RESOLVED NOTABUG
Alias: None
Product: Kernel
Classification: Yocto Project Subprojects
Component: linux-yocto (show other bugs)
Version: 3.1
Hardware: x86 x86_64
: Medium+ normal
Target Milestone: 3.1.2
Assignee: Anuj Mittal
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-06-05 00:04 UTC by robert1030tw
Modified: 2020-06-16 20:21 UTC (History)
1 user (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: Don't know


Attachments
linux-yocto-5.4.34-configure file (144.93 KB, text/plain)
2020-06-05 00:04 UTC, robert1030tw
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description robert1030tw 2020-06-05 00:04:14 UTC
Created attachment 4688 [details]
linux-yocto-5.4.34-configure file

bitbake build info

Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "universal"
TARGET_SYS           = "x86_64-poky-linux"
MACHINE              = "intel-corei7-64"
DISTRO               = "poky"
DISTRO_VERSION       = "3.1"
TUNE_FEATURES        = "m64 corei7"
TARGET_FPU           = ""
meta                 
meta-poky            
meta-yocto-bsp       = "dunfell:6436d102f15a129384d980f65b02b86fc52ae77a"
meta-oe              
meta-filesystems     
meta-python          
meta-networking      = "dunfell:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-intel           = "dunfell:858e7f0f03fe514f0a5b99abde9a5ebc52f55b9c"
meta-dpdk            = "dunfell:04f410e3d26776db5b697dbb63ce00d902d702f2"

Run "shutdown -P now" @ system, PC console will got kernel panic situation
root@intel-x86-64:~# shutdown -P now
systemd-shutdown[1]: Syncing filesystems and block devices.
systemd-shutdown[1]: Sending SIGTERM to remaining processes...
systemd-journald[207]: Received SIGTERM from PID 1 (systemd-shutdow).
systemd-shutdown[1]: Sending SIGKILL to remaining processes...
systemd-shutdown[1]: Unmounting file systems.
[2798]: Remounting '/' read-only in with options '(null)'.
EXT4-fs (sdb2): re-mounted. Opts: (null)
systemd-shutdown[1]: All filesystems unmounted.
systemd-shutdown[1]: Deactivating swaps.
systemd-shutdown[1]: All swaps deactivated.
systemd-shutdown[1]: Detaching loop devices.
systemd-shutdown[1]: All loop devices detached.
systemd-shutdown[1]: Detaching DM devices.
systemd-shutdown[1]: All DM devices detached.
systemd-shutdown[1]: All filesystems, swaps, loop devices and DM devices detached.
systemd-shutdown[1]: Syncing filesystems and block devices.
systemd-shutdown[1]: Powering off.
kvm: exiting hardware virtualization
sd 4:0:0:0: [sda] Synchronizing SCSI cache
sd 4:0:0:0: [sda] Stopping disk
ACPI: Preparing to enter system sleep state S5
reboot: Power down
Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000000
CPU: 0 PID: 1 Comm: systemd-shutdow Tainted: G           O      5.4.34-yocto-standard #1
Hardware name: Default string To be filled by O.E.M./To be filled by O.E.M., BIOS 0.3.2 12/17/2019
Call Trace:
 dump_stack+0x59/0x7a
 panic+0x102/0x2c3
 ? rcuwait_wake_up+0x2a/0x30
 do_exit.cold+0x21/0xb5
 ? acpi_enter_sleep_state+0xb7/0xbf
 ? acpi_power_off+0x27/0x29
 __do_sys_reboot+0x12a/0x210
 ? vfs_writev+0xc3/0xf0
 ? handle_mm_fault+0xbe/0x1f0
 __x64_sys_reboot+0x1e/0x20
 do_syscall_64+0x51/0x180
 entry_SYSCALL_64_after_hwframe+0x44/0xa9
RIP: 0033:0x7fc7744e3323
Code: 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 89 fa be 69 19 12 28 bf ad de e1 fe b8 a9 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 05 c3 0f 1f 40 00 48 8b 15 39 4b 0c 00 f7 d8
RSP: 002b:00007ffc8d426088 EFLAGS: 00000206 ORIG_RAX: 00000000000000a9
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007fc7744e3323
RDX: 000000004321fedc RSI: 0000000028121969 RDI: 00000000fee1dead
RBP: 0000000000000000 R08: 0000000000001004 R09: 00007ffc8d4254b0
R10: 00007fc7742f76a0 R11: 0000000000000206 R12: 0000000000000000
R13: 0000000000000000 R14: 0000000000000006 R15: 0000000000000000
Kernel Offset: 0x12600000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-

Shutdown -H or reboot, can't reproduce the issue.
May i kernel config that it has problem, please help me, thanks.
Comment 1 robert1030tw 2020-06-07 20:07:00 UTC
Hi all:

the issue seem to relate kernel configuration setting

I found some discussions with the situation on Internet, Disable "CONFIG_ACPI_REDUCED_HARDWARE_ONLY" of kernel configuration, the issue will can't be reproduced, so it try this method, the issue can't be reproduced on Poky-3.1 (kernel-5.4.34)

some discussions link is below:
https://github.com/clearlinux/distribution/issues/186

CONFIG_ACPI_REDUCED_HARDWARE_ONLY=y
# CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set
Comment 2 Anuj Mittal 2020-06-16 00:21:36 UTC
(In reply to comment #1)
> Hi all:
> 
> the issue seem to relate kernel configuration setting
> 
> I found some discussions with the situation on Internet, Disable
> "CONFIG_ACPI_REDUCED_HARDWARE_ONLY" of kernel configuration, the issue will
> can't be reproduced, so it try this method, the issue can't be reproduced on
> Poky-3.1 (kernel-5.4.34)
> 
> some discussions link is below:
> https://github.com/clearlinux/distribution/issues/186
> 
> CONFIG_ACPI_REDUCED_HARDWARE_ONLY=y
> # CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set

I don't see it enabled in my configuration. Have you made any changes to the meta revision or are using a custom kernel configuration?
Comment 3 robert1030tw 2020-06-16 19:35:59 UTC
Hi all:
Default configuration, seem no this item "CONFIG_ACPI_REDUCED_HARDWARE_ONLY ", sorry i using a custom kernel configuration from Internet. so i will remove the item on my kernel configuration.
Comment 4 Anuj Mittal 2020-06-16 20:21:40 UTC
(In reply to comment #3)
> Hi all:
> Default configuration, seem no this item "CONFIG_ACPI_REDUCED_HARDWARE_ONLY
> ", sorry i using a custom kernel configuration from Internet. so i will
> remove the item on my kernel configuration.

Thanks, I am closing the bug in that case. Please let me know if you see issues with the default configuration as well.