When starting net-misc/rdesktop-1.5.0-r3 as a client from a Gentoo machine connecting to an XP machine, it completely locks up the client (Gentoo) computer, after partially rendering the screen. The lock-up point varies between partially rendering the login screen of the XP and partial rendering of the Windows desktop after a successful log-in. However, the Gentoo machine gets invariably locked - it responds neither to mouse nor to the keyboard. Only pulling the plug has an affect. Every time rdesktop locks up the client (Gentoo) machine, the caps led starts blinking. rdesktop does not generate a core dump on its own. It does not generate a backtrace when run from gdb either before locking up the computer. # emerge -pv net-misc/rdesktop These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] net-misc/rdesktop-1.5.0-r3 USE="ao -debug* -ipv6 -oss" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB # emerge -pv x11-base/xorg-server These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] x11-base/xorg-server-1.3.0.0-r5 USE="dri nptl xorg (-3dfx) -debug -dmx -ipv6 -kdrive -minimal -sdl -xprint" INPUT_DEVICES="evdev keyboard mouse synaptics -acecad -aiptek -calcomp -citron -digitaledge -dmc -dynapro -elo2300 -elographics -fpit -hyperpen -jamstudio -joystick -magellan -microtouch -mutouch -palmax -penmount -spaceorb -summa -tek4957 -ur98 -vmmouse -void -wacom" VIDEO_CARDS="nvidia -apm -ark -chips -cirrus -cyrix -dummy -epson -fbdev -fglrx -glint -i128 (-i740) -i810 (-impact) (-imstt) -mach64 -mga -neomagic (-newport) (-nsc) -nv -r128 -radeon -rendition -s3 -s3virge -savage -siliconmotion -sis -sisusb (-sunbw2) (-suncg14) (-suncg3) (-suncg6) (-sunffb) (-sunleo) (-suntcx) -tdfx -tga -trident -tseng -v4l -vesa -vga -via -vmware -voodoo" 0 kB Total: 1 package (1 reinstall), Size of downloads: 0 kB
Created attachment 143552 [details] emerge --info
Created attachment 143554 [details] /etc/X11/xorg.conf
(In reply to comment #0) > Every time rdesktop locks up the client (Gentoo) machine, the caps led starts > blinking. This is a kernel problem; attach dmesg and lspci -vvnn output here.
Created attachment 143836 [details] dmesg
Created attachment 143838 [details] lspci -vvnn
Attached outputs of dmesg and lspci -vvnn.
The same exactly problem was encountered using kde-base/krdc-3.5.8.
Does it happen without the proprietary nvidia drivers as well?
Please also test gentoo-sources and vanilla-sources.
1. The open source nv driver doesn't seem to work with this video card - X server simply would not start. Even X server from Live CD, which uses nv driver, does not start. 2. sys-kernel/gentoo-sources-2.6.23-r8 seems to be working fine with the proprietary nvidia driver. 3. sys-kernel/hardened-sources-2.6.23-r6 (on a different machine) with the proprietary nvidia driver also works without a problem. 4. The last time I tried rdesktop with sys-kernel/tuxonice-sources-2.6.24-r2, it worked for about 15 s before locking up. I am attaching the output produced by rdesktop during that time, although I doubt it would be of any use. Nothing new appeared in dmesg, syslog or kernel.log.
Created attachment 144277 [details] rdesktop output
(In reply to comment #10) > 2. sys-kernel/gentoo-sources-2.6.23-r8 seems to be working fine with the > proprietary nvidia driver. Please test gentoo-sources-2.6.24-r2, not 2.6.23. > 3. sys-kernel/hardened-sources-2.6.23-r6 (on a different machine) with the > proprietary nvidia driver also works without a problem. Always please test kernel issues on the same machine.
Tried gentoo-sources-2.6.24-r2 with the proprietary nvidia driver (on the same machine that fails on tuxonice) - works beautifully.
Actually, taking it back - the same problem with gentoo-sources-2.6.24-r2.
(In reply to comment #14) > Actually, taking it back - the same problem with gentoo-sources-2.6.24-r2. Please report the problem upstream and put a link to bug report in URL field in this one. Please also note that proprietary nvidia driver taints your kernel, so you'd have to reproduce the problem without it.
Sorry - was barking at a wrong tree. The problem has nothing to do with rdesktop or nVidia, but is caused by Cisco VPN client, which I had to use in all the tests (I don't have any Windows machine on the same network). Opened bug #212129 describing the problem.
