All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reuben Farrelly <reuben-lkml@reub.net>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: 2.6.14-rc4-mm1
Date: Mon, 17 Oct 2005 19:19:31 +1300	[thread overview]
Message-ID: <43534273.2050106@reub.net> (raw)
In-Reply-To: <fa.h4unqgj.l34e31@ifi.uio.no>

Hi,

On 16/10/2005 10:42 p.m., Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.14-rc4/2.6.14-rc4-mm1/
> 
> - Lots of i2c, PCI and USB updates
> 
> - Large input layer update to convert it all to dynamic input_dev allocation
> 
> - Significant x86_64 updates
> 
> - MD updates
> 
> - Lots of core memory management scalability rework

Compiles and runs here, but noting these messages when ethernet link down:

Oct 17 18:49:40 tornado kernel: NEIGH: BUG, double timer add, state is 1
Oct 17 18:51:04 tornado last message repeated 3 times
Oct 17 18:52:05 tornado last message repeated 5 times
Oct 17 18:52:11 tornado last message repeated 2 times

net/core/neighbour.c has this:

static inline void neigh_add_timer(struct neighbour *n, unsigned long when)
{
         if (unlikely(mod_timer(&n->timer, when))) {
                 printk("NEIGH: BUG, double timer add, state is %x\n",
                        n->nud_state);
         }
}


Network guys?

reuben

       reply	other threads:[~2005-10-17  6:19 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.h4unqgj.l34e31@ifi.uio.no>
2005-10-17  6:19 ` Reuben Farrelly [this message]
2005-10-23  7:30   ` [0/3] Fix timer bugs in neighbour cache Herbert Xu
2005-10-23  7:31     ` [1/3] [NEIGH] Print stack trace in neigh_add_timer Herbert Xu
2005-10-23  7:32     ` [2/3] [NEIGH] Fix add_timer race " Herbert Xu
2005-10-23  7:33     ` [3/3] [NEIGH] Fix timer leak in neigh_changeaddr Herbert Xu
2005-10-23 18:00       ` Ben Greear
2005-10-23 16:16     ` [0/3] Fix timer bugs in neighbour cache Arnaldo Carvalho de Melo
     [not found] <20051006082231.GA21800@elte.hu>
     [not found] ` <20051010172631.59d98198.akpm@osdl.org>
2005-10-17  7:07   ` 2.6.14-rc4-mm1 WU Fengguang
2005-10-16 22:41 2.6.14-rc4-mm1 Andrew Morton
2005-10-17  0:13 ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17  3:19   ` 2.6.14-rc4-mm1 Andrew Morton
2005-10-17  6:03     ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17  6:42     ` 2.6.14-rc4-mm1 Michal Piotrowski
2005-10-17  7:47     ` 2.6.14-rc4-mm1 Russell King
2005-10-17  0:46 ` 2.6.14-rc4-mm1 Con Kolivas
2005-10-17  7:10 ` 2.6.14-rc4-mm1 MAEDA Naoaki
2005-10-17 12:21 ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-17 20:22   ` 2.6.14-rc4-mm1 Andrew Morton
2005-10-17 21:27     ` 2.6.14-rc4-mm1 Vojtech Pavlik
2005-10-17 21:39       ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-17 21:48         ` 2.6.14-rc4-mm1 Greg KH
2005-10-17 21:58           ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18  6:42             ` 2.6.14-rc4-mm1 Greg KH
2005-10-18  6:39         ` 2.6.14-rc4-mm1 Vojtech Pavlik
2005-10-18  6:44           ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18  6:58     ` 2.6.14-rc4-mm1 Greg KH
2005-10-18  7:09       ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18  7:17         ` 2.6.14-rc4-mm1 Greg KH
2005-10-18  7:22           ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-18  7:38             ` 2.6.14-rc4-mm1 Greg KH
2005-10-18  7:30       ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-18  7:40         ` 2.6.14-rc4-mm1 Greg KH
2005-10-18  8:26           ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-19  3:44             ` 2.6.14-rc4-mm1 Greg KH
2005-10-19  3:58               ` 2.6.14-rc4-mm1 Dmitry Torokhov
2005-10-17 20:44   ` 2.6.14-rc4-mm1 Greg KH
2005-10-17 22:06     ` 2.6.14-rc4-mm1 Brice Goglin
2005-10-19 14:04 ` 2.6.14-rc4-mm1 Alexandre Buisse
2005-10-19 15:52   ` 2.6.14-rc4-mm1 Jiri Slaby
2005-10-19 15:04     ` 2.6.14-rc4-mm1 Alexandre Buisse

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=43534273.2050106@reub.net \
    --to=reuben-lkml@reub.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.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 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.