Bug 7284
Summary: | cdrom capabilities wrong | ||
---|---|---|---|
Product: | IO/Storage | Reporter: | Johannes Berg (johannes) |
Component: | IDE | Assignee: | 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
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. 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 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? 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. Indeed, I can confirm that that commit causes the problem. This issue should be fixed in Linus' tree after commit 8770c018da7bbaa3b41371abc401b2aa7e76a71a Can you confirm it's fixed? I'll give it a try tonight or at least over the weekend and report back. Thanks for keeping track. |