From: Noboru Iwamatsu <n_iwamatsu@jp.fujitsu.com>
To: james.harper@bendigoit.com.au, xen-devel@lists.xensource.com
Subject: Re: bug in usbback
Date: Mon, 27 Jul 2009 10:18:28 +0900 [thread overview]
Message-ID: <4A6D0064.807@jp.fujitsu.com> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D016DDE59@trantor>
Hi James,
Reconfiguring/Resconfigured states are used to notify the hotplug
event, as follows.
usb device usbback usbfront
--------- ------- --------
Connected Connected
| |
---plug&probe--->| |
| |
Reconfiguring-------------------->|
| |
| <---------------------Reconfiguring
| |
| |
usbback_do_hotplug() |
| |
| |
Reconfigured-------------------->|
| |
| |
| usbfront_do_hotplug()
| |
| |
|<----------------------Connected
| |
Connected |
| |
You mean:
- Your version of usbfront NOT respond to Reconfiguring state.
It's not bug of original usbfront.
- When usbback is in Reconfiguring state and usbfront NOT respond to
that, rebooting domU causes the BUG.
Is my understanding right?
Regards,
Noboru
James Harper 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@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2009-07-27 1:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-25 10:01 bug in usbback James Harper
2009-07-25 10:12 ` Keir Fraser
2009-07-26 1:26 ` James Harper
2009-07-27 5:13 ` Noboru Iwamatsu
2009-07-27 9:16 ` James Harper
2009-07-28 2:41 ` Noboru Iwamatsu
2009-07-28 4:32 ` James Harper
2009-07-28 9:32 ` Noboru Iwamatsu
2009-07-27 1:18 ` Noboru Iwamatsu [this message]
2009-07-27 1:23 ` James Harper
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=4A6D0064.807@jp.fujitsu.com \
--to=n_iwamatsu@jp.fujitsu.com \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.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.