From: Andrew Morton <akpm@osdl.org>
To: "John Bäckstrand" <sandos@home.se>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: assertion (cnt <= tp->packets_out) failed
Date: Sun, 7 Aug 2005 10:11:05 -0700 [thread overview]
Message-ID: <20050807101105.711b38e9.akpm@osdl.org> (raw)
In-Reply-To: <42F60BE3.6040301@home.se>
John Bäckstrand <sandos@home.se> wrote:
>
> Someone asked if I could try to trigger this assertion again, and I'm
> afraid I probably cannot, I didnt do anything special at the time. But
> I've got something even better for you all, got a BUG from something
> tcp-related. Mind you, I am trying to find a possibly hardware-related
> issue here, so if this bug does not make any sense it might be my hardware!
>
> I would actually want to know it if this is likely hardware-related or
> not, since I have no idea if its RAM, CPU, motherboard or "only" a disk
> that is broken. I know _something_ is broken, due to lockups, and seeing
> a faulty disk indicated in a HDD diag, but only once, the disk is
> apparently fine 99% of the time.
>
> ---
> John Bäckstrand
>
>
> [148475.651000] ------------[ cut here ]------------
> [148475.651050] kernel BUG at net/ipv4/tcp_output.c:918!
I think we've seen a couple of reports of this.
> [148475.651078] invalid operand: 0000 [#1]
> [148475.651103] Modules linked in: sha256 aes_i586 dm_crypt ipt_state
> ipt_multiport ipt_MASQUERADE iptable_filter netconsole md5 ipv6
> af_packet pdc202xx_new e1000 8139cp de2104x i2c_viapro via686a
> i2c_sensor i2c_core uhci_hcd usbcore 3c59x 8139too mii de4x5 crc32
> parport_pc parport reiserfs dm_mod ip_nat_ftp iptable_nat ip_tables
> ip_conntrack_ftp ip_conntrack rtc unix
> [148475.651378] CPU: 0
> [148475.651380] EIP: 0060:[<c0286619>] Not tainted VLI
> [148475.651383] EFLAGS: 00010287 (2.6.13-rc5sand4)
Can you tell us exactly which kernel this is based on? If it's 2.6.13-rc5
then it would be better to be testing 2.6.13-rc5-git<latest>, because some
net fixes have been recently merged.
next prev parent reply other threads:[~2005-08-07 17:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 15:53 John Bäckstrand
2005-08-05 16:32 ` David S. Miller
2005-08-06 2:24 ` Herbert Xu
2005-08-06 7:57 ` Herbert Xu
2005-08-06 12:06 ` John Bäckstrand
2005-08-07 12:02 ` Herbert Xu
2005-08-06 13:30 ` David S. Miller
2005-08-07 13:25 ` John Bäckstrand
2005-08-07 17:11 ` Andrew Morton [this message]
2005-08-07 21:30 ` Herbert Xu
2005-08-07 16:20 Heikki Orsila
2005-08-07 16:29 Heikki Orsila
2005-08-07 16:37 Heikki Orsila
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=20050807101105.711b38e9.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sandos@home.se \
/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®