From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Balaji Rao <balajirrao@gmail.com>
Subject: Re: hpet_late_init hang
Date: Wed, 16 Jan 2008 07:51:33 +0100 [thread overview]
Message-ID: <20080116065133.GA26783@elte.hu> (raw)
In-Reply-To: <86802c440801151932o6aaea248w7d1137eaa2ac3579@mail.gmail.com>
(Balaji Cc:-ed)
* Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> "
> commit e5ed385fa0d6f35406e3e3ed75e5eb9adeb811df
> Author: Balaji Rao <balajirrao@gmail.com>
> Date: Tue Jan 15 16:53:29 2008 +0100
>
> Assign IRQs to HPET Timers
> "
> in x86.git
>
> cause my servers hang
> after
> Calling initcall 0xffffffff80b9a465: hpet_late_init+0x0/0x100()
i'm wondering, where does it hang exactly and why?
> after reverting that I got:
>
> initcall 0xffffffff80b947d1 ran for 19 msecs: pci_iommu_init+0x0/0x13()
> Calling initcall 0xffffffff80b9a465: hpet_late_init+0x0/0x100()
> hpet0: at MMIO 0xfed00000, IRQs 2, 8, 31
> hpet0: 3 32-bit timers, 25000000 Hz
> initcall 0xffffffff80b9a465: hpet_late_init+0x0/0x100() returned 0.
> initcall 0xffffffff80b9a465 ran for 7 msecs: hpet_late_init+0x0/0x100()
>
> CPU0 CPU1 CPU2 CPU3 CPU4 CPU5
> CPU6 CPU7
> 0: 86 0 0 0 0 0
> 1 0 IO-APIC-edge timer
> 4: 0 0 0 0 0 0
> 1 838 IO-APIC-edge serial
> 7: 1 0 0 0 0 0
> 0 0 IO-APIC-edge
> 8: 0 0 0 0 0 0
> 0 0 IO-APIC-edge rtc0
>
> for mcp55, it should already route hpet to ioapic pin2 or the irq0.
hm, these new bits:
+ /* Assign IRQs statically for legacy devices */
+ hpetp->hp_dev[0].hd_hdwirq = hdp->hd_irq[0];
+ hpetp->hp_dev[1].hd_hdwirq = hdp->hd_irq[1];
seem to be different from where we came from:
- for (i = 2; i < nrtimers; timer++, i++)
- hd.hd_irq[i] = (timer->hpet_config & Tn_INT_ROUTE_CNF_MASK) >>
- Tn_INT_ROUTE_CNF_SHIFT;
Ingo
next prev parent reply other threads:[~2008-01-16 6:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 3:32 hpet_late_init hang Yinghai Lu
2008-01-16 6:51 ` Ingo Molnar [this message]
2008-01-16 8:34 ` Balaji Rao
2008-01-16 21:39 ` Yinghai Lu
2008-01-17 16:12 ` Balaji Rao
2008-01-18 12:41 ` Ingo Molnar
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=20080116065133.GA26783@elte.hu \
--to=mingo@elte.hu \
--cc=balajirrao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yhlu.kernel@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 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.