From: Ken Moffat <zarniwhoop@ntlworld.com>
To: "Chen, Tiejun" <tiejun.chen@intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: Qemu e1000 broken in -rc1 and -rc2 : bisected
Date: Mon, 9 Mar 2015 15:05:30 +0000 [thread overview]
Message-ID: <20150309150530.GA27489@milliways> (raw)
In-Reply-To: <54FD100C.3080402@intel.com>
On Mon, Mar 09, 2015 at 11:14:20AM +0800, Chen, Tiejun wrote:
> On 2015/3/7 3:27, Ken Moffat wrote:
> >On Fri, Mar 06, 2015 at 12:02:40AM +0000, Ken Moffat wrote:
> >> I have a very recent qemu i686 image, using a 3.19.0 kernel and
> >>dhclient, which works fine if the host is running a 3.19.0 kernel,
> >>but breaks when the host runs 4.0.0-rc1 or -rc2.
> >>
> >> On those, dhclient does not get an address, so I have no network.
> >>There is a message
> >>e1000 0000:00:03.0 eth0: Reset adaptor
> >>
> >> Before I start trying to bisect this, has anybody already seen, or
> >>fixed, it ?
> >>
> > Bisected.
> >b4eef9b36db461ca44832226fbca614db58c0c33 is the first bad commit
> >commit b4eef9b36db461ca44832226fbca614db58c0c33
> >Author: Tiejun Chen <tiejun.chen@intel.com>
> >Date: Mon Dec 22 10:32:57 2014 +0100
> >
> > kvm: x86: vmx: NULL out hwapic_isr_update() in case of
> >!enable_apicv
> >
[...]
>
> Did you try Linux 4.0-rc3? That includes one relevant fix,
>
> KVM: SVM: fix interrupt injection (apic->isr_count always 0)
>
> Thanks
> Tiejun
I've now tried -rc3, and the problem has gone. Thanks.
ĸen
--
Nanny Ogg usually went to bed early. After all, she was an old lady.
Sometimes she went to bed as early as 6 a.m.
prev parent reply other threads:[~2015-03-09 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 0:02 Qemu e1000 broken in -rc1 and -rc2 Ken Moffat
2015-03-06 19:27 ` Qemu e1000 broken in -rc1 and -rc2 : bisected Ken Moffat
2015-03-09 3:14 ` Chen, Tiejun
2015-03-09 15:05 ` Ken Moffat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150309150530.GA27489@milliways \
--to=zarniwhoop@ntlworld.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=tiejun.chen@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.