From: Tejun Heo <tj@kernel.org>
To: Martin Steigerwald <Martin@lichtvoll.de>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [regression] 2.6.37-rc5: scsi_eh_11 CPU loop
Date: Tue, 21 Dec 2010 12:03:56 +0100 [thread overview]
Message-ID: <20101221110355.GA981@htj.dyndns.org> (raw)
In-Reply-To: <201012211131.27698.Martin@lichtvoll.de>
Hello,
On Tue, Dec 21, 2010 at 11:31:15AM +0100, Martin Steigerwald wrote:
> > diff --git a/drivers/ata/libata-eh.c b/drivers/ata/libata-eh.c
> > index 5e59050..c748b5a 100644
> [...]
> >
> > + if (!(ap->pflags & ATA_PFLAG_LOADING) && xxx < 16) {
> > + ata_port_printk(ap, KERN_WARNING, "XXX ata_eh_set_pending()\n");
> > + dump_stack();
> > + xxx++;
> > + }
> > +
>
> I will do so with my next kernel compile - likely rc7 if it comes out
> before Christmas.
>
> As I do not know what exactly triggers it, it can take a while till I
> experience it again. I hope to be able to trigger it by inserting and
> removing the PCMCIA eSATA adapter lots of times. As the bug happened, I
> forgot to vgchange -an the LVM on the external drive. That might be or
> might not be related to triggering the issue. I will try this as well.
>
> Reported-as: https://bugzilla.kernel.org/show_bug.cgi?id=25392
>
> Might make sense to switch this bugzilla report to mail. Or use the
> bugzilla. Or just use the bugzilla for tracking and continue using mail.
> I'll do whatever suits you best (but prefer mail).
I don't care either way. Just ping me whenever you hit the problem
again.
Thanks.
--
tejun
prev parent reply other threads:[~2010-12-21 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 10:05 [regression] 2.6.37-rc5: scsi_eh_11 CPU loop Martin Steigerwald
2010-12-20 17:12 ` Tejun Heo
2010-12-21 10:31 ` Martin Steigerwald
2010-12-21 11:03 ` 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=20101221110355.GA981@htj.dyndns.org \
--to=tj@kernel.org \
--cc=Martin@lichtvoll.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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).