Comment 144 for bug 1453298
Revision history for this message
|
|
#144 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f399f05
demo site
(Get the code!)
(In reply to Andy Furniss from comment #81)
<snip>
> Recently needed to re-locate and while doing so updated to 4.1.10 = hard
> lock after 7 days uptime. The kernel was not the only difference as I
> attached a usb printer and so have usb module and cups running now, though
> the printer had been off for days when it locked.
>
> Anyway I am back on 4.1.1 now (with printer) and will have to see how long
> it lasts to be sure whether the kernel or the printer (or the move!) was the
> cause.
Still up OK after 20 days back on 4.1.1.
Strange that 4.1.10 seems to be a regression, there don't seem to be any obvious power related i915 commits between the two. Though as I am headless I am not getting and i915 interrupts anyway, which makes me thing that there is some different CPU/IO related regression. In all the testing I did before when using GPU I never locked by just stressing CPU/IO until maybe just before I stopped testing when I could get "make modules_install" to reliably lock (as noted in a previous comment).