From: Tejun Heo <htejun@gmail.com>
To: Parag Warudkar <parag.lkml@gmail.com>
Cc: linux-ide@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: 2.6.28-rc3: OOPS libata-eh.c:3259
Date: Sun, 09 Nov 2008 12:43:25 +0900 [thread overview]
Message-ID: <49165C5D.9090403@gmail.com> (raw)
In-Reply-To: <f7848160811081814q1dff8fa5t82a226a354766c6c@mail.gmail.com>
Hello,
Parag Warudkar wrote:
> Got the below oopses while trying to burn a CDRW.
>
> libata-eh.c:3259 is -
> /* make sure nr_active_links is zero after EH */
> WARN_ON(ap->nr_active_links);
(cc'ing Jens) I saw this yesterday too and am debugging it. I think
it's related to recent conversion to block layer tagging. I'll
investigate and let you know when I know more.
Thanks.
--
tejun
prev parent reply other threads:[~2008-11-09 3:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-09 2:14 2.6.28-rc3: OOPS libata-eh.c:3259 Parag Warudkar
2008-11-09 3:43 ` Tejun Heo [this message]
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=49165C5D.9090403@gmail.com \
--to=htejun@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=parag.lkml@gmail.com \
--cc=torvalds@linux-foundation.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).