Bug 42050 – PC locks up after displaying

Bug 42050 - PC locks up after displaying

Summary:	PC locks up after displaying

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	lilo (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	Doug Ledford
QA Contact:	Brock Organ
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2001-05-23 20:17 EDT by Laurent Dinard
Modified:	2007-04-18 12:33 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 13:48:00 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Laurent Dinard 2001-05-23 20:17:16 EDT

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)

Description of problem:
My PC locks up after displaying "Verifying DMI Pool Data......." when I 
reboot after installing Linux Redhat 7.0 without any problem. There is no 
hard drive activity after the lock-up. 


How reproducible:
Always

Steps to Reproduce:
1.Install redhat
2.Click on "exit" to restart
3.after it restarts, the PC locks up
	

Actual Results:  The PC locks up

Expected Results:  boot normally!

Additional info:

PS: Pentium II 300 w/ 64 RAM
HD: 3 G RAM

Comment 1 Jeremy Katz 2002-06-04 02:26:45 EDT

How many cylinders does your disk have?  Does this work better with more current
versions of Red Hat Linux?

Comment 2 Jeremy Katz 2002-06-29 17:47:07 EDT

Closing due to inactivity.  If you have further information, please reopen this bug.

Comment 3 Red Hat Bugzilla 2006-02-21 13:48:00 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.