linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: linux-kernel@vger.kernel.org
Subject: Re: TCP MSG_PEEK kernel assertions ...
Date: Mon, 12 Mar 2007 12:22:23 -0700	[thread overview]
Message-ID: <20070312122223.3d5d7f48@freekitty> (raw)
In-Reply-To: 8C930AB112CB842-1728-4DAC@webmail-dd15.sysops.aol.com

On Fri, 09 Mar 2007 16:43:10 -0500
davef1624@aol.com wrote:

> 
>  Hello,
> 
>   I periodically see the following TCP kernel assertion errors in 
> /var/log/message
>   (it does seem that networking is eventually able to recover from these 
> errors):
> 
>   kernel: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c 
> (1171)
>   kernel: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c 
> (1171)
>   kernel: KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & 
> (MSG_PEEK | MSG_TRUNC))) failed at net/ipv4/tcp.c (1235)
>   kernel: KERNEL: assertion (flags & MSG_PEEK) failed at net/ipv4/tcp.c 
> (1171)
>   kernel: KERNEL: assertion (tp->copied_seq == tp->rcv_nxt || (flags & 
> (MSG_PEEK | MSG_TRUNC))) failed at net/ipv4/tcp.c (1235)
> 
>   These errors only seem to occur when using the sk98lin (SysKonnect) 
> Network Device Driver,
>   and a Yukon Gigabit Ethernet 10/100/1000Base-T Adapter (from Marvell I 
> believe).
>  (The other NIC cards we're using in-house don't exhibit this issue).

Wrong mailing list. TCP errors should be sent to netdev@vger.kernel.org

>  I've seen postings concerning this issue over the past year or so,
>   but have not seen a clear resolution and/or understanding of the 
> root-cause of this issue.

Also please include more information, like what kernel version and what
other networking features you are using like VLAN's, netfiltering, ...

>   I'm in the process of upgrading my sk98lin network driver to the 
> latest from SysKonnect
>  in an attempt to see if this corrects the problem.

No, that driver is worse, try the skge driver. The sk98lin driver
is headed for removal

>  Does anybody have any insight into this problem?
> 
>  Best regards,
>  Dave F
> 
> 
>   
> ________________________________________________________________________ 
> 
>   AOL now offers free email to everyone. Find out more about what's free 
> from AOL at AOL.com.
>  -
>   To unsubscribe from this list: send the line "unsubscribe linux-net" 
> in
>  the body of a message to majordomo@vger.kernel.org
>  More majordomo info at http://vger.kernel.org/majordomo-info.html
> 
> 
> ________________________________________________________________________
> AOL now offers free email to everyone.  Find out more about what's free 
> from AOL at AOL.com.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
Stephen Hemminger <shemminger@linux-foundation.org>

      reply	other threads:[~2007-03-12 19:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8C930983B0855DF-1728-4769@webmail-dd15.sysops.aol.com>
2007-03-09 21:43 ` TCP MSG_PEEK kernel assertions davef1624
2007-03-12 19:22   ` Stephen Hemminger [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=20070312122223.3d5d7f48@freekitty \
    --to=shemminger@linux-foundation.org \
    --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;
as well as URLs for NNTP newsgroup(s).