Bug 34028

Summary:	X locks up Machine in SMP mode - QA0327
Product:	[Retired] Red Hat Linux	Reporter:	Daniel Powell <djpowell>
Component:	XFree86	Assignee:	Mike A. Harris <mharris>
Status:	CLOSED NOTABUG	QA Contact:	David Lawrence <dkl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.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:	2001-03-30 07:49:21 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:

Description Daniel Powell 2001-03-30 07:35:55 UTC

I know QA0328 is out but.... 


with QA0327 in SMP mode, X completely locks the machine after a bit.

either using KDE, or GNOME, I was browsing with mozilla or netscape, and 
the machine harware locked.... No such issue in uniprocessor mode.

will test with QA 0328 asap.

Comment 1 Mike A. Harris 2001-03-30 07:49:17 UTC

This doesn't mean it is an SMP problem, nor an X problem necessarily.
This isn't conclusive, but I run X SMP for many months on my
server here and I've not had a single crash.  This is using a
Mach64 based Rage IIc.  While that doesn't rule out an X problem
but I would lean more toward it being a kernel issue than an
X problem.

Check your /var/log/messages for "Oops" messages from the kernel.  If
you find one, then it is definitely a kernel issue.  If not, that doesn't
mean it isn't a kernel issue though.

Using the link below, please attach your X config file, and your X server
logs, /var/log/messages from the time of the incident, as well as the
output of "lspci -vn" and also "lspci -v".

Comment 2 Mike A. Harris 2001-05-28 23:51:52 UTC

Bug closed due to lack of requested information.  If this is still a bug
in the final release of seawolf, and not corrected after applying all available
updates that have been released for the distro, please supply the requested
information, and reopen the bug so it can be looked into.  Thanks.