Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Hello.
John Sigler wrote:
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because
your device is too old (or its manufacturer was too lazy) to support
ATA-2 (or EIDE from marketing PoV) is its full glory.
But the data sheet seems to state the drive supports PIO modes 1 and 2?
So what? PIO mode != ATA spec version. ATA-1 specified modes 0 thru 2.
Is there something I need to set in the config? or something I should
not have set?
No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D
Wow! This is a device that was purchased only a few months ago...
I think we'll take care of it soon -- as I said we've discovered pre-EIDE
disk support lately, just before your report...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete
Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete
Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
That means that you've managed to find pre-EIDE/ATA hardware which
doesn't support setting arbitrary PIO modes. What's funny is that
recently being discussed here, so expect a patch RSN. :-)
In 2.6.23?
Yeah, hopefully.
The mode interesting question is how to diable IORDY throrling on host if
a device doesn't have it connected (that was addressed by Alan in libata, IIRC.
Regards.
MBR as well. :-)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Sergei Shtylyov wrote:
John Sigler wrote:
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because your
device is too old (or its manufacturer was too lazy) to support ATA-2
(or EIDE from marketing PoV) is its full glory.
But the data sheet seems to state the drive supports PIO modes 1 and 2?
Is there something I need to set in the config? or something I should
not have set?
No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D
Wow! This is a device that was purchased only a few months ago...
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete
Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete
Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
That means that you've managed to find pre-EIDE/ATA hardware which
doesn't support setting arbitrary PIO modes. What's funny is that
recently being discussed here, so expect a patch RSN. :-)
In 2.6.23?
Regards.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
John Sigler wrote:
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at
Which is perfectly valid in the original ATA spec.
all, or that value which kernel tried is not supported by the drive...
They just should skip programming the drive in this case, and set its
default speed to the chipset.
I would guess that some contractor wrote firmware for device for PQI
in one day for $100, and before that somebody else designed ATA-SD
bridge for PQI for another $100.
Hehe.
I guess that these two printk()s happen because drive claims to
support pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries
Which it shuldn't do since the drive only indicates its default mode (modes
0-2 aren't included in the PIO support mask -- there's only 3 and 4 there).
pio1, drive refuses, and finally as pio0 is default, that one gets
used. Which is more or less confirmed by having no '*' sign in front
of any pio - with "real" drives you should see '*' in front of one of
listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform
to any ATA standard...
Doesn't it conform to ATA? :-)
I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c
via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call
via_set_drive() which calls ide_config_drive_speed().
http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769
if (error)
{
(void) ide_dump_status(drive, "set_drive_speed_status", stat);
printk(KERN_INFO "EXIT %s error\n", __func__);
return error;
}
Does someone know why error is not set to 0?
Why it *does* set to one, you wanted to ask? Because it *does* get set
after a loop above exits.
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255
255 is PIO auto-tuning request.
ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
MBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Hello.
John Sigler wrote:
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
IDE code attempts to autotune PIO mode and fails at that because your
device is too old (or its manufacturer was too lazy) to support ATA-2 (or EIDE
from marketing PoV) is its full glory.
Is there something I need to set in the config? or something I should
not have set?
No, it just means that the IDE code is *too young* to support such
pre-EIDE devices. :-D
Bonus question: is there some way to turn on DMA for hda?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
That means that you've managed to find pre-EIDE/ATA hardware which doesn't
support setting arbitrary PIO modes. What's funny is that resently being
discussed here, so expect a patch RSN. :-)
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
# hdparm -v /dev/hda
/dev/hda:
multcount = 0 (off)
IO_support= 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 500/8/32, sectors = 128000, start = 0
Oh, interesting geometery, and the size too. :-)
# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: PQI IDE DiskOnModule
That explains it. :-)
Serial Number: DOM6B00011677
Firmware Revision: ra03.00e
Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time > 15us
fixed drive
disk xfer rate > 5Mbs
Logical max current
cylinders 500 500
heads 8 8
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 128000
LBAuser addressable sectors: 128000
device size with M = 1024*1024: 62 MBytes
device size with M = 1000*1000: 65 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
That's generally not the device task (although there probably were IDE
devices with 32-bit data bus?.. :-O
R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2
[the rest of logs didn't show anything particurarly interesting]
MBR, Sergei
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Alan Cox wrote: Standards: Likely used: 1 Prehistory LBA, IORDY not likely No DMA, nothing above PIO2 Cool! :-) Buffer type: 0002: dual port, multi-sector Buffer size: 1.0kB bytes avail on r/w long: 4 Cannot perform double-word IO Can't even do double word I/O I have alwayas wondered what the drive's part in 32-bit I/O... this seems to be controller's problem exclusively. B-) WBR, Sergei - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> When a DMA operation is enabled, CS0- and CS1- shall not be asserted and > transfers shall be 16-bits wide. > > I took the above to mean the device was designed to support DMA. > Where did I err? The bus is specified for DMA, not the device. > > > The data sheet says the media can only do 4.1MB/second which is > > consistent with only needing PIO2 (actually it's far slower than PIO2) > > Is such a slow speed typical of DOMs sold today? > > Or do DOMs sold today support DMA bus mastering, much higher interface > rates, and much higher sustained throughput? Most CF is pretty slow but the newer CF cards do DMA and are getting far better. And yes I'd expect your real time app to deal for 3 or 4mS (Mind you you'll get 1mS normal operating worst cases off even a fast DMA IDE disk) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Eric wrote: John Sigler wrote: According to my supplier, herre is the data sheet for the DOMs: http://www.pqimemory.com/documents/domdata.pdf PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken? Page 3 states max interface burst speed is 8.3MB/s in PIO2. I wouldn't assume it supports DMA The reason I suspected DMA support is because I noticed the description of DMACK- (DMA acknowledge) and DMARQ (DMA request). Based on the quoted media transfer rates (1.2MB/s write and 4.1MB/s read), DMA would buy you a transfer checksum but probably not much performance, unless your embedded application is CPU bound. What I fear is that programmed I/O will tie up the CPU and add non-deterministic latency to my real-time apps. Suppose that an app is waiting for an acknowledgement from a PCI device when the OS suddenly decides it is time to write 4 KB to disk. Typical write rate is quoted as 1.2 MB/s i.e. the write would require at least 3.4 ms to complete. My fear is that the entire transfer is done in a non-preemptible critical section. In other words, my real-time app would be delayed several milliseconds, which is unacceptable. Am I mistaken? Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Alan Cox wrote: John Sigler wrote: http://www.pqimemory.com/documents/domdata.pdf PIO mode 2 is mentioned. Even DMA seems to be supported. Or am I mistaken? Could there be a bug in my south bridge? Nothing there about DMA support. cf. document's page 12. DMACK- (DMA acknowledge) This signal shall be used by the host in response to DMARQ to initiate DMA transfers. DMARQ (DMA request) This signal, used for DMA data transfer between host and device, shall be asserted by the device when it is ready to transfer data to or from the host. The direction of data transfer is controlled by DIOR- and DIOW-. This signal is used in a handshake manner with DMACK- i.e., the device shall wait until the host asserts DMACK- before negating DMARQ, and re-asserting DMARQ if there is more data to transfer. This line shall be released (high impedance state) whenever the device is not selected or is selected and no DMA command is in progress. When enabled by DMA transfer, it shall be driven high and low by the device. When a DMA operation is enabled, CS0- and CS1- shall not be asserted and transfers shall be 16-bits wide. I took the above to mean the device was designed to support DMA. Where did I err? The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually it's far slower than PIO2) Is such a slow speed typical of DOMs sold today? Or do DOMs sold today support DMA bus mastering, much higher interface rates, and much higher sustained throughput? Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> PIO mode 2 is mentioned. Even DMA seems to be supported. > Or am I mistaken? > > Could there be a bug in my south bridge? Nothing there about DMA support. The data sheet says the media can only do 4.1MB/second which is consistent with only needing PIO2 (actually its far slower than PIO2) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
John Sigler wrote:
Petr Vandrovec wrote:
John Sigler wrote:
Alan Cox wrote:
Basically your dinosaur is working correctly.
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at
all, or that value which kernel tried is not supported by the drive...
I would guess that some contractor wrote firmware for device for PQI
in one day for $100, and before that somebody else designed ATA-SD
bridge for PQI for another $100.
I guess that these two printk()s happen because drive claims to
support pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries
pio1, drive refuses, and finally as pio0 is default, that one gets
used. Which is more or less confirmed by having no '*' sign in front
of any pio - with "real" drives you should see '*' in front of one of
listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform
to any ATA standard...
I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c
via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call
via_set_drive() which calls ide_config_drive_speed().
http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769
if (error)
{
(void) ide_dump_status(drive, "set_drive_speed_status", stat);
printk(KERN_INFO "EXIT %s error\n", __func__);
return error;
}
Does someone know why error is not set to 0?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255
ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_ide_dma_check
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
According to my supplier, herre is the data sheet for the DOMs:
http://www.pqimemory.com/documents/domdata.pdf
PIO mode 2 is mentioned. Even DMA seems to be supported.
Or am I mistaken?
Could there be a bug in my south bridge?
Regards.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> Buffer size: 1.0kB bytes avail on r/w long: 4 > > (Assuming an 8-bit byte, 4 bytes = 32 bits) R/W Long is a different thing. > When you say "the current libata IDE" do you mean PATA_VIA (in my case)? > I've avoided this driver because it is marked EXPERIMENTAL. Would there > be any benefit in using it over the legacy ATA/MFM/RLL driver? Just less warning messages > > Basically your dinosaur is working correctly. > > What do the warnings mean? :-) Old IDE wrongly tries to issue a set features command for PIO2 to the device. It rejects it and old IDE carries on happy - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Petr Vandrovec wrote:
John Sigler wrote:
Alan Cox wrote:
Basically your dinosaur is working correctly.
What do the warnings mean? :-)
That your drive does not support set transfer mode/speed command at all,
or that value which kernel tried is not supported by the drive...
I would guess that some contractor wrote firmware for device for PQI in
one day for $100, and before that somebody else designed ATA-SD bridge
for PQI for another $100.
I guess that these two printk()s happen because drive claims to support
pio0,1,2 - so Linux tries pio2, drive refuses, Linux tries pio1, drive
refuses, and finally as pio0 is default, that one gets used. Which is
more or less confirmed by having no '*' sign in front of any pio - with
"real" drives you should see '*' in front of one of listed dma/pio modes.
You should ask reseller how they can ship drive which does not conform
to any ATA standard...
I took drivers/ide/pci/via82cxxx.c and sprinkled ENTER/EXIT printk's.
http://lxr.linux.no/source/drivers/ide/pci/via82cxxx.c
via82cxxx_tune_drive() and via82cxxx_ide_dma_check() both call
via_set_drive() which calls ide_config_drive_speed().
http://lxr.linux.no/source/drivers/ide/ide-iops.c#L769
if (error)
{
(void) ide_dump_status(drive, "set_drive_speed_status", stat);
printk(KERN_INFO "EXIT %s error\n", __func__);
return error;
}
Does someone know why error is not set to 0?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
ENTER via82cxxx_tune_drive
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_tune_drive pio == 255
ENTER via82cxxx_ide_dma_check
ENTER via_set_drive
ENTER ide_config_drive_speed
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
EXIT ide_config_drive_speed error
ENTER via_set_speed
EXIT via_set_speed
EXIT via_set_drive
EXIT via82cxxx_ide_dma_check
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
Regards.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Alan Cox wrote: John Sigler wrote: Standards: Likely used: 1 Prehistory The tragic bit is that we were sold similar DOMs in 2007... (It's probably time to change suppliers?) LBA, IORDY not likely No DMA, nothing above PIO2 OK. (Grumble) Buffer type: 0002: dual port, multi-sector Buffer size: 1.0kB bytes avail on r/w long: 4 Cannot perform double-word IO Can't even do double word I/O Double word is 32 bits, right? Isn't "Cannot perform double-word IO" in contradiction with the following statements? IO_support= 1 (32-bit) Buffer size: 1.0kB bytes avail on r/w long: 4 (Assuming an 8-bit byte, 4 bytes = 32 bits) The messages with old IDE should be harmless and the current libata IDE should drive it politely (I debugged a problem the same hardware showed up for someone else). When you say "the current libata IDE" do you mean PATA_VIA (in my case)? I've avoided this driver because it is marked EXPERIMENTAL. Would there be any benefit in using it over the legacy ATA/MFM/RLL driver? Basically your dinosaur is working correctly. What do the warnings mean? :-) Regards. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> Standards: > Likely used: 1 Prehistory > LBA, IORDY not likely No DMA, nothing above PIO2 > Buffer type: 0002: dual port, multi-sector > Buffer size: 1.0kB bytes avail on r/w long: 4 > Cannot perform double-word IO Can't even do double word I/O The messages with old IDE should be harmless and the current libata IDE should drive it politely (I debugged a problem the same hardware showed up for someone else). Basically your dinosaur is working correctly. Alan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Hello,
When my system boots, I get several set_drive_speed_status errors.
(Please see attached dmesg output.)
Can someone explain what they mean? How do I get rid of them?
Is there something I need to set in the config? or something I should
not have set?
Bonus question: is there some way to turn on DMA for hda?
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot :00:07.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci:00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:pio, hdd:pio
Probing IDE interface ide0...
hda: PQI IDE DiskOnModule, ATA DISK drive
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { DriveStatusError }
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hda: max request size: 128KiB
hda: 128000 sectors (65 MB) w/1KiB Cache, CHS=500/8/32
hda: hda1 hda2
# hdparm -v /dev/hda
/dev/hda:
multcount = 0 (off)
IO_support= 1 (32-bit)
unmaskirq = 1 (on)
using_dma = 0 (off)
keepsettings = 0 (off)
readonly = 0 (off)
readahead = 256 (on)
geometry = 500/8/32, sectors = 128000, start = 0
# hdparm -I /dev/hda
/dev/hda:
ATA device, with non-removable media
Model Number: PQI IDE DiskOnModule
Serial Number: DOM6B00011677
Firmware Revision: ra03.00e
Standards:
Likely used: 1
Configuration:
hard sectored
not MFM encoded
head switch time > 15us
fixed drive
disk xfer rate > 5Mbs
Logical max current
cylinders 500 500
heads 8 8
sectors/track 32 32
--
bytes/track: 0 bytes/sector: 528
CHS current addressable sectors: 128000
LBAuser addressable sectors: 128000
device size with M = 1024*1024: 62 MBytes
device size with M = 1000*1000: 65 MBytes
Capabilities:
LBA, IORDY not likely
Buffer type: 0002: dual port, multi-sector
Buffer size: 1.0kB bytes avail on r/w long: 4
Cannot perform double-word IO
R/W multiple sector transfer: Max = 1 Current = 0
DMA: not supported
PIO: pio0 pio1 pio2
# lspci
00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo
PRO133x] (rev c4)
00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo
MVP3/Pro133x AGP]
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
(rev 40)
00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1
Controller (rev 1a)
00:07.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40)
00:08.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro
100 (rev 08)
00:09.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro
100 (rev 08)
00:0a.0 Ethernet controller: Intel Corporation 82557/8/9 Ethernet Pro
100 (rev 08)
00:0b.0 VGA compatible controller: ATI Technologies Inc Rage XL (rev 27)
00:0d.0 PCI bridge: Intel Corporation 21152 PCI-to-PCI Bridge
02:0f.0 Multimedia video controller: DekTec Digital Video B.V. DTA-105
Regards.
Linux version 2.6.22.1-rt9 ([EMAIL PROTECTED]) (gcc version 3.4.4) #2 PREEMPT
RT Wed Aug 29 18:02:44 CEST 2007
BIOS-provided physical RAM map:
BIOS-e820: - 000a (usable)
BIOS-e820: 000f - 0010 (reserved)
BIOS-e820: 0010 - 0fff (usable)
BIOS-e820: 0fff - 0fff3000 (ACPI NVS)
BIOS-e820: 0fff3000 - 1000 (ACPI data)
BIOS-e820: - 0001 (reserved)
255MB LOWMEM available.
Entering add_active_range(0, 0, 65520) 0 entries of 256 used
Zone PFN ranges:
DMA 0 -> 4096
Normal 4096 ->65520
early_node_map[1] active PFN ranges
0:0 ->65520
On node 0 totalpages: 65520
DMA zone: 32 pages used for memmap
DMA zone: 0 pages reserved
DMA zone: 4064 pages, LIFO batch:0
Normal zone: 479 pages used for memmap
Normal zone: 60945 pages, LIFO batch:15
DMI 2.3 present.
ACPI: RSDP 000F7110, 0014 (r0 VIA601)
ACPI: RSDT 0FFF3000, 0028 (r1 VIA601 AWRDACPI 42302E31 AWRD0)
ACPI: FACP 0FFF3040, 0074 (r1 VIA601 AWRDACPI 42302E31 AWRD0)
ACPI: DSDT 0FFF30C0, 2A03 (r1 VIA601 AWRDACPI 1000 MSFT 10C)
ACPI: FACS 0FFF, 0040
ACPI: PM-Timer IO Port: 0x4008
Allocating PCI resources starting a
Re: SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete }
Mikael Pettersson wrote: I was looking briefly at the port mapping issue on 4-port Promise controllers yesterday and noticed a bit of programming magic in Promise's driver that Linux doesn't do, and which affects two of the four ports. That _could_ explain your issues. /Mikael Just as a note, I filed the issue that this thread is about as a kernel bug: http://bugzilla.kernel.org/show_bug.cgi?id=7516 I am also experiencing the port-mapping issue you mention with the SATA300 TX4, but I believe that the port mapping problem and the excess status messages are separate and unrelated problems. Greg - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete }
(cc: linux-ide added)
On Tue, 19 Dec 2006 12:26:07 +0100, Roel Teuwen wrote:
> I am seeing the exact same 'problem'. I have 4 WDC WD2500KS-00MJB0
> drives connected to a promise SATA300 TX4. The messages have been
> flooding syslog since the drives were installed. Running 2.6.18 or
> 2.6.19 vanilla kernels.
>
> Best regards,
>
> Roel Teuwen
>
> On 10/25/06, Gregory Brauer <[EMAIL PROTECTED]> wrote:
> >
> > I have a new Promise SATA300 TX4 4-port SATA controller
> > to which I have attached two older WD2500JD hard drives
> > and two brand new WD2500KS hard drives. The older drives
> > seem to work fine, but both of the brand new hard drives
> > trigger the following errors every few seconds during
> > i/o:
> >
> >
> > Oct 25 13:57:18 gleep kernel: ata3: no sense translation for status: 0x50
> > Oct 25 13:57:18 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:18 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
> > Oct 25 13:57:26 gleep kernel: ata1: no sense translation for status: 0x50
> > Oct 25 13:57:26 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:26 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
> > Oct 25 13:57:27 gleep kernel: ata1: no sense translation for status: 0x50
> > Oct 25 13:57:27 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:27 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
> > Oct 25 13:57:31 gleep kernel: ata1: no sense translation for status: 0x50
> > Oct 25 13:57:31 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:31 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
> > Oct 25 13:57:47 gleep kernel: ata3: no sense translation for status: 0x50
> > Oct 25 13:57:47 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
> > SK/ASC/ASCQ 0xb/00/00
> > Oct 25 13:57:47 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
> >
> >
> > The machine stays running normally, and any processes doing data
> > I/O do not pause noticeably, but these errors are very annoying.
> > Is there anything I can do to help troubleshoot this?
> >
> > (Note that I am aware of the drive id mapping issue with my Promise
> > controller, and I am *positive* that it is the two new drives that
> > are the one's that the error messages refer to.)
If you move the disks around, do the errors stay on the same ports (ata1/ata3),
or do they move to different ports (ata2/ata4)?
I was looking briefly at the port mapping issue on 4-port Promise controllers
yesterday and noticed a bit of programming magic in Promise's driver that
Linux doesn't do, and which affects two of the four ports. That _could_
explain your issues.
/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: SATA300 TX4 + WD2500KS = status=0x50 { DriveReady SeekComplete }
Hello All,
I am seeing the exact same 'problem'. I have 4 WDC WD2500KS-00MJB0
drives connected to a promise SATA300 TX4. The messages have been
flooding syslog since the drives were installed. Running 2.6.18 or
2.6.19 vanilla kernels.
Best regards,
Roel Teuwen
On 10/25/06, Gregory Brauer <[EMAIL PROTECTED]> wrote:
I have a new Promise SATA300 TX4 4-port SATA controller
to which I have attached two older WD2500JD hard drives
and two brand new WD2500KS hard drives. The older drives
seem to work fine, but both of the brand new hard drives
trigger the following errors every few seconds during
i/o:
Oct 25 13:57:18 gleep kernel: ata3: no sense translation for status: 0x50
Oct 25 13:57:18 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:18 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
Oct 25 13:57:26 gleep kernel: ata1: no sense translation for status: 0x50
Oct 25 13:57:26 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:26 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
Oct 25 13:57:27 gleep kernel: ata1: no sense translation for status: 0x50
Oct 25 13:57:27 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:27 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
Oct 25 13:57:31 gleep kernel: ata1: no sense translation for status: 0x50
Oct 25 13:57:31 gleep kernel: ata1: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:31 gleep kernel: ata1: status=0x50 { DriveReady SeekComplete }
Oct 25 13:57:47 gleep kernel: ata3: no sense translation for status: 0x50
Oct 25 13:57:47 gleep kernel: ata3: translated ATA stat/err 0x50/00 to SCSI
SK/ASC/ASCQ 0xb/00/00
Oct 25 13:57:47 gleep kernel: ata3: status=0x50 { DriveReady SeekComplete }
The machine stays running normally, and any processes doing data
I/O do not pause noticeably, but these errors are very annoying.
Is there anything I can do to help troubleshoot this?
(Note that I am aware of the drive id mapping issue with my Promise
controller, and I am *positive* that it is the two new drives that
are the one's that the error messages refer to.)
Thanks.
Greg
System Info
---
Fedora Core 5
2.6.18-1.2200.fc5smp
Device Model: WDC WD2500KS-00MJB0
Firmware Version: 02.01C03
# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge
(rev 03)
00:01.0 PCI bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX AGP bridge
(rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 02)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:0b.0 Mass storage controller: Promise Technology, Inc. PDC20718 (SATA 300
TX4) (rev 02)
00:0d.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 07)
00:0d.1 Input device controller: Creative Labs SB Live! MIDI/Game Port (rev 07)
00:0f.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
Controller (rev 05)
00:11.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:11.1 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:11.2 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:11.3 USB Controller: ALi Corporation USB 2.0 Controller (rev 01)
00:11.4 FireWire (IEEE 1394): ALi Corporation M5253 P1394 OHCI 1.1 Controller
00:13.0 Mass storage controller: Triones Technologies, Inc.
HPT366/368/370/370A/372/372N (rev 01)
00:13.1 Mass storage controller: Triones Technologies, Inc.
HPT366/368/370/370A/372/372N (rev 01)
01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 PF/PRO AGP 4x
TMDS
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Problem on SATA-disk with Promise SATAII 150 TX4 ("DriveReady SeekComplete Error")
Jeff Garzik wrote:: >Johannes Resch wrote: >> Hi, >> >> [please CC me on replies] >> >> I've got a box running 2.6.10 (with the patch[0] needed to support the >> Promise SATAII 150 TX4 controller). >> This box has three software raid1 partitions mirrored on a SATA disk on >> the Promise controller and a disk on the mainboard IDE controller (VIA >> vt8235). >> >> Within 4 days running the raid1, I got those three errors pasted below, >> each marking the SATA-raidmember as faulty. After "raidhotremove" and >> "raidhotadd" the SATA-raidmember syncs again fine and works at least a >> day until it is marked as faulty again. >> >> Any pointers where I could look at to resolve this problem? >> The SATA drive is a new Seagate ST3250823AS. >I would change out your cables, and also make sure you are running >2.6.11-rc3-bk-latest, which includes all the SATAII patches and other fixes. I don't believe it has anything to do with cabling. 2.6.10-ac9 introduced some sata patches. I didn't check -ac9 and -ac10, but -ac11 and -ac12 are not usable on my box with exactly the same symptoms. -jo -- -rw-r--r-- 1 jo users 63 2005-02-12 18:43 /home/jo/.signature - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Problem on SATA-disk with Promise SATAII 150 TX4 ("DriveReady SeekComplete Error")
Johannes Resch wrote: Hi, [please CC me on replies] I've got a box running 2.6.10 (with the patch[0] needed to support the Promise SATAII 150 TX4 controller). This box has three software raid1 partitions mirrored on a SATA disk on the Promise controller and a disk on the mainboard IDE controller (VIA vt8235). Within 4 days running the raid1, I got those three errors pasted below, each marking the SATA-raidmember as faulty. After "raidhotremove" and "raidhotadd" the SATA-raidmember syncs again fine and works at least a day until it is marked as faulty again. Any pointers where I could look at to resolve this problem? The SATA drive is a new Seagate ST3250823AS. I would change out your cables, and also make sure you are running 2.6.11-rc3-bk-latest, which includes all the SATAII patches and other fixes. JEff - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Problem on SATA-disk with Promise SATAII 150 TX4 ("DriveReady SeekComplete Error")
Hi,
[please CC me on replies]
I've got a box running 2.6.10 (with the patch[0] needed to support the
Promise SATAII 150 TX4 controller).
This box has three software raid1 partitions mirrored on a SATA disk on
the Promise controller and a disk on the mainboard IDE controller (VIA
vt8235).
Within 4 days running the raid1, I got those three errors pasted below,
each marking the SATA-raidmember as faulty. After "raidhotremove" and
"raidhotadd" the SATA-raidmember syncs again fine and works at least a
day until it is marked as faulty again.
Any pointers where I could look at to resolve this problem?
The SATA drive is a new Seagate ST3250823AS.
Feb 6 04:49:04 mars kernel: ata4: status=0x51 { DriveReady SeekComplete
Error }
Feb 6 04:49:04 mars kernel: SCSI error : <3 0 0 0> return code = 0x802
Feb 6 04:49:04 mars kernel: FMK Current sda: sense = 70 88
Feb 6 04:49:04 mars kernel: ASC=40 ASCQ=c0
Feb 6 04:49:04 mars kernel: end_request: I/O error, dev sda, sector
311900096
Feb 6 04:49:04 mars kernel: raid1: Disk failure on sda2, disabling device.
Feb 6 04:49:04 mars kernel: ^IOperation continuing on 1 devices
Feb 6 04:49:04 mars kernel: raid1: sda2: rescheduling sector 302518136
Feb 6 04:49:04 mars kernel: RAID1 conf printout:
Feb 6 04:49:04 mars kernel: --- wd:1 rd:2
Feb 6 04:49:04 mars kernel: disk 0, wo:1, o:0, dev:sda2
Feb 6 04:49:04 mars kernel: disk 1, wo:0, o:1, dev:hda2
Feb 6 04:49:04 mars kernel: RAID1 conf printout:
Feb 6 04:49:05 mars kernel: --- wd:1 rd:2
Feb 6 04:49:05 mars kernel: disk 1, wo:0, o:1, dev:hda2
Feb 6 04:49:05 mars kernel: raid1: hda2: redirecting sector 302518136
to another mirror
Feb 7 06:25:18 mars kernel: ata4: status=0x51 { DriveReady SeekComplete
Error }
Feb 7 06:25:18 mars kernel: SCSI error : <3 0 0 0> return code = 0x802
Feb 7 06:25:18 mars kernel: FMK Current sda: sense = 70 88
Feb 7 06:25:18 mars kernel: ASC=40 ASCQ=c0
Feb 7 06:25:18 mars kernel: end_request: I/O error, dev sda, sector
364654755
Feb 7 06:25:18 mars kernel: raid1: Disk failure on sda5, disabling device.
Feb 7 06:25:18 mars kernel: ^IOperation continuing on 1 devices
Feb 7 06:25:18 mars kernel: raid1: sda5: rescheduling sector 3706272
Feb 7 06:25:18 mars kernel: RAID1 conf printout:
Feb 7 06:25:18 mars kernel: --- wd:1 rd:2
Feb 7 06:25:18 mars kernel: disk 0, wo:1, o:0, dev:sda5
Feb 7 06:25:18 mars kernel: disk 1, wo:0, o:1, dev:hda5
Feb 7 06:25:18 mars kernel: RAID1 conf printout:
Feb 7 06:25:18 mars kernel: --- wd:1 rd:2
Feb 7 06:25:18 mars kernel: disk 1, wo:0, o:1, dev:hda5
Feb 7 06:25:18 mars kernel: raid1: hda5: redirecting sector 3706272 to
another mirror
Feb 9 06:25:02 mars kernel: ata4: status=0x51 { DriveReady SeekComplete
Error }
Feb 9 06:25:02 mars kernel: SCSI error : <3 0 0 0> return code = 0x802
Feb 9 06:25:02 mars kernel: FMK Current sda: sense = 70 88
Feb 9 06:25:02 mars kernel: ASC=40 ASCQ=c0
Feb 9 06:25:02 mars kernel: end_request: I/O error, dev sda, sector
310063304
Feb 9 06:25:02 mars kernel: raid1: Disk failure on sda2, disabling device.
Feb 9 06:25:02 mars kernel: ^IOperation continuing on 1 devices
Feb 9 06:25:02 mars kernel: raid1: sda2: rescheduling sector 300681344
Feb 9 06:25:02 mars kernel: RAID1 conf printout:
Feb 9 06:25:02 mars kernel: --- wd:1 rd:2
Feb 9 06:25:02 mars kernel: disk 0, wo:1, o:0, dev:sda2
Feb 9 06:25:02 mars kernel: disk 1, wo:0, o:1, dev:hda2
Feb 9 06:25:02 mars kernel: RAID1 conf printout:
Feb 9 06:25:02 mars kernel: --- wd:1 rd:2
Feb 9 06:25:02 mars kernel: disk 1, wo:0, o:1, dev:hda2
Feb 9 06:25:02 mars kernel: raid1: hda2: redirecting sector 300681344
to another mirror
[0] http://marc.theaimsgroup.com/?l=linux-ide&m=110426005503319&q=raw
Best regards,
-jr
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
{ DriveReady SeekComplete }
Hello,
Just got a message:
hda: status error: status=0x50 { DriveReady SeekComplete }
hda: no DRQ after issuing MULTWRITE
hda is: QUANTUM FIREBALL CX10.2A, 9787MB w/418kB Cache, CHS=19885/16/63, UDMA(33)
Promise Ultra100 controller.
# hdparm /dev/hda
/dev/hda:
multcount= 8 (on)
I/O support = 3 (32-bit w/sync)
unmaskirq= 1 (on)
using_dma= 1 (on)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead= 8 (on)
geometry = 1247/255/63, sectors = 20044080, start = 0
# hdparm -i /dev/hda
/dev/hda:
Model=QUANTUM FIREBALL CX10.2A, FwRev=A3F.0B00, SerialNo=133918662657
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=32256, SectSize=21298, ECCbytes=4
BuffType=DualPortCache, BuffSize=418kB, MaxMultSect=16, MultSect=8
CurCHS=16383/16/63, CurSects=-66060037, LBA=yes, LBAsects=20044080
IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 *udma4
AdvancedPM=no
Drive Supports : ATA/ATAPI-4 T13 1153D revision 15 : ATA-1 ATA-2 ATA-3 ATA-4
2.2.19 with ide.2.2.19.03252001.patch.
Is something wrong with disk?
Regards,
Nerijus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
On Sat, Jan 27 2001, Andre Hedrick wrote:
> > I've been getting this during the boot sequence for quite some time now.
> > They don't seem to impact the functionality of the drive any though. Just
> > another extra-verbose kernel message I should ignore? :)
> >
> > (This is from the 2.4.1-pre10 btw.)
> >
> > hdd: CD-ROM TW 120D, ATAPI CD/DVD-ROM drive
> > hdd: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
> > hdd: set_drive_speed_status: error=0x04
>
> Means your device did not like that command and barfed.
> status=0x51, error=0x04 == command aborted next
My gut tells me that this is the 'get last written' command, and even
with the quiet flag we get the IDE error status printed. Could you
try and add
goto use_toc;
add the top of drivers/cdrom/cdrom.c:cdrom_get_last_written() and
see if that makes the error disappear?
--
* Jens Axboe <[EMAIL PROTECTED]>
* SuSE Labs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
