Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: linux-mips@linux-mips.org
Subject: Re: IRQ problem on cobalt / 2.6.6
Date: Tue, 18 May 2004 17:46:21 -0400	[thread overview]
Message-ID: <40AA842D.9080603@gentoo.org> (raw)
In-Reply-To: <20040518211932.GB29636@getyour.pawsoff.org>

Kieran Fulke wrote:

> yeah. cleared out /usr/src and re-emerged mips-sources-2.6.6, then made 
> the change to include/asm/cobalt/cobalt.h you suggested. kernel 
> .config attached ..
> 
> Kieran.

Just to rule out a few things, try disabling the following options in 
your .config:

CONFIG_IDE_TASK_IOCTL (IDE Taskfile Access)
CONFIG_IDE_TASKFILE_IO (IDE Taskfile IO)

CONFIG_TULIP_MWI (New bus configuration)
CONFIG_TULIP_MMIO (Use PCI shared mem for NIC registers)
CONFIG_TULIP_NAPI (Use NAPI RX polling)
CONFIG_TULIP_NAPI_HW_MITIGATION (Use Interrupt Mitigation)


Taskfile access is, afaict, needed only if you're doing disk forensics 
or such.  The new taskfile IO code hung up on me a few times on Cobalt 
when I was initially testing some of Peter's 2.6.x patches, and as such, 
I haven't cut it on since then.

Tulip, I don't recall which, but I *think* one of them also caused me 
some kind of an issue, I'm unsure if it was a hang or something else. In 
either case, I left them as is.

See if turning those off does anything different.


--Kumba

-- 
"Such is oft the course of deeds that move the wheels of the world: 
small hands do them because they must, while the eyes of the great are 
elsewhere."  --Elrond

  reply	other threads:[~2004-05-18 21:44 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 18:30 IRQ problem on cobalt / 2.6.6 Kieran Fulke
2004-05-14  7:43 ` Peter Horton
2004-05-16 11:36   ` Kieran Fulke
2004-05-16 15:21     ` Johannes Stezenbach
2004-05-16 15:21       ` Johannes Stezenbach
2004-05-16 17:04       ` Ralf Baechle
2004-05-16 17:11         ` Kieran Fulke
2004-05-16 17:21         ` Johannes Stezenbach
2004-05-16 18:04           ` Kieran Fulke
2004-05-17  8:40         ` Peter Horton
2004-05-17 11:46           ` Kieran Fulke
2004-05-17 11:57             ` Peter Horton
2004-05-17 12:04               ` Kieran Fulke
2004-05-17 12:20                 ` Peter Horton
2004-05-17 15:07 ` Stuart Longland
2004-05-18  7:34 ` Peter Horton
2004-05-18 17:39   ` Kieran Fulke
2004-05-18 20:59   ` Kieran Fulke
2004-05-18 21:09     ` Kieran Fulke
2004-05-18 21:12     ` Peter Horton
     [not found]       ` <20040518211810.GA29636@getyour.pawsoff.org>
2004-05-18 21:19         ` Kieran Fulke
2004-05-18 21:46           ` Kumba [this message]
2004-05-18 21:38         ` Peter Horton
2004-05-18 22:02           ` Kieran Fulke
2004-05-19 11:23     ` Maciej W. Rozycki
2004-05-19 12:57       ` Peter Horton
  -- strict thread matches above, loose matches on Subject: below --
2004-05-16 17:37 Kieran Fulke

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=40AA842D.9080603@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=linux-mips@linux-mips.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