Re: Serial port problems with kernel 2.0.36 SMP
|> I recently upraded my motherboard and installed Slink where I was
|> using Hamm before, so a number of things changed at once. But:
|>
|> I am attempting to run pilot-link stuff, as well as connect my UPS
|> again (best power fortress). Both of these things worked with my
|> old motherboard (A Tyan PPro board) and kernel 2.0.34.
|>
|> With 2.0.36 and this Asus P2B-D M/B, I do see the serial ports
|> getting init'ed at boot
|>
|> bash$ dmesg
|> ...
|> Serial driver version 4.13 with no serial options enabled
|> tty00 at 0x03f8 (irq = 4) is a 16550A
|> tty01 at 0x02f8 (irq = 3) is a 16550A
|> ...
|>
|> and the associated /dev/ttyS* files are also enumerated. However,
|> attempting to run, for example
|>
|> pilot-xfer /dev/ttyS0 -L
|>
|> results in nothing happening, and attempting to connect to the UPS
|> results in a seg fault, followed by extremely chopping performance
|> and an error message printed into the ring buffer about kmalloc
|> operations and how an idle process that is running can't sleep
|> (this is slightly painful, but I can do this again and be more
|> precise if this is interesting, which I imagine it is...).
I've had an identical problem with Slink and the 2.0.36 kernel on a
laptop trying to use a PCMCIA Fax/Modem card---identical
(non)-behaviour and identical error messages. I assumed it was a
problem with PCMCIA services and posted a request for help here and on
the PCMCIA message-list. No-one was able to diagnose the
problem. Judging by your message, though, it is not a PCMCIA problem
at all but something more general having to do with the handling of
serial ports. Weirder and weirder ...
If you get any advice or information, I'd appreciate your sharing it
with me,
Jim McCloskey
Reply to: