[BusyBox 0001075]: getty breaks on ioctl on MPC850

[bugs at busybox.net]

The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=1075 
====================================================================== 
Reported By:                RenHoek
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   1075
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             10-20-2006 06:00 PDT
Last Modified:              10-20-2006 06:00 PDT
====================================================================== 
Summary:                    getty breaks on ioctl on MPC850
Description: 
I'm trying upgrade from busybox 1.00 (which works) to 1.2.1, but I'm
running into trouble with getty. I'm on an embedded Motorola platform.

When init tries to start getty I get this error and getty exits:


I traced this to this bit in loginutils/getty.c

        /*
         * The following ioctl will fail if stdin is not a tty, but also
when
         * there is noise on the modem control lines. In the latter case,
the
         * common course of action is (1) fix your cables (2) give the
modem more
         * time to properly reset after hanging up. SunOS users can
achieve (2)
         * by patching the SunOS kernel variable "zsadtrlow" to a larger
value;
         * 5 seconds seems to be a good value.
         */

        if (ioctl(0, TCGETA, tp) < 0)
                error("%s: ioctl: %m", tty);

When I comment it out, I get my login prompt. I fill in my username and
getty break again with this error:

getty: /dev/tts/0: ioctl: TCSETA: Invalid argument

Since 1.00 worked, I'll try and find out what has changed. I realise this
would be hard to reproduce for you guys since it's a custom platform, but
any tips are appreciated. :)
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-20-06 06:00  RenHoek        New Issue                                    
10-20-06 06:00  RenHoek        Status                   new => assigned     
10-20-06 06:00  RenHoek        Assigned To               => BusyBox         
======================================================================