Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 78417 - Dell GX260 ACPI issue
Dell GX260 ACPI issue
Status: CLOSED DUPLICATE of bug 82123
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Garzik
Brian Brock
Depends On:
Blocks: 79578
  Show dependency treegraph
Reported: 2002-11-22 11:57 EST by Michael Redinger
Modified: 2013-07-02 22:08 EDT (History)
2 users (show)

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

Attachments (Terms of Use)
output of lspci -vvv (7.34 KB, text/plain)
2002-11-22 11:59 EST, Michael Redinger
no flags Details
output of lspci -n -vvv (6.37 KB, text/plain)
2002-11-22 12:00 EST, Michael Redinger
no flags Details
output of dmidecode (10.21 KB, text/plain)
2002-11-22 15:32 EST, Michael Redinger
no flags Details

  None (edit)
Description Michael Redinger 2002-11-22 11:57:56 EST
GinGin Beta 1 does not work out of the box on my Dell Optiplex GX 260.
Linux starts ("Uncompressing Linux ...ok, now booting the kernel", and then the
computer is immediately rebooted.

This works fine if I use "ACPI=off".
Comment 1 Michael Redinger 2002-11-22 11:59:02 EST
Created attachment 86067 [details]
output of lspci -vvv
Comment 2 Michael Redinger 2002-11-22 12:00:10 EST
Created attachment 86068 [details]
output of lspci -n -vvv
Comment 3 Arjan van de Ven 2002-11-22 12:27:06 EST
can you also attach dmidecode?
(needed for blacklist purposes)
Comment 4 Michael Redinger 2002-11-22 15:32:43 EST
Created attachment 86107 [details]
output of dmidecode
Comment 5 Jeff Garzik 2003-01-17 16:06:07 EST

*** This bug has been marked as a duplicate of 82123 ***
Comment 6 Red Hat Bugzilla 2006-02-21 13:50:11 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.