Hmm... Does anybody own this bug? Best regards,
Mao Rui > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] 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:[EMAIL PROTECTED] > > 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" <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
