#1207 Mouse driver hangs on init 2.3.7 , 2.4 , 2.4.2

fixed_in_SVN
closed
5
2014-11-02
2009-12-11
dos386
No

Inside BOCHS when initializing a mouse driver (CTMOUSE 2.1b4 with or without "-O" switch
as well as LogiTech driver), it "hangs" in "some" random cases (probability 2/5 ???).

Hanging includes longer (2x ?) delay in the driver initialization, keyboard not working then
in the command prompt (sometimes chars appear on the screen after a VERY long time
(1 minute ?), and I/O not working either.

00197146104i[BIOS ] no PCI device with class code 0x0101fa found at index 0
00197155857i[BIOS ] no PCI device with class code 0x0101f0 found at index 0
00197165636i[BIOS ] no PCI device with class code 0x01018a found at index 0
00203389748i[KBD ] wheel mouse mode request rejected
00203456366i[BIOS ] KBD: int09h_handler(): unknown scancode read: 0x61!
00207602078i[FDD ] controller reset in software
00211666536i[FDD ] controller reset in software
00215731039i[FDD ] controller reset in software
00219795497i[FDD ] controller reset in software
00223860000i[FDD ] controller reset in software
00227924471i[FDD ] controller reset in software
00231988974i[FDD ] controller reset in software
00236053432i[FDD ] controller reset in software
00240117935i[FDD ] controller reset in software
00244182393i[FDD ] controller reset in software
00248246869i[FDD ] controller reset in software
00252311349i[FDD ] controller reset in software
00256375862i[FDD ] controller reset in software
00260440335i[FDD ] controller reset in software
00264504803i[FDD ] controller reset in software


00037480137i[KBD ] wheel mouse mode request rejected
00041638810i[FDD ] controller reset in software
00045703313i[FDD ] controller reset in software
00049767771i[FDD ] controller reset in software
00053832274i[FDD ] controller reset in software
00057896777i[FDD ] controller reset in software
00061961248i[FDD ] controller reset in software
00066025731i[FDD ] controller reset in software
00070090205i[FDD ] controller reset in software
00074154675i[FDD ] controller reset in software
00078219193i[FDD ] controller reset in software
00092829357i[FDD ] controller reset in software
00096893815i[FDD ] controller reset in software
00100958318i[FDD ] controller reset in software
00105022776i[FDD ] controller reset in software
00109087279i[FDD ] controller reset in software
00113151745i[FDD ] controller reset in software
00117216248i[FDD ] controller reset in software
00121280706i[FDD ] controller reset in software
00125345209i[FDD ] controller reset in software
00129409667i[FDD ] controller reset in software
00133474187i[FDD ] controller reset in software
00137538645i[FDD ] controller reset in software
00141603148i[FDD ] controller reset in software
00145667606i[FDD ] controller reset in software
00149732109i[FDD ] controller reset in software
00153796575i[FDD ] controller reset in software
00157861078i[FDD ] controller reset in software
00161925536i[FDD ] controller reset in software
00165990039i[FDD ] controller reset in software
00170054497i[FDD ] controller reset in software

The lines "KBD: int09h_handler(): unknown scancode read: 0x61!" and "00207602078i[FDD ] controller reset in
software" are evil, they occur in the debug report if it "hangs", otherwise they don't. Also "keyboard buffer full"
complaints can occur.

If the driver passes its initialization successfully, no further trouble occurs, and mouse works well.

Rebooting from inside BOCHS (not restarting it on the host) brings a new "chance" to hang.

Discussion

  • dos386
    dos386
    2009-12-13

    http://freefile.kristopherw.us/uploads/temp/bochsbug.zi7 (165 KiB)

    Floppy image to reproduce this BUG. Actually, the behavior tends to repeat itself (OK -> OK -> OK or HANG -> HANG -> HANG), so it's a pain to test, and, I couldn't reproduce it without XDMA so far, but no final idea whether XDMA is really necessary to reproduce. But XDMA itself ALWAYS fails inside BOCHS (works on most PC's, though). Also, the "hang" occurs even if "mouse: enabled=0".

     
  • What are the strange BIOS images you use ?

    romimage: file="B242BIO"
    vgaromimage: file="B242VGA"

    Stanislav

     
  • dos386
    dos386
    2009-12-13

    What are the strange BIOS images you use ?

    Those included in the package. I had already found out that using any other images (like those from previous version) can cause nothing except trouble, for example BIOS from 2.4 used with 2.4.2 TripleFaults on WRMSR instruction ;-)

     
  • Volker Ruppert
    Volker Ruppert
    2014-11-02

    • status: open --> closed
    • assigned_to: Volker Ruppert
    • Group: --> fixed_in_SVN
     
  • Volker Ruppert
    Volker Ruppert
    2014-11-02

    The CTMOUSE issues are fixed in SVN.