Opened 14 years ago
Closed 14 years ago
#68 closed defect (fixed)
Tracer locks up keyboard
| Reported by: | Jiri Svoboda | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 0.4.1 |
| Component: | Version: | mainline | |
| Keywords: | udebug trace hang | Cc: | |
| Blocker for: | Depends on: | ||
| See also: |
Description
In the current trunk revision trying to trace a task (use +s so that you actually get some events) causes the keyboard to stop responding. The cursor still blinks and the heartbeat indicator moves so perhaps only the keyboard driver or part of the console server is locked up and the rest of the system is okay.
Change History (2)
comment:1 Changed 14 years ago by
comment:2 Changed 14 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
The problem was that cons_write() in the console server was waiting for data over IPC while holding the async serialization lock. Fixed in r4352.
Note: See
TracTickets for help on using
tickets.
When I add a hook directly to the keyboard driver to switch me to kcon upon pressing a key, it works. This means that the keyboard driver is OK, fb is probably OK too, only the console server seems to be stuck.