[Resending as the last copy seems to have been lost in the ether -- it
certainly isn't in the GMANE archive]
Well, behavior with the patch applied is certainly different.
The large download I'm running still times out; however, it is now able
to resume without needing to bring the interface down
;[EMAIL PROTECTED]>
> > To: [EMAIL PROTECTED]; qemu-devel@nongnu.org
> > Sent: Friday, August 3, 2007 8:18:50 AM
> > Subject: Re: [Qemu-devel] Re: Network connections stalling (due to
> > lost interrupts/ticks?)
> >
> > Charles,
> >
> > Are you
Well, behavior with the patch applied is certainly different.
The large download I'm running still times out; however, it is now able
to resume without needing to bring the interface down and back up.
However, after the first timeout, subsequent timeouts occur with much
greater frequency -- still
m: Jason Wessel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; qemu-devel@nongnu.org
Sent: Friday, August 3, 2007 8:18:50 AM
Subject: Re: [Qemu-devel] Re: Network connections stalling (due to
lost interrupts/ticks?)
Charles,
Are you willing to try an experimental patch?
Perhaps you could try
essel <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]; qemu-devel@nongnu.org
Sent: Friday, August 3, 2007 8:18:50 AM
Subject: Re: [Qemu-devel] Re: Network connections stalling (due to lost
interrupts/ticks?)
Charles,
Are you willing to try an experimental patch?
Perhaps you could try the attache
Charles,
Are you willing to try an experimental patch?
Perhaps you could try the attached patch and post back if it happens to
solve your problem. There is most definitely a problem where qemu can
get hung up indefinitely after an "interrupt storm". I had not ever
submitted it because there
This appears to only happen with -net tap; I cannot reproduce the issue
with -net user.
This loss of connectivity is still happening; at least within my
environment, it's quite reproducible. While I've eliminated the message
about being unable to set the RTC to 1024Hz by recompiling my host
kernel without CONFIG_HPET_RTC_IRQ, the host's kernel is frequently
complaining "rtc: lost some
Charles Duffy wrote:
> There's a warning on startup that the system can't set a 1024Hz timer,
> which persists even after I set /proc/sys/dev/rtc/max-user-freq to 1024,
> and I occasionally get warnings at runtime ("Your time source seems to
> be instable or some driver is hogging interrupts").
Th
