subject:"\[SATA\] libata\-dev queue updated"

On Fri, Mar 04, 2005 at 11:06:23PM +0100, Joerg Sommrey wrote:
> On Fri, Mar 04, 2005 at 03:43:38PM -0500, Jeff Garzik wrote:
> > Joerg Sommrey wrote:
> > >On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
> > >
> > >>Joerg Sommrey wrote:
> > >>
> > >>>On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
> > >>>
> > >>>
> > Joerg Sommrey wrote:
> > 
> > 
> > >On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> > >
> > >
> > >
> > >>Joerg Sommrey wrote:
> > >>
> > >>
> > >>
> > >>>On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> > >>>
> > >>>
> > >>>
> > >>>
> > Joerg Sommrey wrote:
> > 
> > 
> > 
> > 
> > >Jeff Garzik wrote:
> > >
> > >
> > >
> > >
> > >>Patch:
> > >>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> > >
> > >
> > >Still not usable here.  The same errors as before when backing up:
> > 
> > Please try 2.6.11 without any patches.
> > >>>
> > >>>Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> > >>>2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with 
> > >>>the
> > >>>same symptoms. 
> > >>>
> > >>>Reverting to stable 2.6.10-ac8 :-)
> > >>
> > >>Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> > >>things?
> > >>
> > >
> > >
> > >Still the same with this patch reverted.
> > 
> > Does reverting the attached patch in 2.6.11 fix things?  (apply with 
> > patch -R)
> > 
> > This patch reverts the entire libata back to 2.6.10.
> > 
> > >>>
> > >>>I'm confused.  Still the same with everything reverted.  What shall I do
> > >>>now?
> > >>
> > >>Well, first, thanks for your patience in narrowing this down.
> > >>
> > >>This means we have eliminated libata as a problem source, but we still 
> > >>have the rest of the kernel go to through :)
> > >>
> > >>Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes 
> > >>things.
> > >>
> > >
> > >I tried both settings with plain 2.6.11. Almost the same results, in my
> > >impression apci=off causes the failure to appear even faster.
> > 
> > Just to make sure I have things right, please tell me if this is correct:
> > 
> > * 2.6.10 vanilla works
> > 
> > * 2.6.11 vanilla does not work
> > 
> > * 2.6.11 vanilla + 2.6.10 libata does not work
> >   [2.6.10 libata == reverting all libata changes]
> > 
> > Is that all correct?
> 
> Thanks for asking these precise questions.  After double-checking
> everything I found a typo in my configuration that changes things a bit.
> I repeated some tests and the correct answers are now:
> * 2.6.10 vanilla  works
> * 2.6.10-ac8  works
> * 2.6.10-ac11 does not work
> * 2.6.11 vanilla  does not work
> * 2.6.11 w/o promise.patchdoes not work
> * 2.6.11 + 2.6.10 libata  works!
> 
> This looks much more consistent to me but brings the case back to
> libata.

After one more test using 2.6.11 + 2.6.10 libata I got some errors.
They are different, they end after some time and they don't lock the system:

Mar  4 23:15:00 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  4 23:15:00 bear kernel: sdb: Current: sense key: Recovered Error
Mar  4 23:15:00 bear kernel: ASC=0x26 <> ASCQ=0xc0
Mar  4 23:15:00 bear kernel: FMK, ILI

Got 1900 of these in 90 seconds and silence afterwards.  Maybe that
helps. I'll keep this kernel running and watch it.

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 23:12 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 03:43:38PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
> >
> >>Joerg Sommrey wrote:
> >>
> >>>On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
> >>>
> >>>
> Joerg Sommrey wrote:
> 
> 
> >On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> >
> >
> >
> >>Joerg Sommrey wrote:
> >>
> >>
> >>
> >>>On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> >>>
> >>>
> >>>
> >>>
> Joerg Sommrey wrote:
> 
> 
> 
> 
> >Jeff Garzik wrote:
> >
> >
> >
> >
> >>Patch:
> >>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >
> >
> >Still not usable here.  The same errors as before when backing up:
> 
> Please try 2.6.11 without any patches.
> >>>
> >>>Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> >>>2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with 
> >>>the
> >>>same symptoms. 
> >>>
> >>>Reverting to stable 2.6.10-ac8 :-)
> >>
> >>Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> >>things?
> >>
> >
> >
> >Still the same with this patch reverted.
> 
> Does reverting the attached patch in 2.6.11 fix things?  (apply with 
> patch -R)
> 
> This patch reverts the entire libata back to 2.6.10.
> 
> >>>
> >>>I'm confused.  Still the same with everything reverted.  What shall I do
> >>>now?
> >>
> >>Well, first, thanks for your patience in narrowing this down.
> >>
> >>This means we have eliminated libata as a problem source, but we still 
> >>have the rest of the kernel go to through :)
> >>
> >>Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes 
> >>things.
> >>
> >
> >I tried both settings with plain 2.6.11. Almost the same results, in my
> >impression apci=off causes the failure to appear even faster.
> 
> Just to make sure I have things right, please tell me if this is correct:
> 
> * 2.6.10 vanilla works
> 
> * 2.6.11 vanilla does not work
> 
> * 2.6.11 vanilla + 2.6.10 libata does not work
>   [2.6.10 libata == reverting all libata changes]
> 
> Is that all correct?

Thanks for asking these precise questions.  After double-checking
everything I found a typo in my configuration that changes things a bit.
I repeated some tests and the correct answers are now:
* 2.6.10 vanillaworks
* 2.6.10-ac8works
* 2.6.10-ac11   does not work
* 2.6.11 vanilladoes not work
* 2.6.11 w/o promise.patch  does not work
* 2.6.11 + 2.6.10 libataworks!

This looks much more consistent to me but brings the case back to
libata.

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 22:48 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here. The same errors as before when backing up:
Please try 2.6.11 without any patches.
Plain 2.6.11 doesn't work either. All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms.

Reverting to stable 2.6.10-ac8 :-)
Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.
Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

This patch reverts the entire libata back to 2.6.10.
I'm confused. Still the same with everything reverted. What shall I do
now?
Well, first, thanks for your patience in narrowing this down.
This means we have eliminated libata as a problem source, but we still
have the rest of the kernel go to through :)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.
Just to make sure I have things right, please tell me if this is correct:
* 2.6.10 vanilla works
* 2.6.11 vanilla does not work
* 2.6.11 vanilla + 2.6.10 libata does not work
[2.6.10 libata == reverting all libata changes]
Is that all correct?
Jeff

-
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/

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
> >
> >>Joerg Sommrey wrote:
> >>
> >>>On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> >>>
> >>>
> Joerg Sommrey wrote:
> 
> 
> >On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> >
> >
> >
> >>Joerg Sommrey wrote:
> >>
> >>
> >>
> >>>Jeff Garzik wrote:
> >>>
> >>>
> >>>
> Patch:
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >>>
> >>>
> >>>Still not usable here.  The same errors as before when backing up:
> >>
> >>Please try 2.6.11 without any patches.
> >
> >Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> >2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
> >same symptoms. 
> >
> >Reverting to stable 2.6.10-ac8 :-)
> 
> Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> things?
> 
> >>>
> >>>
> >>>Still the same with this patch reverted.
> >>
> >>Does reverting the attached patch in 2.6.11 fix things?  (apply with 
> >>patch -R)
> >>
> >>This patch reverts the entire libata back to 2.6.10.
> >>
> >
> >I'm confused.  Still the same with everything reverted.  What shall I do
> >now?
> 
> Well, first, thanks for your patience in narrowing this down.
> 
> This means we have eliminated libata as a problem source, but we still 
> have the rest of the kernel go to through :)
> 
> Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes 
> things.
> 
I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 20:54 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Reverting to stable 2.6.10-ac8 :-)
Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.
Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

Jeff

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> >
> >>Joerg Sommrey wrote:
> >>
> >>>On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> >>>
> >>>
> Joerg Sommrey wrote:
> 
> 
> >Jeff Garzik wrote:
> >
> >
> >>Patch:
> >>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >
> >
> >Still not usable here.  The same errors as before when backing up:
> 
> Please try 2.6.11 without any patches.
> >>>
> >>>Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> >>>2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
> >>>same symptoms. 
> >>>
> >>>Reverting to stable 2.6.10-ac8 :-)
> >>
> >>Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> >>things?
> >>
> >
> >
> >Still the same with this patch reverted.
> 
> Does reverting the attached patch in 2.6.11 fix things?  (apply with 
> patch -R)
> 
> This patch reverts the entire libata back to 2.6.10.
> 
I'm confused.  Still the same with everything reverted.  What shall I do
now?

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 18:44 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
 Joerg Sommrey wrote:
 On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
 
 Joerg Sommrey wrote:
 
 On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
 
 
 Joerg Sommrey wrote:
 
 
 Jeff Garzik wrote:
 
 
 Patch:
 http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
 
 
 Still not usable here.  The same errors as before when backing up:
 
 Please try 2.6.11 without any patches.
 
 Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
 2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
 same symptoms. 
 
 Reverting to stable 2.6.10-ac8 :-)
 
 Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
 things?
 
 
 
 Still the same with this patch reverted.
 
 Does reverting the attached patch in 2.6.11 fix things?  (apply with 
 patch -R)
 
 This patch reverts the entire libata back to 2.6.10.
 
I'm confused.  Still the same with everything reverted.  What shall I do
now?

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 18:44 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Reverting to stable 2.6.10-ac8 :-)
Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.
Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

Jeff

-
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/

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here. The same errors as before when backing up:

Please try 2.6.11 without any patches.

Plain 2.6.11 doesn't work either. All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms.

Reverting to stable 2.6.10-ac8 :-)

Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.

Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

This patch reverts the entire libata back to 2.6.10.

I'm confused. Still the same with everything reverted. What shall I do
now?

Well, first, thanks for your patience in narrowing this down.

This means we have eliminated libata as a problem source, but we still
have the rest of the kernel go to through :)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.

-jo

--
-rw-r--r-- 1 jo users 63 2005-03-04 20:54 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Reverting to stable 2.6.10-ac8 :-)
Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.
Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 03:43:38PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here. The same errors as before when backing up:

Please try 2.6.11 without any patches.

Plain 2.6.11 doesn't work either. All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with
the
same symptoms.

Reverting to stable 2.6.10-ac8 :-)

Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.

Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

This patch reverts the entire libata back to 2.6.10.

I'm confused. Still the same with everything reverted. What shall I do
now?

Well, first, thanks for your patience in narrowing this down.

This means we have eliminated libata as a problem source, but we still
have the rest of the kernel go to through :)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.

Just to make sure I have things right, please tell me if this is correct:

* 2.6.10 vanilla works

* 2.6.11 vanilla does not work

* 2.6.11 vanilla + 2.6.10 libata does not work
[2.6.10 libata == reverting all libata changes]

Is that all correct?

Thanks for asking these precise questions. After double-checking
everything I found a typo in my configuration that changes things a bit.
I repeated some tests and the correct answers are now:
* 2.6.10 vanillaworks
* 2.6.10-ac8works
* 2.6.10-ac11 does not work
* 2.6.11 vanilladoes not work
* 2.6.11 w/o promise.patch does not work
* 2.6.11 + 2.6.10 libataworks!

This looks much more consistent to me but brings the case back to
libata.

-jo

--
-rw-r--r-- 1 jo users 63 2005-03-04 22:48 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Fri, Mar 04, 2005 at 11:06:23PM +0100, Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 03:43:38PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
On Fri, Mar 04, 2005 at 01:07:16PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Fri, Mar 04, 2005 at 02:10:14AM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:

Joerg Sommrey wrote:

Jeff Garzik wrote:

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here. The same errors as before when backing up:

Please try 2.6.11 without any patches.

Plain 2.6.11 doesn't work either. All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with
the
same symptoms.

Reverting to stable 2.6.10-ac8 :-)

Does reverting the attached patch in 2.6.11 (apply with patch -R) fix
things?

Still the same with this patch reverted.

Does reverting the attached patch in 2.6.11 fix things? (apply with
patch -R)

This patch reverts the entire libata back to 2.6.10.

I'm confused. Still the same with everything reverted. What shall I do
now?

Well, first, thanks for your patience in narrowing this down.

This means we have eliminated libata as a problem source, but we still
have the rest of the kernel go to through :)

Try disabling ACPI with 'acpi=off' or 'pci=biosirq' to see if that fixes
things.

I tried both settings with plain 2.6.11. Almost the same results, in my
impression apci=off causes the failure to appear even faster.

Just to make sure I have things right, please tell me if this is correct:

* 2.6.10 vanilla works

* 2.6.11 vanilla does not work

* 2.6.11 vanilla + 2.6.10 libata does not work
[2.6.10 libata == reverting all libata changes]

Is that all correct?

Thanks for asking these precise questions. After double-checking
everything I found a typo in my configuration that changes things a bit.
I repeated some tests and the correct answers are now:
* 2.6.10 vanilla works
* 2.6.10-ac8 works
* 2.6.10-ac11 does not work
* 2.6.11 vanilla does not work
* 2.6.11 w/o promise.patchdoes not work
* 2.6.11 + 2.6.10 libata works!

This looks much more consistent to me but brings the case back to
libata.

After one more test using 2.6.11 + 2.6.10 libata I got some errors.
They are different, they end after some time and they don't lock the system:

Mar 4 23:15:00 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error
}Mar 4 23:15:00 bear kernel: sdb: Current: sense key: Recovered Error
Mar 4 23:15:00 bear kernel: ASC=0x26 vendor ASCQ=0xc0
Mar 4 23:15:00 bear kernel: FMK, ILI

Got 1900 of these in 90 seconds and silence afterwards. Maybe that
helps. I'll keep this kernel running and watch it.

-jo

--
-rw-r--r-- 1 jo users 63 2005-03-04 23:12 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> >
> >>Joerg Sommrey wrote:
> >>
> >>>Jeff Garzik wrote:
> >>>
> Patch:
> http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >>>
> >>>
> >>>Still not usable here.  The same errors as before when backing up:
> >>
> >>Please try 2.6.11 without any patches.
> >
> >Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
> >2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
> >same symptoms. 
> >
> >Reverting to stable 2.6.10-ac8 :-)
> 
> Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
> things?
> 

Still the same with this patch reverted.
-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 07:32 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

2005-03-03 Thread Jeff Garzik

Joerg Sommrey wrote:
On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
Joerg Sommrey wrote:
Jeff Garzik wrote:
Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here.  The same errors as before when backing up:
Please try 2.6.11 without any patches.
Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms. 

Reverting to stable 2.6.10-ac8 :-)
Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
things?

Jeff

diff -Nru a/drivers/scsi/sata_promise.c b/drivers/scsi/sata_promise.c
--- a/drivers/scsi/sata_promise.c   2005-03-01 23:39:08 -08:00
+++ b/drivers/scsi/sata_promise.c   2005-03-01 23:39:08 -08:00
@@ -156,10 +156,18 @@
  board_2037x },
{ PCI_VENDOR_ID_PROMISE, 0x3376, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
  board_2037x },
+   { PCI_VENDOR_ID_PROMISE, 0x3574, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_2037x },
+   { PCI_VENDOR_ID_PROMISE, 0x3d75, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_2037x },
+
{ PCI_VENDOR_ID_PROMISE, 0x3318, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
  board_20319 },
{ PCI_VENDOR_ID_PROMISE, 0x3319, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
  board_20319 },
+   { PCI_VENDOR_ID_PROMISE, 0x3d18, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
+ board_20319 },
+
{ } /* terminate list */
 };
 
@@ -406,9 +414,11 @@
return IRQ_NONE;
}
 
-spin_lock(_set->lock);
+   spin_lock(_set->lock);
 
-for (i = 0; i < host_set->n_ports; i++) {
+   writel(mask, mmio_base + PDC_INT_SEQMASK);
+
+   for (i = 0; i < host_set->n_ports; i++) {
VPRINTK("port %u\n", i);
ap = host_set->ports[i];
tmp = mask & (1 << (i + 1));
@@ -546,6 +556,7 @@
unsigned long base;
void *mmio_base;
unsigned int board_idx = (unsigned int) ent->driver_data;
+   int pci_dev_busy = 0;
int rc;
 
if (!printed_version++)
@@ -560,8 +571,10 @@
return rc;
 
rc = pci_request_regions(pdev, DRV_NAME);
-   if (rc)
+   if (rc) {
+   pci_dev_busy = 1;
goto err_out;
+   }
 
rc = pci_set_dma_mask(pdev, ATA_DMA_MASK);
if (rc)
@@ -640,7 +653,8 @@
 err_out_regions:
pci_release_regions(pdev);
 err_out:
-   pci_disable_device(pdev);
+   if (!pci_dev_busy)
+   pci_disable_device(pdev);
return rc;
 }

Re: [SATA] libata-dev queue updated

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
> Joerg Sommrey wrote:
> >Jeff Garzik wrote:
> >>Patch:
> >>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
> >
> >
> >Still not usable here.  The same errors as before when backing up:
> 
> Please try 2.6.11 without any patches.
Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms. 

Reverting to stable 2.6.10-ac8 :-)

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-03 20:23 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Thu, Mar 03, 2005 at 11:09:26PM -0500, Jeff Garzik wrote:
 Joerg Sommrey wrote:
 On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
 
 Joerg Sommrey wrote:
 
 Jeff Garzik wrote:
 
 Patch:
 http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
 
 
 Still not usable here.  The same errors as before when backing up:
 
 Please try 2.6.11 without any patches.
 
 Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
 2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
 same symptoms. 
 
 Reverting to stable 2.6.10-ac8 :-)
 
 Does reverting the attached patch in 2.6.11 (apply with patch -R) fix 
 things?
 

Still the same with this patch reverted.
-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-04 07:32 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

On Wed, Mar 02, 2005 at 05:43:59PM -0500, Jeff Garzik wrote:
 Joerg Sommrey wrote:
 Jeff Garzik wrote:
 Patch:
 http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2
 
 
 Still not usable here.  The same errors as before when backing up:
 
 Please try 2.6.11 without any patches.
Plain 2.6.11 doesn't work either.  All of 2.6.10-ac11, 2.6.11-rc5,
2.6.11-rc5 + 2.6.11-rc5-bk4-libata-dev1.patch and 2.6.11 fail with the
same symptoms. 

Reverting to stable 2.6.10-ac8 :-)

-jo

-- 
-rw-r--r--  1 jo users 63 2005-03-03 20:23 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

2005-03-02 Thread Jeff Garzik

Joerg Sommrey wrote:
Jeff Garzik wrote:

BK users:

	bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here.  The same errors as before when backing up:
Please try 2.6.11 without any patches.
Jeff

-
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/

Re: [SATA] libata-dev queue updated

2005-03-02 Thread Joerg Sommrey

Jeff Garzik wrote:

>BK users:

>   bk pull bk://gkernel.bkbits.net/libata-dev-2.6

>Patch:
>http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here.  The same errors as before when backing up:

Mar  2 21:09:50 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: SCSI error : <1 0 0 0> return code = 0x802
Mar  2 21:09:51 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:51 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed
Mar  2 21:09:51 bear kernel: end_request: I/O error, dev sdb, sector 43099350
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:52 bear kernel: SCSI error : <1 0 0 0> return code = 0x802
Mar  2 21:09:52 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:52 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed
Mar  2 21:09:52 bear kernel: end_request: I/O error, dev sdb, sector 43099358
Mar  2 21:09:52 bear kernel: raid1: Disk failure on sdb2, disabling device.
Mar  2 21:09:52 bear kernel: ^IOperation continuing on 1 devices
Mar  2 21:09:52 bear kernel: raid1: sdb2: rescheduling sector 2904720
Mar  2 21:09:52 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:52 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:52 bear kernel: SCSI error : <1 0 0 0> return code = 0x802
Mar  2 21:09:52 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:52 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed

Using Promise SATA150 TX4 / md-raid1 / lvm / reiserfs

-jo
-- 
-rw-r--r--  1 jo users 63 2005-03-02 21:14 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

2005-03-02 Thread Joerg Sommrey

Jeff Garzik wrote:

BK users:

   bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here.  The same errors as before when backing up:

Mar  2 21:09:50 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:51 bear kernel: SCSI error : 1 0 0 0 return code = 0x802
Mar  2 21:09:51 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:51 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed
Mar  2 21:09:51 bear kernel: end_request: I/O error, dev sdb, sector 43099350
Mar  2 21:09:51 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:51 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:52 bear kernel: SCSI error : 1 0 0 0 return code = 0x802
Mar  2 21:09:52 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:52 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed
Mar  2 21:09:52 bear kernel: end_request: I/O error, dev sdb, sector 43099358
Mar  2 21:09:52 bear kernel: raid1: Disk failure on sdb2, disabling device.
Mar  2 21:09:52 bear kernel: ^IOperation continuing on 1 devices
Mar  2 21:09:52 bear kernel: raid1: sdb2: rescheduling sector 2904720
Mar  2 21:09:52 bear kernel: ata1: status=0x51 { DriveReady SeekComplete Error 
}Mar  2 21:09:52 bear kernel: ata1: called with no error (51)!
Mar  2 21:09:52 bear kernel: SCSI error : 1 0 0 0 return code = 0x802
Mar  2 21:09:52 bear kernel: sdb: Current: sense key: Medium Error
Mar  2 21:09:52 bear kernel: Additional sense: Unrecovered read error - 
auto reallocate failed

Using Promise SATA150 TX4 / md-raid1 / lvm / reiserfs

-jo
-- 
-rw-r--r--  1 jo users 63 2005-03-02 21:14 /home/jo/.signature
-
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/

Re: [SATA] libata-dev queue updated

2005-03-02 Thread Jeff Garzik

Joerg Sommrey wrote:
Jeff Garzik wrote:

BK users:

	bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

Still not usable here.  The same errors as before when backing up:
Please try 2.6.11 without any patches.
Jeff

-
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/

[SATA] libata-dev queue updated

2005-03-01 Thread Jeff Garzik

A minor update, mostly to update to the latest kernel.
BK users:

bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

This will update the following files:

 drivers/scsi/Kconfig |   18 
 drivers/scsi/Makefile|2 
 drivers/scsi/ahci.c  |  107 -
 drivers/scsi/ata_adma.c  |  778 +++
 drivers/scsi/libata-core.c   |  312 +
 drivers/scsi/libata-scsi.c   |  701 --
 drivers/scsi/libata.h|6 
 drivers/scsi/pata_pdc2027x.c |  771 ++
 drivers/scsi/sata_promise.c  |   84 
 drivers/scsi/sata_qstor.c|   20 -
 drivers/scsi/sata_vsc.c  |4 
 include/linux/ata.h  |   15 
 include/linux/libata.h   |   10 
 include/scsi/scsi.h  |3 
 14 files changed, 2531 insertions(+), 300 deletions(-)

through these ChangeSets:

:
  o [libata scsi] support 12-byte passthru CDB
  o [libata scsi] passthru CDB check condition processing
  o T10/04-262 ATA pass thru - patch

:
  o [libata sata_promise] support PATA ports on SATA controllers

:
  o drivers/scsi/ahci: Use the DMA_{64,32}BIT_MASK constants
  o drivers/scsi/sata_vsc: Use the DMA_{64,32}BIT_MASK constants

Adam J. Richter:
  o ata_pci_remove_one used freed memory

Albert Lee:
  o [libata] use init-device-params ATA command where needed
  o [libata] ata_scsi_verify_xlat() fix
  o pdc2027x timing register fix for 100MHz
  o [libata] CHS support: add CHS support to ata_scsi_verify_xlat(), 
ata_scsi_rw_xlat() and ata_scsiop_read_cap().
  o [libata] CHS support: reorganize read/write translation in 
ata_scsi_rw_xlat()
  o [libata] CHS support: rename vars (s/sector/block/) in 
ata_scsi_verify_xlat()
  o [libata] CHS support: detect C/H/S at IDENTIFY DEVICE time
  o [libata] CHS support: add definitions to headers
  o pdc2027x timing register bug fix
  o [libata pdc2027x] fix incorrect pio and mwdma masks
  o [libata pdc2027x] remove quirks and ROM enable
  o [libata] add driver for Promise PATA 2027x

Brad Campbell:
  o libata basic detection and errata for PATA->SATA bridges

Jeff Garzik:
  o [libata ahci] Print out port id on error messages
  o [libata ahci] support PCI MSI interrupt vector
  o [libata adma] Add init code, fix CPB submission code
  o [libata ahci] finish ATAPI support
  o [libata adma] trivial whitespace cleanup
  o [libata dma] fix DMA mode config; add some more initialization code
  o [libata adma] add support for configuring PIO/DMA modes
  o [libata] turn on ATAPI support
  o [libata sata_promise] merge Tobias Lorenz' pdc20619 patch, part 2
  o [libata] small cleanups
  o [libata] remove unused execute-device-diagnostic reset method
  o [libata] add new driver ata_adma
  o [libata pdc2027x] update for upstream struct device conversion
  o [libata sata_promise] fix merge bugs
  o [libata] fix build breakage
  o [libata] fix SATA->PATA bridge detect compile breakage
  o [libata] fix printk warning

John W. Linville:
  o libata: update ATA pass thru opcodes
  o libata: minor style changes in ata_scsi_pass_thru
  o libata: filter SET_FEATURES - XFER MODE from ATA pass thru
  o libata: sync SMART ioctls with ATA pass thru spec (T10/04-262r7)
  o libata: fix command queue leak when xlat_func fails
  o libata: SMART support via ATA pass-thru

Mark Lord:
  o [libata qstor] minor update per LKML comments

Tobias Lorenz:
  o [libata sata_promise] pdc20619 (PATA) support
  o libata-scsi: get-identity ioctl support

[SATA] libata-dev queue updated

2005-03-01 Thread Jeff Garzik

A minor update, mostly to update to the latest kernel.
BK users:

bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc5-bk4-libata-dev1.patch.bz2

This will update the following files:

 drivers/scsi/Kconfig |   18 
 drivers/scsi/Makefile|2 
 drivers/scsi/ahci.c  |  107 -
 drivers/scsi/ata_adma.c  |  778 +++
 drivers/scsi/libata-core.c   |  312 +
 drivers/scsi/libata-scsi.c   |  701 --
 drivers/scsi/libata.h|6 
 drivers/scsi/pata_pdc2027x.c |  771 ++
 drivers/scsi/sata_promise.c  |   84 
 drivers/scsi/sata_qstor.c|   20 -
 drivers/scsi/sata_vsc.c  |4 
 include/linux/ata.h  |   15 
 include/linux/libata.h   |   10 
 include/scsi/scsi.h  |3 
 14 files changed, 2531 insertions(+), 300 deletions(-)

through these ChangeSets:

andyw:pobox.com:
  o [libata scsi] support 12-byte passthru CDB
  o [libata scsi] passthru CDB check condition processing
  o T10/04-262 ATA pass thru - patch

erikbenada:yahoo.ca:
  o [libata sata_promise] support PATA ports on SATA controllers

tklauser:nuerscht.ch:
  o drivers/scsi/ahci: Use the DMA_{64,32}BIT_MASK constants
  o drivers/scsi/sata_vsc: Use the DMA_{64,32}BIT_MASK constants

Adam J. Richter:
  o ata_pci_remove_one used freed memory

Albert Lee:
  o [libata] use init-device-params ATA command where needed
  o [libata] ata_scsi_verify_xlat() fix
  o pdc2027x timing register fix for 100MHz
  o [libata] CHS support: add CHS support to ata_scsi_verify_xlat(), 
ata_scsi_rw_xlat() and ata_scsiop_read_cap().
  o [libata] CHS support: reorganize read/write translation in 
ata_scsi_rw_xlat()
  o [libata] CHS support: rename vars (s/sector/block/) in 
ata_scsi_verify_xlat()
  o [libata] CHS support: detect C/H/S at IDENTIFY DEVICE time
  o [libata] CHS support: add definitions to headers
  o pdc2027x timing register bug fix
  o [libata pdc2027x] fix incorrect pio and mwdma masks
  o [libata pdc2027x] remove quirks and ROM enable
  o [libata] add driver for Promise PATA 2027x

Brad Campbell:
  o libata basic detection and errata for PATA-SATA bridges

Jeff Garzik:
  o [libata ahci] Print out port id on error messages
  o [libata ahci] support PCI MSI interrupt vector
  o [libata adma] Add init code, fix CPB submission code
  o [libata ahci] finish ATAPI support
  o [libata adma] trivial whitespace cleanup
  o [libata dma] fix DMA mode config; add some more initialization code
  o [libata adma] add support for configuring PIO/DMA modes
  o [libata] turn on ATAPI support
  o [libata sata_promise] merge Tobias Lorenz' pdc20619 patch, part 2
  o [libata] small cleanups
  o [libata] remove unused execute-device-diagnostic reset method
  o [libata] add new driver ata_adma
  o [libata pdc2027x] update for upstream struct device conversion
  o [libata sata_promise] fix merge bugs
  o [libata] fix build breakage
  o [libata] fix SATA-PATA bridge detect compile breakage
  o [libata] fix printk warning

John W. Linville:
  o libata: update ATA pass thru opcodes
  o libata: minor style changes in ata_scsi_pass_thru
  o libata: filter SET_FEATURES - XFER MODE from ATA pass thru
  o libata: sync SMART ioctls with ATA pass thru spec (T10/04-262r7)
  o libata: fix command queue leak when xlat_func fails
  o libata: SMART support via ATA pass-thru

Mark Lord:
  o [libata qstor] minor update per LKML comments

Tobias Lorenz:
  o [libata sata_promise] pdc20619 (PATA) support
  o libata-scsi: get-identity ioctl support

Re: [SATA] libata-dev queue updated

Andre Tomt wrote:
Jeff Garzik wrote:
Patch URL, BK URL, and changelog attached.
Recent changes:
* New sata_qstor driver.
* Turn on ATAPI by default.
* Change a couple unconditional use-the-hardware function calls to be 
callbacks instead.  Should have been this way originally.

* Most of C/H/S support.
* Fix bugs in ADMA driver.
* Support PCI MSI in AHCI driver.
* Support ATAPI in AHCI driver.
* Improve ATA passthru (a.k.a. SMART) support
How is the Marvell driver coming along? Did it stall? :-)
Yeah, it's stalled...
Jeff

-
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/

Re: [SATA] libata-dev queue updated

2005-02-19 Thread Andre Tomt

Jeff Garzik wrote:
Patch URL, BK URL, and changelog attached.
Recent changes:
* New sata_qstor driver.
* Turn on ATAPI by default.
* Change a couple unconditional use-the-hardware function calls to be 
callbacks instead.  Should have been this way originally.

* Most of C/H/S support.
* Fix bugs in ADMA driver.
* Support PCI MSI in AHCI driver.
* Support ATAPI in AHCI driver.
* Improve ATA passthru (a.k.a. SMART) support
How is the Marvell driver coming along? Did it stall? :-)
The propetiary source driver works, but its not like its universally 
available (I had to grab it from a different vendor..), "guaranteed" to 
work with future kernels, have a usable license, and so on.
-
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/

[SATA] libata-dev queue updated

Patch URL, BK URL, and changelog attached.
Recent changes:
* New sata_qstor driver.
* Turn on ATAPI by default.
* Change a couple unconditional use-the-hardware function calls to be 
callbacks instead.  Should have been this way originally.

* Most of C/H/S support.
* Fix bugs in ADMA driver.
* Support PCI MSI in AHCI driver.
* Support ATAPI in AHCI driver.
* Improve ATA passthru (a.k.a. SMART) support
BK users:

bk pull bk://gkernel.bkbits.net/libata-dev-2.6

Patch:
http://www.kernel.org/pub/linux/kernel/people/jgarzik/libata/2.6.11-rc4-bk6-libata-dev1.patch.bz2

This will update the following files:

 drivers/scsi/Kconfig |   26 +
 drivers/scsi/Makefile|3 
 drivers/scsi/ahci.c  |  101 -
 drivers/scsi/ata_adma.c  |  778 +++
 drivers/scsi/ata_piix.c  |4 
 drivers/scsi/libata-core.c   |  338 ++
 drivers/scsi/libata-scsi.c   |  701 --
 drivers/scsi/libata.h|7 
 drivers/scsi/pata_pdc2027x.c |  742 +
 drivers/scsi/sata_nv.c   |   10 
 drivers/scsi/sata_promise.c  |   92 -
 drivers/scsi/sata_qstor.c|  700 ++
 drivers/scsi/sata_sil.c  |   10 
 drivers/scsi/sata_sis.c  |   10 
 drivers/scsi/sata_svw.c  |   10 
 drivers/scsi/sata_sx4.c  |8 
 drivers/scsi/sata_uli.c  |   10 
 drivers/scsi/sata_via.c  |  213 ---
 drivers/scsi/sata_vsc.c  |   10 
 include/linux/ata.h  |   14 
 include/linux/libata.h   |   55 ---
 include/scsi/scsi.h  |3 
 22 files changed, 3442 insertions(+), 403 deletions(-)

through these ChangeSets:

:
  o [libata scsi] support 12-byte passthru CDB
  o [libata scsi] passthru CDB check condition processing
  o T10/04-262 ATA pass thru - patch

:
  o [libata sata_promise] support PATA ports on SATA controllers

:
  o [libata] add ->bmdma_{stop,status} hooks

Adam J. Richter:
  o ata_pci_remove_one used freed memory

Albert Lee:
  o [libata] CHS support: add CHS support to ata_scsi_verify_xlat(), 
ata_scsi_rw_xlat() and ata_scsiop_read_cap().
  o [libata] CHS support: reorganize read/write translation in 
ata_scsi_rw_xlat()
  o [libata] CHS support: rename vars (s/sector/block/) in 
ata_scsi_verify_xlat()
  o [libata] CHS support: detect C/H/S at IDENTIFY DEVICE time
  o [libata] CHS support: add definitions to headers
  o pdc2027x timing register bug fix
  o [libata pdc2027x] fix incorrect pio and mwdma masks
  o [libata pdc2027x] remove quirks and ROM enable
  o [libata] add driver for Promise PATA 2027x

Brad Campbell:
  o libata basic detection and errata for PATA->SATA bridges

Jeff Garzik:
  o [libata ahci] support PCI MSI interrupt vector
  o [libata adma] Add init code, fix CPB submission code
  o [libata ahci] finish ATAPI support
  o [libata adma] trivial whitespace cleanup
  o [libata dma] fix DMA mode config; add some more initialization code
  o [libata adma] add support for configuring PIO/DMA modes
  o [libata] do not call pci_disable_device() for certain errors
  o [libata] turn on ATAPI support
  o [libata sata_promise] merge Tobias Lorenz' pdc20619 patch, part 2
  o [libata] small cleanups
  o [libata] remove unused execute-device-diagnostic reset method
  o [libata] add new driver ata_adma
  o [libata sata_via] add support for VT6421 SATA
  o [libata sata_via] minor cleanups
  o [libata pdc2027x] update for upstream struct device conversion
  o [libata sata_promise] fix merge bugs
  o [libata] fix build breakage
  o [libata] fix SATA->PATA bridge detect compile breakage
  o [libata] fix printk warning

John W. Linville:
  o libata: fix command queue leak when xlat_func fails
  o libata: update ATA pass thru opcodes
  o libata: minor style changes in ata_scsi_pass_thru
  o libata: filter SET_FEATURES - XFER MODE from ATA pass thru
  o libata: sync SMART ioctls with ATA pass thru spec (T10/04-262r7)
  o libata: fix command queue leak when xlat_func fails
  o libata: SMART support via ATA pass-thru

Mark Lord:
  o sata_qstor: new basic driver for Pacific Digital

Tobias Lorenz:
  o [libata sata_promise] pdc20619 (PATA) support
  o libata-scsi: get-identity ioctl support

Re: [SATA] libata-dev queue updated

2005-02-19 Thread Andre Tomt

Jeff Garzik wrote:
Patch URL, BK URL, and changelog attached.
Recent changes:
* New sata_qstor driver.
* Turn on ATAPI by default.
* Change a couple unconditional use-the-hardware function calls to be 
callbacks instead.  Should have been this way originally.

* Most of C/H/S support.
* Fix bugs in ADMA driver.
* Support PCI MSI in AHCI driver.
* Support ATAPI in AHCI driver.
* Improve ATA passthru (a.k.a. SMART) support
How is the Marvell driver coming along? Did it stall? :-)
The propetiary source driver works, but its not like its universally 
available (I had to grab it from a different vendor..), guaranteed to 
work with future kernels, have a usable license, and so on.
-
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/

Re: [SATA] libata-dev queue updated

Andre Tomt wrote:
Jeff Garzik wrote:
Patch URL, BK URL, and changelog attached.
Recent changes:
* New sata_qstor driver.
* Turn on ATAPI by default.
* Change a couple unconditional use-the-hardware function calls to be 
callbacks instead.  Should have been this way originally.

* Most of C/H/S support.
* Fix bugs in ADMA driver.
* Support PCI MSI in AHCI driver.
* Support ATAPI in AHCI driver.
* Improve ATA passthru (a.k.a. SMART) support
How is the Marvell driver coming along? Did it stall? :-)
Yeah, it's stalled...
Jeff

-
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/

[SATA] libata-dev queue updated