linux-kernel - RE: Possible CPU_IDLE bug [WAS: Re: Timer unstability on when using C2 and deeper sleep states (Dell Latitude XT)]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <7E82351C108FA840AB1866AC776AEC460945BB44@orsmsx505.amr.corp.intel.com>
Date:	Wed, 13 Aug 2008 11:14:48 -0700
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Milan Plzik <milan.plzik@...il.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: Possible CPU_IDLE bug [WAS: Re: Timer unstability on when using
 C2	and deeper sleep states (Dell Latitude XT)]



>-----Original Message-----
>From: linux-kernel-owner@...r.kernel.org
>[mailto:linux-kernel-owner@...r.kernel.org] On Behalf Of Milan Plzik
>Sent: Wednesday, August 13, 2008 7:16 AM
>To: linux-kernel@...r.kernel.org
>Subject: Possible CPU_IDLE bug [WAS: Re: Timer unstability on
>when using C2 and deeper sleep states (Dell Latitude XT)]
>
>  Hello again,
>
>On St, 2008-08-13 at 12:58 +0200, Milan Plzik wrote:
>> I apologize for replying on my own mail (and also for
>top-posting, but
>> this information is global update, not exactly fitting any of topics
>> mentioned below).
>>
>>   After playing for a longer while I found out that the system ends
>> sometimes in state where, in order to do anything useful, I need to
>> press keys on keyboard. Otherwise, the system just stalls and does
>> nothing. I have no idea why does this happen (especially when I know
>> that OHCI or wireless network adapter produce fair amount of
>> interrupts). My /proc/interrupts is below. Just for the record,
>> chipset
>> on board is ATI RS600 with (apparently from lspci) ATI SB600
>> southbridge.
>
>  it looks like this problem disappears if CONFIG_CPU_IDLE option is
>disabled, system seems to be stable for more than one hour. This
>suggests that something may be wrong with the CPU_IDLE code. I can not
>spend much more time by debugging the kernel, but if anyone has an
>suggestion about what to fix, I will gladly test it.
>
>  Best regards,
>        Milan Plzik

It may not be a problem with cpuidle code per se. We have had issues earlier like this one

http://bugzilla.kernel.org/show_bug.cgi?id=10011

Cpuidle tries to go to C3 state aggressively and thus may be indirectly causing the problem with graphics hardware or something like that.

>From Dave's comment in the above bugzilla:
can you try with Option "DRI" "Off" in your xorg.conf

Does that change anything?

Thanks,
Venki
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/