search for: x8sti

...edac_core dca parport raid10 raid456 async_raid6_recov async_pq usbhid hid raid6_pq async_xor xor async_memcpy async_tx raid1 raid0 multipath linear ahci btrfs zlib_deflate libahci e1000e libcrc32c Pid: 1119, comm: btrfs-delalloc- Tainted: G W 2.6.38-020638-generic #201103151303 Supermicro X8STi/X8STi RIP: 0010:[<ffffffffa00e23cb>] [<ffffffffa00e23cb>] write_extent_buffer+0xbb/0x1b0 [btrfs] RSP: 0018:ffff880303a0bbc0 EFLAGS: 00010a86 RAX: db74000000000000 RBX: 0000000000000d26 RCX: ffff880000000000 RDX: 0000000000000000 RSI: 000000000002fa19 RDI: ffff88023c8353f8 RBP: ffff880...

Hi, I just upgraded to the latest SID after reinstalling my test server. Then, after a while, during the boot process, Xen seems to hang, then my server reboots. It's difficult for me to see anything, since I'm using a KVM over IP, using a quite slow link (from China to UK, using a FreeNX box that connects through a Java KVM over IP to the server), and I don't think it'd be easy

...en replaced by a new one (same model). Still, the VM crash is reproducible. The hardware on the crashing system is: CPU: Intel Xeon E5-2609v2/4x2,5GHz Motherboard: Supermicro X9SRI-F For information, the hardware on non-crashing system is: CPU: Intel XEON L5639/6x2,13 GHz Motherboard: Supermicro X8STi > It seems like the crashes are related to a RT process, even though no > sched_fifo/rr processes are started on this system intentionally. Also, > the > CPU usage is low all the time, no peaks at all. But the kernel reports: > > kernel: [39101.461586] sched: RT throttling acti...

...; the > VM crash is reproducible. > > The hardware on the crashing system is: > CPU: Intel Xeon E5-2609v2/4x2,5GHz > Motherboard: Supermicro X9SRI-F > > For information, the hardware on non-crashing system is: > CPU: Intel XEON L5639/6x2,13 GHz > Motherboard: Supermicro X8STi > >> It seems like the crashes are related to a RT process, even though no >> sched_fifo/rr processes are started on this system intentionally. >> Also, the >> CPU usage is low all the time, no peaks at all. But the kernel >> reports: >> >> kernel: [...