From: Orion Poplawski <orion@cora.nwra.com>
To: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
"''Linux Kernel Mailing List ' '" <linux-kernel@vger.kernel.org>
Subject: Re: Problems (lockup/hang) with PCI-X slot on X5DPL motherboard
Date: Mon, 17 Apr 2006 10:48:58 -0600 [thread overview]
Message-ID: <4443C6FA.8020105@cora.nwra.com> (raw)
In-Reply-To: <4807377b0604161104p5d6e32d9wbbb0184fc7a1b1a1@mail.gmail.com>
Jesse Brandeburg wrote:
>
> On these supermicro systems often they have jumpers to control the slots,
> are they set correctly? Make sure that if your e1000 and slot six are
> sharing a bus, that neither of them is running at faster than PCI-X 100 MHz
> (check in ethtool -d ethX for e1000)
>
Is there a way to find out bus speed for other slots/cards?
> so do the other slots work okay with your MV card? The supermicro systems
> had tons and tons of ACPI table problems, so you may want to look closely at
> your dmesg and / or try acpi=off kernel boot line.
>
In general, yes, though I just had a lockup with this new MV card in my
test system. Otherwise, my X5DPL-TGM with on MV card in slot 4 and one
Intel GigE in slot 5 has been quite stable.
> If you think you're having a network problem posting to
> netdev@vger.kernel.org would be good.
I think it's only related to device/bus issues, not in general.
Thanks a lot for the reply. I'll be trying to turn down the bus speed
in the BIOS to see if that help.
--
Orion Poplawski
System Administrator 303-415-9701 x222
Colorado Research Associates/NWRA FAX: 303-415-9702
3380 Mitchell Lane, Boulder CO 80301 http://www.co-ra.com
prev parent reply other threads:[~2006-04-17 16:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-14 23:13 Problems (lockup/hang) with PCI-X slot on X5DPL motherboard Orion Poplawski
[not found] ` <4807377b0604161104p5d6e32d9wbbb0184fc7a1b1a1@mail.gmail.com>
2006-04-17 16:48 ` Orion Poplawski [this message]
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=4443C6FA.8020105@cora.nwra.com \
--to=orion@cora.nwra.com \
--cc=jesse.brandeburg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox