Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: TheNop <TheNop@gmx.net>
Cc: linux-mips@linux-mips.org
Subject: Re: Kernel crash on yosemite
Date: Tue, 8 Feb 2005 10:54:01 +0000	[thread overview]
Message-ID: <20050208105401.GB6131@linux-mips.org> (raw)
In-Reply-To: <42086846.9060709@gmx.net>

On Tue, Feb 08, 2005 at 08:20:38AM +0100, TheNop wrote:

> I'm sorry, but all the discussion on this thread did'n help me to solve 
> my problem. Since more than a month I'm waitig to get a yosemite board 
> with 1.2 version. This still stops my development, when I can't use the 
> yosemite with 1.1 version.
> 
> In another therad we discuss to create a patch (slowpath) for the titan 
> version 1.1. the patch I apply to the the newer kernel sources 
> (2.6.11.rc1) but, I have the same problems. So I think the problem could 
> be the slowpath thing.
> 
> Have anybody an idee how to figure out what could be the problem when I 
> make "cp foo foo1" (foo is a lage file ~3,5 Mb)?

A network driver bug in the 2.6 Titan driver which I recently fixes was
that the allocated receive and transmit rings were allocated overlapping
which was causing havoc.

Yosemite w/ Titan 1.1 was suffering from unexplained system freezes for me;
a more recent board with Titan 1.2 is very stable.

  Ralf

      reply	other threads:[~2005-02-08 10:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 22:53 Kernel crash on yosemite TheNop
2005-02-08  1:30 ` Ralf Baechle
2005-02-08  1:47   ` Manish Lachwani
2005-02-08  1:51     ` Ralf Baechle
2005-02-08  2:02       ` Manish Lachwani
2005-02-08  2:33         ` Ralf Baechle
2005-02-08  3:04           ` Manish Lachwani
2005-02-08  7:20             ` TheNop
2005-02-08 10:54               ` Ralf Baechle [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=20050208105401.GB6131@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=TheNop@gmx.net \
    --cc=linux-mips@linux-mips.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