linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 13345] panic when reading data from IDE CDROM with >= 2.6.29 kernels
Date: Wed, 20 May 2009 18:19:31 GMT	[thread overview]
Message-ID: <200905201819.n4KIJVfd024057@demeter.kernel.org> (raw)
In-Reply-To: <bug-13345-11633@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=13345





--- Comment #6 from Modestas Vainius <modestas@vainius.eu>  2009-05-20 18:19:31 ---
I'm really sorry, but I realized that I had not rebuilt initrd when I'd
installed a new kernel with the patch applied. So I did that and I can confirm
that I no longer got OOPS but those DMA turn offs were back instead as they
used to happen with <= 2.6.28 kernels:

[  663.442788] hdd: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
[  663.445040] hdd: cdrom_decode_status: error=0x40 <3>{ LastFailedSense=0x04 }
[  663.446768] ide: failed opcode was: unknown
[  663.454549] hdd: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
[  663.456681] hdd: cdrom_decode_status: error=0x40 <3>{ LastFailedSense=0x04 }
[  663.458541] ide: failed opcode was: unknown
[  663.464783] hdd: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
[  663.466847] hdd: cdrom_decode_status: error=0x40 <3>{ LastFailedSense=0x04 }
[  663.468764] ide: failed opcode was: unknown
[  663.473414] hdd: cdrom_decode_status: status=0x51 { DriveReady SeekComplete
Error }
[  663.475365] hdd: cdrom_decode_status: error=0x40 <3>{ LastFailedSense=0x04 }
[  663.477259] ide: failed opcode was: unknown
[  663.477406] hdd: DMA disabled
[  663.520043] hdd: ATAPI reset complete

So yes, I can confirm that the patch fixes the OOPS with 2.6.30-rc5 and
2.6.30-rc6-git5. I'm looking forward to seeing the patch included in 2.6.30-rc7
and 2.6.29.x, it looks pretty important to me.

What is more, I "played" a bit with IDE cabling and switched my CD/DVD drive to
IDE master and I could not even reproduce the errors above (and hence annoying
DMA turn off is gone too) any more. So it is good news on all fronts for me.

I leave it for you to close the bug but it is fully RESOLVED as far as I'm
concerned.

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2009-05-20 18:19 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 21:29 [Bug 13345] New: panic when reading data from IDE CDROM with >= 2.6.29 kernels bugzilla-daemon
2009-05-19 21:43 ` [Bug 13345] " bugzilla-daemon
2009-05-19 21:44 ` bugzilla-daemon
2009-05-19 21:57   ` Bartlomiej Zolnierkiewicz
2009-05-19 21:53 ` bugzilla-daemon
2009-05-20  7:30 ` bugzilla-daemon
2009-05-20 14:39   ` Bartlomiej Zolnierkiewicz
2009-05-20  9:18 ` bugzilla-daemon
2009-05-20 14:35 ` bugzilla-daemon
2009-05-20 18:19 ` bugzilla-daemon [this message]
2009-05-21  7:27 ` bugzilla-daemon
2009-05-21 20:25 ` bugzilla-daemon
2009-05-21 20:53   ` Bartlomiej Zolnierkiewicz
2009-05-21 20:48 ` bugzilla-daemon
2009-05-21 20:53 ` bugzilla-daemon
2009-05-21 21:04 ` bugzilla-daemon
2009-05-23 11:52   ` Bartlomiej Zolnierkiewicz
2009-05-23 11:48 ` bugzilla-daemon
2009-05-24  6:29 ` bugzilla-daemon
2009-06-09 21:04 ` bugzilla-daemon
2009-06-10 11:20   ` Bartlomiej Zolnierkiewicz
2009-06-09 21:24 ` bugzilla-daemon
2009-06-10 11:15 ` bugzilla-daemon
2009-06-10 14:34 ` bugzilla-daemon
2009-06-12  0:49 ` bugzilla-daemon
2009-06-20 19:58 ` bugzilla-daemon
2010-01-25 15:08 ` bugzilla-daemon
2010-01-25 15:09 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200905201819.n4KIJVfd024057@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).