public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: John Mason <john@mmspos.com>
To: linux-scsi@vger.kernel.org
Subject: Re: Where to post actual h/w issue questions?
Date: Wed, 01 Sep 2004 10:49:19 -0300	[thread overview]
Message-ID: <6.1.0.6.1.20040901104615.03ec4048@localhost> (raw)
In-Reply-To: <20040901130644.GB5621@lists.us.dell.com>

At 10:06 AM 9/1/2004, Matt Domsch wrote:
>The driver is developed and
>discussed on this list, anything about the driver is fair game on this
>list.  But most people on this list don't have megaraid hardware, so
>if it's hardware specific, and the LSI guys don't answer immediately,
>and its a failure of a "supported" product, you'll need to contact
>their technical support org.

Ok.  I was hoping someone might recognize the problems I had and point me 
to an updated kernel, or megaraid driver.  I don't expect to get much help 
from Dell since the machine passes all diagnostics I can throw at it, but 
maybe I'll try LSI and see if they have any suggestions.

Thanks for the reply.


      reply	other threads:[~2004-09-01 13:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 12:00 Where to post actual h/w issue questions? John Mason
2004-09-01 13:06 ` Matt Domsch
2004-09-01 13:49   ` John Mason [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=6.1.0.6.1.20040901104615.03ec4048@localhost \
    --to=john@mmspos.com \
    --cc=linux-scsi@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