Comment 477 for bug 500069
Revision history for this message
|
|
#477 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
Bob, (In reply to comment #316)
> This absolutely cannot be an ext3 bug. I'm using reiserfs for my root, and
> it
> happens here too. System totally locks up with a swap storm when memory
> pressure starts forcing things into swap. Firefox using > 2GB memory, and a
> wine memory bug which causes it to report ~4GB VIRT are what triggers it for
> me. Killing either one fixes the storm. (which is often not possible
> because
> keyboard/mouse are unresponsive) Machine has 4GB RAM, 4GB swap.
>
> It must be in the block layer, or elsewhere.
>
> It also seems to happen with swap *off*.
Bob, what exact symptoms are you seeing? There is another issue in the kernel, to which I have been unable to reproduce for the kernel devs. I have seen it numerous times where the kernel has "futex" deadlocks. It is potentially possible that yours could be related to that.
Because this performance problem, in this bug, does not cause a complete lockup. It may seem that way for a bit, but if you leave the machine, it will eventually recover. The futex one appears to be a complete deadlock, as it doesn't appear that it matters how long I leave it, it will never recover.