Comment 24 for bug 219393

Currently running on kubuntu live CD 8.04.

Mobo : P35C-DS3R (rev2.0) with latest BIOS (F11e)
( First version of bios are AWFULL , nothing worked correctly... )

I added "ata_ignore_hpa=0" at boot ... But it did not help :(

still have :

root@ubuntu:~# dmraid -ay
ERROR: isw device for volume "RAID0" broken on /dev/sdb in RAID set "isw_cdgibffddf_RAID0"
ERROR: isw: wrong # of devices in RAID set "isw_cdgibffddf_RAID0" [1/2] on /dev/sdb
ERROR: isw device for volume "Volume0" broken on /dev/sda in RAID set "isw_echgefjfjf_Volume0"
ERROR: isw: wrong # of devices in RAID set "isw_echgefjfjf_Volume0" [1/2] on /dev/sda

dmesg gives :

[ 365.835593] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
[ 365.835599] device-mapper: ioctl: error adding target to table
[ 365.836529] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
[ 365.836533] device-mapper: ioctl: error adding target to table
[ 381.580072] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
[ 381.580076] device-mapper: ioctl: error adding target to table
[ 381.580964] device-mapper: table: 254:0: linear: dm-linear: Device lookup failed
[ 381.580967] device-mapper: ioctl: error adding target to table

grepping in dmesg with "ata" , I noticed :

[ 0.000000] Kernel command line: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed boot=casper initrd=/casper/initrd.gz quiet splash -- ata_ignore_hpa=0 locale=fr_FR console-setup/layoutcode=fr console-setup/variantcode=oss
[ 86.016927] Memory: 3621848k/4194304k available (2164k kernel code, 45784k reserved, 1007k data, 364k init, 2751360k highmem)
[ 86.016935] .data : 0xc031d1bd - 0xc0418dc4 (1007 kB)
[ 89.211303] libata version 3.00 loaded.
[ 90.988408] ata1: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102100 irq 219
[ 90.988411] ata2: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102180 irq 219
[ 90.988412] ata3: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102200 irq 219
[ 90.988414] ata4: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102280 irq 219
[ 90.988416] ata5: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102300 irq 219
[ 90.988418] ata6: SATA max UDMA/133 abar m2048@0xfa102000 port 0xfa102380 irq 219
[ 91.307190] ata1: SATA link down (SStatus 0 SControl 300)
[ 91.945515] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 91.958141] ata2.00: HPA unlocked: 1250261615 -> 1250263728, native 1250263728
[ 91.958145] ata2.00: ATA-7: SAMSUNG HD642JJ, 1AA01109, max UDMA7
[ 91.958147] ata2.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 91.964528] ata2.00: configured for UDMA/133
[ 92.280638] ata3: SATA link down (SStatus 0 SControl 300)
[ 92.599800] ata4: SATA link down (SStatus 0 SControl 300)
[ 93.238126] ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 93.250737] ata5.00: HPA unlocked: 1250261615 -> 1250263728, native 1250263728
[ 93.250740] ata5.00: ATA-7: SAMSUNG HD642JJ, 1AA01109, max UDMA7
[ 93.250743] ata5.00: 1250263728 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 93.257139] ata5.00: configured for UDMA/133

I have numerous dmesg like this one :

[ 195.966487] sda: rw=0, want=2500509696, limit=1250263728
[ 195.966491] attempt to access beyond end of device

I put the full dmesg log in attachment.

Thanks for help. All ideas are welcome :)