similar to: 2.6.30 and XEN_FBDEV_FRONTEND Broken ?

Does anybody please have any experience with the following CentOS 6 warnings in logwatch? WARNING: Kernel Errors Present ACPI Error (psargs-0359): [ ...: 1 Time(s) pci 0000:00:01.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.0: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.5: PCIe errors handled by OS. ...: 1 Time(s) pci 0000:00:1c.6: PCIe errors

Dear CentOS users, I run a small Facebook game at a CentOS 6.3 machine with PostgreSQL 8.4.3 + few PHP scripts + 1 Perl daemon and even though the server worked ok, I've suggested my users to double up the RAM to 32 GB and they have collected money for that. Now my problem is that I don't know, which knob to turn and how to really use the additional memory. Below is my top output at the

Dear all, I have running a DOM-0 on debian squeeze with the most recent kernel: Linux 2.6.32-5-xen-amd64 #1 SMP On 30% of all reboots the system hangs and only a reset helps. acpi=off as an additional kernel parameter solves this problem, but the usb keyboard of the installed ip-kvm is not found then. with acpi=off Ican find a lot stuff like: [ 7.098747] uhci_hcd 0000:00:1d.2: UHCI Host

I'm trying to figure out why 2 machines have a "hard I/O lock" on the HDD when running EL6. I have 4 identical machines, all were stable with EL5. 2 work great with EL6, 2 do not. I've checked momtherboard BIOS versions and settings, SAS controller BIOS versions and settings, they are the same between the working and non- working systems. When booting a non-working system,

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround

Problem still not solved, or any idea whats wrong. here are some msgs: device vif1.0 entered promiscuous mode alloc irq_desc for 1246 on node 0 alloc kstat_irqs on node 0 brI: port 2(vif1.0) entering learning state device vif1.1 entered promiscuous mode brE: port 2(vif1.1) entering learning state physdev match: using --physdev-out in the OUTPUT, FORWARD and POSTROUTING chains for

Trying to debug a database server getting cpu softlocks causing SSHD to hang and not let anybody log in. Figured that a good first step would be to get some kernel dumps when the problem occurs. According to what I read at the following web site, I can get dumps for softlock problems too. Here's the site: http://blog.kreyolys.com/2011/03/17/no-panic-its-just-a-kernel-panic/ Using a

Hello, I''m attempting to boot Xen 4.0.1 on a SuperMicro H8DGi-F motherboard and having not much luck. I can boot the 2.6.32.26 (or .27) kernels alone, but when I add Xen into the mix, I get consistent boot failure. I''ve tried Xen 4.0.1-release, 4.0.2-rc1-pre and 4.0.2-rc2-pre, all get the same failure. xen/next-2.6.37 works and boots great, but since netback isn''t

Ok im trying to play Counter Strike 1.6, but it crashes when i join a server. The Video is set to OpenGL and when i set it to "Software" it started working (but the quality was really shitty so i want OpenGL). I have this video card VGA compatible controller [0300]: ATI Technologies Inc RS480 [Radeon Xpress 200G Series] And when the game crashed i got this error: Code: Allocating

Hi list, I installed 2 HB8 cards each of them with a Quad Bri modules in a HP 360 G6 running Debian Squeeze. Here is an output of dmesg wafter server has booted: [ 9.784123] wctdm24xxp 0000:0b:08.0: PCI INT A -> GSI 31 (level, low) -> IRQ 31 [ 11.847073] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex [ 11.847600] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [

On Sat, Oct 15, 2022 at 12:21:41PM -0700, syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: a1b6b102df03 Merge branch 'phylink_set_mac_pm' > git tree: net > console output: https://syzkaller.appspot.com/x/log.txt?x=179af0c2880000 > kernel config: https://syzkaller.appspot.com/x/.config?x=85495c44a2c25446 > dashboard

I just kickstarted a new machine with the latest CentOS 6.2 files, including kernel 2.6.32-220.13.1.el6.x86_64. It came up without network interfaces. dmesg says: bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011) alloc irq_desc for 36 on node -1 alloc kstat_irqs on node -1 bnx2 0000:01:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 bnx2 0000:01:00.0:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Hello! I'm having problems getting PCI pass-through to work. This is on a AMD64 system, paravirtualized with xen-hypervisor-4.0-amd64 4.0.0-1~experimental.1, dom0: linux-image-2.6.32-5-xen-amd64 2.6.32-12. From IRC, earlier today: <tschwinge> waldi: Aren't the Debian xen domU-capable kernels supposed to contain the PCI frontend (needed for PCI pass-through)? I'm getting:

Got a bunch of servers from Penguin. Supermicro m/b's H8QG6. We put a 3tb drive in for additional workspace for the users, and some of them won't read, others will go for weeks, then spit out DRDY errors. lshw shows the controller as an ATI SB7x0/SB8x0/SB9x0 SATA. I did notice that it shows *-storage description: SATA controller product: SB7x0/SB8x0/SB9x0 SATA

With the .end() accessor having become optional and noting that several of the accessors'' behavior really depends on the result of msi_maskable_irq(), the splits the MSI IRQ chip type into two - one for the maskable ones, and the other for the (MSI only) non-maskable ones. At once the implementation of those methods gets moved from io_apic.c to msi.c. Signed-off-by: Jan Beulich

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/arch/x86/hpet.c +++ b/xen/arch/x86/hpet.c @@ -296,7 +296,7 @@ static void hpet_msi_ack(unsigned int ir { struct irq_desc *desc = irq_to_desc(irq); - irq_complete_move(&desc); + irq_complete_move(desc); move_native_irq(irq); ack_APIC_irq(); } --- a/xen/arch/x86/io_apic.c +++ b/xen/arch/x86/io_apic.c @@

Since IRQ probing may touch all currently unused interrupts, we must prevent probing for those where it doesn''t make sense (to avoid triggering BUG()s or de-referencing NULL function pointers): - dynamic IRQs must never be probed - physical IRQs should only be probed when registered or identity-mapped I haven''t got feedback from the reporting party, yet, but as the change seems

Andy, OSOL 2009.06 been installed in stub domain (hvm domain) at mentioned Dom0 with 2.6.30 xenified kernel via xen-patches-2.6.30-2.tar.bz2 refuse to activate PV drivers. When same Dom0 starts with 2.6.29.4 xenified kernel (xen-patches-2.6.29-6.tar.bz2) kernel OSOL 2009.06 in stub (hvm) domain does activate PV drivers for xdf, xnf . Boris

Afer an upgrade to xorg-server-1.7.0.902 and latest git for the kernel and xorg nouveau drivers I cannot start x with kms under wmaker. As root (just twm and an xterm) it's ok. Dmesg shows: [drm] DAC-6: set mode 1680x1050 1a [drm] nouveau 0000:01:00.0: nv04_dac_mode_set called for encoder 0 [drm] nouveau 0000:01:00.0: Setting dpms mode 0 on CRTC 0 [drm] nouveau 0000:01:00.0: Setting dpms