You are not logged in.

#1 2014-10-25 11:44:10

Dabbeljoe
Member
Registered: 2014-10-25
Posts: 2

Python2 upgrade broke my system (?)

Hi all,

After my weekly upgrade this morning, my system won't start correctly anymore. It seems to come a long way, but X never starts, and remote SSH doesn't work either. That makes it a bit hard to dump the error logs, but most notably I see:

NMI Watchdog: BUG: soft lockup - CPU#3 stuck for 22s [python2:273]
CPU: 3 PID: 273 Comm: python2 Tainted: G  D W  L 3.17.1-1-ARCH

Which keeps coming back every few seconds for each CPU, along with a lot of other information. (I've made a picture)

The system doesn't seem to be completely stuck however. After pressing the power button it succeeds in closing down various services every few minutes.

Any ideas what to do?

Offline

#2 2014-10-26 11:02:23

Dabbeljoe
Member
Registered: 2014-10-25
Posts: 2

Re: Python2 upgrade broke my system (?)

I got a bit further today. At least I got it running again by downgrading, so I'm able to post a bit more information.

I booted into the system using a live USB stick, and first tried downgrading the Python2 packages:

[2014-10-26 11:14] [PACMAN] Running 'pacman -U python2-cryptography-0.6-1-x86_64.pkg.tar.xz'
[2014-10-26 11:14] [PACMAN] downgraded python2-cryptography (0.6.1-1 -> 0.6-1)
[2014-10-26 11:15] [PACMAN] Running 'pacman -U python2-setuptools-1:6.0.2-1-any.pkg.tar.xz'
[2014-10-26 11:15] [PACMAN] downgraded python2-setuptools (1:7.0-1 -> 1:6.0.2-1)
[2014-10-26 11:15] [PACMAN] Running 'pacman -U python2-markdown-2.5-1-any.pkg.tar.xz'
[2014-10-26 11:16] [PACMAN] downgraded python2-markdown (2.5.1-1 -> 2.5-1)
[2014-10-26 11:16] [PACMAN] Running 'pacman -U python2-pillow-2.5.3-2-x86_64.pkg.tar.xz'
[2014-10-26 11:16] [PACMAN] downgraded python2-pillow (2.6.1-1 -> 2.5.3-2)

This allowed me to boot to the commandline (emergency mode), but there were still a lot of errors in the journal, and no X of course. So next I downgraded the Kernel:

[2014-10-26 11:30] [PACMAN] Running 'pacman -U linux-firmware-20140828.13eb208-1-any.pkg.tar.xz linux-3.16.3-1-x86_64.pkg.tar.xz linux-api-headers-3.16.2-1-x86_64.pkg.tar.xz'
[2014-10-26 11:30] [PACMAN] downgraded linux-firmware (20141009.0e5f637-1 -> 20140828.13eb208-1)
[2014-10-26 11:31] [ALPM-SCRIPTLET] >>> Updating module dependencies. Please wait ...
[2014-10-26 11:31] [ALPM-SCRIPTLET] >>> Generating initial ramdisk, using mkinitcpio.  Please wait...
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Starting build: 3.16.3-1-ARCH
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [autodetect]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Starting build: 3.16.3-1-ARCH
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [base]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [udev]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [modconf]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [block]
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: aic94xx
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> WARNING: Possibly missing firmware for module: smsmdtv
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [filesystems]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [keyboard]
[2014-10-26 11:31] [ALPM-SCRIPTLET]   -> Running build hook: [fsck]
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Generating module dependencies
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
[2014-10-26 11:31] [ALPM-SCRIPTLET] ==> Image generation successful
[2014-10-26 11:31] [PACMAN] downgraded linux (3.17.1-1 -> 3.16.3-1)
[2014-10-26 11:31] [PACMAN] reinstalled linux-api-headers (3.16.2-1)

Now everything seems to be working again, but I'd still like to do the upgrade sometime. I've pasted the journalctl of the last failed boot here: http://pastebin.de/152709 (with --priority=4 -thought that would be allright). Hope someone can point me in the right direction.

Offline

Board footer

Powered by FluxBB