From: "Lenar Lõhmus" <lenar@vision.ee>
To: s0348365@sms.ed.ac.uk
Cc: "Arjen Verweij" <A.Verweij2@ewi.tudelft.nl>,
"Andrew Morton" <akpm@osdl.org>,
"Luis Miguel García" <ktech@wanadoo.es>,
linux-kernel@vger.kernel.org, acpi-devel@lists.sourceforge.net
Subject: Re: 2.6.2-mm1 aka "Geriatric Wombat"
Date: Fri, 06 Feb 2004 10:39:05 +0200 [thread overview]
Message-ID: <402352A9.7090705@vision.ee> (raw)
In-Reply-To: <200402052130.30344.s0348365@sms.ed.ac.uk>
Alistair John Strachan wrote:
>This fix doesn't work for me because I get problems if I disable ACPI IRQ
>routing and still have apic enabled. Normally these problems would be
>gracefully solved, but my USB HCD complains about not having been assigned an
>IRQ.
>
>
Actually it's exactly the same here I'm just not bothered by my USB HCD
not having an IRQ since
my USB mouse still works.
It says this when booting:
PCI: No IRQ known for interrupt pin A of device 0000:00:02.0. Please try
using pci=biosirq.
drivers/usb/core/hcd-pci.c: Found HC with no IRQ. Check BIOS/PCI
0000:00:02.0 setup!
All I can say is that in 2.6.1-rc1-mm1 it worked and I could have all my
interrupts off the XT-PIC.
Lenar
next prev parent reply other threads:[~2004-02-06 8:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-05 9:44 2.6.2-mm1 aka "Geriatric Wombat" Andrew Morton
2004-02-05 9:52 ` [PATCH] via crypto beginnings Jeff Garzik
2004-02-05 10:11 ` Andrew Morton
2004-02-05 9:55 ` 2.6.2-mm1 aka "Geriatric Wombat" Nikita Danilov
2004-02-05 10:00 ` Russell King
2004-02-05 10:37 ` Jeff Garzik
2004-02-05 10:50 ` Russell King
2004-02-05 11:47 ` Nick Piggin
2004-02-05 16:11 ` Martin J. Bligh
2004-02-05 16:16 ` Nick Piggin
2004-02-05 16:20 ` Nikita Danilov
2004-02-05 13:57 ` Alistair John Strachan
2004-02-05 14:16 ` Lenar Lõhmus
2004-02-05 19:57 ` 2.6.2-mm1 [are these mine?] Maciej Soltysiak
2004-02-05 20:11 ` Randy.Dunlap
2004-02-05 20:14 ` Randy.Dunlap
2004-02-05 21:30 ` 2.6.2-mm1 aka "Geriatric Wombat" Alistair John Strachan
2004-02-06 8:39 ` Lenar Lõhmus [this message]
2004-02-05 14:16 ` Matthias Urlichs
2004-02-05 17:58 ` John Cherry
2004-02-05 23:12 ` [patch] 2.6.2-mm1: fix warning introduced by input-2wheel-mouse-fix Adrian Bunk
2004-02-06 0:22 ` Zephaniah E. Hull
2004-02-05 19:23 ` 2.6.2-mm1 aka "Geriatric Wombat" Deepak Saxena
2004-02-05 20:05 ` Greg KH
2004-02-05 23:31 ` 2.6.2-mm1 aka "Geriatric Wombat" DIO read race still fails Daniel McNeil
2004-02-05 23:58 ` Badari Pulavarty
2004-02-06 22:37 ` Daniel McNeil
2004-02-06 0:07 ` Andrew Morton
2004-02-06 0:32 ` Daniel McNeil
2004-02-06 18:02 ` 2.6.2-mm1 aka "Geriatric Wombat" Thomas Davis
-- strict thread matches above, loose matches on Subject: below --
2004-02-05 12:01 Luis Miguel García
2004-02-05 16:18 ` Andrew Morton
[not found] <fa.h1qu7q8.n6mopi@ifi.uio.no>
2004-02-05 13:11 ` Robert Gadsdon
2004-02-05 18:26 ` Greg KH
2004-02-05 18:29 ` Ben Collins
2004-02-05 20:14 ` Andrew Morton
2004-02-05 20:29 ` Ben Collins
2004-02-06 14:47 ` Ben Collins
2004-02-06 18:22 ` Greg KH
2004-02-06 18:39 ` Ben Collins
2004-02-07 17:27 ` Ben Collins
2004-02-07 19:13 ` Greg KH
2004-02-07 23:08 ` Ben Collins
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=402352A9.7090705@vision.ee \
--to=lenar@vision.ee \
--cc=A.Verweij2@ewi.tudelft.nl \
--cc=acpi-devel@lists.sourceforge.net \
--cc=akpm@osdl.org \
--cc=ktech@wanadoo.es \
--cc=linux-kernel@vger.kernel.org \
--cc=s0348365@sms.ed.ac.uk \
/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