All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Coulson <david@davidcoulson.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: BUG: warning at net/core/dev.c:1171/skb_checksum_help() 2.6.18-rc3
Date: Mon, 31 Jul 2006 06:24:31 +0200	[thread overview]
Message-ID: <44CD85FF.9010607@trash.net> (raw)
In-Reply-To: <44CD8415.2020403@davidcoulson.net>

David Coulson wrote:
> This machine has four NICs running the e1000 kernel module. Other than
> the BUG() messages, it seems to be running fine. I was running 2.6.15.4
> without any issues on the same hardware, although I noticed the e1000
> has been updated (and I went for rc3 since I was hitting the panic in -rc2)
> 
> Now, I'm not sure if it also has anything to do with this message:
> 
> NAT: no longer support implicit source local NAT
> NAT: packet src 10.1.1.1 -> dst 207.166.203.131

No, this in unrelated. This message tries to tell you that the old
behaviour of changing the source address implicitly to the source
address routing would use for a DNATed connection is no longer done.
This behaviour changed in 2.6.11, so if everything worked in 2.6.15,
you should be fine.

> Any suggestions as to how to go about debugging this?
> 
> BUG: warning at net/core/dev.c:1171/skb_checksum_help()
>  [<c02e0412>] skb_checksum_help+0x4d/0xf0
>  [<c034e4d3>] ip_nat_fn+0x4e/0x19e

This is a known problem with NAT and HW checksum and will probably get
fixed in 2.6.19. The message is just a warning, everything should work
fine.


  reply	other threads:[~2006-07-31  4:24 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-31  4:16 BUG: warning at net/core/dev.c:1171/skb_checksum_help() 2.6.18-rc3 David Coulson
2006-07-31  4:24 ` Patrick McHardy [this message]
2006-07-31  4:59   ` David Miller
2006-07-31  5:07     ` Patrick McHardy
2006-07-31 10:39       ` Patrick McHardy
2006-07-31 11:30         ` Herbert Xu
2006-07-31 18:36           ` Patrick McHardy
2006-07-31 21:15             ` David Miller
2006-07-31 21:36               ` Patrick McHardy
2006-07-31 21:54                 ` David Miller
2006-08-01  7:00             ` David Miller
2006-08-01  7:04               ` Herbert Xu
2006-08-01  7:22               ` Patrick McHardy
2006-08-01 15:34               ` Phil Oester
2006-08-01 22:04                 ` Herbert Xu
2006-08-01  7:19             ` Patrick McHardy
2006-08-01  7:23               ` Herbert Xu
2006-08-01  7:36                 ` David Miller
2006-08-01  7:45                   ` Herbert Xu
2006-08-01 12:00                     ` Jamal Hadi Salim
2006-08-01 12:34                       ` Herbert Xu
2006-08-01 12:55                         ` Jamal Hadi Salim
2006-08-01  7:38                 ` Patrick McHardy
2006-08-01 11:51               ` Herbert Xu
2006-08-03  9:21                 ` Patrick McHardy
2006-08-03  9:30                   ` Herbert Xu
2006-08-03  9:34                     ` Patrick McHardy
2006-08-01 12:29             ` Herbert Xu
2006-08-03  9:29               ` Patrick McHardy
2006-08-03  9:33                 ` Herbert Xu
2006-08-03  9:40                   ` Patrick McHardy
2006-08-03  9:57                     ` Herbert Xu
2006-08-05  7:13                       ` Patrick McHardy
2006-08-05  7:59                         ` Herbert Xu
2006-08-01 22:03             ` Herbert Xu
2006-08-03  9:30               ` Patrick McHardy
2006-08-02  0:49           ` Herbert Xu
2006-08-03  9:32             ` Patrick McHardy
2006-08-03  9:36               ` Herbert Xu
2006-08-03  9:43                 ` Patrick McHardy
2006-07-31  4:34 ` Andrew Morton
2006-07-31  4:42   ` David Coulson
2006-07-31  4:58   ` David Miller

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=44CD85FF.9010607@trash.net \
    --to=kaber@trash.net \
    --cc=david@davidcoulson.net \
    --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.