Opened 18 years ago
Closed 18 years ago
#955 closed bug (fixed)
Haiku wont respond if you boot it with mouse action
Reported by: | diver | Owned by: | marcusoverhagen |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | - General | Version: | R1/pre-alpha1 |
Keywords: | Cc: | mmlr, axeld | |
Blocked By: | Blocking: | ||
Platform: | All |
Description
Haiku wont respond if you boot it moving mouse around. When it boots, everything locks: time (seconds) in deskbar doesn't change, mouse doesn't work. If you stop to move your mouse, two seconds later haiku will alive.
Attachments (1)
Change History (10)
comment:1 by , 18 years ago
Cc: | added |
---|
comment:2 by , 18 years ago
Cc: | added |
---|---|
Summary: | [PS/2] Haiku wont respond if you boot it with mouse action → Haiku wont respond if you boot it with mouse action |
I think it's more likely a problem of USB, please attach a syslog or serial debug log.
comment:3 by , 18 years ago
Cc: | added |
---|---|
Owner: | changed from | to
Diver please attach a syslog or serial debug log.
I couldn't reproduce the behaviour and would like to close this bug.
comment:4 by , 18 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
comment:5 by , 18 years ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
Ok, i could now reproduce it in vmware with hrev19802. Reopening, syslog will follow
follow-up: 7 comment:6 by , 18 years ago
Moving the mouse during boot does trigger sending (in this case) 13200 debug messages from interrupt context directly after the mouse is enabled, before the thread executing ps2_dev_command gets scheduled again and can set the enable flag.
The code responsible for that is:
status = ps2_dev_command(dev, PS2_CMD_ENABLE, NULL, 0, NULL, 0); if (status < B_OK) { TRACE(("mouse_open(): cannot enable PS/2 mouse\n")); goto err4; } atomic_or(&dev->flags, PS2_FLAG_ENABLED);
Please don't move the mouse during boot.
comment:7 by , 18 years ago
Replying to marcusoverhagen:
Moving the mouse during boot does trigger sending (in this case) 13200 debug messages from interrupt context directly after the mouse is enabled, before the thread executing ps2_dev_command gets scheduled again and can set the enable flag.
The code responsible for that is:
status = ps2_dev_command(dev, PS2_CMD_ENABLE, NULL, 0, NULL, 0); if (status < B_OK) { TRACE(("mouse_open(): cannot enable PS/2 mouse\n")); goto err4; } atomic_or(&dev->flags, PS2_FLAG_ENABLED);Please don't move the mouse during boot.
Can't we disable or at least reduce the debug output of the ps2 driver ? Or it's still too early to do that ?
This sounds like a problem of the PS/2 driver (probably a real time thread going nuts or some interrupt problem) - do you have any idea Marcus?