Re: Weird serial problems in 2.6.7

[Ralph Mitchell <rmitchell@eds.com>]

For further information/confirmation, I have an E450 with serial 
console, and there was no problem 2.6.7-rc1.  However, I just booted 
2.6.7 and I'm getting the wierd character problem.  At first glance it 
looked like it might be parity, but then I'd think it would be more 
likely to drop (apparently) random characters, rather than every other 
one...

Anyway, it started OK, then went weird, then recovered:

    Sun Enterprise 450 (4 X UltraSPARC-II 400MHz), No Keyboard
    OpenBoot 3.16, 4096 MB memory installed, Serial #12871523.
    POLB u EEBo rm31. 000/11:2
    [snip lots of garbage...]
    koradsatn. 
o.....±.....)..2éj.Ñ..±....J¡½.É.                                   g

    Gentoo Linux; http://www.gentoo.org/
     Copyright 2001-2004 Gentoo Technologies, Inc.; Distributed under 
the GPL

     * Mounting proc at /proc...  [ ok ]
     * Mounting sysfs at /sys...  [ ok ]

Seems like all the output that matches the 'dmesg' output was weird, 
then it was ok when processing the startup scripts.  Once the boot is 
complete I can login just fine  I have:

    CONFIG_SERIAL_SUNSAB=y
    CONFIG_SERIAL_SUNSAB_CONSOLE=y

in my .config.

Just wondering - could the kernel just be trying to push characters out 
too fast for the chip to handle?

Ralph Mitchell


Marc Zyngier wrote:

>>>>>>"Meelis" = Meelis Roos <mroos@linux.ee> writes:
>>>>>>            
>>>>>>
>
>Meelis> I tried 2.4.27-rc3 on the same Ultra5 and same cable and same
>Meelis> PC, serial console works fine. So it's serial console in 2.6
>Meelis> on U5 it seems.
>
>For information, my Netra AX1105 runs fine with 2.6.7 and 2.6.8-rc2
>using serial console. Uses sunsu, though.
>
>Looks like it is sunsab-related...
>
>	M.
>  
>