similar to: conntrack_ftp problem domU not responding

After installing a Phenom II X4 processor (replacing a single core Semperon) I am getting these messages on the console and in dmesg: Warning Timer ISR/2: Time went backwards: delta=-250135996 delta_cpu=13864004 shadow=1355887856733 off=870052783 processed=1357008044419 cpu_processed=1356744044419 0: 1357004044419 1: 1356696044419 2: 1356744044419 3: 1356696044419 printk: 41 messages

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

Hi Gang. I installed CentOS last night and the sound card detection failled to detect the sound card. I have a Asrock K8NF6G-VSTA mother board, with a nVidia NF6100-405 chip set. I have tried various live distro's and I ran Fedora 7 on it for just over 2 weeks and none of them detected the sound card. I'm a newbie to Red Hat based distributions but have been using Mandriva for

I''m having a strange issue with Xen 4.0.1 AMD64 (debian squeeze). I am importing a iSCSI lun into dom0 from a storage array (using open-iscsi), this is used as the disk [phy:] for my domU. If I use HVM, the install works correctly. As soon as I switch to pv for the disk drivers (after installing a xen kernel in the domU) I get a slew of messages in xm dmesg: (XEN) grant_table.c:1956:d0

This was due to a ProxyRequests On Let this be a lesson to all. [root at localhost log]# cat /proc/net/ip_conntrack | wc -l 11042 [root at localhost log]# cat /proc/sys/net/ipv4/ip_conntrack_max 28632 [root at localhost log]# cat /var/log/messages ... Sep 2 04:04:30 localhost kernel: printk: 213 messages suppressed. Sep 2 04:04:30 localhost kernel: ip_conntrack: table full, dropping

Hi, I have a customer who uses XEN on FC6. This particular virtual triggers a bug in the networking code after several hours of heavy network use. The network stops operating, and the console shows messages like this: printk: 2 messages suppressed. netfront: rx->offset: 10, size: 4294967295 printk: 1 messages suppressed. netfront: rx->offset: 10, size: 4294967295 printk: 4

hello: thanks for Tzafrir Cohen for dahdi testing. I installed dahdi-2.1-r3c svn code and asterisk1-6 for testing OpenVox B400P and junghans card. i fund that there is bug (i think) to dectect NT or TE mode. actually on the board, i set it as TE mode, but after start wcb4xxp, but it show the port is NT mode. to detect the TE mode, I modefy the code in base.c

Hi, Sorry for the need of the long winded email. Looking for some answers to the following. I am setting up a xen PV domU on top of a LVM partitioned DRBD device. Everything was going just fine until I tried to test the filesystems in the domU. Here is my setup; Dom0 OS: CentOS release 5 (Final) Kernel: 2.6.18-8.1.4.el5.centos.plusxen Xen: xen-3.0.3-25.0.3.el5 DRBD:

Hi Johanners Berg, I put the antispam plugin to work (some days ago) and now my imap daemon dies with segfault. I don't have nothing (wrong) in logs, just a lot of segfaults... Dec 10 15:37:21 curie kernel: printk: 22 messages suppressed. Dec 10 15:37:21 curie kernel: imap[4774]: segfault at 8 rip 2afe7fe7d7ff rsp 7fff2b9bdab0 error 6 Dec 10 15:37:21 curie kernel: imap[4779]: segfault at 8

Hello, I have finally managed to understand HFSC up to a level which allowed me to create a QoS script which maintains low VoIP latency while running stuff like eMule. Unfortunately, HFSC seems to have a severe bug. Why do I consider this as a bug defenitely? Well, my script runs without any errors, then QoS works perfectly for some hours, no error messages in kernel log. Then randomly the

Hi, One of my servers has had its dom0 "oops" over and over twice in the last week. Unfortunately this is newly deployed so I have no idea if it is down to Xen or not. xen_changeset : Mon Dec 12 18:47:47 2005 +0100 8270:4ad23e798798 dom0 kernel is a vanilla 2.6.12 with Ralph''s .6+xen kernel patch applied. x86_32 sarge packages were used. The .config is

Package: xen-hypervisor-4.1-amd64 Version: 4.1.3-7 Severity: important Tags: patch Dear Maintainer, The PMU may be enabled on the Dom0 although the needed MSRs are not accessible, causing at least major noise on the xen messages ring buffer. I suspect there might also be a performance decrease, because the MSR write is trapped by Xen. Once the PC is in that state, a reboot won't help. This

Hi all, my name is Hirofumi Tsujimura. We are porting and testing a PV-on-HVM in the IPF. This is a first time to send mail. I probably found the problem when I tested the VNIF. My operation for the test is following. 1. create a domain VTx and attach the VNIF in it. 2. create a domain U. 3. send a packet to the domain VTx from the domain U with ping command. Then, the domain VTx

Hi, all -- I''m in the process of configuring a new machine for use as a Xen server, and am having some rather significant stability issues. The hardware/distro/kernel info is: opensuse 10.3 Linux offxen2 2.6.22.5-31-xen #1 SMP 2007/09/21 22:29:00 UTC x86_64 x86_64 x86_64 GNU/Linux 2 x Dual-Core AMD Opteron(tm) Processor 2212 HE 8 x 2GB PC2-5300 RAM Xen 3.1.0_15042-51 I currently have

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a machine running 2.6.18-rc3 with a bridge config that looks like this: cr1:~# brctl show bridge name bridge id STP enabled interfaces vlan100 36b0.0007e90f40c1 yes eth0.100 eth2.100 vlan101 5dc0.0007e90f40c1 yes

Hi folks, I have lots of messages like these appearing on my local CentOS 5.2 consoles: > Oct 17 12:03:29 machine kernel: printk: 1 messages suppressed. > Oct 17 12:03:29 machine kernel: pbond0: received packet with own address as source address I have disabled console logging in syslog.conf, and even if I shut down syslog and kernel logger, the messages keep coming on the local

Hi, I just noticed one of my XEN domU''s rebooting by itself. No one was logged in and it wasn''t under load, but just rebooted. It rebooted again about an hour or 2 later Is there any way to see why to see what caused this, either from domU, or dom0 ? /var/log/messages has no indicative reason, but here it is: Aug 1 18:47:06 venus shutdown[13758]: shutting down for system

On Thu, Mar 29, 2018 at 7:21 AM, Steven Tardy <sjt5atra at gmail.com> wrote: > A STATEFUL firewall with ?ip any any? can and will still block asymmetric > communications due to the firewall keeping track of state (hence tha name > stateful firewall). > > Tcpdump on your servers /other/ NICs and you?ll see the tftp traffic > leaving your server on some other NIC (probably

On Thu, Mar 29, 2018 at 12:48:15PM -0400, Asif Iqbal wrote: > I do not see tftp traffic is leaving from S > > A:~$ tftp > (to) 192.168.1.20 > tftp> get file > Transfer timed out. > > As you can see no pkt is leaving. If it were leaving S, but A were not > receiving then I would think firewall > is dropping it. > > [ S ~]$ sudo tcpdump -A -nniany host

have you checked that tftp is added to hosts.allow. syslog may be reporting libwrap errors, libwrap is trcpwrappers regards peter On 11 April 2018 16:57:04 "Asif Iqbal" <vadud3 at gmail.com> wrote: > On Thu, Mar 29, 2018 at 12:48 PM, Asif Iqbal <vadud3 at gmail.com> wrote: > > > > > > > On Thu, Mar 29, 2018 at 7:21 AM, Steven Tardy <sjt5atra at