Bug 63415

Summary:	Sony CRX140E cdrom must be marked "no dma", else kernel panic
Product:	[Retired] Red Hat Linux	Reporter:	Bryce Nesbitt <bryce>
Component:	kernel	Assignee:	Arjan van de Ven <arjanv>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Brian Brock <bbrock>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2
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-30 15:39:30 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:
Bug Depends On:	63413
Bug Blocks:

Description Bryce Nesbitt 2002-04-13 14:08:43 UTC

This cdrom drive has defective DMA, leading to kernel panics.

I solve this with an /etc/sysconfig/harddiskhda file, and the
patch from Bug #63413.  The command line for a fix is:


hdparm -d0 -u0 -c0 /dev/hda
hdparm -i /dev/hda

/dev/hda:

 Model=SONY CD-RW CRX140E, FwRev=1.0n, SerialNo=
 Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
 RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
 BuffType=unknown, BuffSize=0kB, MaxMultSect=0
 (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
 IORDY=on/off, tPIO={min:180,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes: pio0 pio1 pio2 pio3 pio4 
 DMA modes: sdma0 sdma1 sdma2 mdma0 mdma1 mdma2 udma0 udma1 *udma2 
 AdvancedPM=no

Comment 1 Arjan van de Ven 2002-04-15 12:41:39 UTC

The plan is to disable dma for cdroms by default; due to the shere amount of
cdrom drives that get it wrong, combined with the effect ("hang")

Comment 2 Bryce Nesbitt 2002-04-24 01:30:45 UTC

Good move.

Comment 3 Bugzilla owner 2004-09-30 15:39:30 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/