9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Geoff Collyer <geoff@collyer.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] venti+fossil woes
Date: Tue, 18 Nov 2003 15:59:15 -0800	[thread overview]
Message-ID: <08790b4d96512506b011f9bedb43ac1f@collyer.net> (raw)
In-Reply-To: <20031118233023.GJ65844@cassie.foobarbaz.net>

Wow, your irqalloc output is already sorted; I have to sort mine by
hand.

It seems odd that sdC doesn't show up (at irq 14).  I only have one
CPU server with IDE disk(s), but its irqs look like this:

; sort +1nb  '#P/irqalloc'
          3           0 debugpt
          7           0 mathemu
          8           0 doublefault
          9           0 mathover
         14           0 fault386
         16           0 matherror
         32           0 clock
         33           1 kbd
         38           6 floppy
         42          10 ether1
         44          12 ether0
         46          14 sdC (ata)
         47          15 sdD (ata)

You've got sdE and sdF sharing irq 9 and usb0 and ether0 sharing irq
11 (yet irqs 10 and 12 are unused).  This could be due to a buggy BIOS
(I've got a few of those), but more likely your BIOS is running out of
irqs that it knows to be free and thus doubles up devices.  It would
be worthwhile to go into BIOS setup and disable any devices you aren't
using, to reclaim their IRQs.  Also visit your PCI/PNP assignment
screen and let PCI/PNP have all free irqs, or turn off manual
selection of free irqs.

On a CPU server, you can probably disable all LPT (parallel) ports at
irqs 5 and 7, COM2 (second serial port) at irq 3, and PS/2 mouse at
irq 12.  If you're not using USB, don't assign it an irq.  If there's
an option to assign your vga card an irq, disable it.  I'm not sure
what's sitting on irq 10; maybe vga.  Make sure your first IDE
controller is enabled (in your `integrated peripherals' screen); it
should appear at irq 14.



  reply	other threads:[~2003-11-18 23:59 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14 23:18 Christopher Nielsen
2003-11-14 23:23 ` Geoff Collyer
2003-11-14 23:34   ` Christopher Nielsen
2003-11-14 23:37 ` Charles Forsyth
2003-11-14 23:43   ` Christopher Nielsen
2003-11-15  0:17     ` Charles Forsyth
2003-11-15  1:00       ` Christopher Nielsen
2003-11-14 23:43   ` boyd, rounin
     [not found] ` <20031116013757.GO834@cassie.foobarbaz.net>
2003-11-18 12:40   ` Christopher Nielsen
2003-11-18 14:08     ` Russ Cox
2003-11-18 15:27       ` Charles Forsyth
2003-11-18 22:35       ` Christopher Nielsen
2003-11-18 23:10         ` jmk
2003-11-18 23:18           ` mirtchov
2003-11-18 23:30           ` Christopher Nielsen
2003-11-18 23:59             ` Geoff Collyer [this message]
2003-11-19  0:35               ` Christopher Nielsen
2003-11-19  1:12                 ` okamoto
2003-11-19  4:51                 ` Dan Cross
2003-11-19  5:59                   ` Christopher Nielsen
2003-11-19  0:03             ` jmk
2003-11-19  0:20               ` Charles Forsyth
2003-11-20  6:04               ` Christopher Nielsen
2003-11-20  9:26                 ` C H Forsyth
2003-11-20 10:14                   ` Christopher Nielsen
2003-11-18 15:36     ` SPAM: " jmk

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=08790b4d96512506b011f9bedb43ac1f@collyer.net \
    --to=geoff@collyer.net \
    --cc=9fans@cse.psu.edu \
    /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).