Bug #124
Spinlock breakpoint in PhysicalMemoryManager::allocatePage
| Status: | Closed | Start: | 08/27/2010 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | 10/28/2010 | |
| Assigned to: |  Matthew Iselin |
% Done: | 100% |
|
| Category: | Kernel | Spent time: | 3.00 hours | |
| Target version: | Foster Post-Release Milestone #1 | Estimated time: | 8.00 hours |
Description
Throws a fatal error due to interrupts being enabled when release() is called, which is incorrect.
History
Updated by Matthew Iselin about 1 year ago
Possibly an OOM error - we need to figure out how to handle OOM errors more gracefully! Kill a process or something, but this has been a recurring issue for a while now.
Updated by Matthew Iselin about 1 year ago
- Status changed from New to Closed
- Assigned to set to Matthew Iselin
- % Done changed from 0 to 100
Side-effect of UnlikelyLock doing exciting things with interrupts. Fixed - but a breakpoint will still come up, this time saying something along the lines of "Out of physical memory". Give the VM some more RAM.