Bug#499198: linux-image-2.6.26-1-amd64: complete system freeze
On Wed, Sep 9, 2009 at 21:00, Moritz Muehlenhoff <jmm@inutil.org> wrote:
> On Sun, Sep 21, 2008 at 04:34:15PM +0200, Sandro Tosi wrote:
>> Hello Maximilian,
>> I'm not quite happy with your downgrade of #499198 to important since
>> this (together with #499046 and #498328) is a clear regretion from
>> 2.6.25 and caused my data loss (hence it qualifies for severity
>> grave).
>>
>> I'm on
>>
>> $ uname -a
>> Linux zion 2.6.25-2-amd64 #1 SMP Mon Jul 14 11:05:23 UTC 2008 x86_64 GNU/Linux
>>
>> since more than 4 days, and none of the above problem ever happened:
>>
>> - the system runs fine, without any "mtrr: type mismatch", partial
>> freeze (#499046) or complete freeze (#499198)
>> - when typing, there are not char repetition or strange behavior (#498328)
>> - I'm running since 1day the long-running task mentioned in (#498328)
>> and it's using 100% of all 4 cores, without me even noticing it.
>>
>> At last: those are all important bug and I believe #499198 to be RC.
>>
>> I renew my willing to help you, just tell me how; but if the only
>> interaction you want to have with my bugs is via control server to
>> downgrade their severity, then I'll find other way to let my concerns
>> be known.
>
> What is the status?
well, I don't know, you tell me :)
> Does this still affect the final Lenny kernel?
>
> Did you try a more recent kernel from backports.org?
I don't know and I didn't try the backport kernel:
- on my machine I jump to 2.6.30 quite a long ago
- on servers at work, while running lenny kernel (at last point
release), I don't face this problem (either because I access trhu ssh,
they don't have X, different/specific hardware).
I don't know what to do with this report, probably you can close it
(even though the note about not "brutally" downgrade still applies).
Cheers,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Reply to: