Bug 190781 - Kernel loop - message log ide-cd: cmd 0x3 timed out
Summary: Kernel loop - message log ide-cd: cmd 0x3 timed out
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 5
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Brian Brock
URL:
Whiteboard: MassClosed
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-05-05 03:47 UTC by Daryl Hochhalter
Modified: 2008-01-20 04:40 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-01-20 04:40:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
boot sequence for message log (27.67 KB, text/plain)
2006-05-05 03:47 UTC, Daryl Hochhalter
no flags Details

Description Daryl Hochhalter 2006-05-05 03:47:36 UTC
Description of problem: After logging in as any user in about 10-15 min. a
continual error message is logged once every 1 min.
May  4 21:56:05 FEDORA5-AMD650 gconfd (root-2220): Resolved address
"xml:readwrite:/root/.gconf" to a writable configuration source at position 1
May  4 21:56:05 FEDORA5-AMD650 gconfd (root-2220): Resolved address
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source
at position 2
May  4 22:11:40 FEDORA5-AMD650 kernel: ide-cd: cmd 0x3 timed out
May  4 22:11:40 FEDORA5-AMD650 kernel: hdd: lost interrupt
May  4 22:12:40 FEDORA5-AMD650 kernel: ide-cd: cmd 0x3 timed out
May  4 22:12:40 FEDORA5-AMD650 kernel: hdd: lost interrupt
May  4 22:13:40 FEDORA5-AMD650 kernel: ide-cd: cmd 0x3 timed out

It begins sooner if I mount the drive. I can read files from it.
It is an older CDR Mitsumi CR2801TE.


Version-Release number of selected component (if applicable):
kernel-2.6.15-1.FC_5

How reproducible:
Every time

Steps to Reproduce:
1.Start the system
2.Log in
3.Wait or mount the drive
  
Actual results:
I can read files but may or may not be able to 
unmount and trying may hang the system.
Expected results:
No lost interrupt.

Additional info:
The AMI BIOS is pre 1997 cutoff
CDR is slave secondary
BIOS Auto set to PIO 3, 32 bit transfer.

Comment 1 Daryl Hochhalter 2006-05-05 03:47:36 UTC
Created attachment 128644 [details]
boot sequence for message log

Comment 2 Daryl Hochhalter 2006-05-14 16:47:49 UTC
The BIOS auto detects this drive as PIO 3 with fast 32bit transfer. I've
disconected this CDR and the log error goes away. Is there a problem having a
master CDROM that is UDMA capable and a CDR that isn't as the slave? I suppose
this could all be related to my MOBO FIC SD11 VT82C686A southbridge, AMD 751
north? However, the kernel seems to have support for this, yet the system
records errors?

Comment 3 Dave Jones 2006-10-16 18:59:48 UTC
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.

Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.

This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.

Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.

In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed.  See bug 207474 for further details.

If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.

If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.

Thank you.

Comment 4 Jon Stanley 2008-01-20 04:40:38 UTC
(this is a mass-close to kernel bugs in NEEDINFO state)

As indicated previously there has been no update on the progress of this bug
therefore I am closing it as INSUFFICIENT_DATA. Please re-open if the issue
still occurs for you and I will try to assist in its resolution. Thank you for
taking the time to report the initial bug.

If you believe that this bug was closed in error, please feel free to reopen
this bug.


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