Bug 7284

Summary: cdrom capabilities wrong
Product: IO/Storage Reporter: Johannes Berg (johannes)
Component: IDEAssignee: Bartlomiej Zolnierkiewicz (bzolnier)
Status: CLOSED CODE_FIX    
Severity: normal CC: axboe, bunk
Priority: P2    
Hardware: i386   
OS: Linux   
Kernel Version: 2.6.19-rc1 Subsystem:
Regression: --- Bisected commit-id:

Description Johannes Berg 2006-10-08 09:19:03 UTC
Most recent kernel where this bug did not occur: 2.6.18-rc6
Distribution: debian
Hardware Environment: powerbook
Software Environment: ?
Problem Description: cdrom driver capabilities are wrong

Steps to reproduce: cat /proc/sys/dev/cdrom/info

2.6.18-rc6 shows:
CD-ROM information, Id: cdrom.c 3.20 2003/12/17

drive name:		hdc
drive speed:		24
drive # of slots:	1
Can close tray:		1
Can open tray:		1
Can lock tray:		1
Can change speed:	1
Can select disk:	0
Can read multisession:	1
Can read MCN:		1
Reports media changed:	1
Can play audio:		1
Can write CD-R:		1
Can write CD-RW:	1
Can read DVD:		1
Can write DVD-R:	1
Can write DVD-RAM:	0
Can read MRW:		1
Can write MRW:		1
Can write RAM:		1


while 2.6.18 shows:
CD-ROM information, Id: cdrom.c 3.20 2003/12/17

drive name:		hdc
drive speed:		0
drive # of slots:	1
Can close tray:		0
Can open tray:		1
Can lock tray:		1
Can change speed:	1
Can select disk:	0
Can read multisession:	1
Can read MCN:		1
Reports media changed:	1
Can play audio:		0
Can write CD-R:		0
Can write CD-RW:	0
Can read DVD:		0
Can write DVD-R:	0
Can write DVD-RAM:	0
Can read MRW:		1
Can write MRW:		1
Can write RAM:		0

drive is a MATSHITADVD-R UJ-835E but that's about all the new kernel can tell
me, older ones had more info which I can add if needed.
Comment 1 Johannes Berg 2006-10-08 10:44:43 UTC
Sorry, that was wrong, my '2.6.18' actually had git commits from 2.6.19-rc1 in it. 

So the bug must have been introduced somewhere between 2.6.18-rc6 and 2.6.19-rc1.
Comment 2 Johannes Berg 2006-10-08 10:47:17 UTC
No, wait, even that is wrong, my 2.6.19-rc1 tree contains post-2.6.19 commits...

Let's put this into hashes to avoid more confusion...

f007cacffc8870702a1473d83ba5e4922d54e17c good
ba00003aa83a61b615542dd66f5af8fb4a7cee1d bad
Comment 3 Adrian Bunk 2006-10-08 11:02:10 UTC
This might be the same issue as described in http://lkml.org/lkml/2006/10/1/45,
caused by commit 4aff5e2333c9a1609662f2091f55c3f6fffdad36.

Can you either confirm this or bisect for what commit caused your problem?
Comment 4 Johannes Berg 2006-10-08 11:45:17 UTC
Unfortunately bisecting tends to take forever on just the powerbook (I usually
distcompile but don't have the machine here I use for that..)

I'll try before and after that commit, thanks for the pointer.
Comment 5 Johannes Berg 2006-10-08 13:22:23 UTC
Indeed, I can confirm that that commit causes the problem.
Comment 6 Adrian Bunk 2006-10-13 02:20:33 UTC
This issue should be fixed in Linus' tree after commit 
8770c018da7bbaa3b41371abc401b2aa7e76a71a

Can you confirm it's fixed?
Comment 7 Johannes Berg 2006-10-13 02:26:03 UTC
I'll give it a try tonight or at least over the weekend and report back. Thanks
for keeping track.