From: Martin Steigerwald <Martin@lichtvoll.de>
To: Tejun Heo <tj@kernel.org>
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 11:31:15 +0100 [thread overview]
Message-ID: <201012211131.27698.Martin@lichtvoll.de> (raw)
In-Reply-To: <4D0F8E98.9070500@kernel.org>
[-- Attachment #1: Type: Text/Plain, Size: 2227 bytes --]
Am Monday 20 December 2010 schrieb Tejun Heo:
> Hello,
>
> On 12/20/2010 11:05 AM, Martin Steigerwald wrote:
> > Hi!
> >
> > top - 10:49:07 up 3 days, 14:24, 8 users, load average: 2.31, 2.62,
> > 2.28 Tasks: 198 total, 2 running, 194 sleeping, 0 stopped, 2
> > zombie Cpu(s): 6.8%us, 93.2%sy, 0.0%ni, 0.0%id, 0.0%wa, 0.0%hi,
> > 0.0%si, 0.0%st
> > Mem: 2073660k total, 1941152k used, 132508k free, 153876k
> > buffers Swap: 4000180k total, 243452k used, 3756728k free,
> > 676612k cached
> >
> > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> > 735 root 20 0 0 0 0 R 85.2 0.0 137:28.94
> > scsi_eh_11
> >
> > I don't see anything in dmesg. Everything appears to work as normal,
> > except for the slowness. Which got a bit better upon renicing
> > scsi_eh_11 to 19 (not knowing whether its really safe, but it works
> > for now).
>
> > Interrupts appear to be within usual range as well:
> Can you please apply the following patch, trigger the problem and
> attach the kernel log?
>
> 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).
Thanks,
--
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-12-21 10:31 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 [this message]
2010-12-21 11:03 ` Tejun Heo
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=201012211131.27698.Martin@lichtvoll.de \
--to=martin@lichtvoll.de \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=tj@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