On Mon, Mar 18, 2013 at 10:07 PM, Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: > On Mon, Mar 18, 2013 at 10:00:32PM -0600, Shuah Khan wrote: >> On Mon, Mar 18, 2013 at 8:00 PM, Greg Kroah-Hartman >> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> > On Mon, Mar 18, 2013 at 07:09:11PM -0600, Shuah Khan wrote: >> >> On Mon, Mar 18, 2013 at 6:57 PM, Greg Kroah-Hartman >> >> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> >> > On Mon, Mar 18, 2013 at 06:51:37PM -0600, Shuah Khan wrote: >> >> >> On Mon, Mar 18, 2013 at 3:06 PM, Greg Kroah-Hartman >> >> >> <gregkh@xxxxxxxxxxxxxxxxxxx> wrote: >> >> >> > This is the start of the stable review cycle for the 3.8.4 release. >> >> >> > There are 75 patches in this series, all will be posted as a response >> >> >> > to this one. If anyone has any issues with these being applied, please >> >> >> > let me know. >> >> >> > >> >> >> > Responses should be made by Wed Mar 20 21:04:55 UTC 2013. >> >> >> > Anything received after that time might be too late. >> >> >> > >> >> >> > The whole patch series can be found in one patch at: >> >> >> > kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.8.4-rc1.gz >> >> >> > and the diffstat can be found below. >> >> >> > >> >> >> > thanks, >> >> >> > >> >> >> > greg k-h >> >> >> > >> >> >> >> >> >> Here is the warn from 3.8.4-rc1 >> >> >> [ 700.009112] Component: resume devices, time: 10004 >> >> >> [ 700.009204] Modules linked in: ip6table_filter ip6_tables >> >> >> ebtable_nat ebtables nf_conntrack_ipv4 nf_defrag_ipv4 xt_state >> >> >> nf_conntrack ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp >> >> >> iptable_filter ip_tables x_tables bridge stp llc bnep rfcomm bluetooth >> >> >> arc4 iwldvm snd_hda_codec_analog radeon snd_hda_intel mac80211 >> >> >> coretemp snd_hda_codec kvm_intel kvm snd_hwdep binfmt_misc snd_pcm >> >> >> snd_seq_midi iwlwifi snd_rawmidi ttm snd_seq_midi_event cfg80211 >> >> >> drm_kms_helper pata_pcmcia snd_seq tpm_infineon drm psmouse snd_timer >> >> >> joydev pcmcia snd_seq_device snd yenta_socket tpm_tis microcode >> >> >> pcmcia_rsrc pcmcia_core ppdev dm_multipath i2c_algo_bit video hp_wmi >> >> >> mac_hid sparse_keymap serio_raw soundcore snd_page_alloc lpc_ich wmi >> >> >> hp_accel lis3lv02d input_polldev parport_pc lp parport firewire_ohci >> >> >> sdhci_pci sdhci firewire_core crc_itu_t e1000e >> >> >> [ 700.009212] Pid: 2637, comm: bash Not tainted 3.8.4-rc1+ #8 >> >> > >> >> > Do you get this same warning on 3.9-rc3? >> >> > >> >> > I thought I got all of the needed fixes for this warning, what am I >> >> > missing here? >> >> > >> >> > thanks, >> >> > >> >> > greg k-h >> >> >> >> I think this is a new one. You did pull in the two patches you needed. >> >> I am getting ready to test it in 3.9.0-rc1. Will let you know in a >> >> bit. I have to do a git pull for the latest and do a compile. >> > >> > Please try 3.9-rc3, -rc1 didn't have the original patch that caused the >> > warning to show up in it. >> > >> > thanks, >> > >> > greg k-h >> >> Seeing the same on 3.9-rc3. I reverted the three commits and re-ran >> the test, still see the same warnings. From what I can tell, this >> warning on my test system has nothing to do with these commits. >> >> 6c4d3bc99b3341067775efd4d9d13cc8e655fd7c >> 2a6e06b2aed6995af401dcd4feb5e79a0c7ea554 >> 1d9d8639c063caf6efc2447f5f26aa637f844ff6 > > Good to know, thanks for testing. > >> With this warning resolved to be an existing condition on my test >> system, 3.0.70-rc1, 3.4.37-rc1, and 3.8.4-rc1 booted on both my test >> systems and cross-compile tests passed. dmesgs look good and no >> regressions from the previous round. >> >> Please let me know if I should do the revert test on 3.0.70-rc1, >> 3.4.37-rc1, and 3.8.4-rc1. I can get to that tomorrow. > > Does 3.8.3 show the same warning? That would be the easiest thing to > test. > > thanks, > > greg k-h Easier than I thought it would be. I thought I removed the older releases and turns out still have them installed. 3.8.3, 3.4.36, and 3.0.69 show the the same warning after resume on my system. -- Shuah -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html