From: Stephan Brauss <sbrauss@bluewin.ch>
To: linux-kernel@vger.kernel.org
Subject: 2.4.4 kernel freeze
Date: Wed, 23 May 2001 16:34:57 +0200 [thread overview]
Message-ID: <3B0BCA91.32B334B8@bluewin.ch> (raw)
Hello,
I have an ASUS A7V133 (VIA VT8363A) with 5 PCI slots
and I installed kernel 2.4.4.
All runs fine when I only use PCI slots 1 to 3.
When I use slots 4 or 5, the system
freezes when data is passed to a device in one of
these slots. I tested with a Promise Ultra100, an Intel
Etherexpress Pro 100, and a DEC EtherWorks.
The problem does not turn up in 2.4.0 and 2.2.18 (standard
kernels from SuSE 7.1). I reproduced the error in a second
simillar system with the same motherboard.
Maybe this information is usefull...
If someone wants to know more details, please email me
directly as I'm currently not subscribed to this list.
Stephan
next reply other threads:[~2001-05-23 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 14:34 Stephan Brauss [this message]
[not found] <Pine.LNX.4.10.10105231215280.11617-100000@coffee.psychology.mcmaster.ca>
2001-05-23 18:12 ` 2.4.4 kernel freeze Stephan Brauss
2001-05-23 23:30 ` Jens Gecius
2001-05-24 23:21 ` Jens Gecius
-- strict thread matches above, loose matches on Subject: below --
2001-05-27 12:02 Stephan Brauss
2001-05-28 2:50 ` Jens Gecius
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=3B0BCA91.32B334B8@bluewin.ch \
--to=sbrauss@bluewin.ch \
--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