netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 92121] New: acpid cannot connect to netlink socket (bisected)
Date: Tue, 27 Jan 2015 12:00:52 +0000	[thread overview]
Message-ID: <20150127120052.2d3f2a20@uryu.home.lan> (raw)



Begin forwarded message:

Date: Mon, 26 Jan 2015 14:15:55 -0800
From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
To: "stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: [Bug 92121] New: acpid cannot connect to netlink socket (bisected)


https://bugzilla.kernel.org/show_bug.cgi?id=92121

            Bug ID: 92121
           Summary: acpid cannot connect to netlink socket (bisected)
           Product: Networking
           Version: 2.5
    Kernel Version: 3.19.0-rc6
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Other
          Assignee: shemminger@linux-foundation.org
          Reporter: ziegler@uni-freiburg.de
        Regression: Yes

acpid ouputs the following:

  Cannot bind netlink socket: No such file or directory
  acpid: cannot open generic netlink socket
  acpid: starting up with netlink and the input layer

The commit responsible for that is

  5ad6300524c0332ac67e912c20d6e5cf262ba58f

  genetlink: disallow subscribing to unknown mcast group

Reverting lets the bug vanish

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2015-01-27 12:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150127120052.2d3f2a20@uryu.home.lan \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).