From: John Sigler <linux.kernel@free.fr>
To: linux-ide@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, vojtech@suse.cz
Subject: Re: hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
Date: Thu, 30 Aug 2007 17:10:46 +0200 [thread overview]
Message-ID: <46D6DDF6.6080400@free.fr> (raw)
In-Reply-To: <46D6B85C.5050509@free.fr>
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 0000: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 pci0000: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.
next prev parent reply other threads:[~2007-08-30 15:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 16:29 hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } John Sigler
2007-08-29 16:46 ` Alan Cox
2007-08-30 8:17 ` John Sigler
[not found] ` <46D69E03.9080403@vc.cvut.cz>
2007-08-30 12:30 ` John Sigler
2007-08-30 15:10 ` John Sigler [this message]
2007-08-30 23:31 ` Alan Cox
2007-08-31 8:22 ` John Sigler
2007-08-31 9:04 ` PROBLEM: kernel 2.6.22.6 pata_pdc202xx_old.c limiting to UDMA/33 instead of UDMA/100 (UPDATED 2.6.22.6) n
2007-09-01 14:58 ` Sergei Shtylyov
2007-08-31 9:04 ` n
2007-08-31 9:04 ` n
2007-08-31 11:49 ` hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error } Alan Cox
[not found] ` <311601c90708301534g47b2bca7t77debde058781572@mail.gmail.com>
2007-08-31 8:41 ` John Sigler
2007-09-01 15:48 ` Sergei Shtylyov
2007-08-30 14:05 ` Alan Cox
2007-08-31 20:22 ` Sergei Shtylyov
2007-09-01 15:38 ` Sergei Shtylyov
2007-09-03 13:17 ` John Sigler
2007-09-03 13:40 ` Sergei Shtylyov
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=46D6DDF6.6080400@free.fr \
--to=linux.kernel@free.fr \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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.