Bug#600846: The problem also exists in 2.6.32-27 version of linux-image-2.6.32-5-amd64 package.
On Tue, Nov 02, 2010 at 04:29:10PM +0100, email@example.com wrote:
> As far as I remember there was no good 2.6.32-XX linux-image which
> didn't show
> the error - all of them did.
> If my memory serves me well the last good kernel that didn't show the
> error was
> 2.6.30-1 , and the error came up in 2.6.30-2 . (If you want I could test
> this kernel version
> again on my system - just tell me how to add a valid public key so that
> synaptic accepts
> the snapshot repository).
oh well you probably mean abi number above and not version number,
so the regression is really old and most probably either due to
switch to libata or to KMS intel drivers.
in that case it be more useful to know if newer linux-2.6 is fixed,
by any chance tried anything newer from experimental?
current 2.6.36 linux-image installs just fine in testing.
can you reproduce it there?
> The problem is that I did not make any notes about this - I didn't
> intend to write
> a bug report at this time but expected the problem to vanish anyway with
> the update
> next week or so (but it didn't - for a lot of weeks now).
> So I am not sure about all of this - not even if the problem is caused
> by the kernel or by
> another component like Xserver or KDE - I must leave it to you linux
> professionals to
> make this decision.
> The only thing I am sure about is that every second or third
> Suspend-To-RAM hangs.
I see, thanks a lot for the quick responsiveness.
P.S.: please keep bug report on cc, to keep record of it, thanks.
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org