All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 13345] New: panic when reading data from IDE CDROM with >= 2.6.29 kernels
Date: Tue, 19 May 2009 21:29:01 GMT	[thread overview]
Message-ID: <bug-13345-11633@http.bugzilla.kernel.org/> (raw)

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

           Summary: panic when reading data from IDE CDROM with >= 2.6.29
                    kernels
           Product: IO/Storage
           Version: 2.5
    Kernel Version: 2.6.30-rc5
          Platform: All
        OS/Version: Linux
              Tree: Mainline
            Status: NEW
          Severity: normal
          Priority: P1
         Component: IDE
        AssignedTo: io_ide@kernel-bugs.osdl.org
        ReportedBy: modestas@vainius.eu
        Regression: Yes


Created an attachment (id=21439)
 --> (http://bugzilla.kernel.org/attachment.cgi?id=21439)
Backtrace of the OOPS with 2.6.30-rc5

Hello,

I get kernel panic when data is read from IDE CDROM with 2.6.29 or later
kernels (testing 2.6.30-rc5 at the moment). I have never had the issue with
2.6.28 and earlier kernels.

I suspect the cause though. My CD/DVD drive is pretty old and might be a bit
faulty (or this might kernel be misinterpreting my drive sometimes). <= 2.6.28
kernels used to turn off DMA due to seek errors (if I recall correctly)
sometimes. However, I used to be able to turn DMA back on with hdparm and I
have never really had read() failures. Now with >= 2.6.29 I have never seen DMA
being turn off on my CD/DVD drive but I guess kernel just panics instead. So I
suspect there is a regression in the latest kernels which triggers
unrecoverable panic instead of drive reset.

I got the attached backtrace (sorry, I couldn't do better than this picture)
with 2.6.30-rc5 on Debian unstable amd64 box while doing a simple:

$ dd if=/dev/cdrom of=/dev/null bs=1M

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

             reply	other threads:[~2009-05-19 21:28 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19 21:29 bugzilla-daemon [this message]
2009-05-19 21:43 ` [Bug 13345] panic when reading data from IDE CDROM with >= 2.6.29 kernels 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
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=bug-13345-11633@http.bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.