On Monday 18 June 2007, Mark Lord wrote:
Thanos Kyritsis wrote:
[snip]
/etc/rc.d/rc.local contains the following:
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hda
/usr/sbin/hdparm -q -d1 -q -u1 -q -c1 -q -k1 /dev/hdb
[snip]
Sounds like a (kernel) timing issue.
The -q option gets rid
On Wed, Jun 20, 2007 at 12:07:19AM +0400, Sergei Shtylyov wrote:
Bartlomiej Zolnierkiewicz wrote:
[...frmware...]
Google seems to show that there is no publically available
firmware updates for Maxtor disks.
It would be useful to see hdparm --Istdout output for *both* disks.
Lets do one
Google seems to show that there is no publically available
firmware updates for Maxtor disks.
There are for some but only if you irritate the tech support people.
hours at high cpu usage There were maybe a a dozen DriveReady
SeekComplete Timeout errors clustered a few minutes apart.
Hi guys,
I'm debugging a system here based on ICH7/ata_piix.
When we hot-pull a drive, it locks up solid.
That's fine, but I'd like to find/fix the lockup.
So as part of poking around, I rebuilt the kernel with frame pointers,
and inserted a WARN_ON(1) into ata_busy_sleep() to see who was
Enable link power management for ata drivers
libata drivers can define a function (enable_pm) that will
perform hardware specific actions to enable whatever power
management policy the user set up from the scsi sysfs
interface if the driver supports it. This power management
policy will be
Enable Aggressive Link Power management for AHCI controllers.
This patch will set the correct bits to turn on Aggressive
Link Power Management (ALPM) for the ahci driver. This
will cause the controller and disk to negotiate a lower
power state for the link when there is no activity (see
the AHCI
Bartlomiej Zolnierkiewicz wrote:
Code intended to check DMA status was checking DMA command register.
Moreover firmware seems to forget to set DMA capable bit for the
slave device (at least in RAID mode but without ITE RAID volumes) so
check device ID for DMA capable bit when deciding whether
Tejun Heo wrote:
More for the NCQ blacklist. One hitachi and one raptor. Other
members of these families of drives are already on the list, so no
surprises.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/libata-core.c |2 ++
1 file changed, 2 insertions(+)
diff --git
Tejun Heo wrote:
If PORTS_IMPL register is zero, ahci initialize it to full mask
corresponding to nr_ports in the CAP register. hpriv-cap, which is
initialized at the end of the function, is incorrectly used as value
of CAP causing ahci to always override PORTS_IMPL to 0x1 if it's zero.
Fix it.
Please pull from 'upstream-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
upstream-linus
to receive the following updates:
drivers/ata/ahci.c|2 +-
drivers/ata/libata-core.c |4 +++-
drivers/ata/pata_amd.c|2 ++
I suppose you were using ata_piix too in older kernel, right? Can you
post the boot dmesg of 2.6.19? We used to ignore mwdma mode before and
enabled it at some point after that. That may be the cause here.
Also, please try the attached patch on top of 2.6.20.
Sorry guys, I've actually
Hello,
It seems if I boot with a disc in the drive (in this case a dual fs
ISO-9660/UDF DVD-R) the drive speed gets reported incorrectly:
hdc: DVDRW DRW-6S160P, ATAPI CD/DVD-ROM drive
hdc: ATAPI 126X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(66)
normal output (w/ no disc) is:
hdc: DVDRW
Hello,
I got a Promise TX4 SATA 300 Controller with 3 SAMSUNG HD400LJ SATA 300
disks (sdc, sdd, sde), the disks runs under a software raid5 with Luks
(Cryptography layer) and Lvm2.
The disks works well and there is no data loss, but i'm continuously and
always getting worrisome error
Andrew Hall wrote:
I suppose you were using ata_piix too in older kernel, right? Can you
post the boot dmesg of 2.6.19? We used to ignore mwdma mode before and
enabled it at some point after that. That may be the cause here.
Also, please try the attached patch on top of 2.6.20.
Sorry
Gabriele Tozzi gabriele.tozzi at gmail.com writes:
Hello,
I got a Promise TX4 SATA 300 Controller with 3 SAMSUNG HD400LJ SATA 300
disks (sdc, sdd, sde), the disks runs under a software raid5 with Luks
(Cryptography layer) and Lvm2.
The disks works well and there is no data loss, but
Mark Lord wrote:
Hi guys,
I'm debugging a system here based on ICH7/ata_piix.
When we hot-pull a drive, it locks up solid.
That's fine, but I'd like to find/fix the lockup.
So as part of poking around, I rebuilt the kernel with frame pointers,
and inserted a WARN_ON(1) into
16 matches
Mail list logo