blah blah blah sata sata sata blah blah blah
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Jeff Garzik wrote:
blah blah blah sata sata sata blah blah blah
Now why in the world would you write that? Silly person.
Jeff
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
From: Matti Linnanvuori [EMAIL PROTECTED]
Correct IDEPCI_SHARE_IRQ description to keeping interrupts enabled
when calling the PCI IDE action handler.
Add IDEPCI_SHARE_IRQ and IDEDISK_MULTI_MODE help text from hdparm
manual page.
Signed-off-by: Matti Linnanvuori [EMAIL PROTECTED]
---
---
Hello,
On Fri, 19 Oct 2007 12:23:15 +0900
Tejun Heo [EMAIL PROTECTED] wrote:
On 26/08/07, Paul Rolland [EMAIL PROTECTED] wrote:
My machine (an ASUS P5W-DH-Deluxe, Core2, 4Go RAM, 3 SATA and 2IDE) is
reporting a :
irq 23: nobody cared (try booting with the irqpoll option)
together with
On Saturday 20 October 2007 19:11:56 Sergei Shtylyov wrote:
What I don't like is that both PIIX4 and PCI-648 are sharing IRQ15
(PIIX4 is in legacy mode, so it uses edge-triggered IRQ15 which is not
shareable). You don't have drives connected to PIIX4, do you? However, it
doesn't look like
Lars Michael Jogbäck wrote:
Hi Tejun et. al.
I'm running a server with Linux 2.6.18.1+Debian's Xen-patches and the
sata+pmp-patches from
http://home-tj.org/files/libata-tj-stable/libata-tj-2.6.18.1-20061020.tar.bz2
Unfortunately I can't upgrade to anything newer than 2.6.18 since there
Yes, link - http://lkml.org/lkml/2007/10/8/93 add the AHCI legacy
support to sata_nv when IDE/RAID mode been set in SBIOS and Device IDs
are not in ahci.c at this moment. To do so, when a new chipset come
out and DIDs haven't been submited to LKML,user still can use ahci
driver to handle it when
Hello,
Didde Brockman wrote:
Oct 20 13:49:00 infra kernel: md: using maximum available idle IO bandwidth
(but not more than 20 KB/sec) for resync.
Oct 20 13:49:00 infra kernel: md: using 128k window, over a total of
244195904 blocks.
Oct 20 13:50:37 infra kernel: res
Hi,
I stumbled over a bug in the sata_nv swncq code of the current
2.6.23-git kernel. ata_port_info.flags is always initialised with the
ATA_FLAG_NCQ flag set, but nv_swncq_host_init(...) is only called
if swncq=1 is passed to the driver (default is swncq=0).
I can can observe ata link resets
Helo,
Soeren Sonnenburg wrote:
I finally managed to find a *reproducible* setup and way to trigger
random corruptions using a sata sil 3114 controller connected to 4
seagate drives
port 1: ST3400832AS sda
port 2: ST3400620AS sdb
port 3: ST3750640AS sdc
port 4: ST3750640AS sdd
sda sdb
Former versions of the SWNCQ patch didn't have this problem as
ATA_FLAG_NCQ was set in nv_swncq_host_init(...). The appended patch
restores this behaviour (or was it changed for a good reason?)
We could also simply drop the option to enable/disable swncq.
Outch - sorry, just found the thread
Gerhard Dirschl wrote:
Hi,
I stumbled over a bug in the sata_nv swncq code of the current
2.6.23-git kernel. ata_port_info.flags is always initialised with the
ATA_FLAG_NCQ flag set, but nv_swncq_host_init(...) is only called
if swncq=1 is passed to the driver (default is swncq=0).
I can can
On Mon, 2007-10-22 at 11:12 +0900, Tejun Heo wrote:
Helo,
Soeren Sonnenburg wrote:
I finally managed to find a *reproducible* setup and way to trigger
random corruptions using a sata sil 3114 controller connected to 4
seagate drives
port 1: ST3400832AS sda
port 2: ST3400620AS sdb
13 matches
Mail list logo
