Messages in this thread | | | Date | Thu, 25 May 2006 09:25:50 -0400 | From | Jeff Garzik <> | Subject | Re: 3ware 7500 not working in 2.6.16.18, 2.6.17-rc5 |
| |
Jan Kasprzak wrote: > Hi all, > > I have a 3ware 75xx P-ATA controller, which has been working in 2.6.15-rc2. > Today I have tried to upgrade to 2.6.16.18, and it cannot boot - the > controller cannot access the drives, with the attached messages. > I have also tried 2.6.17-rc5 with the same results. > > [...] > 3ware Storage Controller device driver for Linux v1.26.02.001. > GSI 18 sharing vector 0xB9 and IRQ 18 > ACPI: PCI Interrupt 0000:01:03.0[A] -> GSI 28 (level, low) -> IRQ 18 > scsi0 : 3ware Storage Controller > 3w-xxxx: scsi0: Found a 3ware Storage Controller at 0x8c00, IRQ: 18. > Vendor: 3ware Model: Logical Disk 0 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 1 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 2 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 3 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 4 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 5 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 6 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > Vendor: 3ware Model: Logical Disk 7 Rev: 1.2 > Type: Direct-Access ANSI SCSI revision: 00 > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back w/ FUA > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > sda: Write Protect is off > SCSI device sda: drive cache: write back w/ FUA > sda:<3>nommu_map_sg: overflow 2053d9000+4096 of device mask ffffffff > 3w-xxxx: tw_map_scsi_sg_data(): pci_map_sg() failed. > nommu_map_sg: overflow 2053d9000+4096 of device mask ffffffff > 3w-xxxx: tw_map_scsi_sg_data(): pci_map_sg() failed.
Can you narrow down which kernel version first introduces the breakage, between 2.6.15-rc2 and 2.6.16.x?
And we will need much more information on your platform, what patches (if any) you have applied, your .config, dmesg, etc.
Jeff
- 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/
| |