public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rddunlap@osdlab.org>
To: colin_bayer@compnerd.net, linux-kernel@vger.kernel.org
Subject: Re: Sticky IO-APIC problem
Date: Tue, 03 Jul 2001 14:58:50 -0700	[thread overview]
Message-ID: <3B424019.552D0BCE@osdlab.org> (raw)

Colin Bayer scribed:
| I have a Pentium III 933/133 (Coppermine, stepping 6) in an
Intel-manufactured
| i810 motherboard (hey, I

What mobo (model/name) is it?
Can you give us the output from "lspci -vv"?

| know it's a lame chipset, but it was on sale). On boot, the kernel
(version
| 2.4.6-pre8) identifies and maps the
| IO-APIC onboard, but does not assign any IRQs to it. 
| 
| The relevant boot log snippet follows. 
| 
| [root@fortytwo i386]# cat /var/log/dmesg 
|  ... 
|  ... 
| mapped APIC to ffffe000 (0121c000) 

This shows that Linux mapped the APIC (part of the processor).
It says nothing about mapping any IO APICs (unless you deleted
that part :).

So, how does one know if a (UP) system has an IO APIC and that
Linux can be configured to use the UP IO APIC code?...

(That's a serious question: does an IO APIC show up in lspci output?)

And why do you think that this system has an IO APIC?
Is it documented to have one?
[just digging for clues]

| Kernel command line: auto BOOT_IMAGE=linux-test ro root=307
| BOOT_FILE=/boot/vmlinuz-2.4.6-pre8
| devfs=mount pirq=9,4 
| PIRQ redirection, working around broken MP-BIOS. 
| ... PIRQ0 -> IRQ 9 
| ... PIRQ1 -> IRQ 4 
|  ... 
|  ... 
| 
| And /proc/interrupts: 
| [root@fortytwo i386]# cat /proc/interrupts 
|            CPU0 
|   0: 79409 XT-PIC timer 
|   1: 5911 XT-PIC keyboard 
|   2: 0 XT-PIC cascade 
|   4: 990 XT-PIC es1371 
|   8: 1 XT-PIC rtc 
|   9: 26402 XT-PIC usb-uhci, serial 
|  11: 16473 XT-PIC i810@PCI:0:1:0 
|  14: 5152 XT-PIC ide0 
|  15: 47 XT-PIC ide1 
| NMI: 0 
| ERR: 0 
| MIS: 0 
| [root@fortytwo i386]# 
| 
| This problem also occurs when booting without the pirq switch. I've
configured
| everything the way it's
| mentioned in Documentation/i386/IO-APIC.txt, but it doesn't help.
Anyway, thx in
| advance for the help. 

~Randy

             reply	other threads:[~2001-07-03 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-03 21:58 Randy.Dunlap [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-07-09 12:38 Sticky IO-APIC problem Colin Bayer
2001-07-05  4:12 Colin Bayer
2001-07-04  0:19 Colin Bayer
2001-07-03 23:03 Manfred Spraul
2001-07-02  9:25 Colin Bayer

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=3B424019.552D0BCE@osdlab.org \
    --to=rddunlap@osdlab.org \
    --cc=colin_bayer@compnerd.net \
    --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