From: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
To: Eric Olson <ejolson@unr.edu>
Cc: linux-kernel@vger.kernel.org,
Jens Dreger <Jens.Dreger@physik.fu-berlin.de>,
David Hansen <David.Hansen@physik.fu-berlin.de>
Subject: Re: FastTrack100+2.4.4 panic
Date: Sun, 13 May 2001 13:55:55 +0200 [thread overview]
Message-ID: <20010513135555.C9805@pua.nirvana> (raw)
In-Reply-To: <200105130635.f4D6ZWX10800@equinox.unr.edu>
In-Reply-To: <200105130635.f4D6ZWX10800@equinox.unr.edu>; from ejolson@unr.edu on Sat, May 12, 2001 at 11:35:32PM -0700
On Sat, May 12, 2001 at 11:35:32PM -0700, Eric Olson wrote:
> I am having trouble with the 2.4.4 kernel using MSI 694D Pro AR dual
> PIII processor motherboard with onboard Promise ATA100.
>
> I have four nearly identically configured motherboards, two of which
> have the Promise ATA100 and two which do not. There are no disks
> hooked to the Promise controller and I am not using it. However, the
> motherboards with the Promise controller panic soon after the Promise
> detection lines
>
> PDC20265: IDE controller on PCI bus 00 dev 60
> PDC20265: chipset revision 2
> PDC20265: not 100% native mode: will probe irqs later
The same happens on an MSI 6330 v3.0 (Turbo). I also tried 2.4.4-ac5 which
does not show this behaviour. The ac series have some patches related to
FastTrack/PDC20265, try it out.
BTW, do your MSI boards have a VIA chipset? If yes, do you get any IRQ
conflicts in your dmesg output?
Regards, Axel.
--
Axel.Thimm@physik.fu-berlin.de
next prev parent reply other threads:[~2001-05-13 12:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-13 6:35 FastTrack100+2.4.4 panic Eric Olson
2001-05-13 11:55 ` Axel Thimm [this message]
2001-05-13 16:20 ` Alan Cox
[not found] <20010513132716.12063.qmail@theseus.mathematik.uni-ulm.de>
2001-05-13 15:09 ` Eric Olson
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=20010513135555.C9805@pua.nirvana \
--to=axel.thimm@physik.fu-berlin.de \
--cc=David.Hansen@physik.fu-berlin.de \
--cc=Jens.Dreger@physik.fu-berlin.de \
--cc=ejolson@unr.edu \
--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.