Displaying 20 results from an estimated 100 matches similar to: "Crash in network stack under Xen"
2016 Mar 10
2
Soft lockups with Xen4CentOS 3.18.25-18.el6.x86_64
I've been running 3.18.25-18.el6.x86_64 + our build of xen 4.4.3-9 on one host for the last couple of weeks and have gotten several soft lockups
within the last 24 hours. I am posting here first in case anyone else has experienced the same issue.
Here is the first instance:
sched: RT throttling activated
NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [swapper/0:0]
Modules linked in:
2016 Jul 03
0
PCI Passthrough not working
From: "Francis Greaves" <francis at choughs.net>
To: "Francis Greaves" <francis at choughs.net>, "centos-virt" <centos-virt at centos.org>
Sent: Sunday, 3 July, 2016 11:19:49
Subject: Re: [CentOS-virt] PCI Passthrough not working
Further to my last post, I have removed the xen-pciback module from the Dom0 kernel, and reloaded it as
modprobe
2016 Jul 04
0
PCI Passthrough not working
I am having trouble getting PCI Passthrough to work from Dom0 running CentOS 7 to DomU runnning Debian 8
I am using Xen 4.6 with CentOS kernel 3.18.34-20.el7.x86_64 on a Dell Poweredge T430.
I think I have set it all up correctly, but I see no message when putting a USB device into any of the USB slots on the DomU
There are three other DomUs running, but I have no need of PCI Passthrough set up
2015 Jan 25
2
Bug#776237: xen-hypervisor-4.4-amd64: kernel panic on dom0 boot
Package: xen-hypervisor-4.4-amd64
Version: 4.4.1-6
Severity: normal
Dear Maintainer,
I'm trying to boot into xen/dom0 but so far all attempts have resulted
in a crash followed by an automatic reboot.
My hardware is
Motherboard: Asus Sabertooth 990FX R2.0
CPU: AMD FX-8350
GPU: Sapphire Radeon R9 285
A trace of the kernel panic follows (full log captured over serial should
2013 Jun 28
0
Re: kernel panic in skb_copy_bits
On Fri, 2013-06-28 at 12:17 +0800, Joe Jin wrote:
> Find a similar issue http://www.gossamer-threads.com/lists/xen/devel/265611
> So copied to Xen developer as well.
>
> On 06/27/13 13:31, Eric Dumazet wrote:
> > On Thu, 2013-06-27 at 10:58 +0800, Joe Jin wrote:
> >> Hi,
> >>
> >> When we do fail over test with iscsi + multipath by reset the switches
2017 Apr 02
2
[Bug 1141] New: trace aborts using pkttype on ingress
https://bugzilla.netfilter.org/show_bug.cgi?id=1141
Bug ID: 1141
Summary: trace aborts using pkttype on ingress
Product: nftables
Version: unspecified
Hardware: x86_64
OS: other
Status: NEW
Severity: major
Priority: P5
Component: kernel
Assignee: pablo at netfilter.org
2016 Jul 03
2
PCI Passthrough not working
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
2002 Apr 04
1
Ext3 related oops and a crash
We have here an knfs fileserver running ext3 on 2.4.18 kernel with three
filesystems:
<CLIP>
Filesystem 1k-blocks Used Available Use% Mounted on
/dev/hda3 10080520 3609632 6368476 37% /
/dev/hda4 16437332 12295408 3974932 76% /home
/dev/md1 1024872060 409906136 614441636 41% /fs
</CLIP>
The /fs filesystem lives on a
2012 Jul 03
13
[PATCH] various Xen fixes for v3.6 (v1).
I am working on some other bugs and perf issues - and while working I noticed
that both sparse and Coverity have reported some issues with Xen drivers.
Please see attached various bug-fixes that I am proposing for 3.6.
2005 Aug 27
1
[LLVMdev] llc problem
I got the following error in 1.5 release. As far as installation is concerned,
everything went fine.
llc hello.bc -o hello.bs
llc((anonymous namespace)::PrintStackTrace()+0x17)[0xd435f1]
llc((anonymous namespace)::SignalHandler(int)+0xbd)[0xd437ff]
/lib64/tls/libc.so.6[0x3ff522e410]
llc(llvm::Type::isFirstClassType() const+0x13)[0x8fc38d]
llc(llvm::FunctionType::FunctionType(llvm::Type const*,
2016 Nov 08
3
Indexing failed: 500 Internal Server Error
Hi,
While running doveadm index on a mailbox this gets printed:
doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server Error
doveadm(neil): Panic: file http-client-request.c: line 792
(http_client_request_send_payload): assertion failed: (ret == 0)
doveadm(neil): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x88662) [0x7f0a52750662] ->
2010 Sep 13
1
irq 58 nobody cared.
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
2015 Jul 24
0
internal server error
I've got a bit more details
Jul 24 10:21:50 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com):
*Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset):
assertion failed: (offset < 0x40000000)*
Jul 24 10:21:50 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7c96f)
[0x7fe4a719d96f] ->
2016 Nov 08
0
Indexing failed: 500 Internal Server Error
Yes, this happens because your SOLR server is reporting 500 Internal
Server Error.
Aki
On 08.11.2016 10:47, W. de Hoog wrote:
> Hi,
>
> While running doveadm index on a mailbox this gets printed:
>
> doveadm(neil): Error: fts_solr: Indexing failed: 500 Internal Server
> Error
> doveadm(neil): Panic: file http-client-request.c: line 792
>
2018 Apr 29
0
Panic when using doveadm fts lookup
Hello,
I am actually testing dovecot fts search, using doveadm fts lookup.
I run this command:
doveadm fts lookup -u andre subject "Test"
And this generate this error:
doveadm(andre): Panic: file mail-storage.c: line 1694
(mailbox_get_open_status): assertion failed: (box->opened)
doveadm(andre): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x95e92) [0x7fa7ac9e8e92]
2003 May 20
2
mdct_backward with fused muladd?
Can anybody point me at any resources that would explain how to optimize
mdct_backward for a cpu with a fused multiply-accumute unit?
>From what I understand from responses to my older postings, Tremor's
mdct_backward could be rewritten to take advantage of a muladd.
My target machine can do either two-wide 32x32 + Accum(64) -> Accum(64)
integer muladd or eight-wide 16x16 + Accum(32)
2009 Mar 04
1
pv_ops kernel 2.6.29-rc6 boot failure
Hi,
I did a git pull on pv_ops tree this morning and now get a crash when
eth0 is started, here is the full boot log:
Booting ''Xen 3.4 / Linux 2.6.29-rc6-tip''
root (hd0,0)
Filesystem type is ext2fs, partition type 0x83
kernel /xen.gz com1=115200,8n1 console=com1,vga iommu=1
[Multiboot-elf, <0x100000:0x131748:0x8e8b8>, shtab=0x2c0078, entry=0x100000]
module
2013 Sep 12
15
large packet support in netfront driver and guest network throughput
Hi All,
I am sure this has been answered somewhere in the list in the past, but I can''t find it. I was wondering if the linux guest netfront driver has GRO support in it. tcpdump shows packets coming in with 1500 bytes, although the eth0 in dom0 and the vif corresponding to the linux guest in dom0 is showing that they receive large packet:
In dom0:
eth0 Link encap:Ethernet HWaddr
2015 Jul 22
3
internal server error
Hi!
Today I've got a client unable to open a mailbox with Thunderbird -
constantly drops connection.
On the server side I can see an error message in the log
Jul 22 11:07:29 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x7c96f)
[0x7fd52575b96f] -> /usr/lib/dovecot/libdovecot.so.0(+0x7c9ce)
[0x7fd52575b9ce] ->
2018 Jul 13
0
[PATCH 2/2] drm/nouveau: Avoid looping through fake MST connectors
When MST and atomic were introduced to nouveau, another structure that
could contain a drm_connector embedded within it was introduced; struct
nv50_mstc. This meant that we no longer would be able to simply loop
through our connector list and assume that nouveau_connector() would
return a proper pointer for each connector, since the assertion that
all connectors coming from nouveau have a full