similar to: CentOS 5 ssloooowww when network unavailable

Hello, While I was doing some tests in Arndale board, the network (iperf) throughput suddenly decreases to 5Mbps (from 100Mbps) out of nowhere. This typically happens when I generate traffic using iperf (100Mbps) while installing some packages using apt-get in dom0. Whenever this behavior happens, I can not see any distinguishable logs from any places. After some debugging, I found that

Hello, We have built a couple of CentOS 5.5 systems on the Intel DH67BL (Sandy Bridge) motherboard and overall they work pretty well. I'm having one problem which keeps cropping up and that is an error message that says: IRQ 177 nobody cared (try booting with the irqpoll option) report bad irq, references CPU idle then it references usb_hcd_irq and e1000_intr then it disables the add-on

Hello, I've been consistently attempting to make the setup mentioned in the subject work on the following hardware: Xeon E3 1275 (v1, Sandy Bridge) Asus P8B WS (Firmware: 0904 and 2009) 16 GB RAM Sapphire Radeon HD 7950 OC (Firmware: 015.013.000.010.000705) Linux 3.4.1 dom0, x86-64, pvops. Xen 4.1.2 (+ security patch) and 4.1.3-rc1. Old qemu-dm setup. (not new mainline qemu) Windows 7 64-bit

Below is a kernel dump that I just got. This is a fresh new install of centos 5.1 on NVIDIA gigabyte MB-GA-M61P-S3. nothing extra has been added. I have not tried the irqpoll but I am surprised to get this. Also the machine keeps running just hod this show on the console... Any ideas??? Jerry Jan 8 05:20:00 localhost kernel: irq 169: nobody cared (try booting with the "irqpoll"

Previous 2.6.31-rc8 kernel was built on F11 and installed with modules on F12. Current kernel has been built on F12 (2.6.31-0.204.rc9.fc12.x86_64) and installed on F12 before loading under Xen 3.4.1. Dmesg log looks similar to Michael Yuong''s ''rc7.git4''  kernel for F12. Boris. --- On Tue, 9/8/09, Boris Derzhavets <bderzhavets@yahoo.com> wrote: From: Boris

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,

Everyone, I have a new installation of Centos 5.1 that I am using on a gateway server that also has dhcp, named servers. I also have cups set up to function as a print server, and sendmail is being used as a relay to our mail server. yum-cron appears to be updating everything daily as desired. This Centos 5.1 gateway was created to replace a Fedora Core 5 system with the same functions. When

Hi all, has anyone seen such a behaviour?: I delegated successfully my NIC to a domU, but access to it from domU is not possible. Device appears, but access to it via ''ifconfig ethX up'' doesn''t work. Ends up in dmesg output like: tg3: tg3_reset_hw timed out for eth1, firmware will not restart magic=00000000 Delegating my USB controllers e.g. works flawlessly. Full

Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as modprobe xen-pciback passthrough=1 I now have the PCI device on the DomU matching the Dom0 Device usb usb1: SerialNumber: 0000:00:1a.0 instead of 0000:00:00.0 However I now have this error ehci_hcd 0000:00:1a.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. does

Hi list, I had a problem with the dahdi XPP driver. After this error in syslog, the Xorcom disconnect from the server: Jun 3 15:03:29 kernel: [361010.637858] *NOTICE-xpp_usb: xusb-0 (usb-0000:00:1d.7-3) [X1047686]: Sluggish USB. Dropping next PCM frame (p** **ending_writes=5)* Jun 3 15:03:52 kernel: [361033.890575]* ERR-xpp: XBUS-00: Failed to send from command_queue (ret=-19)* Jun 3

CentOS Community, Would someone who is familiar with reading boot messages and kernel errors be able to assist with advising me on what the following errors might mean in dmesg. It seems to come up randomly towards the end of the logfile. ------------[ cut here ]------------ WARNING: at arch/x86/kernel/cpu/mtrr/generic.c:467 generic_get_mtrr+0x11e/0x140() (Not tainted) Hardware name: empty

Dear R Help, I work with the Sage project, and we are trying to improve the ability to use R through Sage. Most things work, but make check seems to cause problems on certain platforms, and now that we want to upgrade to 2.10.1 I thought we should ask for help! R builds just fine on both Mac and Linux, but some things in make check seem to break on certain Linux boxes that don't on Mac or

CentOS Experts, I am receiving the following in /var/spool/mail/root. I cleaned out the file and then rebooted and the same errors came back. Is it possible to analyze the data and advise if there is an issue with my system? This is a completely fresh install. From user at localhost.srv.net Tue Jan 17 08:11:56 2012 Return-Path: <user at localhost.srv.net> X-Original-To: root at

Hi Lucas, On Mon, Mar 24, 2014 at 10:19 PM, Lucas Stach <l.stach at pengutronix.de> wrote: > Hi Alexandre, > > Am Montag, den 24.03.2014, 17:42 +0900 schrieb Alexandre Courbot: >> Hi everyone, > [...] >> >> A few lines of hacks (not included here) are still needed to deal with cached >> mappings triggering external aborts and CPU/GPU memory coherency

On 11/20/2017 09:52 PM, Jens Axboe wrote: > On 11/20/2017 01:49 PM, Christian Borntraeger wrote: >> >> >> On 11/20/2017 08:42 PM, Jens Axboe wrote: >>> On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/20/2017 08:20 PM, Bart Van Assche wrote: >>>>> On Fri, 2017-11-17 at 15:42 +0100, Christian

On 11/20/2017 09:52 PM, Jens Axboe wrote: > On 11/20/2017 01:49 PM, Christian Borntraeger wrote: >> >> >> On 11/20/2017 08:42 PM, Jens Axboe wrote: >>> On 11/20/2017 12:29 PM, Christian Borntraeger wrote: >>>> >>>> >>>> On 11/20/2017 08:20 PM, Bart Van Assche wrote: >>>>> On Fri, 2017-11-17 at 15:42 +0100, Christian

https://bugs.freedesktop.org/show_bug.cgi?id=89558 Bug ID: 89558 Summary: Unknown chipset error for GeForce 840M Product: xorg Version: unspecified Hardware: Other OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee: nouveau at

Next version of https://patchwork.freedesktop.org/series/48596/ . Made some important changes to the refactoring patch, but everything else is the same. Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into nouveau_connector drm/nouveau: s/nouveau_backlight_exit/nouveau_backlight_fini/ drm/nouveau: Cleanup indenting in

This series fixes some issues with nouveau's backlight support that were causing kernel panics on module reloads, specifically on systems with nouveau handling the backlight of one of the displays. While we're at it, let's cleanup nouveau_backlight.c as well Lyude Paul (5): drm/nouveau: Check backlight IDs are >= 0, not > 0 drm/nouveau: Move backlight device into

Next version of https://patchwork.freedesktop.org/series/48596/ . Added NV_INFO_ONCE and made "Move backlight device into nouveau_connector" use that instead so we don't print the GMUX warning more then once. Lyude Paul (5): drm/nouveau: Add NV_PRINTK_ONCE and variants drm/nouveau: Move backlight device into nouveau_connector drm/nouveau: