From: Moshe <moshe.gurvich@kabbalah.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: getting up Intel gigE 82547GI (8086:1075) crashes kernel
Date: Tue, 15 Jun 2004 19:36:39 -0700 [thread overview]
Message-ID: <1087353399.3534.20.camel@moshe.kci.kabbalah.com> (raw)
Hi,
I've got few Dell PE750 boxes with P4HT.
Installed Mandrake 10.0 with 2.6.3-smp.
This box have 2 onboard nics:
eth0: 82547GI (8086:1075)
eth1: 82541GI (8086:1076)
When I try to ifup eth0 it crashes kernel, i can't even toggle NumLock,
when i boot with noapic, i can at least toggle NumLock, but nothing
else.
eth1 gets up fine and works perfectly.
I've got suggestions to rebuild kernel without acpi, apm, apic.. will it
help?
Any others ideas?
Thanks..
# lspci -v:
01:01.0 Ethernet controller: Intel Corp.: Unknown device 1075
Subsystem: Dell Computer Corporation: Unknown device 0165
Flags: bus master, 66Mhz, medium devsel, latency 0, IRQ 18
Memory at fe1e0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at ece0 [size=32]
Capabilities: [dc] Power Management version 2
03:02.0 Ethernet controller: Intel Corp.: Unknown device 1076
Subsystem: Dell Computer Corporation: Unknown device 0165
Flags: bus master, 66Mhz, medium devsel, latency 32, IRQ 21
Memory at fdee0000 (32-bit, non-prefetchable) [size=128K]
I/O ports at dcc0 [size=64]
Capabilities: [dc] Power Management version 2
Capabilities: [e4] PCI-X non-bridge device.
# dmesg:
Intel(R) PRO/1000 Network Driver - version 5.2.30.1-k1
Copyright (c) 1999-2004 Intel Corporation.
PCI: Setting latency timer of device 0000:01:01.0 to 64
eth0: Intel(R) PRO/1000 Network Connection
eth1: Intel(R) PRO/1000 Network Connection
next reply other threads:[~2004-06-16 2:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 2:36 Moshe [this message]
2004-06-16 5:03 ` Randy.Dunlap
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=1087353399.3534.20.camel@moshe.kci.kabbalah.com \
--to=moshe.gurvich@kabbalah.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
all inboxes | Powered by JetHome®