All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felix Oxley <lkml@oxley.org>
To: Danny ter Haar <dth@cistron.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rt12: irqs hard off for 657 usecs
Date: Sat, 8 Oct 2005 14:08:34 +0100	[thread overview]
Message-ID: <200510081408.34948.lkml@oxley.org> (raw)
In-Reply-To: <di8ebc$b9k$1@news.cistron.nl>

On Saturday 08 October 2005 13:33, Danny ter Haar wrote:

> Ingo,
> could this be the same bug that's been hitting me since 2.6.13* ?
> usenetgateway (heavy used server) with scsi/gig-E ethernet which
> crashes within couple of days.

Danny, 
I wasn't sure from your post whether you are running Ingo's RT patchset or 
not?
Also, maybe you should not run unstable kernels on a production machine? :-)

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-07 22:38 2.6.13-rt12: irqs hard off for 657 usecs Lee Revell
2005-10-08 11:58 ` Ingo Molnar
2005-10-08 12:33   ` Danny ter Haar
2005-10-08 13:08     ` Felix Oxley [this message]
2005-10-08 13:24       ` Danny ter Haar
2005-10-11 11:20 ` Ingo Molnar
2005-10-11 16:28   ` Lee Revell
2005-10-11 18:44     ` Lee Revell
2005-10-11 19:53       ` Ingo Molnar

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=200510081408.34948.lkml@oxley.org \
    --to=lkml@oxley.org \
    --cc=dth@cistron.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 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.