From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: K G <gege86hu@yahoo.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "irq 16: nobody cared!" -errors after motherboard-switch (ABIT IS7-E2 motherboard)
Date: Wed, 01 Dec 2004 21:33:57 +0000 [thread overview]
Message-ID: <1101936835.30819.69.camel@localhost.localdomain> (raw)
In-Reply-To: <20041201174010.95519.qmail@web60505.mail.yahoo.com>
On Mer, 2004-12-01 at 17:40, K G wrote:
> I've recently switched from an "ASUS P4T533-C"
> motherboard to an "ABIT IS7-E2", and got the errors
> mentioned above after boot. Only the motherboard and
> the ram was changed (rambus -> INFINEON 400Mhz DDR).
Those generally indicate bad interrupt routing but could given the other
information you provide just indicate a dud board.
> got the same error(SourceMage linux). Interestingly
> UHU-Linux hasn't got any errors(maybe because the 2.4
kernel it uses).
Try booting with the option "acpi=off"
> So I've figured that the IRQ is shared between the two
> onboard 1.1 USB hubs and the vga card. My vga is an
> NVIDIA GeForce4 Ti4200 btw.
Thats fine in itself well assuming the Nvidia driver is being polite
which I would imagine it is. Its binary only so we can only hope not
check.
> Oh, and when I tried to install windows XP for my sis
> on the same computer it hangs after it copied the
> files to hdd, and rebooted the system. It stays there
Sounds like a dud board then ? We see a lot of broken interrupt routing
reports but they usually work on Windows XP by chance and that was all
the vendor tested.
next prev parent reply other threads:[~2004-12-01 22:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-01 17:40 "irq 16: nobody cared!" -errors after motherboard-switch (ABIT IS7-E2 motherboard) K G
2004-12-01 19:52 ` K G
2004-12-01 21:33 ` Alan Cox [this message]
2004-12-01 22:45 ` Jeff Garzik
2004-12-03 15:02 ` K G
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=1101936835.30819.69.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=gege86hu@yahoo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.