Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 100764 - ide drive appears confused
Summary: ide drive appears confused
Status: RESOLVED DUPLICATE of bug 99288
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: AMD64 Linux
: High normal (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-29 16:26 UTC by Parag Warudkar
Modified: 2005-07-29 16:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Parag Warudkar 2005-07-29 16:26:35 UTC
With 2.6.12-gentoo-r6 kernel I started getting these errors in dmesg. 
2.6.12-gentoo-r4 works fine for me. 
 
------------------------------------------------------------------------ 
Jul 29 18:29:47 tux [   39.055179] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:30:00 tux kde(pam_unix)[9603]: session opened for user paragw by 
(uid=0) 
Jul 29 18:30:12 tux [   64.788689] codec_semaphore: semaphore is not ready 
[0x1][0x301300] 
Jul 29 18:30:12 tux [   64.788845] codec_write 0: semaphore is not ready for 
register 0x2 
Jul 29 18:30:12 tux [   64.791036] codec_semaphore: semaphore is not ready 
[0x1][0x301300] 
Jul 29 18:30:12 tux [   64.791178] codec_read 1: semaphore is not ready for 
register 0x54 
Jul 29 18:30:21 tux (paragw-9763): starting (version 2.10.0), pid 9763 user 
'paragw' 
Jul 29 18:30:21 tux (paragw-9763): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration 
source at position 0 
Jul 29 18:30:21 tux (paragw-9763): Resolved address 
"xml:readwrite:/home/paragw/.gconf" to a writable configuration source at 
position 1 
Jul 29 18:30:21 tux (paragw-9763): Resolved address 
"xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration 
source at position 2 
Jul 29 18:30:24 tux [   76.161671] codec_semaphore: semaphore is not ready 
[0x1][0x301300] 
Jul 29 18:30:24 tux [   76.161722] codec_write 0: semaphore is not ready for 
register 0x2 
Jul 29 18:31:11 tux [  102.384171] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:31:24 tux [  107.625695] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:31:24 tux [  107.632088] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:31:32 tux [  111.019055] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:31:33 tux dhcpcd[5875]: timed out waiting for a valid DHCP server 
response 
Jul 29 18:32:02 tux [  123.119241] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
Jul 29 18:32:05 tux [  124.085688] hdc: cdrom_pc_intr: The drive appears 
confused (ireason = 0x01) 
 

Reproducible: Always
Steps to Reproduce:
1. Boot kernel 
2. Watch messages in dmesg 
3. Step not necessary 
 
Actual Results:  
Got "hdc: cdrom_pc_intr: The Drive appears confused..." message 

Expected Results:  
Should have worked fine.
Comment 1 Jakub Moc (RETIRED) gentoo-dev 2005-07-29 16:33:51 UTC

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