FS#29317 - cupsd: Signal 4 (Illegal instruction) at start on VIA-C3 Nehemiah

Attached to Project: Arch Linux
Opened by Thomas Trepl (ernibert) - Saturday, 07 April 2012, 07:20 GMT
Last edited by Andreas Radke (AndyRTR) - Saturday, 07 April 2012, 16:12 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Andreas Radke (AndyRTR)
Allan McRae (Allan)
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: I've a VIA-C3 (Mehemia) CPU. So far everything ok, but CUPS does not start:

[root@io ArchLinux]# rc.d start cupsd
:: Starting cupsd daemon [BUSY]
cupsd: Child exited on signal 4 [FAIL]

Here Info about the CPU:
[root@io ArchLinux]# cat /proc/cpuinfo
processor : 0
vendor_id : CentaurHauls
cpu family : 6
model : 9
model name : VIA Nehemiah
stepping : 8
cpu MHz : 800.071
cache size : 64 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr cx8 sep mtrr pge cmov pat mmx fxsr sse up rng rng_en ace ace_en
bogomips : 1600.81
clflush size : 32
cache_alignment : 32
address sizes : 32 bits physical, 32 bits virtual
power management:


Additional info:
* package version(s)
CUPS is 1.5.2-1
* config and/or log files etc.

In the build instructions, there is a "--with-optim=$CFLAGS". Could that be probably the reason?


Steps to reproduce: (Use a VIA-C3 ?)
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Saturday, 07 April 2012, 16:12 GMT
Reason for closing:  None
Comment by Andreas Radke (AndyRTR) - Saturday, 07 April 2012, 07:48 GMT
Can you please try if rebuilding the package with new toolchain fixes it? If not please provide a gdb backtrace with disassemble output.
Comment by Thomas Trepl (ernibert) - Saturday, 07 April 2012, 16:04 GMT
Hi Andreas,

well, in the meanwhile I did a last upgrade (with this I got a new kernel and a new gnutls). Now it starts fine. I really don't know how that all should have to with each other. It's strange. Maybe it hasn't to do with the last update and it was the reboot... I don't know.

Seems so that this "bug" could be closed or at least lowered in severity. Sorry for the noise.
--
Thomas

Loading...