From: Jeff Garzik <jeff@garzik.org>
To: Jan Kasprzak <kas@fi.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 3ware 7500 not working in 2.6.16.18, 2.6.17-rc5
Date: Thu, 25 May 2006 09:25:50 -0400 [thread overview]
Message-ID: <4475B05E.5080101@garzik.org> (raw)
In-Reply-To: <20060525122240.GG19612@fi.muni.cz>
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
next prev parent reply other threads:[~2006-05-25 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 12:22 3ware 7500 not working in 2.6.16.18, 2.6.17-rc5 Jan Kasprzak
2006-05-25 12:35 ` Jan Kasprzak
2006-05-25 13:25 ` Jeff Garzik [this message]
2006-05-25 13:39 ` Jan Kasprzak
[not found] <6gn8D-4AV-13@gated-at.bofh.it>
2006-05-26 2:03 ` Robert Hancock
2006-05-26 10:08 ` Jan Kasprzak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4475B05E.5080101@garzik.org \
--to=jeff@garzik.org \
--cc=kas@fi.muni.cz \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.