Bug 162879
| Summary: | CD drive not mountable | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Geraldo Veiga <gveiga> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED DUPLICATE | QA Contact: | Brian Brock <bbrock> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | wtogami |
| 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: | 2005-07-12 22:08:31 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: | |||
That really looks like a bad CDROM. Do you have any different CDROMs to test with? It started working again after a few days. You could be right. It had happened
before (with FC3 kernels) and I associated the event with kernel updades.
The reasons I am not just saying "never mind" are:
1. Even during the downtime under FC, it still worked under Windows XP.
2. Loading an audio CD would freeze the system.
During the boot process, there is still a funny message:
Jul 11 12:57:29 ggv-win32 kernel: ide-cd: cmd 0x28 timed out
Jul 11 12:57:29 ggv-win32 kernel: hdb: DMA interrupt recovery
Jul 11 12:57:29 ggv-win32 kernel: hdb: lost interrupt
Jul 11 12:57:29 ggv-win32 kernel: hdb: status error: status=0x58 { DriveReady
SeekComplete DataRequest }
Jul 11 12:57:29 ggv-win32 kernel: ide: failed opcode was: unknown
Jul 11 12:57:29 ggv-win32 kernel: hdb: drive not ready for command
Jul 11 12:57:29 ggv-win32 kernel: hdb: status timeout: status=0xd0 { Busy }
Jul 11 12:57:29 ggv-win32 kernel: ide: failed opcode was: unknown
Jul 11 12:57:29 ggv-win32 kernel: hdb: DMA disabled
Jul 11 12:57:29 ggv-win32 kernel: hdb: drive not ready for command
Jul 11 12:57:29 ggv-win32 kernel: hdb: ATAPI reset complete
|
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4 Description of problem: I am running FC4 on a Dell Inspiron 8100 with a SAMSUNG CD-ROM SN-124 CD Drive cannot be mounted. Loading an Audio CD causes a system crash. I had already observed this problem in some kernel releases of FC3. After loading a data CD-ROM the following messages are generated: Jul 11 00:53:57 ggv-win32 kernel: hdb: status error: status=0x58 { DriveReady SeekComplete DataRequest } Jul 11 00:53:57 ggv-win32 kernel: ide: failed opcode was: unknown Jul 11 00:53:57 ggv-win32 kernel: hdb: drive not ready for command Jul 11 00:53:58 ggv-win32 kernel: hdb: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } Jul 11 00:53:58 ggv-win32 kernel: hdb: status error: error=0x7f { IllegalLengthIndication EndOfMedia AbortedCommand MediaChangeRequested LastFailedSense=0x07 } Jul 11 00:53:58 ggv-win32 kernel: ide: failed opcode was: unknown Jul 11 00:53:58 ggv-win32 kernel: hdb: DMA disabled Jul 11 00:53:58 ggv-win32 kernel: hdb: drive not ready for command Jul 11 00:53:58 ggv-win32 kernel: hdb: ATAPI reset complete Jul 11 00:53:58 ggv-win32 kernel: hdb: status error: status=0x7f { DriveReady DeviceFault SeekComplete DataRequest CorrectedError Index Error } Version-Release number of selected component (if applicable): kernel-2.6.12-1.1390_FC4 and kernel-2.6.12-1.1387_FC4 How reproducible: Always Steps to Reproduce: 1. Boot system 2. Load CD-ROM 3. Examine /var/log/messages Actual Results: CD-ROM was not automatically mounted. If I try to open it manually with mount /dev/hdb /media/cdrom -t iso9660 The resualt is the following:mount: block device /dev/hdb is write-protected, mounting read-only mount: wrong fs type, bad option, bad superblock on /dev/hdb, missing codepage or other error (could this be the IDE device where you in fact use ide-scsi so that sr0 or sda or so is needed?) In some cases useful info is found in syslog - try dmesg | tail or so Additional info: