On Sat, Feb 16, 2008 at 06:40:08PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On Saturday 16 February 2008, Borislav Petkov wrote:
> > On Sat, Feb 16, 2008 at 04:24:46PM +0100, Bartlomiej Zolnierkiewicz wrote:
> > >
> > > [ added Borislav (ide-cd maintainer) to cc: ]
> > >
> > > Hi,
> > >
> > > Unless there are some very important reasons to keep the discussion
> > > private
> > > please always cc: linux-ide@ and/or linux-kernel@ ML when reporting
> > > problems.
> > >
> > > Othewise your mail misses many knowledgeable people and is left on mercy
> > > of clueless IDE maintainer... ;-)
> > >
> > > ---------- Forwarded Message ----------
> > >
> > > Subject: IDE cdrom problem
> > > Date: Saturday 16 February 2008
> > > From: WaVeR <[EMAIL PROTECTED]>
> > > To: [EMAIL PROTECTED]
> > >
> > > Hello Bart,
> > >
> > > Sorry to distrub you, but I have a similar problem like this post
> > > http://lkml.org/lkml/2008/2/12/97
> > >
> > > I'm not subscribed to linux ML, so I decide to write you directly.
> > >
> > >
> > > >From my dmesg, I get this error:
> > >
> > > Feb 16 08:01:58 Jupiter kernel: hdc: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> > > Feb 16 08:06:16 Jupiter kernel: hdc: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> > > Feb 16 08:10:45 Jupiter kernel: hdd: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> > > Feb 16 08:37:41 Jupiter kernel: hdd: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> > > Feb 16 08:42:10 Jupiter kernel: hdc: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> > > Feb 16 09:00:07 Jupiter kernel: hdd: cdrom_pc_intr: The drive appears
> > > confused (ireason = 0x01). Trying to recover by ending request.
> >
> > Yeah, this is kinda funny, i think i've seen that somewhere :) But
> > seriously,
>
> Yep, this looks to be the identical problem as discussed recently:
>
> http://www.mail-archive.com/[email protected]/msg16131.html
>
> [ + IIRC the similar issue might be already in the kernel bugzilla... ]
>
> > can you try 2.6.25-rc2 - this one should be stable enough and it has the
> > ide-cd
> > rewrite in there and it would be interesting to see whether the new
> > interrupt
> > handler shows the same behaviour.
> >
> > Bart, since this starts to occur often, i'm thinking of adding a debugging
> > macro
> > similar to the ones we rewrote in ide-floppy and ide-tape besides the
> > CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS facility in ide-cd. What are your
> > thoughts
> > on the matter?
>
> I would rather prefer to see more code removal/unification in ide-cd.
Yep, this is underway. Am working on removing the ide-cd internal buffer and
will get back to you after testing it... Ide floppy will have to wait.
>
> [ If the code is simple/clean enough and have informative printk()-s for
> error conditions there shouldn't be a frequent need for an extra debugging
> information. ]
>
> > > As you can see on the atached file. It's a simple IDE dvdrom and a cd
> > > burner.
> > >
> > > I dont have this problem with the kernel 2.6.21.3
> > >
> > > My actual kernel is:
> > > 9:28 [EMAIL PROTECTED] ~% uname -a
> > > Linux Jupiter 2.6.24.2-waver.1 #1 Wed Feb 13 23:53:31 CET 2008 i686
> > > GNU/Linux
>
> It would also help us if it can be narrowed down to the specific commit.
> Please install git package, get kernel git tree from kernel.org, and do:
>
> git bisect start
> git bisect good 2.6.21
> git bisect bad 2.6.24
What would decrease the number of bisection iterations would be specifying the
path for bisection, like so:
git bisect start -- drivers/ide
and then we'll nail down the evildoer significantly faster, imho.
>
> It will select the kernel to test - compile and boot it to see if the problem
> is still there. If so do "git bisect bad" which will give you new kernel
> to test. If the kernel works fine do "git bisect good" instead. After few
> iterations you should find the exact commit which introduced the bug.
>
> Thanks,
> Bart
--
Regards/Gruß,
Boris.
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
