Re: 2.6.14-git3: scheduling while atomic from cpufreq on Athlon64

From: Andrew Morton (akpm_at_osdl.org)
Date: 10/31/05

  • Next message: Rafael J. Wysocki: "Re: [PATCH 2/3] swsusp: move snapshot-handling functions to snapshot.c" 
    Date:	Mon, 31 Oct 2005 11:34:13 -0800
To: "Rafael J. Wysocki" <rjw@sisk.pl>

    "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
    >
    > Hi,
    >
    > I'm getting some "scheduling while atomic" messages from 2.6.14-git3 on boot
    > and on suspend/resume, eg.:
    >
    > NET: Registered protocol family 1
    > powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.50.4)
    > powernow-k8: 0 : fid 0x0 (800 MHz), vid 0x12 (1100 mV)
    > powernow-k8: 1 : fid 0x8 (1600 MHz), vid 0x6 (1400 mV)
    > powernow-k8: 2 : fid 0xa (1800 MHz), vid 0x2 (1500 mV)
    > cpu_init done, current fid 0xa, vid 0x2
    > scheduling while atomic: swapper/0x00000001/1
    >
    > Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff80163576>{poison_obj+70}
    > <ffffffff801be269>{sysfs_new_dirent+41} <ffffffff80162989>{dbg_redzone1+25}
    > <ffffffff801be269>{sysfs_new_dirent+41} <ffffffff80163908>{cache_alloc_debugcheck_after+280}
    > <ffffffff8011cf1b>{powernowk8_target+139} <ffffffff80162989>{dbg_redzone1+25}
    > <ffffffff802e0830>{cpufreq_stat_notifier_policy+304}
    > <ffffffff802dfdb4>{__cpufreq_driver_target+116} <ffffffff801be269>{sysfs_new_dirent+41}
    > <ffffffff802e097e>{cpufreq_governor_performance+62}
    > <ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df3a8>{__cpufreq_set_policy+440}
    > <ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
    > <ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
    > <ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
    > <ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
    > <ffffffff8010f54e>{child_rip+0}
    > scheduling while atomic: swapper/0x00000001/1
    >
    > Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
    > <ffffffff8011d60c>{powernowk8_target+1916} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
    > <ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
    > <ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df3a8>{__cpufreq_set_policy+440}
    > <ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
    > <ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
    > <ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
    > <ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
    > <ffffffff8010f54e>{child_rip+0}
    > input: AT Translated Set 2 keyboard//class/input as input1
    > scheduling while atomic: swapper/0x00000001/1
    >
    > Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
    > <ffffffff8011cf1b>{powernowk8_target+139} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
    > <ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
    > <ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df417>{__cpufreq_set_policy+551}
    > <ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
    > <ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
    > <ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
    > <ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
    > <ffffffff8010f54e>{child_rip+0}
    > scheduling while atomic: swapper/0x00000001/1
    >
    > Call Trace:<ffffffff8035014a>{schedule+122} <ffffffff802e2453>{cpufreq_frequency_table_target+371}
    > <ffffffff8011d60c>{powernowk8_target+1916} <ffffffff802dfdb4>{__cpufreq_driver_target+116}
    > <ffffffff801be269>{sysfs_new_dirent+41} <ffffffff802e097e>{cpufreq_governor_performance+62}
    > <ffffffff802dec8d>{__cpufreq_governor+173} <ffffffff802df417>{__cpufreq_set_policy+551}
    > <ffffffff802df5bf>{cpufreq_set_policy+79} <ffffffff802df946>{cpufreq_add_dev+806}
    > <ffffffff802df540>{handle_update+0} <ffffffff802ae21a>{sysdev_driver_register+170}
    > <ffffffff802df106>{cpufreq_register_driver+198} <ffffffff8010c122>{init+194}
    > <ffffffff8010f556>{child_rip+8} <ffffffff8010c060>{init+0}
    > <ffffffff8010f54e>{child_rip+0}

    Well I can't find it. Ingo, didn't you have a debug patch which would help
    us identify where this atomic section started?

    > Additionally there are some problems with freezing processes by swsusp.

    More details on this?
    -
    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/

  • Next message: Rafael J. Wysocki: "Re: [PATCH 2/3] swsusp: move snapshot-handling functions to snapshot.c"

    Relevant Pages