From: "Ray Lee" <ray-lk@madrabbit.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
Cc: "kernel list" <linux-kernel@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: assertion (packets <= tp->packets_out) failed
Date: Sun, 2 Mar 2008 09:15:41 -0800 [thread overview]
Message-ID: <2c0942db0803020915y438bd922h8022267f6f7914fe@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0803021041560.17707@kivilampi-30.cs.helsinki.fi>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 1562 bytes --]
On Sun, Mar 2, 2008 at 12:44 AM, Ilpo Järvinen<ilpo.jarvinen@helsinki.fi> wrote:> On Sat, 1 Mar 2008, Ray Lee wrote:>> > Wireless below is b43, wired interface (tg3) was disconnected. I run> > openvpn which uses a tun interface and regularly sends a heartbeat> > even when not in use. The trace appeared twice.> >> > Likely unrelated but reporting just for completeness: about fifteen> > minutes after this the system oopsed when I told my wireless base> > station to switch from mixed B/G to just B. I'll be taking that up> > separately with the bcm43xx list.> >> > Mar 1 11:06:37 phoenix kernel: [35251.208275] eth1: switched to short> > barker preamble (BSSID=00:16:01:d1:44:3e)> > Mar 1 11:06:37 phoenix kernel: [35251.320282] eth1: switched to long> > barker preamble (BSSID=00:16:01:d1:44:3e)> > Mar 1 11:08:28 phoenix kernel: [35274.396163] KERNEL: assertion> > (packets <= tp->packets_out) failed at net/ipv4/tcp_input.c (2139)> > Mar 1 11:08:29 phoenix kernel: [35274.406126] ------------[ cut here> > ]------------> > Mar 1 11:08:29 phoenix kernel: [35274.406132] WARNING: at> > net/ipv4/tcp_input.c:2506 tcp_ack+0xe3f/0x1b12()>> Do people ever look into archives before posting? I'm a bit tired of point> to the debug patch:>> http://marc.info/?l=linux-kernel&m=120418703023153&w=2
I'm sorry, I managed to miss it. I'll apply the patch and report back.
Thank you.ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
prev parent reply other threads:[~2008-03-02 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 23:10 Ray Lee
2008-03-02 8:44 ` Ilpo Järvinen
2008-03-02 17:15 ` Ray Lee [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=2c0942db0803020915y438bd922h8022267f6f7914fe@mail.gmail.com \
--to=ray-lk@madrabbit.org \
--cc=ilpo.jarvinen@helsinki.fi \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®