From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrey Gusev <a.gusev1980@mail.ru>
Cc: linux-ide@vger.kernel.org, petkovbb@gmail.com,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linuxppc-dev@ozlabs.org
Subject: Re: Delay on intialization ide subsystem(most likely)
Date: Thu, 11 Jun 2009 07:46:17 +1000 [thread overview]
Message-ID: <1244670377.3352.12.camel@pasglop> (raw)
In-Reply-To: <20090611003834.7bde5e95@power-debian>
On Thu, 2009-06-11 at 00:38 +0400, Andrey Gusev wrote:
> I try this small fix, traces in disappeared, but lost interrupts on the place:)
> Some interesting thing from dmesg:
>
> [ 0.435806] irq: irq 251 on host /pci@f2000000/mac-io@17/interrupt-controller@40000 mapped to virtual irq 251
> [ 0.435824] irq: irq 252 on host /pci@f2000000/mac-io@17/interrupt-controller@40000 mapped to virtual irq 252
> [ 0.435840] irq: irq 253 on host /pci@f2000000/mac-io@17/interrupt-controller@40000 mapped to virtual irq 253
> [ 0.435856] irq: irq 254 on host /pci@f2000000/mac-io@17/interrupt-controller@40000 mapped to virtual irq 254
> [ 0.435867] CPU0: L2CR is 80080000
> [ 0.435880] CPU0: L3CR is 8f0b0000
> [478142827.057095] CPU1: L2CR was 80000
> [478142827.057133] CPU1: L2CR set to 80080000
> [478142827.057139] CPU1: L3CR was 0
> [478142827.057300] CPU1: L3CR set to 8f0b0000
> [ 0.437529] Processor 1 found.
> [ 0.437588] clockevent: decrementer mult[886] shift[16] cpu[1]
>
> This is don't look good.
What doesn't look good ? It's copying the L2CR and L3CR values over from
CPU 0 to CPU 1 when bringing the later up, I don't see anything wrong.
Cheers,
Ben.
> >
> >
> > > [ 70.584122] hdb:<3>ide-pmac lost interrupt, dma status: 8480
> >
> > DMA status indicates that DMA transfer is still active according to
> > the controller. This one is really a platform/hardware specific
> > issue.
> >
>
> Notes for Ben, I checked only 2.6.26, but may be somebody checked 2.6.24
> or this is interpolation.
>
> Thanks,
> Andrey
next prev parent reply other threads:[~2009-06-10 21:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090425170203.74603b9c@power-debian>
[not found] ` <200905131528.26940.bzolnier@gmail.com>
[not found] ` <20090513211123.24825895@power-debian>
2009-05-13 18:46 ` Delay on intialization ide subsystem(most likely) Bartlomiej Zolnierkiewicz
2009-05-15 20:40 ` Andrey Gusev
2009-05-20 15:56 ` Bartlomiej Zolnierkiewicz
2009-05-30 10:46 ` Andrey Gusev
2009-06-08 20:20 ` Bartlomiej Zolnierkiewicz
2009-06-08 23:26 ` Benjamin Herrenschmidt
2009-06-10 11:44 ` Bartlomiej Zolnierkiewicz
2009-07-05 11:17 ` Andrey Gusev
2009-07-06 15:04 ` Bartlomiej Zolnierkiewicz
2009-07-06 23:23 ` Benjamin Herrenschmidt
2009-07-07 21:18 ` Andrey Gusev
2009-07-08 1:12 ` Benjamin Herrenschmidt
2009-07-13 19:27 ` Andrey Gusev
2009-06-10 20:38 ` Andrey Gusev
2009-06-10 21:46 ` Benjamin Herrenschmidt [this message]
2009-06-10 21:57 ` Andrey Gusev
2009-06-11 0:44 ` Benjamin Herrenschmidt
2009-06-20 18:12 ` Andrey Gusev
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=1244670377.3352.12.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=a.gusev1980@mail.ru \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=petkovbb@gmail.com \
/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).