Spurious input since installing 2.1.3



  • I'm getting spurious input –mostly buffer-filling char repeats-- since installing 2.1.3.  Frequent needs to reboot.

    Is anyone else getting something similar, or should I start looking at hardware?

    It's running on an Intel 2500CCE board connected to a 4-port Rosewill KVM (a very nice kvm, btw, albeit a very basic one).



  • @MMacD:

    I'm getting spurious input –mostly buffer-filling char repeats--

    Input on.. a NIC? The console? A log? Which character are you seeing filling the log?

    @MMacD:

    It's running on an Intel 2500CCE board connected to a 4-port Rosewill KVM (a very nice kvm, btw, albeit a very basic one).

    If it's console input I would try removing the Rosewill and using a regular keyboard and monitor to see if the Rosewill is the cause? (vs. the motherboard) If the input goes away, then perhaps changing to a different Rosewill port (and cable set) to see if that helps?



  • @MindfulCoyote:

    @MMacD:

    I'm getting spurious input –mostly buffer-filling char repeats--

    Input on.. a NIC? The console? A log? Which character are you seeing filling the log?

    @MMacD:

    It's running on an Intel 2500CCE board connected to a 4-port Rosewill KVM (a very nice kvm, btw, albeit a very basic one).

    If it's console input I would try removing the Rosewill and using a regular keyboard and monitor to see if the Rosewill is the cause? (vs. the motherboard) If the input goes away, then perhaps changing to a different Rosewill port (and cable set) to see if that helps?

    Yes, it's console output.  '#' most recently.  The system's crashed twice today.  I'm still sort of hoping it's associated with the fact that I often leave a shell running, but I'll swap connections on the kvm tomorrow and start trying to decide whether to get another d2500cce if it turns out it's the board going bad already.

    THanks for responding.



  • @MMacD:

    Yes, it's console output.  '#' most recently.

    I've used a number of different kvm's and seen them fail a lot of different ways (and more frequently then anticipated). I would suspect the cable first, then the kvm. Temporarily substituting a standard monitor and keyboard in their place would isolate that possibility. Also, if it turns out to be the board, you could try a different USB port for the keyboard input (or swap a USB for the PS2 if it's OG).


Log in to reply