From: Knut Petersen <Knut_Petersen@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: Assert: CPU #..., mangle/filter comefrom(....) = ...
Date: Thu, 09 Feb 2006 06:10:49 +0100 [thread overview]
Message-ID: <43EACED9.2030405@t-online.de> (raw)
As there probably is a reason to printk assertions:
[ 28.616455] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 28.617112] ASSERT: CPU #0, mangle comefrom(f75ae890) = 1
[ 28.617115] ASSERT: CPU #0, filter comefrom(f79ca090) = 2
[ 28.934256] ASSERT: CPU #0, mangle comefrom(f7051890) = 1
[ 28.934260] ASSERT: CPU #0, filter comefrom(f7aa9090) = 2
[ 32.766440] ASSERT: CPU #0, mangle comefrom(f709c090) = 1
[ 32.766443] ASSERT: CPU #0, filter comefrom(f71f3090) = 2
cu,
Knut
reply other threads:[~2006-02-09 5:09 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=43EACED9.2030405@t-online.de \
--to=knut_petersen@t-online.de \
--cc=linux-kernel@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