similar to: Problem with ethernet card: r8169.

I have some new PC hardware I'm using with the Intel H67 chipset. I created a bzImage I use for a PXE environment for a recovery mode, installing OS images, etc. The new mobo doesn't have a VGA port but instead DVI. Everytime I unplug the DVI cable it seems to cause "Disabling IRQ #11". After that the PC is basically unusable. The /proc/interrupts shows that hdd, usb, nic,

Other than when they''re located in I/O port space, accessing them when in MMIO space (currently) implies usage of some sort of global lock: In -unstable this would be due to the use of vmap(), is older trees the necessary locking was introduced by 2ee9cbf9 ("ACPI: fix acpi_os_map_memory()"). This contention was observed to result in Dom0 kernel soft lockups during the loading of

Hi list, I've a problem with my system on CentOS 6.5 x86_64 on a workstation. During utilizzation, after several hours after boot (6/7 hours) I get an error: Disabling IRQ #16 and after this seems be that 3d acceleration is unloaded. This is a workstation with a dedicated vga (nvidia gt450) and 3 nics. This problem started when I've plugged the third nic. Without third nic all works

lspci gives 02:04.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Unknown device 8167 (rev 10) insmod r8169 loads the module but doesn;t pick the card up. Im connecting to internet using a live CD. how do i get centos 5(vanilla install) to recognise my lan card!? thanks R

Two problems I hope to solve: 1. The switch being used has autoneg off and has port set to 100 full duplex. 2. Many times NIC fails to come up properly during PXE boot: r8169: eth0: link down ADDRCONF(NETDEV_UP): eth0: link is not ready I can't use ethtool to disable autoneg because the nic driver is built into a bzImage. The root fs is currently being mounted via nfs during pxeboot at

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

I have no output in the logs, but /etc/init.d/network restart fixes the issue. I am rsync/scp (10GB) data from one 100MB Full duplex host to an ASUS M3A78-EM (RTL8111B/C). It locks up around the 1.5GB Tx mark. If I ethtool -s eth0 autoneg off speed 100 duplex full it does not happen again. Ideas? -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- -

Hi all, Another FYI-mail (and just to verify that I'm not going insane here); I recently purchased an ASUS M3A78-EMH HDMI -board with a tri-core Phenom. This is a small uATX-board with all the garnish integrated motherboards are supposed to come with, and fairly well supported in CentOS 5 and other modern distros. When I installed it (~2 months ago) the NIC was not supported; Ethernet

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

Hi, anybody know how to fix this. May 20 12:16:15 wolfpac kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out May 20 12:16:15 wolfpac kernel: Modules linked in: pf_ring(U) af_key iptable_nat ipt_LOG iptable_filter ip_tables nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6t_LOG xt_limit ip6table_filter ip6_tables bridge stp llc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4

Hi, some more info which I collected during physically accessing the machine while rebooting. I was suprised that while it was not able to do anything it was not a ''static'' kernel panic, but the following text was scrolling continously thru the screen: """ ata3: port reset, p_is 1 is e pis 1 cmd c017 tf 50 ss 113 se 0 ata3: status=0x50 { DriveReady SeekComplete }

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

Hi Lists, sorry for reposting this, but since no response has arrived so far and my time on this project is passing by I need to make a conclusion. Do I better use my DVR cards in dom0 or moving it to a separate physical machine rather than using them in a domU? Could someone shed light on why it is trickier to pass-thru one of these cards than any other pci devices? Do they try to read-write

Hi, I'm new to this list and joined since I am volunteering as a tech admin for a non profit organization called CouchSurfing (.com) where we tried to move the web servers to Xen zones and this has proven quite unstable since the our defined zones tends to crash on a daily basis with the latest CentOS 5 Xen updates. The physical boxes have 2 quad core 1.6GHz Xeon CPU's and 4 GB RAM, there

I have a box that ran perfectly under 4.4. gigabyte motherboard, AM2 4200+ systems. 1 GIG RAM. I installed Centos 5 on the same box. I now see the log entries below and my USB mouse stops working. What to do? Jerry Call Trace: <IRQ> [<ffffffff800b389d>] __report_bad_irq+0x30/0x7d [<ffffffff800b3ad0>] note_interrupt+0x1e6/0x227 [<ffffffff800b3005>]

Hi all, My USB mouse is dying on centos 5. Boots up fine, runs for a little while - 5 minutes perhaps then dies. All I see in the log is: <IRQ> [<ffffffff800b389d>] __report_bad_irq+0x30/0x7d [<ffffffff800b3ad0>] note_interrupt+0x1e6/0x227 [<ffffffff800b3005>] __do_IRQ+0xc7/0x105 [<ffffffff80011c19>] __do_softirq+0x5e/0xd5 [<ffffffff8006a195>]

Hi Centos-virt, I'm new to this list and joined since I am volunteering as a tech admin for a non profit organization called CouchSurfing (.com) where we tried to move the web servers to Xen zones and this has proven quite unstable since the our defined zones tends to crash on a daily basis with the latest CentOS 5 Xen updates. The physical boxes have 2 quad core 1.6GHz Xeon CPU's and 4

I built a new server about 10 days ago running CentOS 5.latest, and it's been presenting a message shortly after booting: irq 58: nobody cared (try booting with the "irqpoll" option) Call Trace: <IRQ> [<ffffffff800bb712>] __report_bad_irq+0x30/0x7d [<ffffffff800bb945>] note_interrupt+0x1e6/0x227 [<ffffffff800bae41>] __do_IRQ+0xbd/0x103

I get the following on an AM2 AMD5000+, nvidia gigabyte motherboard. Irq 169 is the USB. Anyone know why this is happening? If I install Centos 4.5 I do not get this. THanks, Jerry Oct 19 23:43:58 TESTING kernel: irq 169: nobody cared (try booting with the "irqpoll" option) Oct 19 23:43:58 TESTING kernel: Oct 19 23:43:58 TESTING kernel: Call Trace: Oct 19 23:43:58 TESTING kernel:

Hi all! After booting the server I have this message: irq 50: nobody cared (try booting with the "irqpoll" option) Call Trace: <IRQ> [<ffffffff800c17e6>] __report_bad_irq+0x30/0x7d [<ffffffff800c1a19>] note_interrupt+0x1e6/0x227 [<ffffffff800c0f15>] __do_IRQ+0xbd/0x103 [<ffffffff8006e249>] do_IRQ+0x13f/0x14d [<ffffffff8006ca05>]