From: Pauli Borodulin <pauli.borodulin@uta.fi>
To: Christiaan den Besten <chris@scorpion.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Machine dies under heavy I/O or network-access ..?
Date: Thu, 13 Oct 2005 13:44:22 +0300 [thread overview]
Message-ID: <434E3A86.4030509@uta.fi> (raw)
In-Reply-To: <049f01c5b215$91e7c4b0$3d64880a@speedy>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Christiaan den Besten wrote:
> [...]
> Today I noticed the following assertion in dmesg:
> ---
> e1000: eth0: e1000_watchdog_task: NIC Link is Up 1000 Mbps Full Duplex
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
> KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c
> (148)
> ---
> [...]
I upgraded ten of our servers to 2.6.13.3 on tuesday and noticed today
that the following assertations were in one server's dmesg:
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/core/stream.c (279)
KERNEL: assertion (!sk->sk_forward_alloc) failed at net/ipv4/af_inet.c (151)
This server has e1000 NIC just like most of the servers I upgraded. The
difference in our situation is that the server which logged the
assertions is still running fine. Previous kernel version on the servers
was 2.6.12.2 and it was used over 90 days without any problems.
Br,
--
Pauli Borodulin <pauli.borodulin@uta.fi>
Systems Analyst, tel. +358 3 3551 7892
Computer Centre / Room B4179
University of Tampere, Finland
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-10-13 10:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-05 12:30 Christiaan den Besten
2005-09-07 9:16 ` Andrew Morton
2005-10-13 10:44 ` Pauli Borodulin [this message]
2005-10-13 10:53 ` Christiaan den Besten
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=434E3A86.4030509@uta.fi \
--to=pauli.borodulin@uta.fi \
--cc=chris@scorpion.nl \
--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
Powered by JetHome