From: Jose Angel Martinez Conde <joseangel@taller-id.com>
To: Hans-Peter Bock <Hans-Peter.Bock@isw.uni-stuttgart.de>
Cc: RT <linux-rt-users@vger.kernel.org>
Subject: Re: Problem with network on kernel 2.6.29.6-rt23 (Debian)
Date: Tue, 6 Oct 2009 11:18:51 +0200 (CEST) [thread overview]
Message-ID: <1949111338.301254820731590.JavaMail.root@groupware> (raw)
In-Reply-To: <1609492146.281254820627823.JavaMail.root@groupware>
Hi Hans-Peter,
No. My chipset is nForce 650i.
I will try with nForce 780i.
[1] > lspci
00:00.0 Host bridge: nVidia Corporation C55 Host Bridge (rev a2)
00:00.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a2)
00:00.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:00.7 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.3 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.4 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.5 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:01.6 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.0 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.1 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:02.2 RAM memory: nVidia Corporation C55 Memory Controller (rev a1)
00:03.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:05.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:07.0 PCI bridge: nVidia Corporation C55 PCI Express bridge (rev a1)
00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
01:00.0 VGA compatible controller: nVidia Corporation Device 05e1 (rev a1)
02:00.0 VGA compatible controller: nVidia Corporation Device 0614 (rev a2)
03:00.0 SATA controller: JMicron Technologies, Inc. JMicron 20360/20363 AHCI Controller (rev 02)
04:07.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet Controller (rev 05)
04:08.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6306 Fire II IEEE 1394 OHCI Link Layer Controller (rev c0)
--
jose angel
----- "Hans-Peter Bock" <Hans-Peter.Bock@isw.uni-stuttgart.de> wrote:
> Hello Jose,
>
> hmm, i have a similar issue with my network interfaces on one special
> computer. At first I thought it is a bug in some pci card driver. But
> since the same setup works on a mainboard with different chipset and
> CPU, I do not assume that any longer.
>
> My computer with the similar issue has an nVidia chipset, see lspci
> beneath. Does your computer have the same chipset?
>
> $ lspci
> 00:00.0 Host bridge: nVidia Corporation MCP73 Host Bridge (rev a2)
> 00:00.1 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a2)
> 00:01.0 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.1 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.2 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.3 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.4 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.5 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:01.6 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:02.0 RAM memory: nVidia Corporation nForce 630i memory controller
> (rev a1)
> 00:03.0 ISA bridge: nVidia Corporation MCP73 LPC Bridge (rev a2)
> 00:03.1 SMBus: nVidia Corporation MCP73 SMBus (rev a1)
> 00:03.2 RAM memory: nVidia Corporation MCP73 Memory Controller (rev
> a1)
> 00:03.4 RAM memory: nVidia Corporation MCP73 Memory Controller (rev
> a1)
> 00:04.0 USB Controller: nVidia Corporation GeForce 7100/nForce 630i
> (rev a1)
> 00:04.1 USB Controller: nVidia Corporation GeForce 7100/nForce 630i
> (rev a1)
> 00:08.0 IDE interface: nVidia Corporation MCP73 IDE (rev a1)
> 00:09.0 Audio device: nVidia Corporation MCP73 High Definition Audio
> (rev a1)
> 00:0a.0 PCI bridge: nVidia Corporation MCP73 PCI Express bridge (rev
> a1)
> 00:0b.0 PCI bridge: nVidia Corporation MCP73 PCI Express bridge (rev
> a1)
> 00:0c.0 PCI bridge: nVidia Corporation MCP73 PCI Express bridge (rev
> a1)
> 00:0d.0 PCI bridge: nVidia Corporation MCP73 PCI Express bridge (rev
> a1)
> 00:0e.0 IDE interface: nVidia Corporation Device 07f0 (rev a2)
> 00:0f.0 Ethernet controller: nVidia Corporation MCP73 Ethernet (rev
> a2)
> 00:10.0 VGA compatible controller: nVidia Corporation GeForce
> 7100/nForce 630i (rev a2)
> 01:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>
>
> Best regards, Hans-Peter Bock
> --
> (°< Hans-Peter Bock, Dipl.-Ing., http://www.isw.uni-stuttgart.de/ >°)
> (/) ISW - Universität Stuttgart, Seidenstraße 36, 70174 Stuttgart (\)
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2009-10-06 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1609492146.281254820627823.JavaMail.root@groupware>
2009-10-06 9:18 ` Jose Angel Martinez Conde [this message]
[not found] <658461008.621255079453937.JavaMail.root@groupware>
2009-10-09 9:11 ` Problem with network on kernel 2.6.29.6-rt23 (Debian) Jose Angel Martinez Conde
2009-10-09 15:43 ` Thomas Gleixner
[not found] <1804966706.191254768514851.JavaMail.root@groupware>
2009-10-05 18:52 ` Jose Angel Martinez Conde
2009-10-06 6:41 ` Uwe Kleine-König
2009-10-06 9:12 ` Jose Angel Martinez Conde
2009-10-06 6:47 ` Hans-Peter Bock
2009-10-06 9:15 ` Uwe Kleine-König
2009-10-06 9:22 ` Jose Angel Martinez Conde
2009-10-06 9:27 ` Hans-Peter Bock
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=1949111338.301254820731590.JavaMail.root@groupware \
--to=joseangel@taller-id.com \
--cc=Hans-Peter.Bock@isw.uni-stuttgart.de \
--cc=linux-rt-users@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.