From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tim Connors <tconnors@astro.swin.edu.au>,
kernel list <linux-kernel@vger.kernel.org>,
linux-wireless@vger.kernel.org
Subject: Re: iwl4965 dropping packets and __dev_addr_discard: address leakage! da_users=1
Date: Tue, 26 Feb 2008 09:33:18 +0100 [thread overview]
Message-ID: <1204014798.13162.209.camel@johannes.berg> (raw)
In-Reply-To: <20080225223823.db13a7fe.akpm@linux-foundation.org> (sfid-20080226_063910_557503_849EE5CE)
[-- Attachment #1: Type: text/plain, Size: 857 bytes --]
> > Possibly because of the frequent renegotiating my iwl4965 card has
> > been making, it has now decided it's not going to pass packets
> > reliably until presumably next time I reboot.
Can't say anything about that.
> > I've noticed messages in syslog that I hadn't seen when things were
> > working fine. The problem possibly has only surfaced after rmmodding
> > the iwl4965 module, then remodding it. It stays with me through being
> > removed and modprobed again. It is being bonded in conjunction with a
> > physical ethernet, if that is relevant, although I think I reproduced
> > it when it was on its lonesome.
> > Feb 23 03:05:23 dirac kernel: __dev_addr_discard: address leakage! da_users=1
I've seen that before on other hardware but so far haven't managed to
track it down or even reliably reproduce it.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2008-02-26 8:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <slrn-0.9.7.4-5027-27940-200802261551-tc@hexane.ssi.swin.edu.au>
2008-02-26 6:38 ` iwl4965 dropping packets and __dev_addr_discard: address leakage! da_users=1 Andrew Morton
2008-02-26 6:47 ` Tim Connors
2008-02-27 6:14 ` Chatre, Reinette
2008-02-26 8:33 ` Johannes Berg [this message]
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=1204014798.13162.209.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=tconnors@astro.swin.edu.au \
/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