[19005] in Athena Bugs
Re: sun4 9.0.9: workstation
daemon@ATHENA.MIT.EDU (Roger A. Roach)
Thu Jul 5 09:31:48 2001
Message-Id: <200107051331.JAA00726@rar.mit.edu>
To: Garry Zacheiss <zacheiss@MIT.EDU>
cc: "Roger A. Roach" <rar@MIT.EDU>, bugs@MIT.EDU
In-Reply-To: Your message of "Wed, 04 Jul 2001 00:53:08 EDT."
<200107040453.AAA12723@coleco-sidewinder.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 05 Jul 2001 09:31:44 -0400
From: "Roger A. Roach" <rar@MIT.EDU>
Garry,
Yes, they are both turned on. However, things are getting a little more
random. On Monday I was communicating very well with the UPS (seeing its
load, etc.). However, due to the problem during booting, I disconnected
the cable. Today, I changed by rc.conf to turn off autoboot and rebooted
the system. When I tried to connect the cable and look at the UPS, I got
an error saying the cable was not connected. Playing with the cable did
not help. I removed the cable and rebooted, resinstalling the cable after
the
boot. This worked OK once, but after another reboot it isn't.
A couple of observations:
When I use kermit to check the line, I get:
A serial connection might still be active on /dev/term/a.
OK to close?
Also, when I go into su mode to reboot (^P out of login window)
I got once:
Warning: no access to tty (Inappropriate ioctl for device)
Thus no job control in this shell.
I also got once:
ttymon cannot allocate controlling tty on "/dev/console"
there may be another session active on this port.
It does seem that multiple tasks seem to be in conflict.
I am using the cable that came with the UPS. Since it has worked, I assume
that there is not a null-modem wiring problem.
I'll play with the eeprom parms later and let you know if they help.
Roger
> Hi,
>
> A few questions about this:
>
> >> I hooked it up to my new SunBlade (with 18.1" LCD Flat Screen
> >> Monitor) and it seemed to work OK until I rebooted the system. When
> >> the system rebooted, it was unable to communicate with the screen.
> >> The screen had a floating message saying to check the cable and
> >> connections. After a lot of playing around, we discovered that when
> >> disconnected the serial port, it would boot fine.
>
> Silly question: Are the machine and UPS actually turning on?
> We've seen a failure mode where connecting a serial terminal to the DB9
> port on an APC UPS would cause it to power off, and I'd like to make
> sure we're not seeing that again.
>
> Also, what sort of cable are you using? Are you using the same
> one you were using previously? There might be straight through vs. null
> modem sensitivity here.
>
> Lastly, there are a couple of serial port settings from the Sun
> boot ROM:
>
> ttya-ignore-cd
> If true, operating system ignores carrier-detect on
> TTYA. Defaults to true.
>
> ttya-rts-dtr-off
> If true, operating system does not assert DTR and RTS
> on TTYA. Defaults to false.
>
>
> (from the "eeprom" man page). You might want to experiment with these,
> along the lines of:
>
> setenv ttya-rts-dtr-off true
>
> at the "ok" prompt.
>
> If all else fails, I might be able to come by and take a look;
> debugging this might be easier with a machine to experiment with.
>
> Garry
>
>
