Process got signal 8 - Revision history

Jord: removing broken link to original faq

2017-08-16T20:54:57Z

removing broken link to original faq

Jord: Undo revision 2660 by Jord (talk)

2017-08-16T20:54:24Z

Undo revision 2660 by Jord (talk)

Jord: removing box

2017-08-16T20:53:51Z

removing box

Jord: Jord moved page Signal 8 / Error 38 / Linux to Process got signal 8: moving to new title to bring in line with the rest

2016-09-01T21:35:08Z

Jord moved page Signal 8 / Error 38 / Linux to Process got signal 8: moving to new title to bring in line with the rest

Jord: adding table

2016-08-29T22:25:44Z

adding table

Jord: Adding FAQ 377

2016-05-21T21:53:42Z

Adding FAQ 377

New page

When you're running into constant signal 8 / error 38 problems with a project and your operating system is Linux with a Kernel version of between 2.6.20 and 2.6.27, then read on.

The problem is that the Kernel is compiled with CONFIG_PREEMPT=Y while it should be =N
The CONFIG_PREEMPT option preempts any running task in memory, by permitting a low priority process to be preempted involuntarily even if it is in kernel mode executing a system call and would otherwise not be about to reach a natural preemption point. This wrecks the FPU stack, which in return gives you a signal 8 error outcome.

To check what the status of CONFIG_PREEMPT is in your Kernel, check the .config file in the /usr/src/linux directory, or similar directory, so do:
grep PREEMPT /usr/src/linux/.config

Or using /proc/config.gz do:
cat /proc/config.gz | gunzip - | grep PREEMPT

You'll get a list of PREEMPT options, the ones that your Kernel can do and which ones are set.
You'll have to make sure that CONFIG_PREEMPT isn't set to Yes, but preferably that PREEMPT_VOLUNTARY is set.

You can do this by recompiling your kernel. The how and what on that depends on your distro and your skill to roam around in Linux.

There are also runtime /proc/sys knobs and boot-time flags to turn voluntary preemption (CONFIG_VOLUNTARY_PREEMPT) and kernel preemption (CONFIG_PREEMPT) on/off:

# turn on/off voluntary preemption (if CONFIG_VOLUNTARY_PREEMPT)
echo 1 > /proc/sys/kernel/voluntary_preemption
echo 0 > /proc/sys/kernel/voluntary_preemption

# turn on/off the preemptible kernel feature (if CONFIG_PREEMPT)
/proc/sys/kernel/kernel_preemption
/proc/sys/kernel/kernel_preemption

The 'voluntary-preemption=0/1' and 'kernel-preemption=0/1' boot options can be used to control these flags at boot-time.

Not all distros allow for the latter use of startup flags, though.

For more information on this bug in Linux, please read this thread at Einstein for the whole discussion that led to this discovery.

PREEMPT options and what they do:

PREEMPT_NONE â€” No forced preemption (server)

This is the traditional Linux preemption model, geared toward maximizing throughput. It still provides good latency most of the time, occasional longer delays are possible.

Select this option if you are building a kernel for a server or scientific/computation system, or if you want to maximize the raw processing power of the kernel, irrespective of scheduling latencies.

PREEMPT_VOLUNTARY â€” Voluntary kernel preemption (desktop)

This option reduces the latency of the kernel by adding more "explicit preemption points" to the kernel code. These new preemption points have been selected to reduce the maximum latency of rescheduling, which provides faster response to applications at the cost of slighly lower throughput.

This option speeds up reaction to interactive events by allowing a low-priority process to voluntarily preempt itself even if it is in kernel mode executing a system call. This allows applications to appear to run more smoothly even when the system is under load.

Select this if you are building a kernel for a desktop system.

PREEMPT â€” Preemptible kernel (low-latency desktop)

This option reduces the latency of the kernel by making all kernel code (except code executing in a critical section) preemptible. This allows reaction to interactive events by permitting a low priority process to be preempted involuntarily even if it is in kernel mode executing a system call and would otherwise not be about to reach a natural preemption point. This allows applications to appear to run more smoothly even when the system is under load, at the cost of slightly lower throughput and a slight runtime overhead to kernel code.

Select this if you are building a kernel for a desktop or embedded system with latency requirements in the milliseconds range.

Fix
Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.
| Jorden
| 5
| 1
| 16:30:05
| 2008-06-06
| 91410
| 1
| 377
| 2008-06-06 16:30:05
| 2008-08-14 14:37:06

@@ Line 56: / Line 56: @@
   |-
   | Jorden
-  | [http://boincfaq.mundayweb.com/index.php?language=1&view=377 377]
+  | 377
   | 06-06-2008
   |-
   |}

← Older revision		Revision as of 20:54, 16 August 2017
Line 47:		Line 47:

	;Fix<br>		;Fix<br>
−	Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.	+	Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.
		+
		+
		+	{\| class="wikitable" style="text-align: center;"
		+	! Original writer
		+	! Original FAQ
		+	! Date
		+	\|-
		+	\| Jorden
		+	\| [http://boincfaq.mundayweb.com/index.php?language=1&view=377 377]
		+	\| 06-06-2008
		+	\|-
		+	\|}

← Older revision		Revision as of 20:53, 16 August 2017
Line 47:		Line 47:

	;Fix<br>		;Fix<br>
−	Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.	+	Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.
−
−
−	~~{\| class="wikitable" style="text-align: center;"~~
−	~~! Original writer~~
−	~~! Original FAQ~~
−	~~! Date~~
−	\|-
−	~~\| Jorden~~
−	~~\| [http://boincfaq.mundayweb.com/index.php?language=1&view=377 377]~~
−	~~\| 06-06-2008~~
−	\|-
−	\|}

← Older revision	Revision as of 21:35, 1 September 2016
(No difference)

@@ Line 1: / Line 1: @@
 When you're running into constant signal 8 / error 38 problems with a project and your operating system is Linux with a Kernel version of between 2.6.20 and 2.6.27, then read on.
-The problem is that the Kernel is compiled with CONFIG_PREEMPT=Y while it should be =N
+The problem is that the Kernel is compiled with CONFIG_PREEMPT=Y while it should be =N<br>
 The CONFIG_PREEMPT option preempts any running task in memory, by permitting a low priority process to be preempted involuntarily even if it is in kernel mode executing a system call and would otherwise not be about to reach a natural preemption point. This wrecks the FPU stack, which in return gives you a signal 8 error outcome.
@@ Line 7: / Line 7: @@
 grep PREEMPT /usr/src/linux/.config
-Or using /proc/config.gz do:
+Or using /proc/config.gz do:<br>
-cat /proc/config.gz | gunzip - | grep PREEMPT
+ cat /proc/config.gz | gunzip - | grep PREEMPT
 You can do this by recompiling your kernel. The how and what on that depends on your distro and your skill to roam around in Linux.
 There are also runtime /proc/sys knobs and boot-time flags to turn voluntary preemption (CONFIG_VOLUNTARY_PREEMPT) and kernel preemption (CONFIG_PREEMPT) on/off:
-# turn on/off voluntary preemption (if CONFIG_VOLUNTARY_PREEMPT)
+ # turn on/off voluntary preemption (if CONFIG_VOLUNTARY_PREEMPT)
-echo 1 &gt; /proc/sys/kernel/voluntary_preemption
+ echo 1 &gt; /proc/sys/kernel/voluntary_preemption
-echo 0 &gt; /proc/sys/kernel/voluntary_preemption
+ echo 0 &gt; /proc/sys/kernel/voluntary_preemption
-# turn on/off the preemptible kernel feature (if CONFIG_PREEMPT)
+ # turn on/off the preemptible kernel feature (if CONFIG_PREEMPT)
-/proc/sys/kernel/kernel_preemption
+ /proc/sys/kernel/kernel_preemption
-/proc/sys/kernel/kernel_preemption
+ /proc/sys/kernel/kernel_preemption
 The 'voluntary-preemption=0/1' and 'kernel-preemption=0/1' boot options can be used to control these flags at boot-time.
@@ Line 29: / Line 28: @@
 Not all distros allow for the latter use of startup flags, though.
-For more information on this bug in Linux, please read this thread at Einstein for the whole discussion that led to this discovery.
+PREEMPT options and what they do:<br>
-PREEMPT options and what they do:
+:Select this option if you are building a kernel for a server or scientific/computation system, or if you want to maximize the raw processing power of the kernel, irrespective of scheduling latencies.
-PREEMPT_NONE â€” No forced preemption (server)
+:PREEMPT_VOLUNTARY Voluntary kernel preemption (desktop)
-This is the traditional Linux preemption model, geared toward maximizing throughput. It still provides good latency most of the time, occasional longer delays are possible.
+:This option speeds up reaction to interactive events by allowing a low-priority process to voluntarily preempt itself even if it is in kernel mode executing a system call. This allows applications to appear to run more smoothly even when the system is under load.
-Select this option if you are building a kernel for a server or scientific/computation system, or if you want to maximize the raw processing power of the kernel, irrespective of scheduling latencies.
+:Select this if you are building a kernel for a desktop system.
-PREEMPT_VOLUNTARY â€” Voluntary kernel preemption (desktop)
+:PREEMPT Preemptible kernel (low-latency desktop)
-This option reduces the latency of the kernel by adding more &quot;explicit preemption points&quot; to the kernel code. These new preemption points have been selected to reduce the maximum latency of rescheduling, which provides faster response to applications at the cost of slighly lower throughput.
+:Select this if you are building a kernel for a desktop or embedded system with latency requirements in the milliseconds range.
-This option speeds up reaction to interactive events by allowing a low-priority process to voluntarily preempt itself even if it is in kernel mode executing a system call. This allows applications to appear to run more smoothly even when the system is under load.
+;Fix<br>
+Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.
-Select this if you are building a kernel for a desktop or embedded system with latency requirements in the milliseconds range.
+{| class="wikitable" style="text-align: center;"
+ ! Original writer
-Fix
+ ! Original FAQ
-Recently this bug was fixed in the Kernel. You will need a kernel of 2.6.25.6 or higher for this fix.
+ ! Date
   | Jorden
-  | 5
+  | [http://boincfaq.mundayweb.com/index.php?language=1&view=377 377]
- | 1
+  | 06-06-2008
-  | 16:30:05
+  |-
- | 2008-06-06
+  |}