maybe problem with serial.o? maybe 2.0.36p10?

Eyal Lebedinsky (eyal@eyal.emu.id.au)
Tue, 22 Sep 1998 10:56:48 +1000

Recently I started having modem hangups (my ISP is being upgraded). No
problem,
I normally just restart ppp. BTW, I start ppp with private scripts.

However, this time, after pppd dies
------------ /var/log/messages -------------------
Sep 22 09:28:38 eyal pppd[18863]: Hangup (SIGHUP)
Sep 22 09:28:38 eyal pppd[18863]: Modem hangup
Sep 22 09:28:38 eyal pppd[18863]: Connection terminated.
Sep 22 09:28:38 eyal pppd[18863]: Exit.
------------ /var/log/messages -------------------

I cannot access /dev/ttyS1. If I strace something like 'dd
if=/dev/ttyS1'
it stops at the 'open("/dev/ttyS1", O_RDONLY'.

ttyS0 (the mouse) still works during this event.

I find that unloading/loading serial.o is the only way to get ttyS1 back
to life. Not nice since I have to exit X and stop gpm to safely unload.

In the past, hungups were not a problem. What changed? I moved from
redhat-4.2
to debian-2.0 in the last month. I then started using 2.0.36-p10.

I can test with 2.0.35 if anyone wants me to, but I know redhat-4.2 with
2.0.35
works just fine (I was still on glibc5 there).

--
Eyal Lebedinsky		(eyal@eyal.emu.id.au)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/