Hello Ken,
Am 09.02.2016 um 20:42 schrieb Ken Moffat:
> On Tue, Feb 09, 2016 at 05:03:57PM +0100, Karsten Malcher wrote:
>
>> I have to found out that freezing can occur under kernel 3.2 too, but far
>> less common.
>> So the interesting question is why in newer kernels this will occur very
>>
Hello Ken,
Am 09.02.2016 um 20:42 schrieb Ken Moffat:
> On Tue, Feb 09, 2016 at 05:03:57PM +0100, Karsten Malcher wrote:
>
>> I have to found out that freezing can occur under kernel 3.2 too, but far
>> less common.
>> So the interesting question is why in newer kernels this will occur very
>>
I have to found out that freezing can occur under kernel 3.2 too, but far less
common.
So the interesting question is why in newer kernels this will occur very often?
I could found a solution for the problem in the linked Blog.
When you disable Cool' n' Quiet the system is running stable with
Hello Ken,
thank you for the answer!
> On uncommon hardware, anything is possible. I don't actually know
> if that hardware is "uncommon", only that I do not have it.
Before i start to debug the kernel versions i tried to find other problem
reportings for this mainboard.
And i found them!
Hello Ken,
thank you for the answer!
> On uncommon hardware, anything is possible. I don't actually know
> if that hardware is "uncommon", only that I do not have it.
Before i start to debug the kernel versions i tried to find other problem
reportings for this mainboard.
And i found them!
I have to found out that freezing can occur under kernel 3.2 too, but far less
common.
So the interesting question is why in newer kernels this will occur very often?
I could found a solution for the problem in the linked Blog.
When you disable Cool' n' Quiet the system is running stable with
On Mon, Feb 08, 2016 at 07:08:09PM +0100, Karsten Malcher wrote:
> Hello,
>
> i am sorry, but is it possible that a kernel bug for a special chipset is
> alive since kernel 3.2?
>
On uncommon hardware, anything is possible. I don't actually know
if that hardware is "uncommon", only that I do
Hello,
i am sorry, but is it possible that a kernel bug for a special chipset is alive
since kernel 3.2?
I have a backup PC with an Asrock ALiveXFire eSATA2 R3.0 mainboard with CPU
AMD64 X2 6000+.
Before this mainboard runs very stable with Debian wheezy and kernel 3.2.0.
Now i tried to update
On Mon, Feb 08, 2016 at 07:08:09PM +0100, Karsten Malcher wrote:
> Hello,
>
> i am sorry, but is it possible that a kernel bug for a special chipset is
> alive since kernel 3.2?
>
On uncommon hardware, anything is possible. I don't actually know
if that hardware is "uncommon", only that I do
Hello,
i am sorry, but is it possible that a kernel bug for a special chipset is alive
since kernel 3.2?
I have a backup PC with an Asrock ALiveXFire eSATA2 R3.0 mainboard with CPU
AMD64 X2 6000+.
Before this mainboard runs very stable with Debian wheezy and kernel 3.2.0.
Now i tried to update
10 matches
Mail list logo
