Bug 92436 - (IDE HIGHMEM)Rhapsody chipset, Arima Rioworks HDAMA motherboard: panic in pci_map_sg try to write thru IDE driver
Summary: (IDE HIGHMEM)Rhapsody chipset, Arima Rioworks HDAMA motherboard: panic in pci...
Status: CLOSED DUPLICATE of bug 91750
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kernel
Version: GinGin64
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Arjan van de Ven
QA Contact: Brian Brock
Depends On:
TreeView+ depends on / blocked
Reported: 2003-06-06 06:25 UTC by Eric Varsanyi
Modified: 2007-04-18 16:54 UTC (History)
0 users

Clone Of:
Last Closed: 2006-02-21 18:53:29 UTC

Attachments (Terms of Use)

Description Eric Varsanyi 2003-06-06 06:25:20 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

Description of problem:
Dual 244 Opteron processors
HDAMA version 1.40 motherboard
180G IBM IDE drive on PRI IDE channel (master)
Cheap IDE CDROM on SEC IDE channel (master).

Starting installer in text or GUI mode I get a kernel crash right after anaconda
probes the mouse, stack backtrace ends up in pci_map_sg() after making its way
thru the IDE driver.

Tried: turning off DMA in BIOS for drive, different (older 10G) IDE drive

Workaround: linux mem=4g text

After system is installed the default kernel (2.4.20-9.2smp) works fine with all
8G up (so far).

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Acquire 8G of RAM and HDAMA mobo
2. Try to install GinGin64 taking defaults

Actual Results:  Crash as described above.

Expected Results:  Installation runs to screen warning that this is a preview.

Additional info:

Mostly just reporting this to save the next person who trips on this some time
and a keyword hit in bugzilla.

Comment 1 Alan Cox 2003-06-10 17:01:05 UTC

*** This bug has been marked as a duplicate of 91750 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:53:29 UTC
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.