Comment 22 for bug 270798
Revision history for this message
| Petter Eklund (denbevingadebaevern) wrote | #22 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Further investigations and testing indicate that the boot-option noapic provides an usable workaround. I've had the affected computer running with that boot-option for several hours, leaving it unattended with programs that I usually had running when the lockup occured for quite a while (this would usually trigger a lockup) and so far it seems like it is gone.