similar to: [syslinux:master] PXE ISR: Force polling on select hardware WORKAROUND

On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > 13:36:47.964636 IP 192.168.205.1.47973 > 192.168.205.50.1938: UDP, length 30 > > > 13:36:47.964685 IP 192.168.205.50.1938 > 192.168.205.1.47973: UDP, length 4 > >

On Sun, Jul 13, 2014 at 10:26 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/13/2014 10:54 AM, syslinux-bot for Gene Cumm wrote: >> Commit-ID: 3741886cb700e1017d70f1753f013fa10f4d9272 >> Gitweb: http://www.syslinux.org/commit/3741886cb700e1017d70f1753f013fa10f4d9272 >> Author: Gene Cumm <gene.cumm at gmail.com> >> AuthorDate: Sun, 13 Jul 2014

On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux wrote: > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux wrote: > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > 13:36:47.974245 IP 192.168.205.50.1939 > 192.168.205.1.tftp: 47 RRQ

> On Wed, Oct 07, 2015 at 06:01:30PM +0200, Geert Stappers via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 05:35:36PM +0200, Geert Stappers via Syslinux > wrote: > > > On Wed, Oct 07, 2015 at 08:55:53AM -0500, Clements, James wrote: > > > > On Wed, Oct 07, 2015 Geert Stappers wrote > > > > > 13:36:47.974245 IP 192.168.205.50.1939 >

> On Wed, Oct 07, 2015 at 01:58:51PM +0200, James Clements via Syslinux > wrote: > > On Wed, Oct 07, 2015 at 07:21:28AM -0400, Gene Cumm via Syslinux wrote: > > > On Wed, Oct 7, 2015 at 6:40 AM, Clements, James via Syslinux wrote: > > > > Hi, > > > > > > > > I am using a Windows Server 2012 R2 Hyper-V Generation 2 VM as a > > > >

On Fri, Sep 20, 2013 at 5:15 AM, Matt Fleming <matt at console-pimps.org> wrote: > On Tue, 17 Sep, at 04:23:08PM, Gene Cumm wrote: >> On Tue, Sep 17, 2013 at 9:36 AM, Matt Fleming <matt at console-pimps.org> wrote: >> > On Tue, 03 Sep, at 07:31:52PM, Gene Cumm wrote: >> >> The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd:

The behaviour of default ISRs as provided by the BIOS varies wildly between platforms. Some will simply iret, some will send EOI, some will send EOI and disable the interrupt at the PIC, some will crash the machine due to single-bit errors in the ISR address. When PXENV_UNDI_ISR_IN_START returns PXENV_UNDI_ISR_OUT_NOT_OURS, send the EOI ourselves rather than risking the unpredictable behaviour

I am experiencing an issue where I ran ipxe (as an option rom) and downloaded the lpxelinux.0 as the bootloader. Next it should download the ldlinux.c32 file using UNDI API. but before that it will close and open the underlying device (which is ipxe), and hooking the device interrupt so it can start getting some packets. What I'm experiencing is that if the underlying device doesn't

On Sat, Jul 12, 2014 at 3:38 PM, Alexander Perlis <aperlis at math.lsu.edu> wrote: > On 07/12/2014 02:24 PM, Gene Cumm wrote: >> >> On Sat, Jul 12, 2014 at 3:15 PM, Alexander Perlis <aperlis at math.lsu.edu> >> wrote: >>> >>> On 07/11/2014 09:39 PM, Gene Cumm wrote: >>>> >>>> >>>> With everything else from

On Thu, Jul 24, 2014 at 4:56 AM, Philipp Hahn <hahn at univention.de> wrote: > Hello, > > On 23.07.2014 22:46, Alexander Perlis wrote: >> On Wed, 23 Jul 2014, Philipp Hahn wrote: >>> [...] >>> I tried lpxelinux.0, but it fails to resolve the gateway >>> address via ARP: >>> 17:25:51.399119 ARP, Request who-has 10.200.17.1 tell >>>

On Tue, Sep 17, 2013 at 9:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > On Tue, 03 Sep, at 07:31:52PM, Gene Cumm wrote: >> The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd: >> Gene Cumm (1): >> Allow for UNDIIF_ID_DEBUG in 1 mk line >> >> are available in the git repository at: >> >>

On 07/10/2014 06:39 PM, Gene Cumm wrote: > On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: >> On 07/10/2014 04:07 PM, Alexander Perlis wrote: >>> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >>> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >>> lpxelinux.0, I see the PXELINUX banner line,

On Thu, Jul 10, 2014 at 7:24 PM, H. Peter Anvin <hpa at zytor.com> wrote: > On 07/10/2014 04:07 PM, Alexander Perlis wrote: >> Trying to PXE boot a Dell Optiplex 990 with BIOS A16, which has Intel >> Boot Agent 1.3.81 (2.1 build 089). It gets network and launches >> lpxelinux.0, I see the PXELINUX banner line, but there it hangs. >> >> I tried both 6.03-pre18

On Tue, 17 Sep, at 04:23:08PM, Gene Cumm wrote: > On Tue, Sep 17, 2013 at 9:36 AM, Matt Fleming <matt at console-pimps.org> wrote: > > On Tue, 03 Sep, at 07:31:52PM, Gene Cumm wrote: > >> The following changes since commit 6438fbcb6cb7e0cd40e4bb3681ada047fe77ffdd: > >> Gene Cumm (1): > >> Allow for UNDIIF_ID_DEBUG in 1 mk line > >> >

I''m using a NetBSD 3.1 dom0 with Xen 2.0.7 (so far as I know, the latest supported combination for the NetBSD platform). Linux domUs have their logs fill with messages like this: May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -316000 131542680000000 9684000 131542690000000 May 8 02:01:39 debian kernel: Timer ISR: Time went backwards: -277000 131542680000000 9723000

Hi all, Using a slow serial console with sync_console on SMP leaves me with an unusable system: it gets into a flood of Timer ISR/0: Time went backwards: delta=-3566279 cpu_delta=16433721 shadow=2019998373 off=420435384 processed=2444000000 cpu_processed=2424000000 0: 2424000000 1: 2444000000 messages which swamps the console and leaves things almost, but not quite, completely hung. It is a

Changeset 6902 Sep 18 13:37:23 inyoureyes kernel: 1: 5077390000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards: delta=-34786504 cpu_delta=15257914 shadow=5076506780929 off=938478409 processed=50770Sep 18 13:37:23 inyoureyes kernel: 0: 5077480044418 Sep 18 13:37:23 inyoureyes kernel: 1: 5077430000000 Sep 18 13:37:23 inyoureyes kernel: Timer ISR/1: Time went backwards:

Hi all, Based on the commitdiff comments, this looks like what I (and many many others) have been plagued with. Machines typically affected: DELL PowerEdge 2950, R720, R810, etc. (server class) DELL PowerEdge 960 (desktop class) Eagerly awaiting the next pre-release to test this out! : thumbs up : : thumbs up : Regards, Shantanu

Use isr field instead of direct access to ioaddr. This way generalizes easily to virtio 1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index 9be59d9..ee1b54c 100644 --- a/drivers/virtio/virtio_pci.c +++

Use isr field instead of direct access to ioaddr. This way generalizes easily to virtio 1.0. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/virtio/virtio_pci.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/virtio/virtio_pci.c b/drivers/virtio/virtio_pci.c index 9be59d9..ee1b54c 100644 --- a/drivers/virtio/virtio_pci.c +++