mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Oeser <ioe-lkml@rameria.de>
To: Brian Beattie <beattie@beattie-home.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: serverworks usb under 2.4.22
Date: Fri, 14 Nov 2003 08:51:00 +0100	[thread overview]
Message-ID: <200311140851.09228.ioe-lkml@rameria.de> (raw)
In-Reply-To: <1068769021.884.4.camel@kokopelli>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Brian,
hi lkml,

On Friday 14 November 2003 01:17, Brian Beattie wrote:
> I've got a system with a Super Micro P3 dual processor board.  This
> board uses the Serverworks chipset and the 2.4.22 kernel is unable to
> allocate an IRQ when initializing the USB (usb-ohic) interface.  This
> board works fine under 2.4.20 and 2.4.21.

Which Serverworks chipset? There are various.

I for one need to pass "noapic" on the kernel command line. Otherwise
the IRQ routing is broken, I can't get the USB IRQ and the kernel complains.
a lot about a broken APIC IRQ routing.

My board is an ASUS CUR-CLS. The chipset there is "ServerWorks LE".

Hop that helps.


Regards

Ingo Oeser


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/tIlrU56oYWuOrkARAsPBAKDVHqTnQHRlgB7CdMphY70GpVn3fQCdE8bQ
U4/gpKuad2q40FAPqmAeC6I=
=kUSh
-----END PGP SIGNATURE-----


  reply	other threads:[~2003-11-14  7:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-14  0:17 Brian Beattie
2003-11-14  7:51 ` Ingo Oeser [this message]
2003-11-14 16:04   ` Brian Beattie
2003-11-14  1:24 rico-linux-kernel
2003-11-14 14:57 ` Brian Beattie
2003-11-14  8:58 rico-linux-kernel

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=200311140851.09228.ioe-lkml@rameria.de \
    --to=ioe-lkml@rameria.de \
    --cc=beattie@beattie-home.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

all inboxes | Powered by JetHome®