Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755722AbXKRW1V (ORCPT ); Sun, 18 Nov 2007 17:27:21 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752885AbXKRW1L (ORCPT ); Sun, 18 Nov 2007 17:27:11 -0500 Received: from an-out-0708.google.com ([209.85.132.244]:3203 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752570AbXKRW1K (ORCPT ); Sun, 18 Nov 2007 17:27:10 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:content-type:content-transfer-encoding; b=X/zKnQ92KiVuzvhH4CwN0wQtYRYY+d21zTSDWA6A39JN6DduJZMmeklpbW29AWtSSnMjrnzInxmv4TndQx9/rrrlyMd+wEJ3QZyCzdkPyTBeuMQsh82OYwbHje8cBxDNK840rZq+wyotV0t6lOfU0oQ+n5lXZXRzB3Nk8dB551Q= Message-ID: <4740BC36.2070200@gmail.com> Date: Sun, 18 Nov 2007 23:27:02 +0100 From: Jiri Slaby User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Alan Stern CC: "Rafael J. Wysocki" , Andrew Morton , Greg KH , Kernel development list , Linux-pm mailing list , r.marek@assembler.cz, lm-sensors@lm-sensors.org Subject: Re: broken suspend [Was: 2.6.24-rc2-mm1] References: <47408DFF.9070701@gmail.com> In-Reply-To: <47408DFF.9070701@gmail.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2056 Lines: 56 Aah, we probably should let coretemp people known. Whole thread: http://marc.info/?t=119507205800001&r=1&w=2 On 11/18/2007 08:09 PM, Jiri Slaby wrote: > On 11/18/2007 06:07 PM, Alan Stern wrote: >> You'll get more useful results if you redo your changes to >> notifier_call_chain(). Have it print out the address of the routine >> _before_ making the call, and don't limit it to 20. That way you'll >> know exactly which notifier routine ends up hanging. > > The problem is, that notifier_call_chain is called again and again zillion times > by somebody else... > > Anyway you led me to another idea: > * _cpu_down > printk("%s: u\n", __func__); > BUBAK=1; > /* CPU is completely dead: tell everyone. Too late to complain. */ > if (raw_notifier_call_chain(&cpu_chain, CPU_DEAD | 0x88000 | mod, > hcpu) == NOTIFY_BAD) > BUG(); > BUBAK=0; > ----- > * notifier_call_chain > unsigned int a = val & 0x88000; > unsigned int yes = a == 0x88000; > > nb = rcu_dereference(*nl); > > if (a && a != 0x88000) > printk("Somebody calls with val: %lx\n", val); > else > val &= ~0x88000; > > while (nb && nr_to_call) { > next_nb = rcu_dereference(nb->next); > if (unlikely(BUBAK && yes)) > printk("%s: %p\n", __func__, nb->notifier_call); > ret = nb->notifier_call(nb, val, v); > ----- > gives coretemp_cpu_callback -> coretemp_device_remove -> > platform_device_unregister, so coretemp seems to be what I have and you don't. Just in case you are curious: http://www.fi.muni.cz/~xslaby/sklad/susp_hang3.diff produces: http://www.fi.muni.cz/~xslaby/sklad/susp_hang3.png - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/