>> Enabling ACPI is not an option for me in that case. > Why not? Well, the reason is the following: After starting the linux system I switch back the machine to real mode using the kexec system call (then I run some real/protected mode stuff). This works fine in most cases, but on some machines after kexec the machine is in a state where important things (eg. some bios interrupt calls) don't work any more. The reason for that is that the machine's interrupt controller/pci system/chipset is left in an 'unusable' state by the ACPI system... Disabling ACPI solved this issue on almost all machines; however, recently I had to deal with some machines with usb3, and on some of them I observed the behaviour I described before. Now I'm aware that this is not the typical usage scenario of a linux system, and I'm also aware that another option to get things working in real mode again would be trying to re-configure (or reset) the hardware after kexec; but this is not a trivial thing to do; for me it would be easiest to have xhci working without ACPI. That's why I was asking. Thanks and best regards, Christian -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
