plymouthd crashed with SIGSEGV in script_obj_deref_direct()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
plymouth (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Release: 18.04 Ubuntu Bionic Beaver (development branch)
plymouth:
Zainstalowana: 0.9.3-1ubuntu1
Kandydująca: 0.9.3-1ubuntu1
Tabela wersji:
*** 0.9.3-1ubuntu1 500
500 http://
100 /var/lib/
On machine with motherboard Asus PRIME B350M-A with Ryzen 5 2400G using internal vega 11 graphics by DVI interface, after boot there was screen full of artefacts instead desktop. It's repeating after every cold startup, and some but not every reboot.
I belief that issue is related to graphic card driver, because it is detected as Vega 8 mobile and this could be the issue.
inxi dump:
System: Host: teg Kernel: 4.15.0-12-generic x86_64 bits: 64 Console: tty 0
Distro: Ubuntu Bionic Beaver (development branch)
Machine: Device: desktop Mobo: ASUSTeK model: PRIME B350M-A v: Rev X.0x serial: 171013093801837
UEFI: American Megatrends v: 3803 date: 01/22/2018
CPU: Quad core AMD Ryzen 5 2400G with Radeon Vega Graphics (-MT-MCP-)
cache: 2048 KB
clock speeds: max: 3600 MHz 1: 1496 MHz 2: 1455 MHz 3: 1479 MHz
4: 1572 MHz 5: 1506 MHz 6: 1510 MHz 7: 1559 MHz 8: 1440 MHz
Graphics: Card: Advanced Micro Devices [AMD/ATI] Vega [Radeon Vega 8 Mobile]
Display Server: X.Org 1.19.6 driver: amdgpu
OpenGL: renderer: AMD RAVEN (DRM 3.23.0 / 4.15.0-12-generic, LLVM 5.0.1)
version: 4.5 Mesa 18.0.0-rc4
Audio: Card-1 Advanced Micro Devices [AMD] Device 15e3
driver: snd_hda_intel
Card-2 Advanced Micro Devices [AMD/ATI] Device 15de
driver: snd_hda_intel
Sound: Advanced Linux Sound Architecture v: k4.15.0-12-generic
Network: Card-1: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
driver: r8169
IF: enp6s0 state: down mac: 2c:fd:a1:70:87:aa
Card-2: Atheros AR9271 802.11n
IF: N/A state: N/A mac: N/A
Drives: HDD Total Size: 240.1GB (2.8% used)
ID-1: /dev/sda model: SPCC_Solid_State size: 240.1GB
Partition: ID-1: / size: 112G used: 6.3G (6%) fs: ext4 dev: /dev/sda5
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: N/A mobo: N/A gpu: 0.0
Fan Speeds (in rpm): cpu: 0
Info: Processes: 252 Uptime: 9 min Memory: 1433.2/15024.2MB
Client: Shell (sudo) inxi: 2.3.56
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: plymouth 0.9.3-1ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sat Mar 17 19:50:16 2018
DefaultPlymouth: /usr/share/
ExecutablePath: /sbin/plymouthd
InstallationDate: Installed on 2018-03-17 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180316)
MachineType: System manufacturer System Product Name
ProcCmdLine: BOOT_IMAGE=
ProcCmdline: @sbin/plymouthd --mode=boot --pid-file=
ProcEnviron:
LANG=pl_PL.UTF-8
PATH=(custom, no user)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x7fa01771d480 <script_
PC (0x7fa01771d480) ok
source "$0x1" ok
destination "(%rdi)" (0x00000040) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: plymouth
StacktraceTop:
script_
script_
script_
script_
?? () from /usr/lib/
TextPlymouth: /usr/share/
Title: plymouthd crashed with SIGSEGV in script_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 01/22/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3803
dmi.board.
dmi.board.name: PRIME B350M-A
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1745406, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.