Bug 113173

Summary: system hardlocks when connecting using xdmcp
Product: [Fedora] Fedora Reporter: David Juran <djuran>
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED WONTFIX QA Contact: Brian Brock <bbrock>
Severity: high Docs Contact:
Priority: medium    
Version: 1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-09-29 19:57:06 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
process traces and memory dumps aquired using Magic-SysRq none

Description David Juran 2004-01-09 09:36:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030922

Description of problem:
I realize this sounds avefully far fetched. However when connecting to
a FC1 machine remotely using xdmcp after a while (minutes - hours) the
machine hardlocks and needs to be rebooted. This happens only when gdm
is configured to accept xdmcp requests. If gdm is turned off the
machine stays is stable. I've managed to capture some dumps memory
dumps using magic-Sysrq, which I'm submitting here...

Version-Release number of selected component (if applicable):
kernel-smp-2.4.22-1.2140.nptl

How reproducible:
Always

Steps to Reproduce:
1. enable xdmcp
2. log in over xdmcp, start using gnome  
3. do your daily work for a while and watch it hang.
    

Additional info:

Comment 1 David Juran 2004-01-09 09:38:05 UTC
Created attachment 96853 [details]
process traces and memory dumps aquired using Magic-SysRq

Comment 2 David Lawrence 2004-09-29 19:57:06 UTC
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
persists.

The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, 
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/