Modify ↓
Opened 10 years ago
Closed 10 years ago
#248 closed defect (fixed)
Metaticket for 0xffffffff problem
| Reported by: | Suren A. Chilingaryan | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | UFO Camera | Version: | |
| Keywords: | Cc: | Matthias Balzer, Suren A. Chilingaryan, Lorenzo Rota, Michele Caselle |
Description
Michele reports that HEB hardware goes into the 0xffffffff state on some hardware, mostly camera stations, while it is working fine on his PC. The problem is triggered by re-enumerating hardware / reloading the driver.
This is meta-ticket to track all problems resulting in the 0xffffffff state. When the specific problem is identified we will open a stand-alone tickets.
Attachments (0)
Change History (2)
comment:1 Changed 10 years ago by
comment:2 Changed 10 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Note: See
TracTickets for help on using
tickets.
![(please configure the [header_logo] section in trac.ini)](/ufo/chrome/site/your_project_logo.png)
So far, I am unable to reproduce 0xffffffff problem on camera2 (Nicolas computer). I left it overnight reloading the PCI device, but it is still running fine. I think it is either
1) Camera2 is unaffected by the problem and Nicolas 0xffffffff are coming from different problems in his code. To be sure, I can check other systems where you have seen the similar problem.
2) The more complex scenario is required to trigger problem. In this case, we need to collect more information about condition when problem happened (last pci commands/scripts, the hardware status, something else?).