[Pkg-systemd-maintainers] Bug#722070: systemd uses up 100% CPU (in a tight loop) on shutdown, and hangs

Debian BTS debbugs at buxtehude.debian.org
Sat Sep 7 13:51:06 BST 2013


kthxbyte
Reply-To: Paul Tagliamonte <leliel at pault.ag>, 722070 at bugs.debian.org
Resent-From: Paul Tagliamonte <leliel at pault.ag>
Resent-To: debian-bugs-dist at lists.debian.org
Resent-CC: Debian systemd Maintainers <pkg-systemd-maintainers at lists.alioth.debian.org>
X-Loop: owner at bugs.debian.org
Resent-Date: Sat, 07 Sep 2013 12:51:01 +0000
Resent-Message-ID: <handler.722070.B.137855796522707 at bugs.debian.org>
Resent-Sender: owner at bugs.debian.org
X-Debian-PR-Message: report 722070
X-Debian-PR-Package: systemd
X-Debian-PR-Keywords: 
X-Debian-PR-Source: systemd
Received: via spool by submit at bugs.debian.org id=B.137855796522707
          (code B); Sat, 07 Sep 2013 12:51:01 +0000
Received: (at submit) by bugs.debian.org; 7 Sep 2013 12:46:05 +0000
X-Spam-Checker-Version: SpamAssassin 3.3.2-bugs.debian.org_2005_01_02
	(2011-06-06) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-11.7 required=4.0 tests=BAYES_00,FOURLA,HAS_PACKAGE,
	RCVD_IN_DNSWL_LOW,XMAILER_REPORTBUG autolearn=ham
	version=3.3.2-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 43; hammy, 150; neutral, 142; spammy,
	1. spammytokens:1.000-2--blasting hammytokens:0.000-+--H*M:reportbug,
	0.000-+--H*MI:reportbug, 0.000-+--H*x:6.4.4, 0.000-+--H*UA:6.4.4,
	0.000-+--H*x:reportbug
Received: from mail-qc0-f180.google.com ([209.85.216.180])
	by buxtehude.debian.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:128)
	(Exim 4.80)
	(envelope-from <leliel at pault.ag>)
	id 1VIHtt-0005tU-Bn
	for submit at bugs.debian.org; Sat, 07 Sep 2013 12:46:05 +0000
Received: by mail-qc0-f180.google.com with SMTP id p19so2130034qcv.25
        for <submit at bugs.debian.org>; Sat, 07 Sep 2013 05:45:58 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:content-type:mime-version
         :content-transfer-encoding:from:to:subject:message-id:date;
        bh=3NWUY+4cBpbVnv3w4fSNRq70oAQWMKG4tX3S3N4gS+4=;
        b=VvW4hpugPW2N6lyARyakiRaGXSRVbmpLFk9TLgANMA5GFJqVa9hG4SQOtMFKK74vtd
         tzOgtnnUJz8kApHO0Ei5DpPJEe+MMuuiseF4PHnRWPg0n/l9ofK7yHV/5qx8q0ongNk+
         t9/QWaO10voKOw8GZrb0gKrSL3RuABfBLWGZsRhOMB49MeaIzpknTxJAj3wBgwd14Rtp
         rKWY+RbIWavyLJacyKSRUagoMsSg7pDGGM6wReSXStn7EBDMGOBkkfIVXr0vh9oXDyTf
         yh/2X7Q1xFUM9R4xJk8Ys0BaCEkwBoWvqni8IXWO/U0dbfgrKy/7MK+ljQMi0fH/UPCM
         26Xw==
X-Gm-Message-State: ALoCoQnZckUmzsqqvpJAnVRdkbzPGe6NYNZFjMDP5W26OzAfHwnfjhc9sCAHhS5UkV3+L99LInEa
X-Received: by 10.49.82.115 with SMTP id h19mr2936783qey.69.1378557958717;
        Sat, 07 Sep 2013 05:45:58 -0700 (PDT)
Received: from leliel ([2001:0:53aa:64c:2888:4d1f:bde0:340b])
        by mx.google.com with ESMTPSA id 10sm5101226qal.0.1969.12.31.16.00.00
        (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
        Sat, 07 Sep 2013 05:45:58 -0700 (PDT)
Received: by leliel (Postfix, from userid 1000)
	id 228B13644B6; Sat,  7 Sep 2013 08:57:46 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Paul Tagliamonte <leliel at pault.ag>
To: Debian Bug Tracking System <submit at bugs.debian.org>
Message-ID: <20130907125746.17414.76196.reportbug at leliel>
X-Mailer: reportbug 6.4.4
Date: Sat, 07 Sep 2013 08:57:46 -0400
Delivered-To: submit at bugs.debian.org

Package: systemd
Version: 44-12
Severity: normal
Control: found -1 204-2

When I shutdown my machine with the latest systemd in experimental (or
the one in unstable, when I ran it), the CPU enters a tight loop and
hangs.

I've left my machine up before (forgetting it does this), and come back
a few days later, machine still going, face-melting-lava-hot, and fans
blasting.

I've also seen kernel panics due to thermal conditions.

I'm sorta getting annoyed at suffocating my computer when I want to turn
it off, so it'd be really nice to fix this.

Thanks,
  Paul

P.S., the only time it shutdown correctly in recent history would be
      *after* the upgrade to experimental, on the *first* shutdown (but not
      the second).


-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.8-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages systemd depends on:
ii  initscripts          2.88dsf-41
ii  libacl1              2.2.52-1
ii  libaudit0            1:1.7.18-1.1
ii  libc6                2.17-92
ii  libcap2              1:2.22-1.2
ii  libcryptsetup4       2:1.6.1-1
ii  libdbus-1-3          1.6.12-1
ii  libgcrypt11          1.5.3-2
ii  libkmod2             9-3
ii  liblzma5             5.1.1alpha+20120614-2
ii  libpam0g             1.1.3-9
ii  libselinux1          2.1.13-2
ii  libsystemd-daemon0   44-12
ii  libsystemd-journal0  204-2
ii  libudev1             204-2
ii  libwrap0             7.6.q-24
ii  udev                 175-7.2
ii  util-linux           2.20.1-5.4

Versions of packages systemd recommends:
ii  libpam-systemd  204-2

Versions of packages systemd suggests:
pn  systemd-ui  <none>

-- no debconf information




More information about the Pkg-systemd-maintainers mailing list