Arch Linux

doragasu

Member

Registered: 2012-03-03

Posts: 160

[SOLVED] Segfaults everywhere!

Lately I have been experiencing random segfaults on several applications. Mainly in browsers (Firefox, Chromium, even qutebrowser), but also on other programs (e.g. Cups Thunderbird and gcc). The programs start but randomly segfault. Sometimes it may take hours for them to crash, other times it takes seconds.

I'm clueless about how to debug this problem. I have tried starting these apps from terminal to see if there is some useful output but there isnt. I have also examined backtrace of coredumps but I don't know how to extract useful information from them. The only clue I found is cupsd writes a kernel message when segfaulting: "cupsd[409]: segfault at 7f942c634ca0 ip 00007f942c634ca0 sp 00007ffc5711c258 error 14 in libnss_files-2.22.so[7f94683ff000+b000]"

Some backtraces. From cupsd:

#0  0x00007f942c634ca0 in ?? ()
#1  0x00007f946c65c28e in ippOpString () from /usr/lib/libcups.so.2
#2  0x000055b00511af24 in ?? ()
#3  0x000055b005103c54 in ?? ()
#4  0x000055b005106aeb in ?? ()
#5  0x000055b0050f5745 in ?? ()
#6  0x00007f946be2c610 in __libc_start_main () from /usr/lib/libc.so.6
#7  0x000055b0050f6839 in ?? ()

Backtrace from qutebrowser:

#0  0x00007f544fc6b2c0 in ?? () from /usr/lib/libQt5WebKit.so.5
#1  0x00007f544fcbc4f1 in ?? () from /usr/lib/libQt5WebKit.so.5
#2  0x00007f544fcbc862 in ?? () from /usr/lib/libQt5WebKit.so.5
#3  0x00007f544fcaa8f5 in ?? () from /usr/lib/libQt5WebKit.so.5
#4  0x00007f544fcaf311 in ?? () from /usr/lib/libQt5WebKit.so.5
#5  0x00007f544fed81da in ?? () from /usr/lib/libQt5WebKit.so.5
#6  0x00007f544fcb239f in ?? () from /usr/lib/libQt5WebKit.so.5
#7  0x00007f54597a2193 in QObject::event(QEvent*) () from /usr/lib/libQt5Core.so.5
#8  0x00007f5454dc49ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#9  0x00007f5454dc9e86 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQt5Widgets.so.5
#10 0x00007f54556d509e in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#11 0x00007f5459772bab in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#12 0x00007f54597c836d in QTimerInfoList::activateTimers() () from /usr/lib/libQt5Core.so.5
#13 0x00007f54597c8871 in ?? () from /usr/lib/libQt5Core.so.5
#14 0x00007f545ac3ddc7 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#15 0x00007f545ac3e020 in ?? () from /usr/lib/libglib-2.0.so.0
#16 0x00007f545ac3e0cc in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#17 0x00007f54597c954f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#18 0x00007f545977057a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#19 0x00007f545977853c in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#20 0x00007f54556d39db in ?? () from /usr/lib/python3.5/site-packages/PyQt5/QtWidgets.so
#21 0x00007f54616b4a89 in PyCFunction_Call () from /usr/lib/libpython3.5m.so.1.0
#22 0x00007f546172ca01 in PyEval_EvalFrameEx () from /usr/lib/libpython3.5m.so.1.0
#23 0x00007f546172cd52 in PyEval_EvalFrameEx () from /usr/lib/libpython3.5m.so.1.0
#24 0x00007f546172cd52 in PyEval_EvalFrameEx () from /usr/lib/libpython3.5m.so.1.0
#25 0x00007f546172cd52 in PyEval_EvalFrameEx () from /usr/lib/libpython3.5m.so.1.0
#26 0x00007f546172ddf2 in ?? () from /usr/lib/libpython3.5m.so.1.0
#27 0x00007f546172ded3 in PyEval_EvalCodeEx () from /usr/lib/libpython3.5m.so.1.0
#28 0x00007f546172defb in PyEval_EvalCode () from /usr/lib/libpython3.5m.so.1.0
#29 0x00007f546174d074 in ?? () from /usr/lib/libpython3.5m.so.1.0
#30 0x00007f546174f585 in PyRun_FileExFlags () from /usr/lib/libpython3.5m.so.1.0
#31 0x00007f546174f6f6 in PyRun_SimpleFileExFlags () from /usr/lib/libpython3.5m.so.1.0
#32 0x00007f5461766504 in Py_Main () from /usr/lib/libpython3.5m.so.1.0
#33 0x0000000000400af7 in main ()

What might be causing these nasty segfaults?

Last edited by doragasu (2016-02-15 10:05:25)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,435

Re: [SOLVED] Segfaults everywhere!

If you have an Intel processor that isn't Skylake, did you do the Microcode update yet?

If that wasn't it, some more info on your hardware and general setup would be nice

lspci -k
journalctl -b

should already help

Last edited by V1del (2016-02-10 13:42:31)

hmh

Member

Registered: 2015-10-08

Posts: 13

Re: [SOLVED] Segfaults everywhere!

Lately I have been experiencing random segfaults on several applications.

...

What might be causing these nasty segfaults?

Contents of /proc/cpuinfo, please...

Also, test your memory (e.g. using memtest86), and disable any kind of data-destructive behavior like: overclocking, underclocking, overvolting, undervolting, etc.

doragasu

Member

Registered: 2012-03-03

Posts: 160

Re: [SOLVED] Segfaults everywhere!

Thanks for the tips. Contents of /proc/cpuinfo (an old Core2 Duo CPU):

processor	: 0
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz
stepping	: 6
microcode	: 0xd0
cpu MHz		: 1600.000
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 0
cpu cores	: 2
apicid		: 0
initial apicid	: 0
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow
bugs		:
bogomips	: 3725.04
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

processor	: 1
vendor_id	: GenuineIntel
cpu family	: 6
model		: 15
model name	: Intel(R) Core(TM)2 CPU          6320  @ 1.86GHz
stepping	: 6
microcode	: 0xd0
cpu MHz		: 1600.000
cache size	: 4096 KB
physical id	: 0
siblings	: 2
core id		: 1
cpu cores	: 2
apicid		: 1
initial apicid	: 1
fpu		: yes
fpu_exception	: yes
cpuid level	: 10
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm tpr_shadow
bugs		:
bogomips	: 3725.04
clflush size	: 64
cache_alignment	: 64
address sizes	: 36 bits physical, 48 bits virtual
power management:

lspci -k

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
	Subsystem: Gigabyte Technology Co., Ltd Device 5000
	Kernel modules: intel_agp
00:01.0 PCI bridge: Intel Corporation 82945G/GZ/P/PL PCI Express Root Port (rev 02)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD (Realtek ALC887)
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)
	Kernel driver in use: pcieport
	Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD
	Kernel driver in use: uhci_hcd
	Kernel modules: uhci_hcd
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-D525TUD
	Kernel driver in use: ehci-pci
	Kernel modules: ehci_pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Device 5001
	Kernel driver in use: lpc_ich
	Kernel modules: intel_rng, lpc_ich, leds_ss4200
00:1f.2 IDE interface: Intel Corporation NM10/ICH7 Family SATA Controller [IDE mode] (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Device b002
	Kernel driver in use: ata_piix
	Kernel modules: ata_piix, pata_acpi, ata_generic
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd GA-8I945PG-RH/GA-D525TUD Mainboard
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 Series]
	Subsystem: Gigabyte Technology Co., Ltd Device 21e2
	Kernel driver in use: radeon
	Kernel modules: radeon
01:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cedar HDMI Audio [Radeon HD 5400/6300 Series]
	Subsystem: Gigabyte Technology Co., Ltd Device aa68
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 01)
	Subsystem: Gigabyte Technology Co., Ltd Motherboard
	Kernel driver in use: r8169
	Kernel modules: r8169

journalctl -b (I cut it a bit at the end, mainly URLs being ad-blocked and that kind of stuff).

I did the microcode update some months ago, and I have no "data-destructive thingies" enabled (no overclocking/undervolting, latest default kernel, etc.).

I'll try the memtest86 suggestion and report.

doragasu

Member

Registered: 2012-03-03

Posts: 160

Re: [SOLVED] Segfaults everywhere!

Tried memtest, and it spits error like crazy!

Problem solved, thanks for the tips!