Hi all, Have a Debian Wheezy system with the Xen and XCP packages installed. When I first installed Debian, the USB keyboard and mouse all worked Ok. After installing Xen, the USB devices stopped working. Now, even with nothing plugged in to the USB ports, I still get the following errors during boot: [ 39.193178] usb 3-1: device not accepting address 3, error -110 [ 39.305178] usb 3-1: new high-speed USB device number 4 using ehci_hcd [ 49.737367] usb 3-1: device not accepting address 4, error -110 [ 49.849378] usb 3-1: new high-speed USB device number 5 using ehci_hcd [ 60.281573] usb 3-1: device not accepting address 5, error -110 [ 60.281647] hub 3-0:1.0: unable to enumerate USB device on port 1 [ 60.417571] usb 4-1: new high-speed USB device number 2 using ehci_hcd [ 65.417672] ehci_hcd 0000:00:1d.0: Unlink after no-IRQ? Controller is probably using the wrong IRQ. [ 75.973866] usb 4-1: device not accepting address 2, error -110 [ 76.085919] usb 4-1: new high-speed USB device number 3 using ehci_hcd [ 91.642145] usb 4-1: device not accepting address 3, error -110 [ 91.754164] usb 4-1: new high-speed USB device number 4 using ehci_hcd [ 102.186347] usb 4-1: device not accepting address 4, error -110 [ 102.298356] usb 4-1: new high-speed USB device number 5 using ehci_hcd [ 112.730542] usb 4-1: device not accepting address 5, error -110 [ 112.730619] hub 4-0:1.0: unable to enumerate USB device on port 1 It''s not the end of the world at the moment, as I have no USB devices plugged in. However, I might want to connect USB hardware in the future, and it would appear that this won''t work. This is a 32 bit dom0, with all 64 bit guests (I saw recommendations to install this way). Linux xcp 3.2.0-4-686-pae #1 SMP Debian 3.2.46-1 i686 GNU/Linux The xen hypervisor is 64 bit, v4.1. Any suggestions? Andy
On Mon, 2013-06-24 at 20:45 +0000, Andy Hawkins wrote:> Hi all, > > Have a Debian Wheezy system with the Xen and XCP packages installed. When I > first installed Debian, the USB keyboard and mouse all worked Ok. > > After installing Xen, the USB devices stopped working. Now, even with > nothing plugged in to the USB ports, I still get the following errors during > boot: > > [ 39.193178] usb 3-1: device not accepting address 3, error -110 > [ 39.305178] usb 3-1: new high-speed USB device number 4 using ehci_hcd > [ 49.737367] usb 3-1: device not accepting address 4, error -110 > [ 49.849378] usb 3-1: new high-speed USB device number 5 using ehci_hcd > [ 60.281573] usb 3-1: device not accepting address 5, error -110 > [ 60.281647] hub 3-0:1.0: unable to enumerate USB device on port 1 > [ 60.417571] usb 4-1: new high-speed USB device number 2 using ehci_hcd > [ 65.417672] ehci_hcd 0000:00:1d.0: Unlink after no-IRQ? Controller is > probably using the wrong IRQ.I had a vague feeling this was related to interrupts and then I spotted this message in the middle here ;-) I''d start by making sure you have the latest firmware for your hardware, in order to make sure your BIOS tables are all up to date.> [ 75.973866] usb 4-1: device not accepting address 2, error -110 > [ 76.085919] usb 4-1: new high-speed USB device number 3 using ehci_hcd > [ 91.642145] usb 4-1: device not accepting address 3, error -110 > [ 91.754164] usb 4-1: new high-speed USB device number 4 using ehci_hcd > [ 102.186347] usb 4-1: device not accepting address 4, error -110 > [ 102.298356] usb 4-1: new high-speed USB device number 5 using ehci_hcd > [ 112.730542] usb 4-1: device not accepting address 5, error -110 > [ 112.730619] hub 4-0:1.0: unable to enumerate USB device on port 1 > > It''s not the end of the world at the moment, as I have no USB devices > plugged in. However, I might want to connect USB hardware in the future, and > it would appear that this won''t work. > > This is a 32 bit dom0, with all 64 bit guests (I saw recommendations to > install this way). > > Linux xcp 3.2.0-4-686-pae #1 SMP Debian 3.2.46-1 i686 GNU/Linux > > The xen hypervisor is 64 bit, v4.1. > > Any suggestions? > > Andy > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Hi,
In article <1372178958.18901.93.camel@zakaz.uk.xensource.com>,
Ian Campbell<Ian.Campbell@citrix.com>
wrote:> I had a vague feeling this was related to interrupts and then I spotted
> this message in the middle here ;-)
>
> I''d start by making sure you have the latest firmware for your
hardware,
> in order to make sure your BIOS tables are all up to date.
I should probably add that I''m booting with
''acpi=noirq'' in the kernel
command line. If I don''t do this it locks up mid way through boot.
I''ll double check the BIOS on the motherboard, it might well not be the
latest version. However, the USB stuff *does* work just fine if I book to
''vanilla'' linux rather than Xen.
Andy
On Tue, 2013-06-25 at 17:08 +0000, Andy Hawkins wrote:> Hi, > > In article <1372178958.18901.93.camel@zakaz.uk.xensource.com>, > Ian Campbell<Ian.Campbell@citrix.com> wrote: > > I had a vague feeling this was related to interrupts and then I spotted > > this message in the middle here ;-) > > > > I''d start by making sure you have the latest firmware for your hardware, > > in order to make sure your BIOS tables are all up to date. > > I should probably add that I''m booting with ''acpi=noirq'' in the kernel > command line. If I don''t do this it locks up mid way through boot.I think you should take a step back and report/tackle that lockup issue head on rather than working around it. I strongly suspect that it is causing your USB issue. The first step for the lockup issue would still be to check you have the latest BIOS though.> I''ll double check the BIOS on the motherboard, it might well not be the > latest version. However, the USB stuff *does* work just fine if I book to > ''vanilla'' linux rather than Xen.Including if you use the Linux equivalent of "acpi=noirq" ? Ian.
Hi,
In article <1372243702.7337.28.camel@zakaz.uk.xensource.com>,
Ian Campbell<Ian.Campbell@citrix.com>
wrote:> I think you should take a step back and report/tackle that lockup issue
> head on rather than working around it. I strongly suspect that it is
> causing your USB issue.
>
> The first step for the lockup issue would still be to check you have the
> latest BIOS though.
Ok, I''ll give that a go. It was odd that it booted just fine all
through the
installation of Debian, but since the first boot after the installation it
would lock up solid.
acpi parameters were all I could do to get it to boot.
>> I''ll double check the BIOS on the motherboard, it might well
not be the
>> latest version. However, the USB stuff *does* work just fine if I book
to
>> ''vanilla'' linux rather than Xen.
>
> Including if you use the Linux equivalent of "acpi=noirq" ?
Not sure what you mean here. I''m passing the
''acpi=noirq'' on the linux
command line at boot. The USB stuff did work just fine when I did that (at
least, I''m 99% sure it did).
Andy
On Wed, 2013-06-26 at 18:26 +0000, Andy Hawkins wrote:> Hi, > > In article <1372243702.7337.28.camel@zakaz.uk.xensource.com>, > Ian Campbell<Ian.Campbell@citrix.com> wrote: > > I think you should take a step back and report/tackle that lockup issue > > head on rather than working around it. I strongly suspect that it is > > causing your USB issue. > > > > The first step for the lockup issue would still be to check you have the > > latest BIOS though. > > Ok, I''ll give that a go. It was odd that it booted just fine all through the > installation of Debian, but since the first boot after the installation it > would lock up solid. > > acpi parameters were all I could do to get it to boot. > > >> I''ll double check the BIOS on the motherboard, it might well not be the > >> latest version. However, the USB stuff *does* work just fine if I book to > >> ''vanilla'' linux rather than Xen. > > > > Including if you use the Linux equivalent of "acpi=noirq" ? > > Not sure what you mean here. I''m passing the ''acpi=noirq'' on the linux > command line at boot. The USB stuff did work just fine when I did that (at > least, I''m 99% sure it did).OK, then I''m a bit confused about under which circumstances you are seeing the various issues. Are you saying that a native boot of Linux (without Xen) with no commandline acpi=noirq parameters works, or that it locks up? If you boot natively (no Xen) with acpi=noirq does USB work? Ian.
Hi,
In article <1372320313.28443.3.camel@zakaz.uk.xensource.com>,
Ian Campbell<Ian.Campbell@citrix.com>
wrote:> OK, then I''m a bit confused about under which circumstances you
are
> seeing the various issues.
>
> Are you saying that a native boot of Linux (without Xen) with no
> commandline acpi=noirq parameters works, or that it locks up?
>
> If you boot natively (no Xen) with acpi=noirq does USB work?
Sorry, I probably should have been a bit more clear. Here''s the
sequence of
events when I got the machine:
1. Boot from Debian installer via USB, install Debian. USB keyboard etc. all
fine
2. Finish installing Debian, reboot. Locks up during boot.
3. Add ''acpi=noirq'' to kernel command line, boots fine. I
*believe* the USB
keyboard was still working at this point, although I may have done the
remainder of the configuration via SSH. However, I tend to tell Debian to
install no packages, then add SSH from the command line after the install
has finished.
4. Install Xen and XCP. Reboot into Xen. Keyboard no longer works, USB
errors displayed on console and in dmesg.
Hope that''s a bit more clear.
I''ll try to check the BIOS version and upgrade it if necessary, but the
machine is now in the loft! As far as hardware goes, there''s nothing
connected to the motherboard apart from CPU, RAM and two SATA disks.
It''s one of these if it''s relevant:
http://www.jetwaycomputer.com/NF9E.html
Andy
On Thu, 2013-06-27 at 10:01 +0000, Andy Hawkins wrote:> Hi, > > In article <1372320313.28443.3.camel@zakaz.uk.xensource.com>, > Ian Campbell<Ian.Campbell@citrix.com> wrote: > > OK, then I''m a bit confused about under which circumstances you are > > seeing the various issues. > > > > Are you saying that a native boot of Linux (without Xen) with no > > commandline acpi=noirq parameters works, or that it locks up? > > > > If you boot natively (no Xen) with acpi=noirq does USB work? > > Sorry, I probably should have been a bit more clear. Here''s the sequence of > events when I got the machine: > > 1. Boot from Debian installer via USB, install Debian. USB keyboard etc. all > fine > > 2. Finish installing Debian, reboot. Locks up during boot.OK, so you have an issue with the native kernel on this hardware. It is probably worth resolving this (perhaps via a Debian bug report, unless BIOS update helps) before going on to worry about Xen. Presumably the version of the installer you picked up had a slightly different kernel to the one which actually ended up installed. If you can identify which is which then that might be useful information for the Debian bug report.> 3. Add ''acpi=noirq'' to kernel command line, boots fine. I *believe* the USB > keyboard was still working at this point, although I may have done the > remainder of the configuration via SSH. However, I tend to tell Debian to > install no packages, then add SSH from the command line after the install > has finished. > > 4. Install Xen and XCP. Reboot into Xen. Keyboard no longer works, USB > errors displayed on console and in dmesg.If at this point you remove the noirq thing does it work under Xen?> Hope that''s a bit more clear. > > I''ll try to check the BIOS version and upgrade it if necessary, but the > machine is now in the loft! As far as hardware goes, there''s nothing > connected to the motherboard apart from CPU, RAM and two SATA disks. > > It''s one of these if it''s relevant: > > http://www.jetwaycomputer.com/NF9E.html > > Andy > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xen.org > http://lists.xen.org/xen-users
Hi,
In article <1372327974.28443.29.camel@zakaz.uk.xensource.com>,
Ian Campbell<Ian.Campbell@citrix.com>
wrote:> OK, so you have an issue with the native kernel on this hardware. It is
> probably worth resolving this (perhaps via a Debian bug report, unless
> BIOS update helps) before going on to worry about Xen.
I''ve checked with the place I bought the motherboard from in May.
Latest
BIOS for that was issued back in January, so they think that it''ll
already
have it in. I''ll double check obviously.
> Presumably the version of the installer you picked up had a slightly
> different kernel to the one which actually ended up installed. If you
> can identify which is which then that might be useful information for
> the Debian bug report.
Quite possibly. I''ll have to have a look and see if I can arrange for a
serial console to this machine so that I can fully log the output during
boot.
> If at this point you remove the noirq thing does it work under Xen?
I''m pretty sure I''ve tried this, but I get a similar panic
when Dom0 boots.
I''ll try this again however.
Andy