* [POSSIBLE BUG] Failure to bind event channel
@ 2014-01-15 12:30 Wei Liu
2014-01-15 12:37 ` Ian Campbell
2014-01-28 16:55 ` Wei Liu
0 siblings, 2 replies; 5+ messages in thread
From: Wei Liu @ 2014-01-15 12:30 UTC (permalink / raw)
To: xen-devel; +Cc: wei.liu2
Xen: master branch
Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
linux-next
When I tried to start a HVM domain running squeeze with 2.6.32, I got
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
(XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
[... more of this ...]
[67196.736733] device vif5.0 entered promiscuous mode
[67196.746221] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
[67196.911973] device vif5.0-emu entered promiscuous mode
[67196.921890] xenbr0: port 3(vif5.0-emu) entered forwarding state
[67196.927833] xenbr0: port 3(vif5.0-emu) entered forwarding state
(d5) HVM Loader
(d5) Detected Xen v4.4-unstable
(d5) Xenbus rings @0xfeffc000, event channel 3
(d5) System requested SeaBIOS
(d5) CPU speed is 2660 MHz
(d5) Relocating guest memory for lowmem MMIO space disabled
(XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
(d5) PCI-ISA link 0 routed to IRQ5
(XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
(d5) PCI-ISA link 1 routed to IRQ10
The guest was eventually up and running and seemed to be working fine.
The failure in log was not that harmful after all... But it would be
nice to figure out what's going on here. I suspect the toolstack was
trying to setup something, failed, then retried and eventually succeed.
Sadly the error log wasn't elaborated enough to provide direct insight
into the root cause and I couldn't tell which side (toolstack, kernel,
Xen) to blame.
The failing snippet in Xen common/event_channel.c
269 if ( (rchn->state != ECS_UNBOUND) ||
270 (rchn->u.unbound.remote_domid != ld->domain_id) )
271 ERROR_EXIT_DOM(-EINVAL, rd);
Wei.
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: [POSSIBLE BUG] Failure to bind event channel
2014-01-15 12:30 [POSSIBLE BUG] Failure to bind event channel Wei Liu
@ 2014-01-15 12:37 ` Ian Campbell
2014-01-15 14:29 ` Wei Liu
2014-01-28 16:55 ` Wei Liu
1 sibling, 1 reply; 5+ messages in thread
From: Ian Campbell @ 2014-01-15 12:37 UTC (permalink / raw)
To: Wei Liu; +Cc: Julien Grall, xen-devel
On Wed, 2014-01-15 at 12:30 +0000, Wei Liu wrote:
> Xen: master branch
> Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> linux-next
>
> When I tried to start a HVM domain running squeeze with 2.6.32, I got
>
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
Julien mentioned having seen something very similar with BSD on ARM
yesterday...
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> [... more of this ...]
> [67196.736733] device vif5.0 entered promiscuous mode
> [67196.746221] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
> [67196.911973] device vif5.0-emu entered promiscuous mode
> [67196.921890] xenbr0: port 3(vif5.0-emu) entered forwarding state
> [67196.927833] xenbr0: port 3(vif5.0-emu) entered forwarding state
> (d5) HVM Loader
> (d5) Detected Xen v4.4-unstable
> (d5) Xenbus rings @0xfeffc000, event channel 3
> (d5) System requested SeaBIOS
> (d5) CPU speed is 2660 MHz
> (d5) Relocating guest memory for lowmem MMIO space disabled
> (XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
> (d5) PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
> (d5) PCI-ISA link 1 routed to IRQ10
>
> The guest was eventually up and running and seemed to be working fine.
> The failure in log was not that harmful after all... But it would be
> nice to figure out what's going on here. I suspect the toolstack was
> trying to setup something, failed, then retried and eventually succeed.
> Sadly the error log wasn't elaborated enough to provide direct insight
> into the root cause and I couldn't tell which side (toolstack, kernel,
> Xen) to blame.
>
> The failing snippet in Xen common/event_channel.c
>
> 269 if ( (rchn->state != ECS_UNBOUND) ||
> 270 (rchn->u.unbound.remote_domid != ld->domain_id) )
> 271 ERROR_EXIT_DOM(-EINVAL, rd);
>
> Wei.
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [POSSIBLE BUG] Failure to bind event channel
2014-01-15 12:37 ` Ian Campbell
@ 2014-01-15 14:29 ` Wei Liu
2014-01-15 14:34 ` Julien Grall
0 siblings, 1 reply; 5+ messages in thread
From: Wei Liu @ 2014-01-15 14:29 UTC (permalink / raw)
To: Ian Campbell; +Cc: Julien Grall, Wei Liu, xen-devel
On Wed, Jan 15, 2014 at 12:37:57PM +0000, Ian Campbell wrote:
> On Wed, 2014-01-15 at 12:30 +0000, Wei Liu wrote:
> > Xen: master branch
> > Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> > linux-next
> >
> > When I tried to start a HVM domain running squeeze with 2.6.32, I got
> >
> > (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
>
> Julien mentioned having seen something very similar with BSD on ARM
> yesterday...
>
Weird, this error message was gone after I rebooted my server. I
wouldn't bother with heisenbug at this stage. :-)
Wei.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [POSSIBLE BUG] Failure to bind event channel
2014-01-15 14:29 ` Wei Liu
@ 2014-01-15 14:34 ` Julien Grall
0 siblings, 0 replies; 5+ messages in thread
From: Julien Grall @ 2014-01-15 14:34 UTC (permalink / raw)
To: Wei Liu; +Cc: Ian Campbell, xen-devel
On 01/15/2014 02:29 PM, Wei Liu wrote:
> On Wed, Jan 15, 2014 at 12:37:57PM +0000, Ian Campbell wrote:
>> On Wed, 2014-01-15 at 12:30 +0000, Wei Liu wrote:
>>> Xen: master branch
>>> Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
>>> linux-next
>>>
>>> When I tried to start a HVM domain running squeeze with 2.6.32, I got
>>>
>>> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
>>
>> Julien mentioned having seen something very similar with BSD on ARM
>> yesterday...
>>
>
> Weird, this error message was gone after I rebooted my server. I
> wouldn't bother with heisenbug at this stage. :-)
>
I had the same bug on ARM platform with FreeBSD and Linux guest. It
happens once a while but I'm unable to reproduce reliably.
As for you, the bug disappear after reboot.
--
Julien Grall
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [POSSIBLE BUG] Failure to bind event channel
2014-01-15 12:30 [POSSIBLE BUG] Failure to bind event channel Wei Liu
2014-01-15 12:37 ` Ian Campbell
@ 2014-01-28 16:55 ` Wei Liu
1 sibling, 0 replies; 5+ messages in thread
From: Wei Liu @ 2014-01-28 16:55 UTC (permalink / raw)
To: xen-devel; +Cc: wei.liu2
On Wed, Jan 15, 2014 at 12:30:45PM +0000, Wei Liu wrote:
> Xen: master branch
> Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
> linux-next
>
> When I tried to start a HVM domain running squeeze with 2.6.32, I got
>
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
Julien has successfully reproduced this issue. This is actually caused
by two xenconsoled's running at the same time. Nothing needs fixing. :-)
Wei.
> [... more of this ...]
> [67196.736733] device vif5.0 entered promiscuous mode
> [67196.746221] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
> [67196.911973] device vif5.0-emu entered promiscuous mode
> [67196.921890] xenbr0: port 3(vif5.0-emu) entered forwarding state
> [67196.927833] xenbr0: port 3(vif5.0-emu) entered forwarding state
> (d5) HVM Loader
> (d5) Detected Xen v4.4-unstable
> (d5) Xenbus rings @0xfeffc000, event channel 3
> (d5) System requested SeaBIOS
> (d5) CPU speed is 2660 MHz
> (d5) Relocating guest memory for lowmem MMIO space disabled
> (XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
> (d5) PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
> (d5) PCI-ISA link 1 routed to IRQ10
>
> The guest was eventually up and running and seemed to be working fine.
> The failure in log was not that harmful after all... But it would be
> nice to figure out what's going on here. I suspect the toolstack was
> trying to setup something, failed, then retried and eventually succeed.
> Sadly the error log wasn't elaborated enough to provide direct insight
> into the root cause and I couldn't tell which side (toolstack, kernel,
> Xen) to blame.
>
> The failing snippet in Xen common/event_channel.c
>
> 269 if ( (rchn->state != ECS_UNBOUND) ||
> 270 (rchn->u.unbound.remote_domid != ld->domain_id) )
> 271 ERROR_EXIT_DOM(-EINVAL, rd);
>
> Wei.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-01-28 16:55 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-01-15 12:30 [POSSIBLE BUG] Failure to bind event channel Wei Liu
2014-01-15 12:37 ` Ian Campbell
2014-01-15 14:29 ` Wei Liu
2014-01-15 14:34 ` Julien Grall
2014-01-28 16:55 ` Wei Liu
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.