similar to: RE: "netdev watchdog" error and non-working sis900 networkcard - solution

> Like I just mentioned in a different thread, I need to use > the ''noapic'' > options on both the PowerEdge models I''ve tried.. I''ll try to > build up a Xen vs. non-Xen kernel tomorrow or Tuesday and > grab a diff for you. Which PE models are they? We have quite a few different Dell PowerEdge models running 24x7 in the test lab, and

Yes, acpi=off seems to have decided my problem of instability. Soon, then I will be returning the HD in the machine in production and I dispatched by post the result. -- Leonardo Pinto listas#openlogic dot com br > The troubles went away when adding kernel options "noapic > acpi=off" to > the modules grub line. > > Both noapic and acpi=off make big difference to the

Hi , all : Sometimes my server network connection on Linux goes down with short message in syslog saying: "[localhost kernel] NETDEV WATCHDOG: eth0: transmit timed out" (or similar). By the way , I installed the CentOS 5.4 x86_64 bit and the kernel version was 2.6.18-164. Has anyone experienced this problem or is it the bug of the kernel ? I restart the network and that problem

Apologies if this is posted on the wrong list, but when I try to get pci passthrough to work on a Wheezy Xen box I get NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out and then not much else works at all. The same hardware works just fine with Xen and Squeeze. It seemed to me that the problem I am seeing is very similar to

Hi, anybody know how to fix this. May 20 12:16:15 wolfpac kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out May 20 12:16:15 wolfpac kernel: Modules linked in: pf_ring(U) af_key iptable_nat ipt_LOG iptable_filter ip_tables nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6t_LOG xt_limit ip6table_filter ip6_tables bridge stp llc nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_defrag_ipv4

All, I seem to be experiencing the same problem that Michal Urbanski talked about in an email dated March 24th with a subject of "hanging dell hardware". Looking through the archives I can not find any resolution to the problem. The specs on my machine are Dell Poweredge 1850 Dual Xeon 2.8s 1gig ram PERC 4e/SI raid controller in mirror configuration with 2 73 gb drives (uses the

Hello there ! I was writing to freebsd lists some time ago, again asking for some help about SIS900 NIC. Then some other people also complained that the sis900 driver that comes with FreeBSD 4.x and FreeBSD-CURRENT (later 5.0) doesn't actually work at all. So some patches were released and also the drivers in -STABLE and -CURRENT were also updated. And guess what, it is still not working on

Hello everybody: Since sis900 chip has the problem with pxelinux simple menu (menu.c32, for version 3.0.7 to 3.10) as we posted in http://syslinux.zytor.com/archives/2005-August/005636.html We'd like to buy sis900 network card and send it to HPA so that he might give it a try if he has time to do that. We live in Taiwan, so the best way is that we can buy it online in USA and put HPA as the

Hi, HPA: Thanks for the nice new features, appreciate that. Syslinux is always a nice program. For the new version, 3.10-pre20, I encountered a problem now, my client machine uses sis900 chip, and it still can not run simple menu with pxelinux in this version (3.10-pre20). It's same situation as I encountered when I used syslinux 3.07, 3.08 and 3.09. For 3.10-pre20, I compiled in Fedora

Okay guys, This is separate from my last few messages. Along with those attempts, I decided to migrate from pxelinux.0 to gpxelinux.0 in my existing setup. Admittedly I haven't tried previous gpxelinux.0's but I am willing to if someone thinks it would be useful. Everything works as expected with pxelinux.0 of the same version. With gpxelinux.0: TFTP Prefix: Trying to load:

Hi, I am currently testing Xen on my laptop and was wondering if there was any way to enable ACPI sleep so that I can resume sessions when I''m on the go. Is this possible? If so, could you please highlight how to achieve this? Thank you. -- Mathew Brown mathewbrown@fastmail.fm -- http://www.fastmail.fm - Access all of your messages and folders

Greetings. I''ve been asked to work on a PXE solution for booting Xen domU''s from a network, and would like some feedback and any help anyone is willing to provide. I''ve been limiting my work to HVM domU''s at the moment, because I don''t think the NBI''s (as far as I know, these are bootloaders) that I have available work in paravirtualized

Hi, Updated to current bk today, and my machine stopped booting ... I''ve tracked it down to the apic changes from end of last week. cset 1.1307 boots fine, 1.1308 doesn''t. Diff of the boot messages is below. Full logs are also attached. Gerd --- log-1.1307 2005-04-21 14:40:57.372885027 +0200 +++ log-1.1308 2005-04-21 14:38:52.236553392 +0200 @@ -7,7 +7,7 @@

Hi, I'm having lots of difficulties with BCM5719, which is the default network card of HP Proliant DL 360 G8 servers. I can get a few ping replies before I get a couple of these: bge0: watchdog timeout -- resetting bge0: watchdog timeout -- resetting Then everything hangs. Can not log in using ssh.

> When running on 4GB of total memory instead of 12GB, > everything is just fine. (the three virtual machines, Dom0 + > 2 x DomU are assigned 1GB of memory each, in both test runs). > Does that help? Is this with the kernel and xen from -unstabele/3.0.3 ? Have you changed the config? What storage device do you have? What NIC? Are you setting mem=4096M on the Xen command line? If

It seems that VCPU system time isn''t monotonic (using 3.0.4). It seems it might be correlated to when a VCPU is switched across real CPUs but I haven''t conclusively proved that. But e.g.: { old = { time = { version = 0x4ec pad0 = 0xe8e0 tsc_timestamp = 0x22cc8398b7194 system_time =

BUG: soft lockup detected on CPU#0! Pid: 2213, comm: smbiod EIP: 0061:[<f4990f2e>] CPU: 0 EIP is at smbiod+0x116/0x16d [smbfs] EFLAGS: 00000246 Tainted: GF (2.6.16-xen-automount #1) EAX: 00000000 EBX: f4996400 ECX: f2c99f68 EDX: f2c98000 ESI: f2c98000 EDI: c06f5780 EBP: f2c99fb8 DS: 007b ES: 007b CR0: 8005003b CR2: b7f77000 CR3: 326e2000 CR4: 00000640

Good morning! On a CentOS 6.4 / 64 bit server I have installed the watchdog 5.5 package. The rpm -qi watchdog states: The watchdog program can be used as a powerful software watchdog daemon or may be alternately used with a hardware watchdog device such as the IPMI hardware watchdog driver interface to a resident Baseboard Management Controller (BMC). ... This configuration file is also used to

Hi all, I've got a Portwell NANO-6060 board I am testing out for potential use in a project of ours. One of the nice features of this board, beyond nice NICs, is that it has a hardware watchdog timer. The problem is that I don't get a /dev/watchdog device file. I know the hardware works, because when I enable it in BIOS, the box will reboot after the timer expires. However,

All, I have an GigaByte motherboard GA-M61P-S3 and I was wondering if any kernel watchdog processes will work with that? Jerry ----------------------------- /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/softdog.ko /lib/modules/2.6.18-53.1.4.el5/kernel/drivers/char/watchdog/ibmasr.ko