From: Rene Rebe <rene@exactcode.de>
To: sparclinux@vger.kernel.org
Subject: Re: Oops in tcp_sendmsg on T1000
Date: Sun, 02 Jul 2006 15:14:19 +0000 [thread overview]
Message-ID: <200607021714.19680.rene@exactcode.de> (raw)
In-Reply-To: <200607011421.56811.rene@exactcode.de>
Hi,
On Sunday 02 July 2006 00:19, David Miller wrote:
> From: Rene Rebe <rene@exactcode.de>
> Date: Sat, 1 Jul 2006 14:21:56 +0200
>
> > 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:
>
> If you can reproduce this with gcc-4.0.x I'd really appreciate
> it.
I feared that. It will not be easy to reproduce it since it only happend once,
yesterday, and the machine continued to run fine (despite the oops) for
serveral more hours under high load so far.
Is there any chance the post 2.6.17 sparc64 and tg3 changes make a
difference or should I rather really try hard to reprouce it with the
2.6.17.2 kernel to find the real culprit?
Yours,
--
René Rebe - Rubensstr. 64 - 12157 Berlin (Europe / Germany)
http://exactcode.de | http://t2-project.org | http://rebe.name
+49 (0)30 / 255 897 45
next prev parent reply other threads:[~2006-07-02 15:14 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 [this message]
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
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=200607021714.19680.rene@exactcode.de \
--to=rene@exactcode.de \
--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.