Linux stuck when serial cable is disconnected
Hi all, I am running on a MIPS machine, with my kernel and debian distribution (file system). The kernel messages are configured to get out from the serial connection, i.e. serial console. When the serial output of my MIPS is connected to my PC everything is OK and I can see the outputs in the terminal. When I disconnect the serial cable my Linux get stuck. Even my telnet connection doesnt responds. When I re-connect the serial everything is OK again. Do you know what can be the problem? I am working with HW flow control? can it be the problem? Thanks a lot! Hagit -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
gconf strange message
Hi all, I am having a stable Debian distribution with GNOME on MIPS24KF (mipsel). When I run several applications after a while (3-4 hours not deterministic) my applications crashes. My dmesg shows the following: Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): starting (version 2.16.1), pid 1799 user 'root' Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0 Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1 Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2 Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3 Nov 6 21:08:43 hz-stb-1 gconfd (root-1799): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4 Does anyone knows why this could be? Thanks! -- View this message in context: http://www.nabble.com/gconf-strange-message-tf4698544.html#a13431286 Sent from the Debian Devel mailing list archive at Nabble.com. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
