From: Dennis Gilmore <dennis@ausil.us>
To: sparclinux@vger.kernel.org
Subject: Re: Oops in tcp_sendmsg on T1000
Date: Mon, 03 Jul 2006 00:02:46 +0000 [thread overview]
Message-ID: <200607021902.46352.dennis@ausil.us> (raw)
In-Reply-To: <200607011421.56811.rene@exactcode.de>
On Saturday 01 July 2006 7:21 am, Rene Rebe wrote:
> Hi all,
>
> I just test the freshly installed T1000 under load and got a single stray
> oops after 5 hours of uptime with excessive load (software compilation).
> The software is the T2 release from this week (software compiled from
> vanilla sources) with GCC 4.1.1, Kernel 2.6.17.2:
>
> Linux version 2.6.17.2-dist (root@localhost) (gcc version 4.1.1) #1 SMP Fri
> Jun 30 14:30:38 /TOOLCHAIN/localtime 2006
>
> The same kernel binary runs on Ultra30 and Ultra5 since days without any
> problem, however I already can imagine that David will slap me for using
> GCC 4.1.1. Maybe someone is interested anyway:
I am using a 2.6.17pre kernel on my T1000
Linux version 2.6.16-1.2241sp7 (root@arthur.devel.redhat.com) (gcc version
3.4.2 20041017 (Red Hat 3.4.2-6.fc3)) #1 SMP Thu Jun 29 10:59:22 EDT 2006
i have been using it with an average load of around 10 for a couple of days
now. It has received 125gb in that time. and have not seen any issues at
all.
--
Dennis Gilmore, RHCE
Proud Australian
next prev parent reply other threads:[~2006-07-03 0:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-01 12:21 Oops in tcp_sendmsg on T1000 Rene Rebe
2006-07-01 22:19 ` David Miller
2006-07-02 15:14 ` Rene Rebe
2006-07-02 16:32 ` David Miller
2006-07-02 17:35 ` Rene Rebe
2006-07-02 19:13 ` Jurij Smakov
2006-07-03 0:02 ` Dennis Gilmore [this message]
2006-07-03 16:16 ` Ben Collins
2006-07-03 16:22 ` Dennis Gilmore
2006-07-03 18:20 ` David Miller
2006-07-04 2:21 ` Jurij Smakov
2006-07-08 1:21 ` David Miller
2006-07-08 18:57 ` Rene Rebe
2006-07-08 20:49 ` 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=200607021902.46352.dennis@ausil.us \
--to=dennis@ausil.us \
--cc=sparclinux@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.