WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] bug in usbback

To: "Keir Fraser" <keir.fraser@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] bug in usbback
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Sun, 26 Jul 2009 11:26:21 +1000
Cc: n_iwamatsu@xxxxxxxxxxxxxx
Delivery-date: Sat, 25 Jul 2009 18:31:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C690992F.106D3%keir.fraser@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <AEC6C66638C05B468B556EA548C1A77D016DDE59@trantor> <C690992F.106D3%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcoNDt3t1TxYd8LiTa2w33vQ+iSYiQAAZc/NAB/IjYA=
Thread-topic: [Xen-devel] bug in usbback
Also, a question on behaviour:

When we receive a reconfigure event, I assume that we should then read
'num-ports' and scan through each of the port-n values in xenstore. Is
there any guarantee that a device hasn't been unplugged and replugged
from the same port during the reconfiguration window? How should I
detect such a thing if the value of port-n hasn't changed? Should I then
probe each device? I'm doing this under Windows which is a bit more
picky and much less flexible...

Thanks

James

> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Saturday, 25 July 2009 20:13
> To: James Harper; xen-devel@xxxxxxxxxxxxxxxxxxx
> Cc: n_iwamatsu@xxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] bug in usbback
> 
> Cc'ing the author...
> 
>  K.
> 
> On 25/07/2009 11:01, "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
wrote:
> 
> > I think there is a bug in pvusb when the DomU does not respond to
the
> > XenbusStateReconfiguring state change and is then rebooted. This
caused
> > the following Dom0 (after a long freeze):
> >
> > BUG: soft lockup detected on CPU#0!
> >
> > Call Trace:
> >  <IRQ> [<ffffffff802a938c>] softlockup_tick+0xe1/0xef
> >  [<ffffffff80268f82>] timer_interrupt+0x408/0x466
> >  [<ffffffff8020fb41>] handle_IRQ_event+0x4d/0x95
> >  [<ffffffff802a9870>] __do_IRQ+0xb4/0x127
> >  [<ffffffff8026729c>] do_IRQ+0x44/0x4d
> >  [<ffffffff80375f6b>] evtchn_do_upcall+0x1b3/0x26e
> >  [<ffffffff8025c8d2>] do_hypervisor_callback+0x1e/0x2c
> >  <EOI> [<ffffffff88355b7e>] :usbbk:usbbk_schedule+0x1e0/0xa3f
> >  [<ffffffff8029482f>] autoremove_wake_function+0x0/0x2e
> >  [<ffffffff802947ba>] keventd_create_kthread+0x0/0x62
> >  [<ffffffff8835599e>] :usbbk:usbbk_schedule+0x0/0xa3f
> >  [<ffffffff802947ba>] keventd_create_kthread+0x0/0x62
> >  [<ffffffff802325e4>] kthread+0xd4/0x108
> >  [<ffffffff8025cb24>] child_rip+0xa/0x12
> >  [<ffffffff802947ba>] keventd_create_kthread+0x0/0x62
> >  [<ffffffff8025c827>] error_exit+0x0/0x71
> >  [<ffffffff80232510>] kthread+0x0/0x108
> >  [<ffffffff8025cb1a>] child_rip+0x0/0x12
> >
> > FYI, I am trying to get pvusb working under GPLPV and I had never
seen
> > the Reconfiguring/Reconfigured states before and so I wasn't doing
> > anything with them...
> >
> > James
> >
> >
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>