Goodmorning.
My name's Mauro Ziliani from Parma ITALY.
I use two disk Seagate ST3808110AS with an Sil3114 SATA controller.
The first disk is sdb and the second is sdc.
I configured a RAID1 software mirror onto this two disk where sdb1 is
the master disk for RAID.
I often receive the following
Mauro Ziliani wrote:
Dec 11 00:47:27 mercurio kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr 0x28 action 0x0
Dec 11 00:47:27 mercurio kernel: ata1.00: (BMDMA stat 0x60)
Dec 11 00:47:27 mercurio kernel: ata1.00: tag 0 cmd 0x25 Emask 0x1 stat
0x51 err 0x4 (device error)
Dec 11 00:47:27
Uwe Koziolek wrote:
The SiS966/966L has different PCI-IDs for native mode and AHCI mode.
The SiS966 supports four SATA ports only in native mode.
Added additional PCI-ID 0x0183 for SiS965/965L.
this patch is based on the code from David Wang from SiS Corporation published
on SiS Website.
Sylvain Munaut wrote:
This patch adds initial libata support for the Freescale
MPC5200 integrated IDE controller.
Signed-off-by: Sylvain Munaut [EMAIL PROTECTED]
---
Hi Jeff,
There you go ;) Hopefully this one is the good one.
applied, thanks
-
To unsubscribe from this list: send the line
Andrew Morton wrote:
[ 231.948000] SCSI device sda: 195371568 512-byte hdwr sectors (100030 MB)
[ 232.232000] ata1.00: configured for UDMA/33
[ 232.404000] WARNING (1) at arch/i386/mm/highmem.c:47 kmap_atomic()
It's using KM_USER0 from softirq.
I thought that was OK if it was
Hi,
I´m using the OS Debian 3.1rc1 and Kernel 2.4.27-2-386, but I need help,
when I execute the backup script´s, the hardware can´t read and writer
in the HDD (30GB) SATA.
The backup is accomplished of a disk Sata for another Sata of same model
and
mark.
My hardware are: Attached
Hi,
I'm having problems booting from a SATA disk with 2.6.19.
Grub loads fine, but when the kernel boots, it *sometimes* ends up with
VFS: Cannot open root device sda5 or unknown-block(0,0).
This issue appears to be identical with the one reported in
http://lkml.org/lkml/2006/10/19/327 except
On 12/11/06, Kasimir Müller [EMAIL PROTECTED] wrote:
Hi Tejun,
I have tested your patches with the vanilla 2.6.18.1 - Kernel and it works like
a charm.
I have spent hours of copying, reading and deleting data to a software-raid-5
on a Machine with
Mainboard: Elitegroup K8T890-A
Prozessor:
Matthew Wilcox wrote:
Some of the drivers (AHCI was mentioned to me as a culprit) take a long
time to discover all the devices attached to them. Even for ones which
are relatively quick, if you put a lot of them in a machine, it will
take a long time in aggregate. This can be fixed by adding
On Mon, Dec 11, 2006 at 10:58:06AM -0500, Jeff Garzik wrote:
The time-consuming portion already takes place in a thread. Do you mean
multiple threads? Or, ATA's scan is in one thread, while work continues
in other threads?
Patch seems sane, provided that I am educated a bit :)
Each host
Matthew Wilcox wrote:
Some of the drivers (AHCI was mentioned to me as a culprit) take a long
time to discover all the devices attached to them. Even for ones which
are relatively quick, if you put a lot of them in a machine, it will
take a long time in aggregate. This can be fixed by adding
Fernando Faria Mariano wrote:
Dec 2 02:26:11 localhost kernel: SCSI device sda: 312581808 512-byte hdwr
sectors (160042 MB)
Dec 2 02:26:11 localhost kernel: sda: Write Protect is off
Dec 2 02:26:11 localhost kernel: sda: Mode Sense: 00 3a 00 00
Dec 2 02:26:11 localhost kernel: SCSI
Hello,
Steve Graham wrote:
My name is Steve Graham and I work for a small
startup. Our company is developing a server board
with the Silicon Images 3512 and we are getting some
strange lockups during high levels of disk activity.
The test I'm currently running to cause the problem is
to
[EMAIL PROTECTED] wrote:
Hello,
I recently upgraded my system and I have an Asus P5W DH Deluxe
motherboard. It has an Intel ICH7 chipset where the second SATA
connector is used for a Sil4723 hardware RAID device. The Sil4723 has
two SATA ports using the shared ICH7 port.
I have one
Two subtle hotplug related bugs are found.
* SCSI didn't use to issue commands to devices in SDEV_CANCEL state
but now it does. For ATA devices, it means that SYNCHRONIZE_CACHE
is issued even after libata tells SCSI midlayer that the SCSI device
is offline now. When devices are swapped,
It is wrong to configure SCSI device according to disabled ATA device.
Use regular ata_scsi_find_dev() instead of the underbarred version in
ata_scsi_slave_config().
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/libata-scsi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi
How did this go? I doubt I'm the only one who fell afoul of the has linux
drivers implication on initio's website...
I know its early days, but any idea when this might be ready for production?
Regards thanks,
--
Matthias Urlichs wrote:
libata driver will follow, just needs a test
On Mon, Dec 11, 2006 at 11:18:17AM -0500, Jeff Garzik wrote:
ACK. I tried to apply the patch, but git-applymbox choked on every
single file modified. Quite possibly, its due to a whitespace cleanup
in Alan territory.
If you would either (a) wait several hours for libata-dev.git#upstream
On Mon, Dec 11, 2006 at 10:02:40PM -0700, Matthew Wilcox wrote:
On Mon, Dec 11, 2006 at 11:18:17AM -0500, Jeff Garzik wrote:
ACK. I tried to apply the patch, but git-applymbox choked on every
single file modified. Quite possibly, its due to a whitespace cleanup
in Alan territory.
piix_init_one() allocates host private data which should be freed by
piix_host_stop(). ich_pata_ops wasn't converted to piix_host_stop()
while merging, leaking 4 bytes on driver detach. Fix it.
This was spotted using Kmemleak by Catalin Marinas.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
Cc:
Benjamin Herrenschmidt wrote:
Could that be related to the fix
[PATCH] libata: fix oops with sparsemem
That Arnd Bergmann just posted ? I'm copying it below in case you
haven't seen it.
Seems to be the same problem to me. I'll reply in the original thread.
Thanks.
--
tejun
-
To
Calling sg_init_one() with NULL buf causes oops on certain
configurations. Don't initialize sg in ata_exec_internal() if
DMA_NONE and make the function complain if @buf is NULL when dma_dir
isn't DMA_NONE. While at it, fix comment.
The problem is discovered and initial patch was submitted by
On Mon, 11 Dec 2006 22:26:25 +0900
Tejun Heo [EMAIL PROTECTED] wrote:
piix_init_one() allocates host private data which should be freed by
piix_host_stop(). ich_pata_ops wasn't converted to piix_host_stop()
while merging, leaking 4 bytes on driver detach. Fix it.
This was spotted using
Tejun Heo wrote:
I'll follow up with conversion to ata_do_simple_cmd().
The current situation is...
ata_exec_internal_sg() : no user except for ata_exec_internal() yet
ata_exec_internal() : one data transferring user. other are non-data
ata_do_simple_cmd() : three users
So, adding
Arnd Bergmann wrote:
On Monday 11 December 2006 15:02, Tejun Heo wrote:
{
struct scatterlist sg;
+ unsigned int n_elem = 0;
- sg_init_one(sg, buf, buflen);
+ if (dma_dir != DMA_NONE) {
+ WARN_ON(!buf);
+ sg_init_one(sg, buf, buflen);
+
Robert Hancock wrote:
+static void nv_remove_one (struct pci_dev *pdev)
+{
+ struct ata_host *host = dev_get_drvdata(pdev-dev);
+ struct nv_host_priv *hpriv = host-private_data;
+
+ kfree(hpriv);
+ ata_pci_remove_one(pdev);
+}
It is unwise to free the
Calling sg_init_one() with NULL buf causes oops on certain
configurations. Don't initialize sg in ata_exec_internal() if
DMA_NONE and make the function complain if @buf is NULL when dma_dir
isn't DMA_NONE. While at it, fix comment.
The problem is discovered and initial patch was submitted by
Jeff Garzik wrote:
It is unwise to free the struct before the ports are even detached.
Right, theoretically something bad could happen here (though not
likely). Here's a fix. Sorry for attaching with something so trivial,
but Thunderbird isn't very cooperative..
---
The suspend/resume
Darrick J. Wong wrote:
The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
response to a REPORT LUNS packet. If this happens to an ATAPI device
that is attached to a SAS controller (this is the case with sas_ata),
the device does not load because SCSI won't touch a SCSI device
On Mon, 2006-12-11 at 11:24 -0500, Jeff Garzik wrote:
Darrick J. Wong wrote:
The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
response to a REPORT LUNS packet. If this happens to an ATAPI device
that is attached to a SAS controller (this is the case with sas_ata),
the
James Bottomley wrote:
On Mon, 2006-12-11 at 11:24 -0500, Jeff Garzik wrote:
Darrick J. Wong wrote:
The Quantum GoVault SATAPI removable disk device returns ATA_ERR in
response to a REPORT LUNS packet. If this happens to an ATAPI device
that is attached to a SAS controller (this is the case
31 matches
Mail list logo
