public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: m.delahaye@esiee.fr (Matthieu Delahaye)
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] swiotlb on rx4610, again
Date: Fri, 18 Apr 2003 15:19:28 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590723705565@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705531@msgid-missing>

On Fri, Apr 18, 2003 at 08:52:43AM -0600, Bdale Garbee wrote:
> m.delahaye@esiee.fr (Matthieu Delahaye) writes:
> 
> > But the fact this kernel worked without this option and that now it is
> > required, I'm quite "annoyed" hoping this is not an hardware issue. 
> 
> A couple of general suggestions.
> 
> [...]

Thanks Bdale for the suggestions. But I think I didn't express correctly the
main objective of my mail:

I can make by servers running under Linux...
and I've justed tell I were using Debian stock kernel just for explaining it
wasn't an home made with a possible error manually inserted, and to tell
I was sure it was the same kernel I was using before my crash.

My problem is not here. I am just trying to know if someone have
an hint on the fact my servers behaviour change over the time with the
same kernel/softwares.

Sure I can add a more recent kernel and this may work correctly without
adding kernel options. But If I have an hardware issue, perhaps it is better to know it now than
latter.

So that's why I've posted here. I just wanted to know if someone else already have noticed that before. No more.
I was quite busy today so that I didn't have perform further tests with
different kernel/configurations and debugging to learn more.

Best regards,

Matthieu



      parent reply	other threads:[~2003-04-18 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 13:06 [Linux-ia64] swiotlb on rx4610, again Matthieu Delahaye
2003-04-17 15:49 ` Bjorn Helgaas
2003-04-18 14:52 ` Bdale Garbee
2003-04-18 15:19 ` Matthieu Delahaye [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=marc-linux-ia64-105590723705565@msgid-missing \
    --to=m.delahaye@esiee.fr \
    --cc=linux-ia64@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