search for: acknowledges

Displaying 20 results from an estimated 750 matches for "acknowledges".

Did you mean: acknowledge
2007 Aug 09
1
pxelinux doesn't answer ARP requests when it should
Hi there. Regarding currently known problem as stated on http://syslinux.zytor.com/pxe.php: we should probably call the UDP receive function in the keyboard entry loop, so that we answer ARP requests. Here's another illustration of the problem, description of related pxelinux problem and workaround for both problems. Configuration: dhcp/tftp server -- 213.180.194.116
2009 Mar 17
3
PXE boot hangs while transferring vmlinuz or initrd.img
Hi, I have a user that is experiencing problems pxe booting several identical servers. pxelinux.0 is from syslinux 3.63 and the TFTP server is 0.42 running on CentOS 5.2. After loading pxelinux.0, the client will then start transferring vmlinuz and initrd.img via tftp. More than half the time, the transfer will get stuck and then eventually print a timeout message. I ran tcpdump and I can see
2010 Jun 22
9
PRI span problem - no D channel
Hi, I have the following happen to me after the restart of one of my servers: out of my 3 PRIs (all configured with the same technical settings), the last one isn''t coming back. It''s underutilized (chances it didn''t get a call since my reboot), if it makes a difference . The PRI goes from provisioned to unprovisioned, and I get this regularly: [Jun 22 09:03:48]
2010 May 17
1
PRI down due to chan_zap.c: No more room in scheduler....Got SABME and Sending Unnumbered Acknowledgement...Any thoughts?
Hi Guys, Running the following with a Sangoma A101D PRI card: *Asterisk 1.4.21.2* *LibPRI version: 1.4.10* No inbound or outbound calls can be made. In fact Asterisk CLI doesn''t show any activity. Problem goes away on restart of the system or maybe asterisk. I see post about upgrading Libpri to 1.4.10.2 and then I see posts that even that didn''t work. Anyone can weigh in this
2014 Mar 11
2
syslinux.efi [PXELINUX EFI 64 boot] not properly TFTP'ing ldlinux.e64
Gene and co, Now my pxelinux efi 64 boot is properly loading syslinux.efi (via TFTP) It then issues a TFTP file request for efi.x64/pxelinux.cfg/ldlinux.e64. (All my efi x64 content is under efi.x64/pxelinux.cfg). However, I see that it fails to properly negotiate the TFTP options with my TFTP server. so it never transfers ldlinux.e64 over. In its file request packet, it asks
2014 Sep 23
5
[PATCH RFC] virtio_pci: fix virtio spec compliance on restore
On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin
2014 Sep 23
5
[PATCH RFC] virtio_pci: fix virtio spec compliance on restore
On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK Cc: stable at vger.kernel.org Cc: Amit Shah <amit.shah at redhat.com> Signed-off-by: Michael S. Tsirkin
2008 May 04
4
UK BT ISDN30e PRI Problem
Ok Guys, I''ve done a tonne of hunting around on this problem, but can''t find much help. I''m running: asterisk 1.4.19.1 libpri 1.4.3 and zaptel 1.4.9.2 which I believe has been modified by RedFone to add the ztd-ethmf module. My interface is a RedFone foneBridge2 4 Span; and I''m connecting to a BT E1 PRI / ISDN30e with 15 lines on span 1, and a legacy
2005 Sep 15
1
PXE boot hangs after trying to load cfg/<max address>
Hi, i'm trying to get my VIA Epia with VIA Rhine ethernet device to boot PXELinux. I have done this before, but now i can't get it to work. The machine loads pxelinux.0, i see some messages. But it fails just after trying reading the first config file (the one with the mac address). It kinda says this (transcribed): CLIENT IP: 192.168.1.23 MASK: 255.255.255.0 DHCP IP: 192.168.1.93
2003 Jul 10
2
tftp-hpa server with multiple network interfaces
Hello, A host of mine which acts as a gateway for a cluster also acts as a dhcp and tftp server for the cluster nodes. Recently, for reasons that are not really important we changed the interfaces so that eth0 is conencted to our production network and the eth1 network is connected to the cluster's internal network. It was the opposite before. Normally, we want most of the services running on
2014 Mar 24
2
[PATCH 06/12] drm/nouveau/ibus: add GK20A support
On Mon, Mar 24, 2014 at 05:42:28PM +0900, Alexandre Courbot wrote: [...] > diff --git a/drivers/gpu/drm/nouveau/core/subdev/ibus/nvea.c b/drivers/gpu/drm/nouveau/core/subdev/ibus/nvea.c [...] > +#include <subdev/ibus.h> > + > +struct nvea_ibus_priv { > + struct nouveau_ibus base; > +}; > + > +static
2014 Oct 06
2
[PATCH v2 01/15] virtio_pci: fix virtio spec compliance on restore
On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK This behaviour will break with hypervisors that assume spec compliant behaviour. It seems like a good idea to have
2014 Oct 06
2
[PATCH v2 01/15] virtio_pci: fix virtio spec compliance on restore
On restore, virtio pci does the following: + set features + init vqs etc - device can be used at this point! + set ACKNOWLEDGE,DRIVER and DRIVER_OK status bits This is in violation of the virtio spec, which requires the following order: - ACKNOWLEDGE - DRIVER - init vqs - DRIVER_OK This behaviour will break with hypervisors that assume spec compliant behaviour. It seems like a good idea to have
2005 Dec 19
2
Network Loading of freeBSD
I have spent a couple of days and quite some time during the nights googling and experimenting in pursuing subject objective and I feel like failing, if I cannot get competent help: My objective: boot a FreeBSD-package over the network by Systems lacking HW-Support for PXE My Testconfiguration: Server IBM-PC300 Client Siemes Fujitsu ErgoPro with freeBSD6.0 installed Network card in
2007 Sep 05
1
FWIW - small bug in a PXE client
...rk window, so I'll summarize: client sends Read Request (1) for pxelinux.0 with option tsize=0, tftpd sends Option Acknowledgement (6), tsize = 13940 (the size of v3.51) client responds with Error Code (5) not defined It then re-requests Read, this time with option blksize = 1456 tftpd-hpa acknowledges (6) this client then send Acknowledgment (4) for block 0 tftpd sends Data Packet (3), block 1, data (1456 bytes) client acknoldeges (4) block 1, cycle repeats to completion.
1999 Mar 17
0
CIAC Bulletin J-035: Linux Blind TCP Spoofing
...izes a state based model. In a typical client-server application, the client initiates a connection by transmitting a TCP segment to a listening server process. This causes the state of the process to move from the LISTEN state into SYN_RECEIVE if a SYN flag is present. During this state the server acknowledges the clients request setting both the SYN and ACK flags. To complete the three way handshake the client acknowledges the servers response, moving the server from SYN_RECEIVE to ESTABLISHED state. To establish a forged TCP session an attacker must have knowledge of or be able to predict the initial...
2007 Feb 02
0
Bug#409392: Acknowledgement (xen-utils-3.0-unstable-1: xensto red creates /dev/xen/evtchn with the wrong minor)
close 409392 thanks Disregard - I should be using the stable hypervisor. -- nate carlson / ncarlson@ibsys.com / 651-365-4124 sr. systems administrator - nbcsports.com @ ib
2007 Jun 13
0
Processed (with 5 errors): Re: Bug#428685: Acknowledgement (kernel bugs when running xen in HVM mode)
Processing commands for control at bugs.debian.org: > reassign 428685 xen-ioemu-3.0.3-1 Bug#428685: kernel bugs when running xen in HVM mode Warning: Unknown package 'xen' Bug reassigned from package `xen' to `xen-ioemu-3.0.3-1'. > Debian Bug Tracking System wrote: Unknown command or malformed arguments to command. > > Thank you for the problem report you have sent
2014 Mar 14
1
syslinux.efi [PXELINUX EFI 64 boot] not properly TFTP'ing ldlinux.e64
H Peter, I notice the Intel Boot Agent (in the BOOT ROM) takes a different approach. When TFTP loading the initial syslinux.efi. It receives the OACK with both options set -- tsize (of 145744) and blksize (of 1408). Apparently it has challenges parsing this "two option" OACK packet. But it remembers the tsize of 145744. So it issues another read request, this time requesting only a
2010 Jan 16
1
[PATCH] drm/nouveau: Acknowledge DMA_VTX_PROTECTION PGRAPH interrupts
Currently Nouveau is unable to dismiss DMA_VTX_PROTECTION errors, which results in an infinite loop in the interrupt handler. These errors are caused both by bugs in the Gallium driver and by user-specified index buffers with out of bounds indices. By mmio-tracing the nVidia drivers, I found out how this is done. On DMA_VTX_PROTECTION, The nVidia driver reads the register 0x402000, always