FS#29905 - Pacman segfaulting when trying to update system

Attached to Project: Pacman
Opened by tardo (tardo) - Wednesday, 16 May 2012, 01:49 GMT
Last edited by Allan McRae (Allan) - Saturday, 04 August 2012, 09:28 GMT
Task Type Bug Report
Category General
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version 4.0.3
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Summary and Info:
Trying to upgrade my system (mythtv is failing). I tend not to update for long periods so I have lots of packages.
Anyways, pacman is segfaulting when loading files or something...

[root@tigerbot shez]# pacman -V

.--. Pacman v4.0.3 - libalpm v7.0.3
/ _.-' .-. .-. .-. Copyright (C) 2006-2012 Pacman Development Team
\ '-. '-' '-' '-' Copyright (C) 2002-2006 Judd Vinet
'--'
This program may be freely redistributed under
the terms of the GNU General Public License.

[root@tigerbot shez]# uname -a
Linux tigerbot 3.0-ARCH #1 SMP PREEMPT Tue Aug 16 07:25:56 UTC 2011 i686 Intel(R) Core(TM) CPU 230 @ 1.60GHz GenuineIntel GNU/Linux
[root@tigerbot shez]#


Steps to Reproduce:
pacman --debug -Sfu
Probably happens on my system only.
   pacman segfault.txt (714 KiB)
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 04 August 2012, 09:28 GMT
Reason for closing:  Not a bug
Additional comments about closing:  Reported decided it was a glibc issue in the linked forum thread. So not a pacman bug.
Comment by tardo (tardo) - Wednesday, 16 May 2012, 01:52 GMT
Don't know if this helps, but I get this too:

[root@tigerbot shez]# pacman -S xz
resolving dependencies...
looking for inter-conflicts...

Targets (1): xz-5.0.3-2

Total Installed Size: 1.05 MiB
Net Upgrade Size: 0.02 MiB

Proceed with installation? [Y/n]
(1/1) checking package integrity [######################] 100%
(1/1) loading package files [######################] 100%
(1/1) checking for file conflicts [######################] 100%
warning: could not get filesystem information for devpts: No such file or directory
warning: could not get filesystem information for tmpfs: No such file or directory
(1/1) checking available disk space [######################] 100%
(1/1) upgrading xz [######################] 100%
[root@tigerbot shez]#

[root@tigerbot shez]# mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=127214,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=journal)
/dev/pts on devpts type rw,relatime,mode=600,ptmxmode=000 (rw)
/dev/shm on tmpfs type rw,relatime (rw)
none on /dev/shm type tmpfs (rw)
/dev/sda2 on /var type xfs (rw)
/dev/sda4 on /home type xfs (rw)
none on /proc/bus/usb type usbfs (rw,busgid=108,busmode=0775,devgid=108,devmode=0664)
[root@tigerbot shez]#
Comment by Dave Reisner (falconindy) - Wednesday, 16 May 2012, 01:59 GMT
SIGILL is very much NOT a SIGSEGV. It indicates that there's an instruction compiled into pacman or libalpm that your processor isn't capable of executing.

Your mount output also is incredibly strange -- devpts (/dev/pts) and tmpfs (/dev/shm) literally have their source and target reversed. I'm sure this is unrelated, but you've done something horrible here...
Comment by tardo (tardo) - Wednesday, 16 May 2012, 02:48 GMT
I don't think I got a SIGSEGV, unless pacman caught it. I did see a "error: segfaulting" or something similar when I didn't use the --debug switch.

Anyway, I thought that perhaps something was screwy with my system so I tried freeing up memory, rebooting, fixing fstab. My mountpoints look like this now:

[shez@tigerbot ~]$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=10240k,nr_inodes=127214,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=10240k,mode=755)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=journal)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
/dev/shm on tmpfs type rw,relatime (rw)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev)
/dev/sda2 on /var type xfs (rw)
/dev/sda4 on /home type xfs (rw)

Still no dice. I still get the illegal instruction.
I have a first generation Intel Atom processor if that helps...
My fstab:

tmpfs /tmp tmpfs nodev,nosuid 0 0
/dev/sda1 / ext3 defaults 0 0
/dev/sda2 /var xfs defaults 0 0
/dev/sda3 swap swap defaults 0 0
/dev/sda4 /home xfs defaults 0 0

More info:
[root@tigerbot shez]# pacman -Q initscripts
initscripts 2011.07.3-1
Comment by tardo (tardo) - Monday, 21 May 2012, 03:34 GMT
Forum thread here:
https://bbs.archlinux.org/viewtopic.php?id=141896

Loading...