mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mao Rui" <maorui@yuvad.com>
To: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: SATA DOM is not identified by ata_piix module
Date: Wed, 30 Jan 2008 10:42:12 +0800	[thread overview]
Message-ID: <071501c862e9$c0bf1770$7740a8c0@cmaorui2> (raw)
In-Reply-To: <00da01c85999$0856e540$7740a8c0@cmaorui2>

Hmm... Does anybody own this bug?

Best regards,

Mao Rui


> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Mao Rui
> Sent: Friday, January 18, 2008 2:12 PM
> To: 'Alan Cox'
> Cc: linux-kernel@vger.kernel.org
> Subject: RE: SATA DOM is not identified by ata_piix module
> 
> I tried to nail down when the problem was introduced. I compiled some
> official kernel release. Here is the result.
> 2.6.17.14   IDE -- Failed   SATA -- passed
> 2.6.18   IDE -- Failed   SATA -- failed
> 2.6.18.8   IDE -- Failed   SATA -- failed
> 2.6.24-rc7-git6  IDE -- passed   SATA DOM -- failed
> linux-2.6.24-rc8-git1   IDE -- passed    SATA -- failed
> All IDE failed reason is xfermode error, and all SATA failure is IDENTIFY
> error.
> 
> As you can find out, the failure of SATA DOM was introduced from kernel
> 2.6.18.
> 
> I'm not good at low level driver programming, so I cannot find out the
root
> cause by myself. But if Alan or someone else needs more info or wants to
> test the patch, I'm glad to do it in my platform.
> 
> Best regards,
> Mao Rui
> 
> > -----Original Message-----
> > From: Alan Cox [mailto:alan@lxorguk.ukuu.org.uk]
> > Sent: Tuesday, January 15, 2008 7:02 PM
> > To: Mao Rui
> > Cc: linux-kernel@vger.kernel.org
> > Subject: Re: SATA DOM is not identified by ata_piix module
> >
> > On Tue, 15 Jan 2008 18:11:25 +0800
> > "Mao Rui" <maorui@yuvad.com> wrote:
> >
> > > Hi,
> > >
> > > I have a PQI Turbo SATA DOM. It works well under Windows. I installed
it
> in
> > > a SuperMicro motherboard, Intel 5000P chipset. The OS is Ubuntu 7.04,
> kernel
> > > 2.6.20-15. But the DOM is not appeared as a device node, and I found
> several
> > > error messages in kernel log.
> >
> > Generally it is a good idea to report problems with vendor built kernels
> > to the vendor and their support, especially one that is 3 releases
behind.
> > They have a much better idea what is in that kernel and who else has
seen
> > problems.
> >
> > > [   67.124299] ata2.00: qc timeout (cmd 0x91)
> > > [   67.124306] ata2.00: failed to IDENTIFY (INIT_DEV_PARAMS failed,
> > > err_mask=0x4)
> >
> > We issued commands, it didn't respond. That could be a libata problem
but
> > actually looks more like an IRQ routing problem.
> >
> > > Actually I also have a PQI IDE DOM, it have same error with Ubuntu
7.04
> /
> >
> > The PQI DOM is a bit odd, it is however known to work with libata at
> > least for the PATA one, and the versions which don't understand
> > SET_XFER_MODE to work with current kernels. (Your failure mode isn't the
> > SET_XFER_MODE one - it hasn't got that far).
> >
> > Alan
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/



  reply	other threads:[~2008-01-30  2:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 10:11 Mao Rui
2008-01-15 11:02 ` Alan Cox
2008-01-18  6:11   ` Mao Rui
2008-01-30  2:42     ` Mao Rui [this message]
2008-02-04 13:00       ` Alan Cox
2008-02-02  8:41     ` Tejun Heo
2008-02-02  9:25       ` Mao Rui
2008-02-02 11:20         ` Tejun Heo

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='071501c862e9$c0bf1770$7740a8c0@cmaorui2' \
    --to=maorui@yuvad.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome