Re: System still hangs with "ata1-master: TIMEOUT - SETFEATURES SET TRANSFER MODE"

From: Panagiotis Astithas <past_at_noc.ntua.gr>
Date: Thu, 29 Jan 2004 14:02:18 +0200
Panagiotis Astithas wrote:
> Lefteris Chatzibarbas wrote:
> 
>> Hello,
>>
>> Devices are:
>>
>>   ad0: <WDC WD800JB-00ETA0/77.07W77> ATA-6 disk at ata0-master
>>   acd0: <DV-516E/3.04> DVDROM drive at ata1 as master
>>   acd1: <CD-W524E/1.0A> CDRW drive at ata1 as slave
>>
>> Verbose boot of a good kernel:
>>
>>   http://members.hellug.gr/lefcha/dmesg.out
>>
>> System still hangs during boot with the message:
>>
>>   ata1-master: TIMEOUT - SETFEATURES SET TRANSFER MODE retrying (0 
>> retries left)
>>
>> ... and verbose boot:
>>
>>   ata1: reiniting channel ..
>>   ata1: reset tp1 mask=03 ostat0=50 ostat1=50
>>   ata1-master: stat=0x10 err=0x01 lib=0x14 msb=0xeb
>>   ata1-slave: stat=0x10 err=0x01 lib=0x14 msb=0xeb
>>   ata1: reset tp2 mask=03 stat0=10 stat1=00 
>> devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
>>   ata1: resetting done ..
>>   ata1-slave: pio=0x0c wdma=0x22 udma=0x42 cable=80pin
>>   ata1: reiniting channel ..
>>   ata1: reset tp1 mask=03 ostat0=50 ostat1=50
>>   ata1-master: stat=0x10 err=0x01 lib=0x14 msb=0xeb
>>   ata1-slave: stat=0x10 err=0x01 lib=0x14 msb=0xeb
>>   ata1: reset tp2 mask=03 stat0=10 stat1=00 
>> devices=0xc<ATAPI_SLAVE,ATAPI_MASTER>
>>   ata1: resetting done ..
>>   ata1-slave: pio=0x0c wdma=0x22 udma=0x42 cable=80pin
>>
>> Soren Schmidt's commit 2004/01/19 07:20:00 PST:
>>
>>   1.202     +2 -1      src/sys/dev/ata/ata-all.c
>>   1.71      +1 -1      src/sys/dev/ata/ata-all.h
>>   1.17      +23 -21    src/sys/dev/ata/ata-queue.c
>>   1.161     +1 -1      src/sys/dev/ata/atapi-cd.c
>>
>> ... or:
>>
>>   http://lists.freebsd.org/pipermail/cvs-src/2004-January/016880.html
>>
>> ... didn't correct the problem.
>>
>> Thanks
> 
> 
> "Me too".
> Same controller, same hard disk, only one device on the second channel:
> acd0: DVDROM <DVD-ROM DDU1621> at ata1-master UDMA33
> I used 5.2-RELEASE and the -current snapshot form 24/1. The former 
> freezes after the "TIMEOUT" message, the latter just locks up solid. The 
> machine runs happily a -current from last October though.

I found out that booting with "Safe mode" (I knew there should be some 
use for it :-)) allows me to complete the process and get to sysinstall, 
in both 5.2-RELEASE & the -current snapshot from 24/1. But I tried to do 
the same from the loader prompt, to no avail. I used the following and 
then "boot" or "boot -v" but every attempt resulted in the traditional 
freeze.

unset acpi_load
set hint.acpi.0.disabled=1
set loader.acpi_disabled_by_user=1
set hw.ata.ata_dma=0
set hw.ata.atapi_dma=0
set hw.ata.wc=0
set hw.eisa_slots=0

 From what I can tell from the beastie.4th file, that is all that should 
be needed. Am I missing something?

Cheers,
-- 
Panagiotis Astithas
Electrical & Computer Engineer, PhD
Network Management Center
National Technical University of Athens, Greece
Received on Thu Jan 29 2004 - 03:02:39 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:40 UTC