Regression - with v10.182 USB worked - with v10.183 USB do not work

[Robert Blair]

With v10.183 USB devices plugged in at boot work will work. If USB devices were not plugged in at boot and later plugged in they do not work. If USB devices are plugged in at boot and are later unplugged and then plugged back in they do not work.

[Lars Erdmann]

run pci.exe -D and attach output
run trace for USBUHCD.SYS,USBEHCD.SYS,USBOHCD.SYS as necessary (see readme.txt) and attach output

[Robert Blair]

USB183_1.ftf no USB devices pluggeg in at boot then plugged in memory stick it did not work.

USB183_2.ftf memory stick plugged in at boot it worked correctly.

[Lars Erdmann]

Try voyage.zip.

[Robert Blair]

Using voyage.zip.

Trace USB183_3.ftf, nothing connected at boot. Tried mouse, keyboard, and memory stick and none of the worked.

Trace USB183_4.ftf, mouse, keyboard, and memory stick plugged in at boot. All devices worked. Unplugged all devices and plugged them back in, none worked.

[Lars Erdmann]

Try the new version. Beware: make sure you use the one with note "Enabling asynchronous schedule after HC reset".

[Robert Blair]

Using the new voyage.zip.

Trace USB183_5.ftf, nothing connected at boot. Tried mouse, keyboard, and memory stick and none of them worked.

Trace USB183_6.ftf, mouse, keyboard, and memory stick plugged in at boot. All devices worked. Unplugged all devices and plugged them back in, none worked.

[Lars Erdmann]

Try new voyage.zip. For the time being: use USBD.SYS version 10.162 (the one that came with eComStation).

[Robert Blair]

Using the new voyage.zip and USBD.SYS version "IBM 10.162".

Trace USB183_7.ftf, nothing connected at boot. Tried mouse, keyboard, and memory stick and none of them worked.

Trace USB183_8.ftf, mouse, keyboard, and memory stick plugged in at boot. All devices worked. Unplugged all devices and plugged them back in, none worked.

[Lars Erdmann]

Try updated voyage.zip. This time:

1) first, try with USBUHCD.SYS only. The best would be if you temporarily disabled USB 2.0 through BIOS. Check if the devices will then properly attach or not. Take a trace for major code 224 (USBUHCD.SYS) only.

2) if that works, add USBEHCD.SYS. Now, take a trace for major codes 224 and 226.

I think it will be enough if you only do the "attach/detach devices after boot" test case.

[Robert Blair]

I can enable/disable "USB Support" and enable/disable "Front USB Ports" (I assume the "Front USB Ports" are USB2 ports). For this test "USB Support" was enabled and "Front USB Ports" was disabled.

REMed out USBEHCD.SYS and only traced 224.

Using the new voyage.zip.

Trace USB183_9.ftf, nothing connected at boot. Tried mouse and keyboard and none of them worked.

Trace USB183_10.ftf, mouse and keyboard plugged in at boot. All devices worked. Unplugged all devices and plugged them back in, none worked.

[Lars Erdmann]

1) No, all of your USB ports are both: USB 1.x and USB 2.0. There is an automatism that will tie either USBUHCD.SYS or USBEHCD.SYS to a specific port, depending on if the plugged in device is a USB 1.x or a USB 2.0 device. "Disable front USB ports" means just that: your USB front ports will be plain "dead".

2) Did you have USBEHCD.SYS commented out in both cases ? If yes, you should at least get USB keyboard and mouse to properly attach and detach. Unfortunately, I produced too much trace info for USBUHCD.SYS. I have now reduced that. Please redo the trace with USBUHCD.SYS ONLY (and only trace 224). Sorry for the hassle. But I need to find out why the devices do not attach at all. That is very odd.

[Lars Erdmann]

By the way: if your system is a desktop system: please completely power down your system (with the switch on the back). I have had issues on my system where only a complete power down would help.

[Lars Erdmann]

retry with updated zip. For the time being, REM out USBEHCD.SYS from config.sys.
First we need to be USBUHCD.SYS to operate properly. Trace 224 as usual.

[Robert Blair]

Using the latest voyage.zip.

REMed out USBEHCD.SYS in config.sys and only traced 224.

Powered off/on the system.

Trace USB183_11.ftf, nothing connected at boot. Tried mouse and keyboard and they did not work.

Powered off/on the system.

Trace USB183_12.ftf, mouse and keyboard plugged in at boot. All devices worked. Unplugged all devices and plugged them back in they did not work.

[Lars Erdmann]

1) you said that it also does not work with the original IBM drivers, correct ? 2) have you tried all on all 8 ports that you have ? If you have no devices attached on bootup, I cannot see even a device attach which should be the minimum. Please try all 8 ports. 3) If you have devices attached on boot, I CAN see device attach on 2 different ports. Have you tried these very same 2 ports when you attached the devices later on ?

[Robert Blair]

Using the same version of voyage.zip as the last test.

Powered off/on the system before each test.

REMed out USBEHCD.SYS in config.sys and only traced 224.

1) you said that it also does not work with the original IBM drivers, correct ?

All drivers are what was installed by eCS v2.0 except for what you supply.

2) have you tried all on all 8 ports that you have ? If you have no devices attached on bootup, I cannot see even a device attach which should be the minimum. Please try all 8 ports.

I don't know if I have used all 8 ports but I do try to use different ports for each test.

Trace USB183_13.ftf, nothing connected at boot. Plugged in keyboard in all 8 ports, it did not work in any of them. Then I plugged in the mouse in all 8 ports, it did not work in any port.

3) If you have devices attached on boot, I CAN see device attach on 2 different ports. Have you tried these very same 2 ports when you attached the devices later on ?

Normally I use a different port when I unplug and then plug a device back in.

Trace USB183_14.ftf, mouse and keyboard plugged at boot, both worked. Unplugged both and plugged them into the same port, neither worked.

[Lars Erdmann]

No, what I meant was: did you also have problems with USBUHCD.SYS 10.162 (that one that came with eComStatio) ?
In any case, try updated driver.

[Lars Erdmann]

By the way: do you have legacy BIOS support, that is, can you use USB mouse /keyboard in your BIOS for example ?
Also from now on, try USBUHCD.SYS only, then add USBEHCD.SYS and try again and see if that makes a difference. You only need to take one trace for each test case (only try to attach devices after system start).

[Robert Blair]

This is an IBM Think Centre M51 computer, the first version of eCS installed on this computer was eCS 2.0, USB did not work at all, it would not recognize any USB device, I tried memory sticks, USB hard drives, a keyboard, and a mouse or two. Up until USBHCD179 no functional USB. Installing 179 everything started working. I then installed USBHCD181 and I was back to having non functional USB. I went back to 179. USB worked again after installing USBHCD182. After installing USBHCD183 I am back to a non functional USB.

Legacy BIOS support is disabled. The computer is connected through a KVM switch which has OS/2 connectors.

Powered off/on the system before each test.

Trace USB183_15.ftf, after boot plugged in mouse and keyboard, neither worked. Only using USBUHCD and tracing only 224.

Trace USB183_16.ftf, after boot plugged in mouse and keyboard, neither worked. Using USBUHCD and USBEHCD and tracing both 224 and 226.

[Lars Erdmann]

Can you attach the USB devices directly to the computer and see if that makes a difference ?
You might also want to try and toggle between Legacy BIOS support on/off and see if that makes a difference.
From the trace log it looks like the USB ports are plain dead. I cannot see any reaction on device attach. As a test I can revert the one change I made for USBEHCD.SYS between 10.182 and 10.183. But I cannot revert back permanently because 10.182 will not work for other people (for known reasons).

[Lars Erdmann]

Retry with updated zip. Replace both, USBUHCD.SYS and USBEHCD.SYS

[Robert Blair]

The KVM switch has PS/2 connectors and the mouse and keyboard connected to the switch have PS/2 connectors so has nothing to do with any USB devices.

For all of the tests USB devices are plugged directly into USB ports on the computer.

I have tried Legacy BIOS support both enabled/disabled and there is no difference in how USB devices work, currently disabled.

USB works correctly in Windows and with your updates USBHCD179 and USBHCD182.

Using the latest voyager.zip.

Trace USB183_17.ftf, after boot plugged in mouse and keyboard, neither worked. Tracing both 224 and 226.

[Lars Erdmann]

Have you ever tried WITHOUT tracing enabled ? I suspect this problem to be a timing issue. From 10.182 to 10.183 I added additional trace points. Maybe that makes all the difference.
If you DO NOT enable tracing, these additional tracepoints won't matter (it's more or less a no-op). However, if tracing is enabled, the trace points will add noticeable delay which might disrupt the timing.

[Lars Erdmann]

By the way: I understand that really you are using PS/2 mouse and keyboard. This DOES matter as the USB legacy support needs to emulate a USB mouse/keyboard to appear as a PS/2 mouse/keyboard and therefore there is some HW connection between USB and the real PS/2 HW (keyboard controller).
As a test, can you disconnect all PS/2 devices from the computer in question and then retry device attache/detach with USB mouse/keyboard ?
If this works ok, I will need to rework the handoff from legacy USB support to native USB support instead of what I am fiddling with right now.

[Robert Blair]

Trace off. No difference in how the USB devices worked.

Power off/on, USB mouse and keyboard plugged in after boot. Neither USB devices worked.

Power off/on, USB mouse and keyboard plugged in at boot. Both USB devices worked, unplugged the keyboard and mouse and plugged them back in, they did not work.

Switching from USBHCD182 to the latest voyager.zip I did notice that if I did not do the power off/on with the keyboard and mouse plugged in at boot the keyboard worked but the mouse did not work.

More traces later removing the PS/2 keyboard and mouse.

[Robert Blair]

Test with no PS/2 keyboard or mouse plugged in. The USB keyboard must be plugged in or the system will not boot. Powered off/on between each test.

The following were done with "USB Legacy" enabled.

Trace USB183_18.ftf. Boot with both USB keyboard and mouse plugged in, both worked.

Trace USB183_19.ftf. Boot with both USB keyboard and mouse plugged in, both worked. Unplugged USB mouse and plugged it back in, the mouse did not work.

Trace USB183_20.ftf. USB keyborad plugged in at boot, it works. After boot plugged in USB mouse and it did not work.

The following were done with "USB Legacy" disabled.

Trace USB183_21.ftf. Boot with both USB keyboard and mouse plugged in, both worked. Unplugged USB mouse and plugged it back in, the mouse did not work.

Trace USB183_22.ftf. USB keyborad plugged in at boot, it works. After boot plugged in USB mouse and it did not work.

[Lars Erdmann]

please retry with updated .zip. Since it does not seem to make a difference if "USB Legacy" is enabled or not and likewise for PS/2 devices attached or not you can take trace the way you normally operate your system.

[Robert Blair]

Testing with "USB Legacy" disabled and a PS/2 keyboard and mouse plugged in. Powered off/on before each test.

Trace USB183_23.ftf, after boot plugged in USB mouse and keyboard, neither worked.

Trace USB183_24.ftf. Boot with both USB keyboard and mouse plugged in, both worked. Unplugged USB keyboard and mouse and plugged them back in, neither worked.

[Lars Erdmann]

Try updated zip.

[Robert Blair]

Powered off/on before each test.

Trace USB183_26.ftf, after boot plugged in USB mouse and keyboard, neither worked.

Trace USB183_25.ftf. Boot with both USB keyboard and mouse plugged in, both worked. Unplugged USB keyboard and mouse and plugged them back in, neither worked.

[Lars Erdmann]

Sorry but I can see no device attaches/detaches whatsoever. Therefore I cannot help as the system looks as if it is plain dead even though all ports are powered. Maybe you can run Windows and get the USB ports working that way.

[Lars Erdmann]

By the way: did you recently install a new ACPI ? Was IBMKBD.SYS replaced ?

Please do a:
bldlevel c:\os2\boot\ibmkbd.sys
and post result. Maybe you need to backlevel to the one that came with original eComStation.

[Lars Erdmann]

Try updated zip (file date USBEHCD.SYS: 5/14/2012)

[Robert Blair]

I start Windows and plug in USB mouse/keyboard/memory stick all USB devices work. If I then reboot to eCS and plug in USB mouse/keyboard/memory stick none of the USB devices work, so booting Windows first does not help the USB devices work.

Booting eCS and plugging in the USB memory stick only it does not work. The USB memory stick works if plugged in at boot.

Added BASEDEV=IBMKBD.SYS /NONE same results as above. If USB memory stick is plugged in at boot it works with or without the "/NONE" parameter.

I have not changed this eCS system except for updating the USB device drivers.

Update voyage.zip

Trace USB183_27.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

Trace USB183_28.ftf USB mouse/keyboard/memory stick plugged in at boot they all worked. Unplugged and plugged them back in and they did not work.

[Lars Erdmann]

Retry with new zip. If it does not work try these (and report results):
1) move USBEHCD.SYS BEFORE any USBUHCD.SYS in config.sys
2) disable tracing

As always, take trace.

[Robert Blair]

USBEHCD.SYS after USBUHCD.SYS.

Trace USB183_29.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

Trace USB183_30.ftf USB mouse/keyboard/memory stick plugged in at boot they all worked. Unplugged and plugged them back in and they did not work.

USBEHCD.SYS before USBUHCD.SYS.

Trace USB183_31.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

Trace USB183_32.ftf USB mouse/keyboard/memory stick plugged in at boot they all worked. Unplugged and plugged them back in and they did not work.

Turned off trace. USBEHCD.SYS before USBUHCD.SYS.

USB mouse/keyboard/memory stick plugged in after boot none worked.

USB mouse/keyboard/memory stick plugged in at boot they all worked. Unplugged and plugged them back in and they did not work.

[Lars Erdmann]

please take trace with new zip. I added additional tracing to see if I ever get device attach/detach interrupts or not. It's enough to take trace only when you attach devices after boot. Just attach/detach device a couple of times.

[Lars Erdmann]

I have updated again. As a test I have removed some code that I think is wrong.
In case it works with this latest version, please hang on because I will need to find the correct solution to what it is intended to do.

[Robert Blair]

USBEHCD.SYS after USBUHCD.SYS.

Trace USB183_33.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

Please try updated zip. Make sure you update USBEHCD and USBUHCD (if you don't do that already).

[Robert Blair]

Trace USB183_34.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

Please retry with updated zip.

[Lars Erdmann]

I have updated again. Please retry.

[Lars Erdmann]

And yet again an update.

[Robert Blair]

Trace USB183_35.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

Please comment out USBUHCD.SYS and try with USBEHCD.SYS only.
Also, on a command line do a "rmview.exe /IRQ >irq.txt" and attach irq.txt here.

[Lars Erdmann]

please retry with new zip. If it works: It's only a test I will need to find the real solution.

[Robert Blair]

Commented out all USBUHCD.SYS statements.

Trace USB183_36.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

Updated USB drivers using the latest voyager.zip.

Trace USB183_37.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

Ran rmview /IRQ >irq.txt

[Lars Erdmann]

Please retry updated zip but I have little hope: it seems that the IRQ for the EHCI controller never fires:
1) what version of ACPI are you using ? Use latest version 3.20.1.
2) try ACPI with other flags, for example /VW.
3) you can add back in USBUHCD.SYS. But try OTHER USB ports for device attach/detach, not only the front ports.

[Lars Erdmann]

added more tracing to see if interrupt ever fires for EHCI.

[Robert Blair]

Updated ACPI to version 3.20.1.

Trace USB183_38.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

Added the parameter /VW to ACPI.

Trace USB183_39.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

Are you sure your USB ports are enabled in BIOS ? Enable "USB front ports" and then please try all ports, front/back.
I can say this: the IRQ fires but it is shared with one of the UHCI drivers. And I can say that the EHCI driver did NOT trigger the interrupt. Therefore the UHCI driver did. But that does not help as the EHCI driver has to get it first.

[Robert Blair]

Using your drivers USBHCD179.ZIP or USBHCD182.ZIP all USB ports work for all USB devices I have which are a mouse, keyboard, and memory stick. I also have an external USB disk drive which works but that I do not use during my testing.

Other than your drivers USBHCD179.ZIP or USBHCD182.ZIP all other drivers fail to work using eCS v2.0.

[Lars Erdmann]

Ok, I just wanted to be sure. Find updated drivers. Please try and take trace.

[Robert Blair]

No parameters on the ACPI.PSD statement.

Trace USB183_40.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

try updated zip.

[Robert Blair]

Trace USB183_41.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

See Lenovo website:

​http://support.lenovo.com/en_US/detail.page?LegacyDocID=MIGR-60598

version 2BKT51A

•Fixes a highly intermittent problem with handing USB ownership to the OS. The user sees many different types of hangs.

Could you make sure that you update the BIOS at least to that version ?

[Robert Blair]

The BIOS shows "Flash EEPROM Revision Level 2BKT53AUS".

[Lars Erdmann]

Ok, BIOS version is ok then.

Try updated zip.
Also,REM USBEHCD.SYS from config.sys and check if you can get USB mouse and keyboard to work (with USBUHCD.SYS only).
Additionally, turn trace off and check if it makes a difference. I just want to be sure that tracing does not have a negative impact.
Report on these 3 combinations (USBEHCD+USBUHCD with tracing, USBUHCD only with tracing, USBUHCD without tracing).

By the way: do you have problems with other devices (sound, network, whatever) ?

[Robert Blair]

USBEHCD+USBUHCD

Trace USB183_42.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

USBUHCD only

Trace USB183_43.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

Trace OFF

USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

can you specify in config.sys:

BASEDEV=USBEHCD.SYS /V /FS /S:1

and see if it makes a difference ?

[Lars Erdmann]

Try updated zip. Please try with and without the /S:1 switch.

[Robert Blair]

Added /S:1 to BASEDEV=USBEHCD.SYS /V /FS /S:1

Trace USB183_44.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

Removed /S:1 from BASEDEV=USBEHCD.SYS /V /FS

Trace USB183_45.ftf USB mouse/keyboard/memory stick plugged in after boot none worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

[Lars Erdmann]

try the updated .zip.
When you do the tests, in addition to your normal tests, please also have devices plugged in on bootup (as you did in the past) and also try with tracing disabled. For these cases you do not need to trace. I just need a "it works/it doesn't work" answer.

[Lars Erdmann]

Do you have Theseus installed ? If not:
​http://www.os2site.com/sw/util/memory/thes4001.exe

You need to run this self-extracting file to any directory you like.

It's a tool that allows you to investigate about everything in your system. We might need it to check how memory is mapped.

[Robert Blair]

USB mouse/keyboard/memory stick plugged in at boot all worked. Unplugged USB mouse/keyboard/memory stick and plugged them back into the same port, none worked.

USB mouse/keyboard/memory stick plugged in after boot none worked.

All tests were done with trace on and off.

I have now installed Theseus

[Lars Erdmann]

Please take trace when you have devices plugged in on boot. I need to check something.

[Lars Erdmann]

Tool for dumping MTRR regs.

[Lars Erdmann]

please run tool accmtrr.exe as such:

accmtrr.exe -l mtrrdump.txt

and upload file "mtrrdump.txt".
Also, run:

rmview.exe /mem > mem.txt

and upload file "mem.txt"

[Robert Blair]

Trace USB183_46.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

This trace is too big to upload so I split it in two parts. USB183_46A.ftf first part USB183_46B.ftf second part

[Robert Blair]

Trace USB183_47.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

If a USB device is plugged in at boot and later unplugged and then plugged back in it does not work. This is not in this trace.

[Lars Erdmann]

please test with updated zip and take trace with devices plugged in on boot and without devices plugged in on boot but later.

[Robert Blair]

Trace USB183_48.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

Trace USB183_49.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

[Lars Erdmann]

Can you please again download the zip ? I had updated it and you may have potentially pulled an old version. If that still does not work I am going to upload under a different name.

[Lars Erdmann]

USBEHCD: reset configure flag before HC reset + set wakeup flags on all ports + move intr. enable right before HC start

[Lars Erdmann]

I have again uploaded. This time I added the date to the filename.

[Robert Blair]

Using voyage_2012_06_15.zip.

Trace USB183_50.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

Trace USB183_51.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

[Lars Erdmann]

USBEHCD: set configure flag immediately after resetting HC

[Lars Erdmann]

please retry with latest zip.

[Robert Blair]

Using voyage_2012_06_16.zip.

Trace USB183_52.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

Trace USB183_53.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

[Lars Erdmann]

USBEHCD: move setting config flag after HC RUN, add wait after run, add wait after setting config flag

[Lars Erdmann]

try updated zip.

[Lars Erdmann]

USBEHCD: in irq routine, if status flag = 0, scan for port status change in each port reg

[Lars Erdmann]

try also this updated zip.

[Robert Blair]

Using voyage_2012_06_19.zip.

Trace USB183_54.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

Trace USB183_55.ftf USB mouse/keyboard/memory stick plugged in after boot none worked.

---

Using voyage_2012_06_19_2.zip.

Trace USB183_56.ftf USB mouse/keyboard/memory stick plugged in at boot all worked.

Trace USB183_57.ftf USB mouse/keyboard/memory stick plugged in after boot all worked.

---

After trace 57 (so were not traced) I unplugged all USB devices and plugged them back in the same or different USB port and they all worked.

[Lars Erdmann]

Ok. Your hardware has a HW flaw. I have now established a workaround to work around the problem (but the workaround is going to stay for good). I would like to change yet something else.
If you please would retest that version once I have uploaded it here.

[Lars Erdmann]

USBEHCD: ultimate check

[Lars Erdmann]

Please do a final check. Make sure you also replace the USBUHCD.SYS with the version contained in the zip. If everything still works well I will freeze this version and rerelease the drivers.

[Robert Blair]

voyage_2012_06_20.zip works the same as voyage_2012_06_19_2.zip.

[Lars Erdmann]

fixed in 10.184