From: Ben Hutchings <ben@decadent.org.uk>
To: Reinhard Karcher <reinhard.karcher@gmx.net>, 664064@bugs.debian.org
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Bug#664064: linux-image-3.3.0-rc6-amd64: 4 messages every minute in syslog from netlink
Date: Thu, 15 Mar 2012 17:14:13 +0000 [thread overview]
Message-ID: <1331831653.3022.228.camel@deadeye> (raw)
In-Reply-To: <20120315120008.14655.64028.reportbug@apollon>
[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]
On Thu, 2012-03-15 at 13:00 +0100, Reinhard Karcher wrote:
> Package: linux-2.6
> Version: 3.3~rc6-1~experimental.1
> Severity: normal
>
> The kernel log says all!
> I have 2 laptops showing the messages, both amd64.
> One of them runs a 32-bit system in a VM with the linux-image-3.3.0-rc6-686-pae kernel,
> that does not have this problem.
> The amd64 kernel from unstable (3.2.0-2) does not show the messages.
>
> Reinhard
>
> -- Package-specific info:
> ** Version:
> Linux version 3.3.0-rc6-amd64 (Debian 3.3~rc6-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 20:53:11 UTC 2012
>
> ** Command line:
> BOOT_IMAGE=/boot/vmlinuz-3.3.0-rc6-amd64 root=UUID=9bb56ba6-3117-47d6-b07c-2cca477643e9 ro quiet cgroup_enable=memory
>
> ** Not tainted
>
> ** Kernel log:
> [46368.760279] netlink: 140 bytes leftover after parsing attributes.
[...]
The code that generates this warning (nla_parse()) has not changed
between 3.2 and 3.3-rc6, so this is probably due to a difference
elsewhere. It seems to indicate a bug in the userland program sending
the message that is being parsed, but perhaps I misunderstand.
It would be useful if we could tell which program is sending the
message, but I think that may be difficult to do.
Ben.
--
Ben Hutchings
Life would be so much easier if we could look at the source code.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next parent reply other threads:[~2012-03-15 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120315120008.14655.64028.reportbug@apollon>
2012-03-15 17:14 ` Ben Hutchings [this message]
2012-03-16 8:53 ` Bug#664064: linux-image-3.3.0-rc6-amd64: 4 messages every minute in syslog from netlink Reinhard Karcher
[not found] ` <4F622E92.9010007@gmx.net>
2012-03-18 3:15 ` Ben Hutchings
2012-03-18 10:59 ` Reinhard Karcher
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=1331831653.3022.228.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=664064@bugs.debian.org \
--cc=netdev@vger.kernel.org \
--cc=reinhard.karcher@gmx.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.