similar to: NIC Throwing errors I dont understand

I am having an issue where eth1 is throwing some messages and stops responding. Restarting networking doesn't work and also just bringing down eth1 with 'ifdown' doesn't fix it. I have never seen anything like these messages: eth1: no IPv6 routers present r8169 0000:03:00.0: eth1: rtl_counters_cond == 1 (loop: 1000, delay: 10). r8169 0000:03:00.0: eth1: rtl_chipcmd_cond == 1

On 16/02/2019 02:43, Saurabh Nanda via samba wrote: >>> 2) Is this normal -- fs/cifs/smb2misc.c: Calculated size 157 length 156 >>> mismatch mid 11907 >> Could be a bug or miscalculated length + non critical warning, I also >> see this on master kernel. Either way I doubt it's slowing everything down. >> > Should I file a bug for this? > > >>

I am trying to transport a dd image between to hosts over a cross linked gigabit connection. Both hosts have an eth1 configured to a non routable ip addr on a shared network. No other devices exist on this link. When transferring via sftp I received a stall warning. Checking the logs I see this: dmesg | grep eth e1000e 0000:00:19.0: eth0: (PCI Express:2.5GT/s:Width x1) 00:1c:c0:f2:1f:bb

Hi all. I have two servers 2.6.18-308.4.1.el5PAE CentOS release 5.7 (Final) Both have two external gigabit network cards (installed Planet with Realtek r8169 chipset). lspci 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) 04:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8169 Gigabit Ethernet (rev 10) /var/log/messages May 3

Bill, your CentOS 5 RTL8110 page should probably be updated. I've confirmed that there's a newer r8169 driver in the kernel that works with the RTL8110. RealTek's web site now carries the new r8169 instead of the r1000. The newer driver fixed a problem I was having on one host so we should probably recommend it over the older r1000. I've updated my CentOS 4 page. Kirk Bocek

Hi all, I've recently upgraded a system from CentOS 4.4 to CentOS5, and now when the system boots, the r8169 ethernet card doesn't come up. After the boot sequence, if I type "ifup eth1 | ifup eth1.10 | ifup eth1.203" then the adapter starts up ok. It seems to be something with the boot sequence it loads the ethernet adapters a different way around (ie 4.4 eth0 is now

On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]

On 38+ Intel-based Asus products, the nvidia GPU becomes unusable after S3 suspend/resume. The affected products include multiple generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs many errors such as: fifo: fault 00 [READ] at 0000005555555000 engine 00 [GR] client 04 [HUB/FE] reason 4a [] on channel -1 [007fa91000 unknown] DRM: failed to idle channel 0 [DRM]

[+cc LKML] On Tue, Sep 18, 2018 at 04:32:44PM -0500, Bjorn Helgaas wrote: > On Thu, Sep 13, 2018 at 11:37:45AM +0800, Daniel Drake wrote: > > On 38+ Intel-based Asus products, the nvidia GPU becomes unusable > > after S3 suspend/resume. The affected products include multiple > > generations of nvidia GPUs and Intel SoCs. After resume, nouveau logs > > many errors such

hello Ned. On 07/26/2016 02:04 PM, Ned Slider wrote: > On 26/07/16 19:04, geo.inbox.ignored wrote: <<>> >> ]$ lspci|grep Realtek >> 0e:00.0 Network controller: Realtek Semiconductor Co., Ltd. \ >> RTL8187SE Wireless LAN Controller (rev 22) >> 14:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. \ >> RTL8101/2/6E PCI Express

Hello, I am having a weird networking issue. Now I know this is a centos mailinglist, and the system I am having issues with is proxmox ve 3.3 (debian based) but I am sure one of you guys faced this issue. So I am having an issue of no connectivity with my NICs. I have manually configured and I have tried dhcp. The OS sees the NICs loads the drivers, but I cannout ping anything on the lan. The

I''m needing to put a network card on a test server XCP 1.0. I''m seeing the citrix hcl (http://hcl.xensource.com) and I''m a doubt. I base that on which version to look for a compatible card? If the kernel is the same as in 5.6.0 FP1, but if the version of XCP uses the hypervisor 3.4.2 neither appears on the list. ps: I had a RTL-8169 but stopped working with update 0.5

Dear All, I have an onboard Realtek RTL8111/8168B NIC. from lspci -vv : 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) It is detected, but why the speed is always 100Mbps, already change cable but still no luck. I use ethtool and from the output it seems that system know that this NIC support gigabit speed : ???????

Howdy, It appears that CentOS 5.2's support for the RTL8111B/C chip is incomplete. The wiki has some blanket statements regarding this support: http://wiki.centos.org/AdditionalResources/HardwareList/CentOS5/RealTek/r1000 http://wiki.centos.org/AdditionalResources/HardwareList/RealTekRTL8111b I could dive in an make the changes *I* think need to happen but I'd like to talk to people

So I'm back to this problem. A quick run down of what the original problem was: I have a machine that I'm configuring to use kickstart to setup. It has two builtin ethernet ports (labeled ports 1 and 2) and I'm adding a third one on its PCIe bus. Originally I was using an r8169 clone a default kickstart always put it as eth0 with the builtin ones as eth1 and eth2 respectively. After

Greetings- I'm attempting to get CentOS 5.5 x86 (yes, very specific version required for specific software usage scenario... don't ask) running on an Intel D425KT mini-ITX motherboard. Everything works fine, with the exception of the onboard ethernet, which is a Realtek RTL8105E chip. The stock CentOS installation attempts to use the r8169 driver, which does not work. I've been around

I hope this is a good mailing list for this problem. I have a Jetson TK1 board and I am trying to get the nouveau drivers running on it without success. I am using the following: Nouveau linux kernel 4.8.0-rc4+ Nouveau DRM git master xf86-video-nouveau git master Gnurou xserver git branch GK20A My base system is Debian. When I try to start X I get: X: drmmode_display.c:783:

I''m trying to build out a test cloud using XCP 1.0.0 beta with 3 machines of 18 cores total (Phenom II 1090s). I''ve built three machines, installed XCP 1.0.0 beta on them and they all three have the same problem - the Realtek network cards don''t work. The following is the output from lspci 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI

While untar''ing an image to an sd card via a reader, I got the following bug. The system also has a btrfs root, and a whole swath of processes went into uninterruptable sleep. I was able to poke around via ssh and sysrq, and already had netconsole set up to capture the bug. Root fs is on /dev/sdi1, and /dev/sdj2 is the card reader which was the target of the untar. [29571.448889] sd

I''ve upgraded to linux 3.10 and enabled extended inode refs and skinny metadata extent refs with these commands: btrfstune -r /dev/sdc1 btrfstune -x /dev/sdc1 Since then, I have "WARNING: at fs/btrfs/backref.c:903 find_parent_nodes+0x616/0x815 [btrfs]()" showing up like crazy: # grep -c "WARNING: at fs/btrfs/backref.c:903" syslog 181819 That''s after just