Difference between revisions of "Bug Tracking"
From Ultibo.org
| Line 9: | Line 9: | ||
! style="text-align:left;"| Description | ! style="text-align:left;"| Description | ||
! style="text-align:left;"| Status | ! style="text-align:left;"| Status | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|- | |- | ||
| Line 56: | Line 50: | ||
| Connecting 2 low speed devices to the same hub results in one of them failing. Does not affect full or high speed devices or devices on different hubs. | | Connecting 2 low speed devices to the same hub results in one of them failing. Does not affect full or high speed devices or devices on different hubs. | ||
| Resolved in 1.3.327 | | Resolved in 1.3.327 | ||
| + | |||
| + | |- | ||
| + | | DNS | ||
| + | | High | ||
| + | | Deadlock between DNS lookup and DNS flush due to timing. | ||
| + | | Resolved in 2.5.211 | ||
|} | |} | ||
Revision as of 22:26, 1 November 2022
This is a temporary record of current issues pending a permanent bug tracking mechanism
Current bugs
| Item | Priority | Description | Status |
|---|---|---|---|
| USB | High | Raspberry Pi official Keyboard/Hub not working when directly connected to Pi A+/Zero/Zero2W. | Under investigation |
Resolved bugs
| Item | Priority | Description | Status |
|---|---|---|---|
| Boot | Critical | Occasional boot failures that appear to be caused by deadlocks due to timing. | Resolved in 1.2.089 |
| TCP | Critical | Socket timer not handling high volume incoming data correctly. Affects Shell Update module with random failures. | Resolved in 1.2.047 |
| Console | High | Very occasional deadlocks during console scroll. Suspected to be DMA related but hard to reproduce. | Resolved in 1.3.077 |
| USB | High | Connecting 2 low speed devices to the same hub results in one of them failing. Does not affect full or high speed devices or devices on different hubs. | Resolved in 1.3.327 |
| DNS | High | Deadlock between DNS lookup and DNS flush due to timing. | Resolved in 2.5.211 |
