kern/64637: ata1-slave: stat=0x01 err=0x00 lsb=0x00 msb=0x00 <- repeats for exactly 30 seconds during boot when no slave is wired

Paul Seniura pdseniura at techie.com
Tue Mar 23 14:50:13 PST 2004


>Number:         64637
>Category:       kern
>Synopsis:       ata1-slave:  stat=0x01 err=0x00 lsb=0x00 msb=0x00  <- repeats for exactly 30 seconds during boot when no slave is wired
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Mar 23 14:50:12 PST 2004
>Closed-Date:
>Last-Modified:
>Originator:     "Paul Seniura" <pdseniura at techie.com>
>Release:        FreeBSD 5.2-CURRENT i386
>Organization:
State of Okla. D.O.T.
>Environment:
System: FreeBSD techpc04.okladot.state.ok.us 5.2-CURRENT FreeBSD 5.2-CURRENT #0: Tue Mar 23 03:34:06 CST 2004 root at techpc04.okladot.state.ok.us:/usr/obj/src/sys/IBM300SY_4BSD_O2 i386

>Description:

We have a newish drive made by LG/HDST with latest firmware.  As shown in dmesg:
acd0: <HL-DT-ST RW/DVD GCC-4120B/2.02> CDRW drive at ata1 as master

While the kernel is probing for ATA/IDE devices, we see the following line repeatedly for exactly 30 seconds:
ata1-slave:  stat=0x01 err=0x00 lsb=0x00 msb=0x00

After the ttys come up, it seems the drive actually has no problems and is quite usable, albeit with the same known problems seen by others with different models when using apps such as 'burncd'.

Waiting an extra 30 seconds for a development machine to reboot is really trying my patience.  It is showing the kernel still needs some work.  (I must follow -Current via CTM due to political firewall issues here.)

This drive is installed in an IBM 300PL PC with latest BIOS firmware.  There are only two ATA/IDE devices: a primary/master HD and this secondary/master Combo drive.  There are no 'slaves' wired, in fact IBM's ribbon cables do not have an extra connector to do this.  Yes I've quintuple-checked the jumpers(!).

I bought this drive brand-new only a year ago.  It is exactly the same model+firmware Apple was using for its 'Combo' iMacs.  I used it for a while in my G4 Sawtooth running Jaguar and Panther.  A friend used it with Win2K for a while.  Now we have installed it into an IBM 300PL PC and want to use it for FreeBSD-current projects.

The original drive in the 300PL was an earlier LG model CDROM-only with latest firmware.  I still have access to it: it does not produce this problem (when wired in place of the new LG-Combo).

I tested a Pioneer DVR-107 the same way: it does not produce this problem (however, this drive will not be used on the 300PL).

I have tried setting sysctl values to change the timeouts for ATA devices -- the kernel msgs do not change and we still see exactly 30 seconds worth of repeated lines.

I have tried changing ATA DMA<->PIO modes -- it does not change the kernel msgs.

I have tried different schedulers: ULE and 4BSD produce the same msgs.

I have tried enabling ACPI: the same msgs.  (We cannot use ACPI for other reasons; see maillist archives, search for my name, to find out why).

I have messed with BIOS settings -- IBM's SurePath[tm] BIOS does not have many features here, and nothing will change the msgs.

I have asked for help in the -current maillist every so often since February 2004 and have received no replies.  So I open this PR.

>How-To-Repeat:

Install the LG 'Combo' CD/DVD drive.  Boot up.  See the msgs.

>Fix:

I need help & direction, please -- what to test, what to change, etc.  I'm fresh out of ideas.  I'm very much afraid when FreeBSD 5.3 "goes GM" it will still have this bug and many users will be asking "Why am I seeing this problem?".

>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list