Kumba <firstname.lastname@example.org> wrote:
> Out of curiosity, don't suppose you've seen the oops on IP22 that can
> sometimes be triggered by closing the serial client on another box?
Haven't seen this one, no. I'm using a hardware console on the serial
line most of the time (though I still haven't found the proper
configuration and it's hardly usable for anything advanced making use
of terminal features).
> Haven't investigated it too much, but I've seen the odd case on Indy
> and IP28 (which also uses the zilog driver) where shutting down my
> serial client or sometimes rebooting the system running the client
> oopses the driver. I suspect some rogue data gets passed that zilog
> doesn't know how to handle properly.
It looks a bit like the serial driver crash on reboot which Martin
Michlmayr fixed a couple of months back by backporting fixes from the
sunzilog driver. But I think this one made its way into the kernel, so
it must be something else.
Julien BLACHE <email@example.com> | Debian, because code matters more
Debian & GNU/Linux Developer | <http://www.debian.org>
Public key available on <http://www.jblache.org> - KeyID: F5D6 5169
GPG Fingerprint : 935A 79F1 C8B3 3521 FD62 7CC7 CD61 4FD7 F5D6 5169