From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: bennyb@ntplx.net (Benedict Bridgwater)
Cc: linux-kernel@vger.kernel.org (Linux-Kernel)
Subject: Re: 2.4.4-ac5 aic7xxx causes hang on my machine
Date: Wed, 9 May 2001 15:06:06 +0100 (BST) [thread overview]
Message-ID: <E14xUbS-0002Op-00@the-village.bc.nu> (raw)
In-Reply-To: <3AF93F2B.8EC5F912@ntplx.net> from "Benedict Bridgwater" at May 09, 2001 08:59:23 AM
> This has been reported to both Mandrake and Redhat:
>
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=29555
>
> I've been trying to find out if there's a fix (if it's aic7xxx 6.1.13
> that's great!), but Redhat seem to believe it's a 2.4 kernel PCI bug:
Personally I still think its a BIOS bug in those Intel BIOS boards. Hopefully
some of the VA folks will eventually have time to double check the BIOS
$PIRQ routing table on these systems and verify if the kernel is parsing it
wrong or if its wrong in the BIOS ROM
next prev parent reply other threads:[~2001-05-09 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 12:59 Benedict Bridgwater
2001-05-09 14:06 ` Alan Cox [this message]
2001-05-09 15:25 ` Doug Ledford
2001-05-09 15:49 ` Alan Cox
2001-05-09 15:52 ` Doug Ledford
2001-05-09 16:10 ` Alan Cox
2001-05-09 16:21 ` Doug Ledford
2001-05-09 16:59 ` Alan Cox
2001-05-09 17:08 ` Doug Ledford
2001-05-09 17:16 ` Alan Cox
[not found] ` <3AF96271.81C27F57@mandrakesoft.com>
[not found] ` <3AF9661B.1707F5E3@redhat.com>
[not found] ` <3AF96811.3C6C196D@mandrakesoft.com>
[not found] ` <3AF96B39.7C7888F4@redhat.com>
[not found] ` <3AF96D99.AB18CB4F@mandrakesoft.com>
[not found] ` <3AF97DE0.3C6455A6@ntplx.net>
2001-05-10 14:39 ` Ben Bridgwater
2001-05-09 16:21 ` Andy Carlson
-- strict thread matches above, loose matches on Subject: below --
2001-05-07 12:43 [Patch] Do not account shmem pages to the page cache Christoph Rohland
2001-05-07 13:04 ` 2.4.4-ac5 aic7xxx causes hang on my machine Andy Carlson
2001-05-07 13:58 ` Oyvind Jagtnes
2001-05-07 14:14 ` Justin T. Gibbs
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=E14xUbS-0002Op-00@the-village.bc.nu \
--to=alan@lxorguk.ukuu.org.uk \
--cc=bennyb@ntplx.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®