Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness

2011-05-24 Thread Sabahattin Gucukoglu
On 17 May 2011, at 04:05, Ben Hutchings wrote: Please report this bug upstream at https://bugzilla.kernel.org under product 'ACPI', component 'Other'. Include the information you've sent here - the logs from 2.6.32 and from 2.6.39-rc6, and the possible connection with brltty. Let us know the

Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness

2011-05-15 Thread Sabahattin Gucukoglu
On Thu, 12 May 2011, Ben Hutchings wrote: On Wed, 2011-05-11 at 22:55 +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually

Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness

2011-05-14 Thread Sabahattin Gucukoglu
On 12 May 2011, at 01:43, Ben Hutchings wrote: On Wed, 2011-05-11 at 22:55 +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually

Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness

2011-05-12 Thread Sabahattin Gucukoglu
On 11 May 2011, at 23:54, maximilian attems wrote: On Wed, May 11, 2011 at 10:55:13PM +0100, Sabahattin Gucukoglu wrote: Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text

Bug#626427: linux-image-2.6.38-2-686: Horrible Time Skew, Eventual Near-zero Responsiveness

2011-05-11 Thread Sabahattin Gucukoglu
Package: linux-2.6 Version: 2.6.38-5 Severity: important (reportbug script died, hope you've got everything.) The machine runs with *HORRIBLE* clock drift (see text). Eventually, the system will slow right down, so that new processes or threads will not start. It *seems* to be related to the