From: Matt Domsch <Matt_Domsch@dell.com>
To: John Mason <john@mmspos.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Where to post actual h/w issue questions?
Date: Wed, 1 Sep 2004 08:06:44 -0500 [thread overview]
Message-ID: <20040901130644.GB5621@lists.us.dell.com> (raw)
In-Reply-To: <6.1.0.6.1.20040901085756.00b37330@localhost>
On Wed, Sep 01, 2004 at 09:00:33AM -0300, John Mason wrote:
>
> I joined the list last week and most of the discussion here seems to be
> related to patches to various drivers and kernels. I've only seen one post
> other than my own about a hardware or driver failure (on a Dell with
> megaraid), so is there another list I should be asking on?
Hardware failures are best handled by the tech support organization of
the company who you purchased the hardware from.
If it's not truly a hardware failure, but an interaction of their
device driver with the hardware, and the driver is part of the
standard kernel.org kernels, then sure, this list is a good place to
ask. megaraid is a good example. 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.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2004-09-01 13:06 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 [this message]
2004-09-01 13:49 ` John Mason
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=20040901130644.GB5621@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=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