From: Al Boldi <a1426z@gawab.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Why do so many machines need "noapic"?
Date: Sat, 8 Sep 2007 07:12:51 +0300 [thread overview]
Message-ID: <200709080712.51339.a1426z@gawab.com> (raw)
Chuck Ebbert wrote:
> On 09/06/2007 07:31 AM, Andi Kleen wrote:
> > Chuck Ebbert <cebbert@redhat.com> writes:
> >> Some systems lock up without the noapic option.
> >
> > Please find patterns: cpu type, chipsets, mainboard vendors etc.
>
> This is the first one I've actually had in front of me:
>
> HP TX1000 notebook
> Nvidia C51/MCP51 mobile chipset
>
> Booting with "noapic" gives some very strange results. This is two
> snapshots of /proc/interrupts taken one second apart. It almost looks
> like timer interrupts are occurring on IRQ 0 and IRQ7 on different
> CPUs:
>
> CPU0 CPU1
> 0: 446096 6224 XT-PIC-XT timer
> 1: 342 6 XT-PIC-XT i8042
> 2: 0 0 XT-PIC-XT cascade
> 5: 3099 865 XT-PIC-XT sata_nv
> 7: 8145 494718 XT-PIC-XT ehci_hcd:usb2
> 8: 0 0 XT-PIC-XT rtc0
> 9: 323 9 XT-PIC-XT acpi
> 10: 136 36 XT-PIC-XT HDA Intel
> 11: 43884 1091 XT-PIC-XT ohci_hcd:usb1, eth0
> 12: 104 19 XT-PIC-XT i8042
> 14: 1011 25 XT-PIC-XT libata
> 15: 0 0 XT-PIC-XT libata
> NMI: 0 0
> LOC: 6212 445951
> ERR: 403241
> MIS: 0
You may want to try to reconfigure your bios to reserve irq 5/7 for isa only.
Then post /proc/interrupts again.
Thanks!
--
Al
next reply other threads:[~2007-09-08 4:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-08 4:12 Al Boldi [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-05 23:30 Chuck Ebbert
2007-09-06 11:31 ` Andi Kleen
2007-09-07 19:34 ` Chuck Ebbert
2007-09-08 5:17 ` Prakash Punnoor
2007-09-10 19:12 ` Chuck Ebbert
2007-09-10 19:44 ` Andi Kleen
2007-09-10 23:33 ` Chuck Ebbert
2007-09-13 16:38 ` Chuck Ebbert
2007-09-25 9:06 ` Thomas Gleixner
2007-09-15 7:39 ` Andrew Morton
2007-09-15 10:58 ` Ingo Oeser
2007-09-15 11:08 ` Andrew Morton
2007-09-15 12:08 ` Matthew Garrett
2007-09-24 21:32 ` Dave Jones
2007-09-27 22:03 ` Phillip Susi
2007-09-15 18:42 ` Rafael J. Wysocki
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=200709080712.51339.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®