Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[1qay beer]

Hello,
Dear Alan Cox,
Dear Jeff Garzik,

Everyone a happy new year!

We are in stable Kernel 2.6.14.5, year 2006.
Since 1997 people asking on several list for a functional PDC202XX Driver.
Since some years I spend hours and hours finding a solution for a stable driver. 
(PDC20269/Promise Ultra133 TX2)
There seem to be none.

There are two Solution:
-The IDE Driver (pdc202xx_new) has still problems with "DMA Timeout".
-The Libata Driver (pata_pdc2027x) seems to be still somewhat experimental.

Unfortunatly I'am not a kernel developper else there would be probably already
a solution ;-)

So what is the Solution for the PDC20269 Ultra ATA Controller?
I would mark this bold on the wishlist for 2006 ;-)

Thanx


=========================================================
Anyone wants a small summary of the halfworking solutions

Way 1 - IDE pdc202xx_new  --> /dev/hdxx )
------------------------------------------
  Just compile your kernel with a module (or built in):
  $make menuconfig
       -> Device Drivers                                                                                 
         -> ATA/ATAPI/MFM/RLL support                                                                     
           -> ATA/ATAPI/MFM/RLL support (IDE [=y])                                                       
             -> Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support (BLK_DEV_IDE [=y])                    
               -> PCI IDE chipset support (BLK_DEV_IDEPCI [=y])                                           
                 -> Generic PCI bus-master DMA support (BLK_DEV_IDEDMA_PCI
		   ->PROMISE PDC202{68|69|70|71|75|76|77} support
   $make-kpkg kernel_image
Problems:)
hde: dma_timer_expiry: dma status == 0x60
 hde: DMA timeout retry
 PDC202XX: Primary channel reset.
 hde: timeout waiting for DMA
 hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
 ide: failed opcode was: unknown
 hde: drive not ready for command
 hde: status error: status=0x50 { DriveReady SeekComplete }
 ide: failed opcode was: unknown
 hde: no DRQ after issuing MULTWRITE_EXT
 hde: status error: status=0x50 { DriveReady SeekComplete }
 ide: failed opcode was: unknown
 hde: no DRQ after issuing MULTWRITE_EXT
 hde: status error: status=0x50 { DriveReady SeekComplete }
 ide: failed opcode was: unknown
 hdf: DMA disabled
 PDC202XX: Primary channel reset.
 hde: no DRQ after issuing MULTWRITE_EXT
 ide2: reset: success
 hde: dma_timer_expiry: dma status == 0x20
 hde: DMA timeout retry
 PDC202XX: Primary channel reset.
 hde: timeout waiting for DMA

or similar


Way 2 - libata  (emulates SCSI device) --> /dev/sdxx  )
-------------------------------------------------------
     Get the latest libata patch/kernel
          http://www.kernel.org/pub/linux/kernel/people/jgarzik/patchkits/2.6/2.6.15-rc4-libata1.patch.bz2
ftp://ftp.kernel.org/pub/linux/kernel/v2.6/testing/linux-2.6.15-rc5.tar.bz2
       ....(untar)...
       $make menuconfig
        -> Device Drivers                                                                                  
         -> SCSI device support                                                                           
           -> SCSI device support (SCSI [=m])                                                             
             -> SCSI low-level drivers                                                                    
               -> Serial ATA (SATA) support (SCSI_SATA [=m])  
                  ->SCSI_PATA_PDC2027X
  
        Enable PATA as suggested here:
        -http://lkml.org/lkml/2004/8/1/100
        -http://seclists.org/lists/linux-kernel/2005/May/0503.html
           In include/linux/libata.h
              #define ATA_ENABLE_ATAPI /* undefine to disable ATAPI support */
              #define ATA_ENABLE_PATA /* define to enable PATA support in some
                                       * low-level drivers */ 
         
        Compile and pray!

        With some harddisk it works without problem (seagate 7200.8)
        With others Maxtor Maxline III it's not working at all:
        Kernel Panics even at boottime:
         ATA1: Abnormal status 0x8 on port 0xD...........
         or Lost Interrupts...
         or the drivers seems to be loaded (lsmod) but there are no
            harddiscs under /prov/scsi/... /dev/sdxx



-- 
_______________________________________________
The coolest e-mail address on the web and it’s FREE!  Sign-up today for Beer Mail @ beer.com.

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alistair John Strachan]

On Sunday 01 January 2006 17:39, 1qay beer wrote:
> Hello,
> Dear Alan Cox,
> Dear Jeff Garzik,
>
> Everyone a happy new year!
>
> We are in stable Kernel 2.6.14.5, year 2006.
> Since 1997 people asking on several list for a functional PDC202XX Driver.
> Since some years I spend hours and hours finding a solution for a stable
> driver. (PDC20269/Promise Ultra133 TX2)
> There seem to be none.
>
> There are two Solution:
> -The IDE Driver (pdc202xx_new) has still problems with "DMA Timeout".
> -The Libata Driver (pata_pdc2027x) seems to be still somewhat experimental.
>
> Unfortunatly I'am not a kernel developper else there would be probably
> already a solution ;-)
>
> So what is the Solution for the PDC20269 Ultra ATA Controller?
> I would mark this bold on the wishlist for 2006 ;-)

I own this controller and it's been working with the kernel driver since 
2002.. I'm not sure what you expect people to do about clearly faulty 
hardware. Just buy a new one?

-- 
Cheers,
Alistair.

'No sense being pessimistic, it probably wouldn't work anyway.'
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Joshua Kwan]

On 01/01/2006 09:39 AM, 1qay beer wrote:
> Since 1997 people asking on several list for a functional PDC202XX Driver.
> Since some years I spend hours and hours finding a solution for a stable driver. 
> (PDC20269/Promise Ultra133 TX2)
> There seem to be none.

It's been working for me since 2003 as well on a production box, even
through migration to 2.6.

Get a new board.

-- 
Joshua Kwan

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Pasi Kärkkäinen]

On Sun, Jan 01, 2006 at 01:22:41PM -0800, Joshua Kwan wrote:
> On 01/01/2006 09:39 AM, 1qay beer wrote:
> > Since 1997 people asking on several list for a functional PDC202XX Driver.
> > Since some years I spend hours and hours finding a solution for a stable driver. 
> > (PDC20269/Promise Ultra133 TX2)
> > There seem to be none.
> 
> It's been working for me since 2003 as well on a production box, even
> through migration to 2.6.
> 
> Get a new board.
> 

I can confirm this too.

Works 100% OK for me too, in fact has worked for many years already.. currently
using 2.6 series. *knocking wood* :)

-- Pasi Kärkkäinen
       
                                   ^
                                .     .
                                 Linux
                              /    -    \
                             Choice.of.the
                           .Next.Generation.

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Barry K. Nathan]

Add my voice to the chorus of people who are having no problems with
their PDC20269's, for several years now (since 2002, I think -- and I
didn't have problems before then, I just didn't have a PDC20269
before).
--
-Barry K. Nathan <barryn@pobox.com>

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

On Sul, 2006-01-01 at 13:39 -0400, 1qay beer wrote:
> Hello,
> Dear Alan Cox,
> Dear Jeff Garzik,
> 
> Everyone a happy new year!

Ditto

> -The IDE Driver (pdc202xx_new) has still problems with "DMA Timeout".

The legacy IDE layer is handled by Bartlomiej so you should direct your
enquiries and requests to him and the linux-ide list.

> -The Libata Driver (pata_pdc2027x) seems to be still somewhat experimental.

and while I'm working on libata pata a fair bit the pdc202xx driver is
the excellent work of Albert Lee.

The 20269 has always shown up as a problem for some users but not for
most. Nobody ever really got to the bottom of it to be honest. Please
send Albert your reports about which hardware works and which fails
(<albertcc@tw.ibm.com>) as it may be very useful. In particular the
drive that works appears to be UDMA 100 and the failing one UDMA 133

Alan

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[1qay beer]

Thanx to everyone.

The Controller Board is fine.

What i noticed is that if you have the controller in a 
full PCI Bus Master Slot without IRQ sharing - the Controller works better
than in shared slot.

Generally the first PCI Slot is shared with AGP.
The Second is normaly complet "IRQ share free" and the way to go.

Slot 4/5 is mostly shared (as long you have that many slots).
Slot 3 may be shared with onboard stuff like sound, onboard graphic, usb or others.

The Board is now working without Problems.
What I did is Remove the IDE-Driver from the Kernel and use the Libata Driver,
which now even works with S.M.A.R.T. without Problem.

I removed the UDMA-133 Drive and have now only connected UDMA-100 Drives to the Controller. The UDMA-133 is connected to the Motherboard now.

Mostly Maxtor produced UDMA-133 Drives which are going to fail in half a year anyway ;-(.

Now i use only Seagate Drives which have 5 Years warranty and I never had Problem with them. (too bad maxtor is part of seagate now...I hope they will not fail in their good quality)

Cheers

----- Original Message -----
From: "Alan Cox" <alan@lxorguk.ukuu.org.uk>
To: "1qay beer" <1qay@beer.com>
Subject: Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver	for PDC202XX
Date: Mon, 02 Jan 2006 22:35:51 +0000

> 
> On Sul, 2006-01-01 at 13:39 -0400, 1qay beer wrote:
> > Hello,
> > Dear Alan Cox,
> > Dear Jeff Garzik,
> >
> > Everyone a happy new year!
> 
> Ditto
> 
> > -The IDE Driver (pdc202xx_new) has still problems with "DMA Timeout".
> 
> The legacy IDE layer is handled by Bartlomiej so you should direct your
> enquiries and requests to him and the linux-ide list.
> 
> > -The Libata Driver (pata_pdc2027x) seems to be still somewhat experimental.
> 
> and while I'm working on libata pata a fair bit the pdc202xx driver is
> the excellent work of Albert Lee.
> 
> The 20269 has always shown up as a problem for some users but not for
> most. Nobody ever really got to the bottom of it to be honest. Please
> send Albert your reports about which hardware works and which fails
> (<albertcc@tw.ibm.com>) as it may be very useful. In particular the
> drive that works appears to be UDMA 100 and the failing one UDMA 133
> 
> Alan


-- 
_______________________________________________
The coolest e-mail address on the web and it’s FREE!  Sign-up today for Beer Mail @ beer.com.

Re: [patch 8/8] lock validator: add s390 to supported options

[Andrew Morton]

Heiko Carstens <heiko.carstens@de.ibm.com> wrote:
>
>  config DEBUG_SPINLOCK_ALLOC
>  	bool "Spinlock debugging: detect incorrect freeing of live spinlocks"
> -	depends on DEBUG_SPINLOCK && X86
> +	depends on DEBUG_SPINLOCK && (X86 || S390)

Can we please stomp this out before it starts to look like
CONFIG_FRAME_POINTER?

We should define CONFIG_ARCH_SUPPORTS_LOCKDEP down in
arch/[i386|x86_64|s390]/Kconfig and use that in lib/Kconfig.debug.

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Erik Ohrnberger]

Good thing that I googled groups this thread.  I thought that I was the only
one that had this problem.

I've gone from three 133TX2 controllers, 5 80-GB drives in a RAID5, and 3
drives in drive linking (all managed by EVMS) to 2 controllers with just the
3 drive linking drives, and still get the mda_expiry error messages.

Last thing that I've done is to force the data drives to use UDMA2, with the
hope that it'll work around this problem.  May be working, as I've not had
an error in 24 hours of running the system, but then I'm not accessing the
drives either.  They are dismounted to protect the data.  Didn't matter
before, got the errors with just the smartd daemon checking up on the drive
health, but so far so good.

Regardless, count me as another one of the interested parties for a cure.
I've read the thread, and will prepare two current kernels, one using the
PDC202XX_NEW and one using the PDC202XX_OLD configuration options.  I'm
hoping that the PDC202XX_OLD will also resolve this issue.

Any further advice on how to work around this would be greatly appreciated.

Erik.

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

Ar Llu, 2006-06-19 am 18:18 -0400, ysgrifennodd Erik Ohrnberger:
> Regardless, count me as another one of the interested parties for a cure.
> I've read the thread, and will prepare two current kernels, one using the
> PDC202XX_NEW and one using the PDC202XX_OLD configuration options.  I'm
> hoping that the PDC202XX_OLD will also resolve this issue.

Bartlomiej is the old IDE layer maintainer. I would direct any enquiries
to him about those drivers.

> Any further advice on how to work around this would be greatly appreciated.

2.6.17 with the libata pata patch from
http://zeniv.linux.org.uk/~alan/IDE has a Promise driver for the PDC
20268 and higher that was written by Albert Lee. There is also a test
driver for the older chips (20265 etc).

To try that build 2.6.17 with the patch and then say "N" to CONFIG_IDE,
"Y" to the SATA options under SCSI and the right controller. It will
move your disks to /dev/sda /dev/sdb etc as it uses the SCSI layer.

Alan

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Erik Ohrnberger]

Alan,
    I thank you persaonlly for these pointers.

    Erik.

On Tue, June 20, 2006 04:20, Alan Cox wrote:
> Ar Llu, 2006-06-19 am 18:18 -0400, ysgrifennodd Erik Ohrnberger:
>> Regardless, count me as another one of the interested parties for a
>> cure.
>> I've read the thread, and will prepare two current kernels, one using
>> the
>> PDC202XX_NEW and one using the PDC202XX_OLD configuration options.  I'm
>> hoping that the PDC202XX_OLD will also resolve this issue.
>
> Bartlomiej is the old IDE layer maintainer. I would direct any enquiries
> to him about those drivers.
>
>> Any further advice on how to work around this would be greatly
>> appreciated.
>
> 2.6.17 with the libata pata patch from
> http://zeniv.linux.org.uk/~alan/IDE has a Promise driver for the PDC
> 20268 and higher that was written by Albert Lee. There is also a test
> driver for the older chips (20265 etc).
>
> To try that build 2.6.17 with the patch and then say "N" to CONFIG_IDE,
> "Y" to the SATA options under SCSI and the right controller. It will
> move your disks to /dev/sda /dev/sdb etc as it uses the SCSI layer.
>
> Alan
>

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Erik Ohrnberger]

Hate to be a bother, but I think I must have botched something.

Here is what I did:
Downloaded kernel code.  
Applied the IDE patches (http://zeniv.linux.org.uk/~alan/IDE)
	(had to apply the change from ata_data_xfer calls to ops->data_xfer
	(no big deal, I speak C )

CONFIG_IDE is set to N
Device Drives\SCSI device support\Probe all LUNs on each SCSI device: Y
Device Drives\SCSI device support\Serial ATA (SATA) support: Y
Device Drives\SCSI device support\Serial ATA (SATA) support\NVIDIA SATA
support: Y
Device Drives\SCSI device support\Serial ATA (SATA) support\Promise SATA
TX2/TX4 Support: Y
Device Drives\SCSI device support\Serial ATA (SATA) support\Promise SATA SX4
Support: Y
Device Drives\SCSI device support\Older Promise PATA controller Support
(Raving Lunatic): Y
Device Drives\SCSI device support\Legacy ISA PATA support (Raving Lunatic):
Y
Device Drives\SCSI device support\Older Promise PATA controller support
(Raving Lunatic): Y

Build the kernel, put it in /boot etc. and boot it.  The kernel finds the
motherboard IDE controllers and recognizes the two hard drives and the DVD
ROM drive there, but it does not appear to find the two Promise 20269
controllers.  What'd I do wrong?  Should I have applied the kernel-2.6.17
patches from kernel.org before the http://zeniv.linux.org.uk/~alan/IDE
patches?

If I ATA/ATAPI/MFM/RLL support\PROMISE PDC202{68|69|70|71|75|76|77} support:
Y
Then the kernel find the controllers, but uses that failing driver rather
than the SCSI/PATA driver.  Yea, well duhh.  So I can't turn that on.

lspci:
00:00.0 Host bridge: nVidia Corporation nForce2 AGP (different version?)
(rev c1)
00:00.1 RAM memory: nVidia Corporation nForce2 Memory Controller 0 (rev c1)
00:00.2 RAM memory: nVidia Corporation nForce2 Memory Controller 4 (rev c1)
00:00.3 RAM memory: nVidia Corporation nForce2 Memory Controller 3 (rev c1)
00:00.4 RAM memory: nVidia Corporation nForce2 Memory Controller 2 (rev c1)
00:00.5 RAM memory: nVidia Corporation nForce2 Memory Controller 5 (rev c1)
00:01.0 ISA bridge: nVidia Corporation nForce2 ISA Bridge (rev a4)
00:01.1 SMBus: nVidia Corporation nForce2 SMBus (MCP) (rev a2)
00:08.0 PCI bridge: nVidia Corporation nForce2 External PCI Bridge (rev a3)
00:09.0 IDE interface: nVidia Corporation nForce2 IDE (rev a2)
00:1e.0 PCI bridge: nVidia Corporation nForce2 AGP (rev c1)
01:06.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02)
01:07.0 Mass storage controller: Promise Technology, Inc. 20269 (rev 02)
01:0a.0 Ethernet controller: Accton Technology Corporation SMC2-1211TX (rev
10)
02:00.0 VGA compatible controller: ATI Technologies Inc Radeon R200 QM
[Radeon 9100]

> -----Original Message-----
> From: Erik Ohrnberger [mailto:Erik@EchoHome.org] 
> Sent: Tuesday, June 20, 2006 8:52 AM
> To: Alan Cox
> Cc: linux-kernel@vger.kernel.org
> Subject: RE: Wish for 2006 to Alan Cox and Jeff Garzik: A 
> functional Driver for PDC202XX
> 
> Alan,
>     I thank you persaonlly for these pointers.
> 
>     Erik.
> 
> On Tue, June 20, 2006 04:20, Alan Cox wrote:
> > Ar Llu, 2006-06-19 am 18:18 -0400, ysgrifennodd Erik Ohrnberger:
> >> Regardless, count me as another one of the interested 
> parties for a 
> >> cure.
> >> I've read the thread, and will prepare two current 
> kernels, one using 
> >> the PDC202XX_NEW and one using the PDC202XX_OLD configuration 
> >> options.  I'm hoping that the PDC202XX_OLD will also resolve this 
> >> issue.
> >
> > Bartlomiej is the old IDE layer maintainer. I would direct any 
> > enquiries to him about those drivers.
> >
> >> Any further advice on how to work around this would be greatly 
> >> appreciated.
> >
> > 2.6.17 with the libata pata patch from 
> > http://zeniv.linux.org.uk/~alan/IDE has a Promise driver for the PDC
> > 20268 and higher that was written by Albert Lee. There is 
> also a test 
> > driver for the older chips (20265 etc).
> >
> > To try that build 2.6.17 with the patch and then say "N" to 
> > CONFIG_IDE, "Y" to the SATA options under SCSI and the right 
> > controller. It will move your disks to /dev/sda /dev/sdb 
> etc as it uses the SCSI layer.
> >
> > Alan
> >
> 

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

Ar Maw, 2006-06-20 am 21:19 -0400, ysgrifennodd Erik Ohrnberger:
> Downloaded kernel code.  
> Applied the IDE patches (http://zeniv.linux.org.uk/~alan/IDE)
> 	(had to apply the change from ata_data_xfer calls to ops->data_xfer
> 	(no big deal, I speak C )

What tree are you working against. The patches I put up are versus
2.6.17 not -mm. Also check in include/linux/libata.h that
ATA_ENABLE_PATA is defined (its down with the debug options). The patch
should have enabled it however.

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Erik Ohrnberger]

On Wed, June 21, 2006 06:51, Alan Cox wrote:
> Ar Maw, 2006-06-20 am 21:19 -0400, ysgrifennodd Erik Ohrnberger:
>> Downloaded kernel code.
>> Applied the IDE patches (http://zeniv.linux.org.uk/~alan/IDE)
>> 	(had to apply the change from ata_data_xfer calls to ops->data_xfer
>> 	(no big deal, I speak C )
>
> What tree are you working against. The patches I put up are versus
> 2.6.17 not -mm. Also check in include/linux/libata.h that
> ATA_ENABLE_PATA is defined (its down with the debug options). The patch
> should have enabled it however.
>
I downloaded linux-2.6.17.tar.gz from kernel.org, when extraceted created
linux-2.6.17 directory.  I zmore'd the patch-2.6.17-rc4-ide1.gz file and
noticed that it was working against linux-2.6.17-rc4-ide1, so I renamed
the linux-2.6.17 to linux-2.6.17-rc4-ide1 and zcat | patch -p0.
(Did I do this wrong?  Seemed to apply except for the two function calls
that I had to edit by hand)

Checking include/linux/libata.h reveals that: ATA_ENABLE_PATA is defined.

Thanks for all the help.  I really appreciate it, but hope that it's not
taking up too much of your time.

     Erik.

RE: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

Ar Mer, 2006-06-21 am 09:09 -0400, ysgrifennodd Erik Ohrnberger:
> noticed that it was working against linux-2.6.17-rc4-ide1, so I renamed
> the linux-2.6.17 to linux-2.6.17-rc4-ide1 and zcat | patch -p0.

Get linux-2.6.17-ide1.gz instead of the rc4 patch

> Thanks for all the help.  I really appreciate it, but hope that it's not
> taking up too much of your time.

Not a problem. I'd like to get to the bottom of the problems you are
seeing and this all helps.

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Mike Snitzer]

On 6/21/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Mer, 2006-06-21 am 09:09 -0400, ysgrifennodd Erik Ohrnberger:
> > noticed that it was working against linux-2.6.17-rc4-ide1, so I renamed
> > the linux-2.6.17 to linux-2.6.17-rc4-ide1 and zcat | patch -p0.
>
> Get linux-2.6.17-ide1.gz instead of the rc4 patch

I have a PDC20267 and tried out 2.6.17 + linux-2.6.17-ide1.gz  The
resulting pata_pdc202xx_old module didn't initialize the controller on
boot (via initrd).  Is there some other CONFIG option or linux cmdline
that should be used?

thanks.

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

Ar Mer, 2006-06-21 am 09:34 -0400, ysgrifennodd Mike Snitzer:
> I have a PDC20267 and tried out 2.6.17 + linux-2.6.17-ide1.gz  The
> resulting pata_pdc202xx_old module didn't initialize the controller on
> boot (via initrd).  Is there some other CONFIG option or linux cmdline
> that should be used?

No it should find it as soon as you load the module. If the device is
not the primary IDE controller (hda-hdd) you can set CONFIG_IDE = y,
include drivers for your other controller and get some debug info.

Usually "it didnt initialize" reports are from people with mixed old/new
IDE in their kernel or initrd, or initrds missing the required modules.

Stick a printk in pdc_init before the pci_register_driver call and
you'll know for sure if the module is getting loaded. If it is then send
me an lspci and I'll have a deeper look


Alan

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Mike Snitzer]

On 6/21/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Mer, 2006-06-21 am 09:34 -0400, ysgrifennodd Mike Snitzer:
> > I have a PDC20267 and tried out 2.6.17 + linux-2.6.17-ide1.gz  The
> > resulting pata_pdc202xx_old module didn't initialize the controller on
> > boot (via initrd).  Is there some other CONFIG option or linux cmdline
> > that should be used?
>
> No it should find it as soon as you load the module. If the device is
> not the primary IDE controller (hda-hdd) you can set CONFIG_IDE = y,
> include drivers for your other controller and get some debug info.
>
> Usually "it didnt initialize" reports are from people with mixed old/new
> IDE in their kernel or initrd, or initrds missing the required modules.
>
> Stick a printk in pdc_init before the pci_register_driver call and
> you'll know for sure if the module is getting loaded. If it is then send
> me an lspci and I'll have a deeper look

The PDC20267 is the primary controller, I do not have CONFIG_IDE set.
The issue with my initrd was mkinitrd --with=pata_pdc202xx_old didn't
include sd_mod; setting scsi_hostadapter accordingly in modprobe.conf
took care of this.

Once the kernel booted the system was seemingly starting without any
problems until various services tried to write files to the root
filesystem.  Each write attempt resulted in a "Read-only filesystem"
error yet all filesystems were mounted read-write.

The kernel had a ton of errors:

Buffer I/O error on device sda3, logical block 4869508
lost page write due to I/O error on sda3
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
ata1: status=0x51 { DriveReady SeekComplete Error }
ata1: error=0x84 { DriveStatusError BadCRC }
sd 0:0:0:0: SCSI error: return code = 0x8000002
sda: Current: sense key: Aborted Command
    Additional sense: Scsi parity error
Info fld=0x27a3f9b

lspci output is:

00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM
Controller/Host-Hub Interface (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated
Graphics Controller (rev 02)
00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #1 (rev 02)
00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #2 (rev 02)
00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB
UHCI Controller #4 (rev 02)
00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2
EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2)
00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC
Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE
Controller (rev 02)
00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus
Controller (rev 02)
00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER
(ICH5/ICH5R) AC'97 Audio Controller (rev 02)
01:01.0 Unknown mass storage controller: Promise Technology, Inc.
PDC20267 (FastTrak100/Ultra100) (rev 02)
01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet
Controller (rev 02)

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Alan Cox]

Ar Mer, 2006-06-21 am 11:20 -0400, ysgrifennodd Mike Snitzer:
> ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
> ata1: status=0x51 { DriveReady SeekComplete Error }
> ata1: error=0x84 { DriveStatusError BadCRC }

Thats a speed mistune somewhere in the code. 

Can you send me an lspci -vxx and the information on the drive (or
dmesg) with a "normal" kernel boot and I'll hunt it down.


Alan

Re: Wish for 2006 to Alan Cox and Jeff Garzik: A functional Driver for PDC202XX

[Mike Snitzer]

[-- Attachment #1: Type: text/plain, Size: 2700 bytes --]

On 6/21/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Ar Mer, 2006-06-21 am 11:20 -0400, ysgrifennodd Mike Snitzer:
> > ata1: translated ATA stat/err 0x51/84 to SCSI SK/ASC/ASCQ 0xb/47/00
> > ata1: status=0x51 { DriveReady SeekComplete Error }
> > ata1: error=0x84 { DriveStatusError BadCRC }
>
> Thats a speed mistune somewhere in the code.
>
> Can you send me an lspci -vxx and the information on the drive (or
> dmesg) with a "normal" kernel boot and I'll hunt it down.

Please see attached for the lspci -vxx output.

Here is the the relevant IDE info from dmesg:

 ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
PDC20267: IDE controller at PCI slot 0000:01:01.0
ACPI: PCI Interrupt Link [LNKG] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:01:01.0[A] -> Link [LNKG] -> GSI 10 (level,
low) -> IRQ 10
PDC20267: chipset revision 2
PDC20267: ROM enabled at 0x40000000
PDC20267: 100% native mode on irq 10
PDC20267: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode.
    ide0: BM-DMA at 0xdf00-0xdf07, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0xdf08-0xdf0f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: SAMSUNG SP0401N, ATA DISK drive
ide0 at 0xdef0-0xdef7,0xdeea on irq 10
Probing IDE interface ide1...
ICH5: IDE controller at PCI slot 0000:00:1f.1
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 5
PCI: setting IRQ 5 as level-triggered
ACPI: PCI Interrupt 0000:00:1f.1[A] -> Link [LNKC] -> GSI 5 (level,
low) -> IRQ 5
ICH5: chipset revision 2
ICH5: not 100% native mode: will probe irqs later
    ide2: BM-DMA at 0xffa8-0xffaf, BIOS settings: hde:DMA, hdf:pio
Probing IDE interface ide2...
hde: GCR-8483B, ATAPI CD/DVD-ROM drive
ide2 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide1...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 128KiB
hda: Host Protected Area detected.
        current capacity is 78125000 sectors (40000 MB)
        native  capacity is 78242976 sectors (40060 MB)
hda: Host Protected Area disabled.
hda: 78242976 sectors (40060 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
hda: cache flushes supported
 hda: hda1 hda2 hda3


also smartctl info:

=== START OF INFORMATION SECTION ===
Device Model:     SAMSUNG SP0401N
Serial Number:    S004J10Y647557
Firmware Version: TJ100-28
User Capacity:    40,060,403,712 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Wed Jun 21 13:45:56 2006 EDT
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

[-- Attachment #2: lspci.txt.gz --]
[-- Type: application/x-gzip, Size: 1484 bytes --]