Re: linux-next: Tree for Jan 18 (objtool: 2 warnings)

[Josh Poimboeuf]

On Mon, Jan 18, 2021 at 09:16:14AM -0800, Randy Dunlap wrote:
> On 1/17/21 10:48 PM, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20210115:
> > 
> 
> on x86_64:
> 
> lib/iov_iter.o: warning: objtool: iovec_from_user()+0x157: call to 
> __ubsan_handle_add_overflow() with UACCESS enabled
> fs/select.o: warning: objtool: do_sys_poll()+0x669: call to 
> __ubsan_handle_sub_overflow() with UACCESS enabled

Under discussion:

  
https://lkml.kernel.org/r/590998aa9cc50f431343f76cae72b2abf8ac1fdd.1608699683.git.jpoim...@redhat.com

-- 
Josh

Re: linux-next: Tree for Jan 18 (objtool: 2 warnings)

[Randy Dunlap]

On 1/17/21 10:48 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20210115:
> 

on x86_64:

lib/iov_iter.o: warning: objtool: iovec_from_user()+0x157: call to 
__ubsan_handle_add_overflow() with UACCESS enabled
fs/select.o: warning: objtool: do_sys_poll()+0x669: call to 
__ubsan_handle_sub_overflow() with UACCESS enabled


Full randconfig file is attached.

-- 
~Randy
You can't do anything without having to do something else first.
-- Belefant's Law


config-r7251.gz
Description: application/gzip

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20210115:

New trees: oprofile-removal gpio-brgl-fixes

The drm tree gained a conflict against Linus' tree but still had its
build failure so I used the version from next-20210107.

The amdgpu tree lost its build failure.

The drm-intel tree still had its build failure from merging the drm tree,
so I have used the version from next-20210108.

The tip tree lost its build failure.

The scsi-mkp tree gained a conflict against the scsi-fixes tree.

The kspp tree gained a conflict against the mips tree.

I still reverted a commit from the iomem-mmap-vs-gup tree that caused
a boot failure on PowerPC.

The oprofile-removal tree gained a build failure for which I applied
a patch.

Non-merge commits (relative to Linus' tree): 3623
 3948 files changed, 148349 insertions(+), 78579 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig and htmldocs. And finally, a simple boot test
of the powerpc pseries_le_defconfig kernel in qemu (with and without
kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 333 trees (counting Linus' and 86 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (e2da783614bb Merge tag 'perf-tools-fixes-2021-01-17' of 
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux)
Merging fixes/fixes (e71ba9452f0b Linux 5.11-rc2)
Merging kbuild-current/fixes (0bc9bc1d8b2f Merge tag 'ext4_for_linus_stable' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4)
Merging arc-current/for-curr (7c53f6b671f4 Linux 5.11-rc3)
Merging arm-current/fixes (e64ab473ddda ARM: 9034/1: __div64_32(): straighten 
up inline asm constraints)
Merging arm64-fixes/for-next/fixes (3a57a643a851 arm64: selftests: Fix spelling 
of 'Mismatch')
Merging arm-soc-fixes/arm/fixes (8a996b2d8a03 ARM: dts: ux500: Reserve memory 
carveouts)
Merging drivers-memory-fixes/fixes (5c8fe583cce5 Linux 5.11-rc1)
Merging m68k-current/for-linus (2ae92e8b9b7e MAINTAINERS: Update m68k Mac entry)
Merging powerpc-fixes/fixes (41131a5e54ae powerpc/vdso: Fix 
clock_gettime_fallback for vdso32)
Merging s390-fixes/fixes (a1a322a62dba s390/vfio-ap: clean up vfio_ap resources 
when KVM pointer invalidated)
Merging sparc/master (0a95a6d1a4cd sparc: use for_each_child_of_node() macro)
Merging fscrypt-current/for-stable (d19d8d345eec fscrypt: fix inline encryption 
not used on new files)
Merging net/master (66c556025d68 skbuff: back tiny skbs with kmalloc() in 
__netdev_alloc_skb() too)
Merging bpf/master (e23a8d002198 Merge 
https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf)
Merging ipsec/master (da64ae2d35d3 xfrm: Fix wraparound in 
xfrm_policy_addr_delta())
Merging netfilter/master (c8a8ead01736 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/pablo/nf)
Merging ipvs/master (869f4fdaf4ca netfilter: nf_nat: Fix memleak in nf_nat_init)
Merging wireless-drivers/master (a6616bc9a0af iwlwifi: dbg: Don't touch the tlv 
data)
Merging mac80211/master (c13cf5c15966 mac80211: check if atf has been disabled 
in __ieee80211_schedule_txq)
Merging rdma-fixes/for-rc (7c7b3e5d9aee RDMA/cma: Fix error flow in 
default_roce_mode_store)
Merging sound-current/for-linus (f84d3a1ec375 ALSA: hda: Add Cometlake-R PCI ID)
Merging sound-asoc-fixes/for-linus (7505c06dabb5 MAINTAINERS: update qcom ASoC 
drivers list)
Merging regmap-fixes/for-linus (7c53f6b671f4 Linux 5.11-rc3)
Merging regulator-fixes/for-linus (09db7311ca61 Merge v5.11-rc3)
Merging spi-fixes/for-linus (4d163ad79b15 spi: cadence: cache reference 

Re: linux-next: Tree for Jan 18 (i2c-designware-platdrv.c)

[Jarkko Nikula]

Hi

On 1/18/19 6:27 PM, Randy Dunlap wrote:

On 1/17/19 8:24 PM, Stephen Rothwell wrote:

Hi all,

Changes since 20190117:



on i386 or x86_64:

ld: drivers/i2c/busses/i2c-designware-platdrv.o: in function 
`dw_i2c_plat_resume':
i2c-designware-platdrv.c:(.text+0x4b): undefined reference to 
`i2c_dw_prepare_clk'
ld: drivers/i2c/busses/i2c-designware-platdrv.o: in function 
`dw_i2c_plat_suspend':
i2c-designware-platdrv.c:(.text+0x95): undefined reference to 
`i2c_dw_prepare_clk'
ld: drivers/i2c/busses/i2c-designware-platdrv.o: in function 
`dw_i2c_plat_probe':
i2c-designware-platdrv.c:(.text+0x63f): undefined reference to 
`i2c_dw_prepare_clk'
ld: i2c-designware-platdrv.c:(.text+0x686): undefined reference to 
`i2c_dw_read_comp_param'
ld: i2c-designware-platdrv.c:(.text+0x7b7): undefined reference to 
`i2c_dw_probe_slave'
ld: i2c-designware-platdrv.c:(.text+0x7c1): undefined reference to 
`i2c_dw_probe'


probably related to:

WARNING: unmet direct dependencies detected for I2C_DESIGNWARE_PLATFORM
   Depends on [n]: I2C [=y] && HAS_IOMEM [=y] && (ACPI [=y] && COMMON_CLK [=n] 
|| !ACPI [=y])
   Selected by [y]:
   - MFD_TPS68470 [=y] && HAS_IOMEM [=y] && ACPI [=y] && I2C [=y]=y

Thanks, this is due CONFIG_MFD_TPS68470 which selects the 
I2C_DESIGNWARE_PLATFORM but not the dependencies. There are two others 
in drivers/mfd/Kconfig. I'll send a patch changing them to depend on 
I2C_DESIGNWARE_PLATFORM=y.


--
Jarkko

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20190117:

The arc-current tree gained a conflict against Linus' tree.

The vfs tree still had its build failure for which I applied a patch.

The mali-dp tree still had its failure for which I applied a merge
fix patch.

The imx-drm tree gained a build failure for which I reverted a commit.

Non-merge commits (relative to Linus' tree): 2439
 2664 files changed, 79722 insertions(+), 38102 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 295 trees (counting Linus' and 69 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (a3a80255d58d Merge tag 'afs-fixes-20190117' of 
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs)
Merging fixes/master (0ce4e20ca4ea x86/syscalls: Mark expected switch 
fall-throughs)
Merging kbuild-current/fixes (e00d88804814 kbuild: mark prepare0 as PHONY to 
fix external module build)
Merging arc-current/for-curr (51769fabee34 ARCv2: lib: memeset: fix doing 
prefetchw outside of buffer)
CONFLICT (content): Merge conflict in arch/arc/mm/fault.c
Merging arm-current/fixes (c2a3831df6dc ARM: 8816/1: dma-mapping: fix potential 
uninitialized return)
Merging arm64-fixes/for-next/fixes (7fa1e2e6afa7 kasan, arm64: remove redundant 
ARCH_SLAB_MINALIGN define)
Merging m68k-current/for-linus (bed1369f5190 m68k: Fix memblock-related crashes)
Merging powerpc-fixes/fixes (7bea7ac0ca01 powerpc/syscalls: Fix syscall tracing)
Merging sparc/master (b71acb0e3721 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (cb12d72b27a6 atm: he: fix sign-extension overflow on large 
shift)
Merging bpf/master (c61c27687a5a bpf: Correctly annotate implicit fall through 
in bpf_base_func_proto)
Merging ipsec/master (e2612cd496e7 xfrm: Make set-mark default behavior 
backward compatible)
Merging netfilter/master (80b3671e9377 ip6_gre: update version related info 
when changing link)
Merging ipvs/master (feb9f55c33e5 netfilter: nft_dynset: allow dynamic updates 
of non-anonymous set)
Merging wireless-drivers/master (ec5aecc0b227 iwlwifi: make IWLWIFI depend on 
CFG80211)
Merging mac80211/master (1d51b4b1d3f2 Merge tag 'm68k-for-v4.20-tag2' of 
git://git.kernel.org/pub/scm/linux/kernel/git/geert/linux-m68k)
Merging rdma-fixes/for-rc (d6f4a21f309d RDMA/uverbs: Mark ioctl responses with 
UVERBS_ATTR_F_VALID_OUTPUT)
Merging sound-current/for-linus (687ae9e287b3 ASoC: intel: skl: Fix display 
power regression)
Merging sound-asoc-fixes/for-linus (f06f20da6565 Merge branch 'asoc-5.0' into 
asoc-linus)
Merging regmap-fixes/for-linus (b3ffce399349 Merge branch 'regmap-5.0' into 
regmap-linus)
Merging regulator-fixes/for-linus (b4c4aa249eff Merge branch 'regulator-5.0' 
into regulator-linus)
Merging spi-fixes/for-linus (601ea15da77b Merge branch 'spi-5.0' into spi-linus)
Merging pci-current/for-linus (d2fd6e81912a PCI: Fix __initdata issue with 
"pci=disable_acs_redir" parameter)
Merging driver-core.current/driver-core-linus (1c7fc5cbc339 Linux 5.0-rc2)
Merging tty.current/tty-linus (1c7fc5cbc339 Linux 5.0-rc2)
Merging usb.current/usb-linus (1c7fc5cbc339 Linux 5.0-rc2)
Merging usb-gadget-fixes/fixes (87b6d2c56825 usb: dwc2: gadget: Fix Remote 
Wakeup interrupt bit clearing)

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20180117:

The powerpc tree gained a conflict against the powerpc-fixes tree.

The f2fs tree gained a build failure due to an interaction with the
btrfs tree for which I reverted a commit.

The net-next tree gained a conflict against the net tree.

Non-merge commits (relative to Linus' tree): 9595
 9650 files changed, 397215 insertions(+), 259560 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 256 trees (counting Linus' and 44 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (88dc7fca1800 Merge branch 'x86-pti-for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip)
Merging fixes/master (820bf5c419e4 Merge tag 'scsi-fixes' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (8bbfbc2df6e9 ARCv2: cache: fix slc_entire_op: 
flush only instead of flush-n-inv)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (5e387199c17c m68k/defconfig: Update defconfigs 
for v4.14-rc7)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (1b689a95ce74 powerpc/pseries: include 
linux/types.h in asm/hvcall.h)
Merging sparc/master (59585b4be9ae sparc64: repair calling incorrect hweight 
function from stubs)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (0b1655143df0 r8152: disable RX aggregation on Dell TB16 
dock)
Merging bpf/master (f37a8cb84cce bpf: reject stores into ctx via st and xadd)
Merging ipsec/master (76a420119181 xfrm: Fix a race in the xdst pcpu cache.)
Merging netfilter/master (889c604fd0b5 netfilter: x_tables: fix int overflow in 
xt_alloc_table_info())
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (cc124d5cc8d8 brcmfmac: fix CLM load error for 
legacy chips when user helper is enabled)
Merging mac80211/master (59b179b48ce2 cfg80211: check dev_set_name() return 
value)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (b3defb791b26 ALSA: seq: Make ioctls race-free)
Merging pci-current/for-linus (d6c1efecd1e1 x86/PCI: Enable AMD 64-bit window 
on resume)
Merging driver-core.current/driver-core-linus (30a7acd57389 Linux 4.15-rc6)
Merging tty.current/tty-linus (30a7acd57389 Linux 4.15-rc6)
Merging usb.current/usb-linus (a8750ddca918 Linux 4.15-rc8)
Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7)
Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new 
device ID ELV ALC 8xxx)
Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: 
fix ulpi-node lookup)
Merging phy/fixes (2b88212c4cc6 phy: rcar-gen3-usb2: select USB_COMMON)
Merging staging.current/staging-linus (a8750ddca918 Linux 4.15-rc8)
Merging char-misc.current/char-misc-linus (a8750ddca918 Linux 4.15-rc8)
Merging input-current/for-linus (4d94e776bd29 Input: ALPS - fix multi-touch 
decoding on SS4 plus touchpads)
Merging crypto-current/master (9a00674213a3 crypto: algapi - fix NULL 
dereference in crypto_remove_spawns())
Merging ide/master 

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20180117:

The powerpc tree gained a conflict against the powerpc-fixes tree.

The f2fs tree gained a build failure due to an interaction with the
btrfs tree for which I reverted a commit.

The net-next tree gained a conflict against the net tree.

Non-merge commits (relative to Linus' tree): 9595
 9650 files changed, 397215 insertions(+), 259560 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
multi_v7_defconfig for arm and a native build of tools/perf. After
the final fixups (if any), I do an x86_64 modules_install followed by
builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
and sparc64 defconfig. And finally, a simple boot test of the powerpc
pseries_le_defconfig kernel in qemu (with and without kvm enabled).

Below is a summary of the state of the merge.

I am currently merging 256 trees (counting Linus' and 44 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (88dc7fca1800 Merge branch 'x86-pti-for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip)
Merging fixes/master (820bf5c419e4 Merge tag 'scsi-fixes' of 
git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi)
Merging kbuild-current/fixes (36c1681678b5 genksyms: drop *.hash.c from 
.gitignore)
Merging arc-current/for-curr (8bbfbc2df6e9 ARCv2: cache: fix slc_entire_op: 
flush only instead of flush-n-inv)
Merging arm-current/fixes (091f02483df7 ARM: net: bpf: clarify tail_call index)
Merging m68k-current/for-linus (5e387199c17c m68k/defconfig: Update defconfigs 
for v4.14-rc7)
Merging metag-fixes/fixes (b884a190afce metag/usercopy: Add missing fixups)
Merging powerpc-fixes/fixes (1b689a95ce74 powerpc/pseries: include 
linux/types.h in asm/hvcall.h)
Merging sparc/master (59585b4be9ae sparc64: repair calling incorrect hweight 
function from stubs)
Merging fscrypt-current/for-stable (ae64f9bd1d36 Linux 4.15-rc2)
Merging net/master (0b1655143df0 r8152: disable RX aggregation on Dell TB16 
dock)
Merging bpf/master (f37a8cb84cce bpf: reject stores into ctx via st and xadd)
Merging ipsec/master (76a420119181 xfrm: Fix a race in the xdst pcpu cache.)
Merging netfilter/master (889c604fd0b5 netfilter: x_tables: fix int overflow in 
xt_alloc_table_info())
Merging ipvs/master (f7fb77fc1235 netfilter: nft_compat: check extension hook 
mask only if set)
Merging wireless-drivers/master (cc124d5cc8d8 brcmfmac: fix CLM load error for 
legacy chips when user helper is enabled)
Merging mac80211/master (59b179b48ce2 cfg80211: check dev_set_name() return 
value)
Merging rdma-fixes/for-rc (ae59c3f0b6cf RDMA/mlx5: Fix out-of-bound access 
while querying AH)
Merging sound-current/for-linus (b3defb791b26 ALSA: seq: Make ioctls race-free)
Merging pci-current/for-linus (d6c1efecd1e1 x86/PCI: Enable AMD 64-bit window 
on resume)
Merging driver-core.current/driver-core-linus (30a7acd57389 Linux 4.15-rc6)
Merging tty.current/tty-linus (30a7acd57389 Linux 4.15-rc6)
Merging usb.current/usb-linus (a8750ddca918 Linux 4.15-rc8)
Merging usb-gadget-fixes/fixes (b2cd1df66037 Linux 4.15-rc7)
Merging usb-serial-fixes/usb-linus (d14ac576d10f USB: serial: cp210x: add new 
device ID ELV ALC 8xxx)
Merging usb-chipidea-fixes/ci-for-usb-stable (964728f9f407 USB: chipidea: msm: 
fix ulpi-node lookup)
Merging phy/fixes (2b88212c4cc6 phy: rcar-gen3-usb2: select USB_COMMON)
Merging staging.current/staging-linus (a8750ddca918 Linux 4.15-rc8)
Merging char-misc.current/char-misc-linus (a8750ddca918 Linux 4.15-rc8)
Merging input-current/for-linus (4d94e776bd29 Input: ALPS - fix multi-touch 
decoding on SS4 plus touchpads)
Merging crypto-current/master (9a00674213a3 crypto: algapi - fix NULL 
dereference in crypto_remove_spawns())
Merging ide/master 

Re: linux-next: Tree for Jan 18

[Ard Biesheuvel]

On 18 January 2017 at 20:44, Paul Gortmaker
 wrote:
> On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> Changes since 20170117:
>>
>> The arm-soc tree gained a conflict against the arm tree.
>>
>> The amlogic tree gained a conflict against the arm-soc tree.
>>
>> Non-merge commits (relative to Linus' tree): 3676
>>  4511 files changed, 139928 insertions(+), 85028 deletions(-)
>
> Crypto now fails on arm allmodconfig:
>
> arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
> need binutils 2.23 or higher
> arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
> ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
>   AS [M]  arch/arm/crypto/aes-neonbs-core.o
>   CC [M]  arch/arm/crypto/aes-neonbs-glue.o
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler 
> messages:
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[0],r9'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[1],r8'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[0],r7'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[0],r9'
>
> [many more similar scalar errors deleted]
>
> The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
> an older binutils 2.22 from the kernel.org crosstool stuff.
>
> Seems sfr's builds get the same issue:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/
>
> A mindless "git bisect run" comes up with:
>
> cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
> commit cc477bf645736739e69d31fdf715281ef0dd5f9b
> Author: Ard Biesheuvel 
> Date:   Wed Jan 11 16:41:54 2017 +
>
> crypto: arm/aes - replace bit-sliced OpenSSL NEON code
>
> Maybe binnutils 2.22 is finally too old?
>

This fixes it for me

diff --git a/arch/arm/crypto/aes-neonbs-core.S
b/arch/arm/crypto/aes-neonbs-core.S
index c9477044fbba..12da247164d1 100644
--- a/arch/arm/crypto/aes-neonbs-core.S
+++ b/arch/arm/crypto/aes-neonbs-core.S
@@ -766,13 +766,13 @@ ENTRY(aesbs_cbc_decrypt)
 ENDPROC(aesbs_cbc_decrypt)

.macro  next_ctr, q
-   vmov\q\()h[1], r10
+   vmov.32 \q\()h[1], r10
addsr10, r10, #1
-   vmov\q\()h[0], r9
+   vmov.32 \q\()h[0], r9
adcsr9, r9, #0
-   vmov\q\()l[1], r8
+   vmov.32 \q\()l[1], r8
adcsr8, r8, #0
-   vmov\q\()l[0], r7
+   vmov.32 \q\()l[0], r7
adc r7, r7, #0
vrev32.8\q, \q
.endm

so I will propose this to Herbert as a followup patch.

Thanks,
Ard.

Re: linux-next: Tree for Jan 18

[Ard Biesheuvel]

On 18 January 2017 at 20:44, Paul Gortmaker
 wrote:
> On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> Changes since 20170117:
>>
>> The arm-soc tree gained a conflict against the arm tree.
>>
>> The amlogic tree gained a conflict against the arm-soc tree.
>>
>> Non-merge commits (relative to Linus' tree): 3676
>>  4511 files changed, 139928 insertions(+), 85028 deletions(-)
>
> Crypto now fails on arm allmodconfig:
>
> arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
> need binutils 2.23 or higher
> arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
> ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
>   AS [M]  arch/arm/crypto/aes-neonbs-core.o
>   CC [M]  arch/arm/crypto/aes-neonbs-glue.o
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler 
> messages:
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[0],r9'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[1],r8'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[0],r7'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[0],r9'
>
> [many more similar scalar errors deleted]
>
> The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
> an older binutils 2.22 from the kernel.org crosstool stuff.
>
> Seems sfr's builds get the same issue:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/
>
> A mindless "git bisect run" comes up with:
>
> cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
> commit cc477bf645736739e69d31fdf715281ef0dd5f9b
> Author: Ard Biesheuvel 
> Date:   Wed Jan 11 16:41:54 2017 +
>
> crypto: arm/aes - replace bit-sliced OpenSSL NEON code
>
> Maybe binnutils 2.22 is finally too old?
>

This fixes it for me

diff --git a/arch/arm/crypto/aes-neonbs-core.S
b/arch/arm/crypto/aes-neonbs-core.S
index c9477044fbba..12da247164d1 100644
--- a/arch/arm/crypto/aes-neonbs-core.S
+++ b/arch/arm/crypto/aes-neonbs-core.S
@@ -766,13 +766,13 @@ ENTRY(aesbs_cbc_decrypt)
 ENDPROC(aesbs_cbc_decrypt)

.macro  next_ctr, q
-   vmov\q\()h[1], r10
+   vmov.32 \q\()h[1], r10
addsr10, r10, #1
-   vmov\q\()h[0], r9
+   vmov.32 \q\()h[0], r9
adcsr9, r9, #0
-   vmov\q\()l[1], r8
+   vmov.32 \q\()l[1], r8
adcsr8, r8, #0
-   vmov\q\()l[0], r7
+   vmov.32 \q\()l[0], r7
adc r7, r7, #0
vrev32.8\q, \q
.endm

so I will propose this to Herbert as a followup patch.

Thanks,
Ard.

Re: linux-next: Tree for Jan 18

[Ard Biesheuvel]

(+ Arnd)

On 18 January 2017 at 20:44, Paul Gortmaker
 wrote:
> On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> Changes since 20170117:
>>
>> The arm-soc tree gained a conflict against the arm tree.
>>
>> The amlogic tree gained a conflict against the arm-soc tree.
>>
>> Non-merge commits (relative to Linus' tree): 3676
>>  4511 files changed, 139928 insertions(+), 85028 deletions(-)
>
> Crypto now fails on arm allmodconfig:
>
> arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
> need binutils 2.23 or higher
> arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
> ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
>   AS [M]  arch/arm/crypto/aes-neonbs-core.o
>   CC [M]  arch/arm/crypto/aes-neonbs-glue.o
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler 
> messages:
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[0],r9'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[1],r8'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[0],r7'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[0],r9'
>
> [many more similar scalar errors deleted]
>
> The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
> an older binutils 2.22 from the kernel.org crosstool stuff.
>
> Seems sfr's builds get the same issue:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/
>
> A mindless "git bisect run" comes up with:
>
> cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
> commit cc477bf645736739e69d31fdf715281ef0dd5f9b
> Author: Ard Biesheuvel 
> Date:   Wed Jan 11 16:41:54 2017 +
>
> crypto: arm/aes - replace bit-sliced OpenSSL NEON code
>
> Maybe binnutils 2.22 is finally too old?
>

I am not sure what the current policy is (Arnd?), but if all errors
pertain to vmovs from scalar to NEON register, I suppose I could work
around it. But perhaps the best solution is the simplest one: not
build the module for < 2.23, like we do for the Crypto Extensions
modules.

Re: linux-next: Tree for Jan 18

[Ard Biesheuvel]

(+ Arnd)

On 18 January 2017 at 20:44, Paul Gortmaker
 wrote:
> On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> Changes since 20170117:
>>
>> The arm-soc tree gained a conflict against the arm tree.
>>
>> The amlogic tree gained a conflict against the arm-soc tree.
>>
>> Non-merge commits (relative to Linus' tree): 3676
>>  4511 files changed, 139928 insertions(+), 85028 deletions(-)
>
> Crypto now fails on arm allmodconfig:
>
> arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
> need binutils 2.23 or higher
> arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
> ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
>   AS [M]  arch/arm/crypto/aes-neonbs-core.o
>   CC [M]  arch/arm/crypto/aes-neonbs-glue.o
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler 
> messages:
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1h[0],r9'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[1],r8'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
> Error: bad type for scalar -- `vmov q1l[0],r7'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[1],r10'
> /home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
> Error: bad type for scalar -- `vmov q2h[0],r9'
>
> [many more similar scalar errors deleted]
>
> The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
> an older binutils 2.22 from the kernel.org crosstool stuff.
>
> Seems sfr's builds get the same issue:
>
> http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/
>
> A mindless "git bisect run" comes up with:
>
> cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
> commit cc477bf645736739e69d31fdf715281ef0dd5f9b
> Author: Ard Biesheuvel 
> Date:   Wed Jan 11 16:41:54 2017 +
>
> crypto: arm/aes - replace bit-sliced OpenSSL NEON code
>
> Maybe binnutils 2.22 is finally too old?
>

I am not sure what the current policy is (Arnd?), but if all errors
pertain to vmovs from scalar to NEON register, I suppose I could work
around it. But perhaps the best solution is the simplest one: not
build the module for < 2.23, like we do for the Crypto Extensions
modules.

Re: linux-next: Tree for Jan 18

[Paul Gortmaker]

On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
wrote:
> Hi all,
>
> Changes since 20170117:
>
> The arm-soc tree gained a conflict against the arm tree.
>
> The amlogic tree gained a conflict against the arm-soc tree.
>
> Non-merge commits (relative to Linus' tree): 3676
>  4511 files changed, 139928 insertions(+), 85028 deletions(-)

Crypto now fails on arm allmodconfig:

arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
need binutils 2.23 or higher
arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
  AS [M]  arch/arm/crypto/aes-neonbs-core.o
  CC [M]  arch/arm/crypto/aes-neonbs-glue.o
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler messages:
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[0],r9'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[1],r8'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[0],r7'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[0],r9'

[many more similar scalar errors deleted]

The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
an older binutils 2.22 from the kernel.org crosstool stuff.

Seems sfr's builds get the same issue:

http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/

A mindless "git bisect run" comes up with:

cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
commit cc477bf645736739e69d31fdf715281ef0dd5f9b
Author: Ard Biesheuvel 
Date:   Wed Jan 11 16:41:54 2017 +

crypto: arm/aes - replace bit-sliced OpenSSL NEON code

Maybe binnutils 2.22 is finally too old?

Paul.
--

Re: linux-next: Tree for Jan 18

[Paul Gortmaker]

On Wed, Jan 18, 2017 at 12:32 AM, Stephen Rothwell  
wrote:
> Hi all,
>
> Changes since 20170117:
>
> The arm-soc tree gained a conflict against the arm tree.
>
> The amlogic tree gained a conflict against the arm-soc tree.
>
> Non-merge commits (relative to Linus' tree): 3676
>  4511 files changed, 139928 insertions(+), 85028 deletions(-)

Crypto now fails on arm allmodconfig:

arch/arm/crypto/Makefile:25: These ARMv8 Crypto Extensions modules
need binutils 2.23 or higher
arch/arm/crypto/Makefile:26:  aes-arm-ce.o sha1-arm-ce.o sha2-arm-ce.o
ghash-arm-ce.o crct10dif-arm-ce.o crc32-arm-ce.o
  AS [M]  arch/arm/crypto/aes-neonbs-core.o
  CC [M]  arch/arm/crypto/aes-neonbs-glue.o
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S: Assembler messages:
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1h[0],r9'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[1],r8'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:817:
Error: bad type for scalar -- `vmov q1l[0],r7'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[1],r10'
/home/paul/git/linux-head/arch/arm/crypto/aes-neonbs-core.S:818:
Error: bad type for scalar -- `vmov q2h[0],r9'

[many more similar scalar errors deleted]

The 2.2.3 warning was there in the past, but it wasn't fatal.  I'm using
an older binutils 2.22 from the kernel.org crosstool stuff.

Seems sfr's builds get the same issue:

http://kisskb.ellerman.id.au/kisskb/buildresult/12910945/

A mindless "git bisect run" comes up with:

cc477bf645736739e69d31fdf715281ef0dd5f9b is the first bad commit
commit cc477bf645736739e69d31fdf715281ef0dd5f9b
Author: Ard Biesheuvel 
Date:   Wed Jan 11 16:41:54 2017 +

crypto: arm/aes - replace bit-sliced OpenSSL NEON code

Maybe binnutils 2.22 is finally too old?

Paul.
--

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20170117:

The arm-soc tree gained a conflict against the arm tree.

The amlogic tree gained a conflict against the arm-soc tree.

Non-merge commits (relative to Linus' tree): 3676
 4511 files changed, 139928 insertions(+), 85028 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
and pseries_le_defconfig and i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 251 trees (counting Linus' and 36 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (4b19a9e20bf9 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging fixes/master (30066ce675d3 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP 
defines before declaring the functions)
Merging arc-current/for-curr (1adc3c8a6aad ARCv2: smp-boot: MCIP: use 
Inter-Core-Debug unit to kick start non master cpus)
Merging arm-current/fixes (90f92c631b21 ARM: 8613/1: Fix the uaccess crash on 
PB11MPCore)
Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in 
atari_get_hardware_list())
Merging metag-fixes/fixes (35d04077ad96 metag: Only define 
atomic_dec_if_positive conditionally)
Merging powerpc-fixes/fixes (69973b830859 Linux 4.9)
Merging sparc/master (5d0e7705774d sparc: Fixed typo in sstate.c. Replaced 
panicing with panicking)
Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and 
linking special files)
Merging net/master (93b43fd137cd net: phy: dp83848: add DP83620 PHY support)
Merging ipsec/master (4e5da369df64 Documentation/networking: fix typo in 
mpls-sysctl)
Merging netfilter/master (e4670b058af6 netfilter: Fix typo in NF_CONNTRACK 
Kconfig option description)
Merging ipvs/master (045169816b31 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging wireless-drivers/master (7195439d1d71 Revert "bcma: init serial console 
directly from ChipCommon code")
Merging mac80211/master (dbef53621116 mac80211: prevent skb/txq mismatch)
Merging sound-current/for-linus (6cf4569ce356 Merge tag 'asoc-fix-v4.10-rc3' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (ea2a7fb12093 Revert "PCI: Add runtime PM support 
for PCIe ports")
Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4)
Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4)
Merging usb.current/usb-linus (833674a45ec7 Merge tag 'fixes-for-v4.10-rc5' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix 
Wmaybe-uninitialized warning)
Merging usb-serial-fixes/usb-linus (49def1853334 Linux 4.10-rc4)
Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move 
the lock initialization to core file)
Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1)
Merging staging.current/staging-linus (a121103c9228 Linux 4.10-rc3)
Merging char-misc.current/char-misc-linus (49def1853334 Linux 4.10-rc4)
Merging input-current/for-linus (1c3415a06b10 Input: elants_i2c - avoid divide 
by 0 errors on bad touchscreen data)
Merging crypto-current/master (07825f0acd85 crypto: aesni - Fix failure when 
built-in with modular pcbc)
Merging ide/master (da095587e6be Revert "ide: Fix interface autodetection in 
legacy IDE driver (trial #2)")
Merging vfio-fixes/for-linus (94a6fa899d2c vfio/type1: 

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20170117:

The arm-soc tree gained a conflict against the arm tree.

The amlogic tree gained a conflict against the arm-soc tree.

Non-merge commits (relative to Linus' tree): 3676
 4511 files changed, 139928 insertions(+), 85028 deletions(-)



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" and checkout or reset to the new
master.

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log
files in the Next directory.  Between each merge, the tree was built
with a ppc64_defconfig for powerpc and an allmodconfig (with
CONFIG_BUILD_DOCSRC=n) for x86_64, a multi_v7_defconfig for arm and a
native build of tools/perf. After the final fixups (if any), I do an
x86_64 modules_install followed by builds for x86_64 allnoconfig,
powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig, allyesconfig
and pseries_le_defconfig and i386, sparc and sparc64 defconfig.

Below is a summary of the state of the merge.

I am currently merging 251 trees (counting Linus' and 36 trees of bug
fix patches pending for the current merge release).

Stats about the size of the tree over time can be seen at
http://neuling.org/linux-next-size.html .

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

-- 
Cheers,
Stephen Rothwell

$ git checkout master
$ git reset --hard stable
Merging origin/master (4b19a9e20bf9 Merge 
git://git.kernel.org/pub/scm/linux/kernel/git/davem/net)
Merging fixes/master (30066ce675d3 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging kbuild-current/rc-fixes (c7858bf16c0b asm-prototypes: Clear any CPP 
defines before declaring the functions)
Merging arc-current/for-curr (1adc3c8a6aad ARCv2: smp-boot: MCIP: use 
Inter-Core-Debug unit to kick start non master cpus)
Merging arm-current/fixes (90f92c631b21 ARM: 8613/1: Fix the uaccess crash on 
PB11MPCore)
Merging m68k-current/for-linus (ad595b77c4a8 m68k/atari: Use seq_puts() in 
atari_get_hardware_list())
Merging metag-fixes/fixes (35d04077ad96 metag: Only define 
atomic_dec_if_positive conditionally)
Merging powerpc-fixes/fixes (69973b830859 Linux 4.9)
Merging sparc/master (5d0e7705774d sparc: Fixed typo in sstate.c. Replaced 
panicing with panicking)
Merging fscrypt-current/for-stable (42d97eb0ade3 fscrypt: fix renaming and 
linking special files)
Merging net/master (93b43fd137cd net: phy: dp83848: add DP83620 PHY support)
Merging ipsec/master (4e5da369df64 Documentation/networking: fix typo in 
mpls-sysctl)
Merging netfilter/master (e4670b058af6 netfilter: Fix typo in NF_CONNTRACK 
Kconfig option description)
Merging ipvs/master (045169816b31 Merge branch 'linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6)
Merging wireless-drivers/master (7195439d1d71 Revert "bcma: init serial console 
directly from ChipCommon code")
Merging mac80211/master (dbef53621116 mac80211: prevent skb/txq mismatch)
Merging sound-current/for-linus (6cf4569ce356 Merge tag 'asoc-fix-v4.10-rc3' of 
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound into for-linus)
Merging pci-current/for-linus (ea2a7fb12093 Revert "PCI: Add runtime PM support 
for PCIe ports")
Merging driver-core.current/driver-core-linus (49def1853334 Linux 4.10-rc4)
Merging tty.current/tty-linus (49def1853334 Linux 4.10-rc4)
Merging usb.current/usb-linus (833674a45ec7 Merge tag 'fixes-for-v4.10-rc5' of 
git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb into usb-linus)
Merging usb-gadget-fixes/fixes (efe357f4633a usb: dwc2: host: fix 
Wmaybe-uninitialized warning)
Merging usb-serial-fixes/usb-linus (49def1853334 Linux 4.10-rc4)
Merging usb-chipidea-fixes/ci-for-usb-stable (c7fbb09b2ea1 usb: chipidea: move 
the lock initialization to core file)
Merging phy/fixes (7ce7d89f4883 Linux 4.10-rc1)
Merging staging.current/staging-linus (a121103c9228 Linux 4.10-rc3)
Merging char-misc.current/char-misc-linus (49def1853334 Linux 4.10-rc4)
Merging input-current/for-linus (1c3415a06b10 Input: elants_i2c - avoid divide 
by 0 errors on bad touchscreen data)
Merging crypto-current/master (07825f0acd85 crypto: aesni - Fix failure when 
built-in with modular pcbc)
Merging ide/master (da095587e6be Revert "ide: Fix interface autodetection in 
legacy IDE driver (trial #2)")
Merging vfio-fixes/for-linus (94a6fa899d2c vfio/type1: 

Re: linux-next: Tree for Jan 18 (x509)

[David Howells]

Randy Dunlap  wrote:

> > Changes since 20130117:
> > 
> 
> on x86_64:
> 
> make[2]: *** No rule to make target `signing_key.x509', needed by 
> `kernel/x509_certificate_list'.  Stop.
> 
> 
> Full randconfig file is attached.

Works for me.  It's likely that the changes I made on the 18th aren't in the
linux-next tree for the 18th.

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

Re: linux-next: Tree for Jan 18 (x509)

[David Howells]

Randy Dunlap rdun...@infradead.org wrote:

  Changes since 20130117:
  
 
 on x86_64:
 
 make[2]: *** No rule to make target `signing_key.x509', needed by 
 `kernel/x509_certificate_list'.  Stop.
 
 
 Full randconfig file is attached.

Works for me.  It's likely that the changes I made on the 18th aren't in the
linux-next tree for the 18th.

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

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:22 PM, Sedat Dilek  wrote:
> On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki  wrote:
>> On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki  wrote:
>>> > On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
>>> >> On 01/17/13 20:37, Stephen Rothwell wrote:
>>> >> > Hi all,
>>> >> >
>>> >> > Changes since 20130117:
>>> >> >
>>> >>
>>> >>
>>> >> on x86_64:
>>> >>
>>> >>   CC  drivers/acpi/device_pm.o
>>> >> drivers/acpi/device_pm.c:778:5: error: redefinition of 
>>> >> 'acpi_dev_suspend_late'
>>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>>> >>  from drivers/acpi/device_pm.c:33:
>>> >> include/linux/acpi.h:526:19: note: previous definition of 
>>> >> 'acpi_dev_suspend_late' was here
>>> >> drivers/acpi/device_pm.c:810:5: error: redefinition of 
>>> >> 'acpi_dev_resume_early'
>>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>>> >>  from drivers/acpi/device_pm.c:33:
>>> >> include/linux/acpi.h:527:19: note: previous definition of 
>>> >> 'acpi_dev_resume_early' was here
>>> >> drivers/acpi/device_pm.c:828:5: error: redefinition of 
>>> >> 'acpi_subsys_prepare'
>>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>>> >>  from drivers/acpi/device_pm.c:33:
>>> >> include/linux/acpi.h:528:19: note: previous definition of 
>>> >> 'acpi_subsys_prepare' was here
>>> >> drivers/acpi/device_pm.c:846:5: error: redefinition of 
>>> >> 'acpi_subsys_suspend_late'
>>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>>> >>  from drivers/acpi/device_pm.c:33:
>>> >> include/linux/acpi.h:529:19: note: previous definition of 
>>> >> 'acpi_subsys_suspend_late' was here
>>> >> drivers/acpi/device_pm.c:861:5: error: redefinition of 
>>> >> 'acpi_subsys_resume_early'
>>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>>> >>  from drivers/acpi/device_pm.c:33:
>>> >> include/linux/acpi.h:530:19: note: previous definition of 
>>> >> 'acpi_subsys_resume_early' was here
>>> >> make[3]: *** [drivers/acpi/device_pm.o] Error 1
>>> >>
>>> >>
>>> >>
>>> >>
>>> >> Full randconfig file is attached.
>>> >
>>> > Thanks, I'll take it for inclusion into the build testing framework.
>>> >
>>> > The appended patch fixes the problem for me.
>>> >
>>> > Thanks,
>>> > Rafael
>>> >
>>> >
>>> > ---
>>> > From: Rafael J. Wysocki 
>>> > Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
>>> >
>>> > CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
>>> > although that is unusual.  For this reason, make the headers of
>>> > functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
>>> > simultaneously depend on that combination of Kconfig options
>>> > instead of CONFIG_ACPI_SLEEP.
>>> >
>>> > This fixes a build problem reported by Randy Dunlap.
>>> >
>>> > Signed-off-by: Rafael J. Wysocki 
>>> > ---
>>> >  include/linux/acpi.h |2 +-
>>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>>> >
>>> > Index: linux-pm/include/linux/acpi.h
>>> > ===
>>> > --- linux-pm.orig/include/linux/acpi.h
>>> > +++ linux-pm/include/linux/acpi.h
>>>
>>> Can you tell me how do you create such a patch with "Index:" line?
>>>
>>> linux-pm.orig as a reference is not very meaninful :-).
>>>
>>> If this is against Linux-Next (next-20130118) I would like to see:
>>> --- next-20130118.orig/path/to/file
>>> +++ next-20130118/path/to/file
>>>
>>> I had used 'git format-patch' with '--subject-prefix="PATCH
>>> next-20130118"' option in such a case.
>>> Just as a hint by not telling you how you should do your job.
>>>
>>> /me is still a Git n00b!
>>
>> Well, I use quilt to generate patches. :-)
>>
>> This particular one was generated with "quilt refresh --diffstat", I'm not
>> sure how to get the same result using git, sorry.
>>
>
> OK, I know I am a bad Git teacher, but from my p00r Git experiences...
>
> I required some of the below options of 'git format-patch' for the
> Freetz router project.
>
> [ Fight with "p0" VS. "p1" patch-format aka w/ or w/o prefix ]
>
> In general Freetz wants its patches in "p0" patch-format to fit its
> own "freetz_patch" tool.
> ( When I asked on the Git ML people did not know/like the terms "p0"
> and "p1" so it's in parenthesis. )
> This means patches should NOT contain "a/" and "b/" prefixes.
>
>--no-prefix
>Do not show any source or destination prefix.
>
> [ Add a "source" (override "a/") and a "destination" (override "b/") prefix ]
>
> You will like this one :-).
> In combination with the above I had to add
> "--src-prefix=linux-2.6.13.1.orig" and -dst-prefix="linux-2.6.13.1"
> for kernel-patches.
> YES, my router has a very ancient kernel-release :-(!
>
>--src-prefix=
>Show the given source prefix instead of "a/".
>
>--dst-prefix=
>Show the 

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki  wrote:
> On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki  wrote:
>> > On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
>> >> On 01/17/13 20:37, Stephen Rothwell wrote:
>> >> > Hi all,
>> >> >
>> >> > Changes since 20130117:
>> >> >
>> >>
>> >>
>> >> on x86_64:
>> >>
>> >>   CC  drivers/acpi/device_pm.o
>> >> drivers/acpi/device_pm.c:778:5: error: redefinition of 
>> >> 'acpi_dev_suspend_late'
>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>> >>  from drivers/acpi/device_pm.c:33:
>> >> include/linux/acpi.h:526:19: note: previous definition of 
>> >> 'acpi_dev_suspend_late' was here
>> >> drivers/acpi/device_pm.c:810:5: error: redefinition of 
>> >> 'acpi_dev_resume_early'
>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>> >>  from drivers/acpi/device_pm.c:33:
>> >> include/linux/acpi.h:527:19: note: previous definition of 
>> >> 'acpi_dev_resume_early' was here
>> >> drivers/acpi/device_pm.c:828:5: error: redefinition of 
>> >> 'acpi_subsys_prepare'
>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>> >>  from drivers/acpi/device_pm.c:33:
>> >> include/linux/acpi.h:528:19: note: previous definition of 
>> >> 'acpi_subsys_prepare' was here
>> >> drivers/acpi/device_pm.c:846:5: error: redefinition of 
>> >> 'acpi_subsys_suspend_late'
>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>> >>  from drivers/acpi/device_pm.c:33:
>> >> include/linux/acpi.h:529:19: note: previous definition of 
>> >> 'acpi_subsys_suspend_late' was here
>> >> drivers/acpi/device_pm.c:861:5: error: redefinition of 
>> >> 'acpi_subsys_resume_early'
>> >> In file included from include/acpi/acpi_drivers.h:29:0,
>> >>  from drivers/acpi/device_pm.c:33:
>> >> include/linux/acpi.h:530:19: note: previous definition of 
>> >> 'acpi_subsys_resume_early' was here
>> >> make[3]: *** [drivers/acpi/device_pm.o] Error 1
>> >>
>> >>
>> >>
>> >>
>> >> Full randconfig file is attached.
>> >
>> > Thanks, I'll take it for inclusion into the build testing framework.
>> >
>> > The appended patch fixes the problem for me.
>> >
>> > Thanks,
>> > Rafael
>> >
>> >
>> > ---
>> > From: Rafael J. Wysocki 
>> > Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
>> >
>> > CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
>> > although that is unusual.  For this reason, make the headers of
>> > functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
>> > simultaneously depend on that combination of Kconfig options
>> > instead of CONFIG_ACPI_SLEEP.
>> >
>> > This fixes a build problem reported by Randy Dunlap.
>> >
>> > Signed-off-by: Rafael J. Wysocki 
>> > ---
>> >  include/linux/acpi.h |2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > Index: linux-pm/include/linux/acpi.h
>> > ===
>> > --- linux-pm.orig/include/linux/acpi.h
>> > +++ linux-pm/include/linux/acpi.h
>>
>> Can you tell me how do you create such a patch with "Index:" line?
>>
>> linux-pm.orig as a reference is not very meaninful :-).
>>
>> If this is against Linux-Next (next-20130118) I would like to see:
>> --- next-20130118.orig/path/to/file
>> +++ next-20130118/path/to/file
>>
>> I had used 'git format-patch' with '--subject-prefix="PATCH
>> next-20130118"' option in such a case.
>> Just as a hint by not telling you how you should do your job.
>>
>> /me is still a Git n00b!
>
> Well, I use quilt to generate patches. :-)
>
> This particular one was generated with "quilt refresh --diffstat", I'm not
> sure how to get the same result using git, sorry.
>

OK, I know I am a bad Git teacher, but from my p00r Git experiences...

I required some of the below options of 'git format-patch' for the
Freetz router project.

[ Fight with "p0" VS. "p1" patch-format aka w/ or w/o prefix ]

In general Freetz wants its patches in "p0" patch-format to fit its
own "freetz_patch" tool.
( When I asked on the Git ML people did not know/like the terms "p0"
and "p1" so it's in parenthesis. )
This means patches should NOT contain "a/" and "b/" prefixes.

   --no-prefix
   Do not show any source or destination prefix.

[ Add a "source" (override "a/") and a "destination" (override "b/") prefix ]

You will like this one :-).
In combination with the above I had to add
"--src-prefix=linux-2.6.13.1.orig" and -dst-prefix="linux-2.6.13.1"
for kernel-patches.
YES, my router has a very ancient kernel-release :-(!

   --src-prefix=
   Show the given source prefix instead of "a/".

   --dst-prefix=
   Show the given destination prefix instead of "b/".

[ Do NOT number patches in a series ]

And last but not least, I personally do not like to see "[PATCH]
12/23" in a series of patches.
Suppress this by using 

Re: linux-next: Tree for Jan 18 (acpi)

[Rafael J. Wysocki]

On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki  wrote:
> > On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
> >> On 01/17/13 20:37, Stephen Rothwell wrote:
> >> > Hi all,
> >> >
> >> > Changes since 20130117:
> >> >
> >>
> >>
> >> on x86_64:
> >>
> >>   CC  drivers/acpi/device_pm.o
> >> drivers/acpi/device_pm.c:778:5: error: redefinition of 
> >> 'acpi_dev_suspend_late'
> >> In file included from include/acpi/acpi_drivers.h:29:0,
> >>  from drivers/acpi/device_pm.c:33:
> >> include/linux/acpi.h:526:19: note: previous definition of 
> >> 'acpi_dev_suspend_late' was here
> >> drivers/acpi/device_pm.c:810:5: error: redefinition of 
> >> 'acpi_dev_resume_early'
> >> In file included from include/acpi/acpi_drivers.h:29:0,
> >>  from drivers/acpi/device_pm.c:33:
> >> include/linux/acpi.h:527:19: note: previous definition of 
> >> 'acpi_dev_resume_early' was here
> >> drivers/acpi/device_pm.c:828:5: error: redefinition of 
> >> 'acpi_subsys_prepare'
> >> In file included from include/acpi/acpi_drivers.h:29:0,
> >>  from drivers/acpi/device_pm.c:33:
> >> include/linux/acpi.h:528:19: note: previous definition of 
> >> 'acpi_subsys_prepare' was here
> >> drivers/acpi/device_pm.c:846:5: error: redefinition of 
> >> 'acpi_subsys_suspend_late'
> >> In file included from include/acpi/acpi_drivers.h:29:0,
> >>  from drivers/acpi/device_pm.c:33:
> >> include/linux/acpi.h:529:19: note: previous definition of 
> >> 'acpi_subsys_suspend_late' was here
> >> drivers/acpi/device_pm.c:861:5: error: redefinition of 
> >> 'acpi_subsys_resume_early'
> >> In file included from include/acpi/acpi_drivers.h:29:0,
> >>  from drivers/acpi/device_pm.c:33:
> >> include/linux/acpi.h:530:19: note: previous definition of 
> >> 'acpi_subsys_resume_early' was here
> >> make[3]: *** [drivers/acpi/device_pm.o] Error 1
> >>
> >>
> >>
> >>
> >> Full randconfig file is attached.
> >
> > Thanks, I'll take it for inclusion into the build testing framework.
> >
> > The appended patch fixes the problem for me.
> >
> > Thanks,
> > Rafael
> >
> >
> > ---
> > From: Rafael J. Wysocki 
> > Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
> >
> > CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
> > although that is unusual.  For this reason, make the headers of
> > functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
> > simultaneously depend on that combination of Kconfig options
> > instead of CONFIG_ACPI_SLEEP.
> >
> > This fixes a build problem reported by Randy Dunlap.
> >
> > Signed-off-by: Rafael J. Wysocki 
> > ---
> >  include/linux/acpi.h |2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > Index: linux-pm/include/linux/acpi.h
> > ===
> > --- linux-pm.orig/include/linux/acpi.h
> > +++ linux-pm/include/linux/acpi.h
> 
> Can you tell me how do you create such a patch with "Index:" line?
> 
> linux-pm.orig as a reference is not very meaninful :-).
> 
> If this is against Linux-Next (next-20130118) I would like to see:
> --- next-20130118.orig/path/to/file
> +++ next-20130118/path/to/file
> 
> I had used 'git format-patch' with '--subject-prefix="PATCH
> next-20130118"' option in such a case.
> Just as a hint by not telling you how you should do your job.
> 
> /me is still a Git n00b!

Well, I use quilt to generate patches. :-)

This particular one was generated with "quilt refresh --diffstat", I'm not
sure how to get the same result using git, sorry.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki  wrote:
> On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
>> On 01/17/13 20:37, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Changes since 20130117:
>> >
>>
>>
>> on x86_64:
>>
>>   CC  drivers/acpi/device_pm.o
>> drivers/acpi/device_pm.c:778:5: error: redefinition of 
>> 'acpi_dev_suspend_late'
>> In file included from include/acpi/acpi_drivers.h:29:0,
>>  from drivers/acpi/device_pm.c:33:
>> include/linux/acpi.h:526:19: note: previous definition of 
>> 'acpi_dev_suspend_late' was here
>> drivers/acpi/device_pm.c:810:5: error: redefinition of 
>> 'acpi_dev_resume_early'
>> In file included from include/acpi/acpi_drivers.h:29:0,
>>  from drivers/acpi/device_pm.c:33:
>> include/linux/acpi.h:527:19: note: previous definition of 
>> 'acpi_dev_resume_early' was here
>> drivers/acpi/device_pm.c:828:5: error: redefinition of 'acpi_subsys_prepare'
>> In file included from include/acpi/acpi_drivers.h:29:0,
>>  from drivers/acpi/device_pm.c:33:
>> include/linux/acpi.h:528:19: note: previous definition of 
>> 'acpi_subsys_prepare' was here
>> drivers/acpi/device_pm.c:846:5: error: redefinition of 
>> 'acpi_subsys_suspend_late'
>> In file included from include/acpi/acpi_drivers.h:29:0,
>>  from drivers/acpi/device_pm.c:33:
>> include/linux/acpi.h:529:19: note: previous definition of 
>> 'acpi_subsys_suspend_late' was here
>> drivers/acpi/device_pm.c:861:5: error: redefinition of 
>> 'acpi_subsys_resume_early'
>> In file included from include/acpi/acpi_drivers.h:29:0,
>>  from drivers/acpi/device_pm.c:33:
>> include/linux/acpi.h:530:19: note: previous definition of 
>> 'acpi_subsys_resume_early' was here
>> make[3]: *** [drivers/acpi/device_pm.o] Error 1
>>
>>
>>
>>
>> Full randconfig file is attached.
>
> Thanks, I'll take it for inclusion into the build testing framework.
>
> The appended patch fixes the problem for me.
>
> Thanks,
> Rafael
>
>
> ---
> From: Rafael J. Wysocki 
> Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
>
> CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
> although that is unusual.  For this reason, make the headers of
> functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
> simultaneously depend on that combination of Kconfig options
> instead of CONFIG_ACPI_SLEEP.
>
> This fixes a build problem reported by Randy Dunlap.
>
> Signed-off-by: Rafael J. Wysocki 
> ---
>  include/linux/acpi.h |2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> Index: linux-pm/include/linux/acpi.h
> ===
> --- linux-pm.orig/include/linux/acpi.h
> +++ linux-pm/include/linux/acpi.h

Can you tell me how do you create such a patch with "Index:" line?

linux-pm.orig as a reference is not very meaninful :-).

If this is against Linux-Next (next-20130118) I would like to see:
--- next-20130118.orig/path/to/file
+++ next-20130118/path/to/file

I had used 'git format-patch' with '--subject-prefix="PATCH
next-20130118"' option in such a case.
Just as a hint by not telling you how you should do your job.

/me is still a Git n00b!

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

Re: linux-next: Tree for Jan 18 (acpi)

[Rafael J. Wysocki]

On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
> On 01/17/13 20:37, Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20130117:
> > 
> 
> 
> on x86_64:
> 
>   CC  drivers/acpi/device_pm.o
> drivers/acpi/device_pm.c:778:5: error: redefinition of 'acpi_dev_suspend_late'
> In file included from include/acpi/acpi_drivers.h:29:0,
>  from drivers/acpi/device_pm.c:33:
> include/linux/acpi.h:526:19: note: previous definition of 
> 'acpi_dev_suspend_late' was here
> drivers/acpi/device_pm.c:810:5: error: redefinition of 'acpi_dev_resume_early'
> In file included from include/acpi/acpi_drivers.h:29:0,
>  from drivers/acpi/device_pm.c:33:
> include/linux/acpi.h:527:19: note: previous definition of 
> 'acpi_dev_resume_early' was here
> drivers/acpi/device_pm.c:828:5: error: redefinition of 'acpi_subsys_prepare'
> In file included from include/acpi/acpi_drivers.h:29:0,
>  from drivers/acpi/device_pm.c:33:
> include/linux/acpi.h:528:19: note: previous definition of 
> 'acpi_subsys_prepare' was here
> drivers/acpi/device_pm.c:846:5: error: redefinition of 
> 'acpi_subsys_suspend_late'
> In file included from include/acpi/acpi_drivers.h:29:0,
>  from drivers/acpi/device_pm.c:33:
> include/linux/acpi.h:529:19: note: previous definition of 
> 'acpi_subsys_suspend_late' was here
> drivers/acpi/device_pm.c:861:5: error: redefinition of 
> 'acpi_subsys_resume_early'
> In file included from include/acpi/acpi_drivers.h:29:0,
>  from drivers/acpi/device_pm.c:33:
> include/linux/acpi.h:530:19: note: previous definition of 
> 'acpi_subsys_resume_early' was here
> make[3]: *** [drivers/acpi/device_pm.o] Error 1
> 
> 
> 
> 
> Full randconfig file is attached.

Thanks, I'll take it for inclusion into the build testing framework.

The appended patch fixes the problem for me.

Thanks,
Rafael


---
From: Rafael J. Wysocki 
Subject: ACPI / PM: Fix build for unusual combination of Kconfig options

CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
although that is unusual.  For this reason, make the headers of
functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
simultaneously depend on that combination of Kconfig options
instead of CONFIG_ACPI_SLEEP.

This fixes a build problem reported by Randy Dunlap.

Signed-off-by: Rafael J. Wysocki 
---
 include/linux/acpi.h |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-pm/include/linux/acpi.h
===
--- linux-pm.orig/include/linux/acpi.h
+++ linux-pm/include/linux/acpi.h
@@ -511,7 +511,7 @@ static inline int acpi_subsys_runtime_su
 static inline int acpi_subsys_runtime_resume(struct device *dev) { return 0; }
 #endif
 
-#ifdef CONFIG_ACPI_SLEEP
+#if defined(CONFIG_ACPI) && defined(CONFIG_PM_SLEEP)
 int acpi_dev_suspend_late(struct device *dev);
 int acpi_dev_resume_early(struct device *dev);
 int acpi_subsys_prepare(struct device *dev);



-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN tty-next on suspend ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  wrote:
> Hi all,
>
> Changes since 20130117:
>
> Undropped tree: samung
>
> The powerpc tree still had a build failure.
>
> The driver-core tree gained a build failure for which I applied a merge
> fix patch.
>
> The gpio-lw tree gained a build failure so I used the version from
> next-20130117.
>
> The samsung tree lost the majority of its conflicts but gained more
> against the arm-soc and slave-dma tree.
>
> 
>

[ TO TTY folks ] + [ CC Rafael and linux-pm ML ]

In the end it turned out to be a problem with tty-next (see thread in [1]).
I am hitting the problem reproducibly on PM/suspend.
Rafael gave me some cool help on pm-testing, thanks (see also thread in [1])

Ilya has sent a patch to [3] which needs to be refreshed.
AFAICS also be adapted to the recent changes to tty_port and tty_buf.
But hey, I am no TTY expert so it is up to you.

Hope you will CC me on the patch.

Thanks!

- Sedat -

[1] http://marc.info/?t=13585471403=1=2
[2] 
http://git.kernel.org/?p=linux/kernel/git/gregkh/tty.git;a=shortlog;h=refs/heads/tty-next
[3] http://marc.info/?t=13545286833=1=2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:13 AM, Sedat Dilek  wrote:
> On Sat, Jan 19, 2013 at 2:55 AM, Sedat Dilek  wrote:
>> On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki  wrote:
>>> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
 > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
 >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  
 >> wrote:
 >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
 >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek 
 >> >>  wrote:
 >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
 >> >> > wrote:
 >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
 >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
 >> >> >>>  wrote:
 >> >> >>> > Hi all,
 >> >> >>> >
 >> >> >>> > Changes since 20130117:
 >> >> >>> >
 >> >> >>> > Undropped tree: samung
 >> >> >>> >
 >> >> >>> > The powerpc tree still had a build failure.
 >> >> >>> >
 >> >> >>> > The driver-core tree gained a build failure for which I 
 >> >> >>> > applied a merge
 >> >> >>> > fix patch.
 >> >> >>> >
 >> >> >>> > The gpio-lw tree gained a build failure so I used the version 
 >> >> >>> > from
 >> >> >>> > next-20130117.
 >> >> >>> >
 >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
 >> >> >>> > more
 >> >> >>> > against the arm-soc and slave-dma tree.
 >> >> >>> >
 >> >> >>> > 
 >> >> >>> >
 >> >> >>>
 >> >> >>> From my dmesg diff-file:
 >> >> >>>
 >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
 >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
 >> >> >>> seconds) done.
 >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
 >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
 >> >> >>> tasks
 >> >> >>> refusing to freeze, wq_busy=0):
 >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297   
 >> >> >>>2 0x
 >> >> >>> +[  314.098865]  880117ec5b68 0046 
 >> >> >>> 880117ec5b08
 >> >> >>> 81044c29
 >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 
 >> >> >>> 880117ec5fd8
 >> >> >>> 880117ec5fd8
 >> >> >>> +[  314.098871]  880119b34560 88011829dc80 
 >> >> >>> 880117ec5b68
 >> >> >>> 88011fad4738
 >> >> >>> +[  314.098873] Call Trace:
 >> >> >>> +[  314.098881]  [] ? 
 >> >> >>> default_spin_lock_flags+0x9/0x10
 >> >> >>> +[  314.098885]  [] ? 
 >> >> >>> __wait_on_buffer+0x30/0x30
 >> >> >>> +[  314.09]  [] schedule+0x29/0x70
 >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
 >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
 >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
 >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
 >> >> >>> +[  314.098900]  [] ? 
 >> >> >>> __wait_on_buffer+0x30/0x30
 >> >> >>> +[  314.098903]  [] 
 >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
 >> >> >>> +[  314.098906]  [] ? 
 >> >> >>> autoremove_wake_function+0x40/0x40
 >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
 >> >> >>> +[  314.098913]  []
 >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
 >> >> >>> +[  314.098917]  [] ? 
 >> >> >>> sched_clock_cpu+0xbd/0x110
 >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
 >> >> >>> +[  314.098923]  [] ? 
 >> >> >>> try_to_del_timer_sync+0x4f/0x70
 >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
 >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
 >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
 >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
 >> >> >>> +[  314.098933]  [] ? 
 >> >> >>> flush_kthread_worker+0xb0/0xb0
 >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
 >> >> >>> +[  314.098938]  [] ? 
 >> >> >>> flush_kthread_worker+0xb0/0xb0
 >> >> >>> +[  314.098969]
 >> >> >>> +[  314.098970] Restarting kernel threads ... done.
 >> >> >>> +[  314.099052] Restarting tasks ... done.
 >> >> >>>
 >> >> >>> Please, have a lot at it.
 >> >> >>
 >> >> >> This is a freezer failure while freezing kernel threads, so I 
 >> >> >> don't think it's
 >> >> >> related to ACPI or PM directly.
 >> >> >>
 >> >> >> Does it happen on every suspend?
 >> >> >>
 >> >> >
 >> >> > No, I only did one S/R.
 >> >> >
 >> >> > I have built a 2nd new kernel where I pulled-in latest 
 >> >> > pm.git#linux-next.
 >> >> > With this kernel two S/Rs were fine - but that says not much.
 >> >> >
 >> >>
 >> >> After several S/Rs on the "buggy" -1 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:13 AM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Sat, Jan 19, 2013 at 2:55 AM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl 
  wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek 
   sedat.di...@gmail.com wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I 
 applied a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version 
 from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297   
   2 0x
+[  314.098865]  880117ec5b68 0046 
880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 
880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 
880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? 
__wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? 
__wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? 
sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I 
don't think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot 
   CPUs ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are 

Re: linux-next: Tree for Jan 18 [ BROKEN tty-next on suspend ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained more
 against the arm-soc and slave-dma tree.

 


[ TO TTY folks ] + [ CC Rafael and linux-pm ML ]

In the end it turned out to be a problem with tty-next (see thread in [1]).
I am hitting the problem reproducibly on PM/suspend.
Rafael gave me some cool help on pm-testing, thanks (see also thread in [1])

Ilya has sent a patch to [3] which needs to be refreshed.
AFAICS also be adapted to the recent changes to tty_port and tty_buf.
But hey, I am no TTY expert so it is up to you.

Hope you will CC me on the patch.

Thanks!

- Sedat -

[1] http://marc.info/?t=13585471403r=1w=2
[2] 
http://git.kernel.org/?p=linux/kernel/git/gregkh/tty.git;a=shortlog;h=refs/heads/tty-next
[3] http://marc.info/?t=13545286833r=1w=2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 (acpi)

[Rafael J. Wysocki]

On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
 On 01/17/13 20:37, Stephen Rothwell wrote:
  Hi all,
  
  Changes since 20130117:
  
 
 
 on x86_64:
 
   CC  drivers/acpi/device_pm.o
 drivers/acpi/device_pm.c:778:5: error: redefinition of 'acpi_dev_suspend_late'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:526:19: note: previous definition of 
 'acpi_dev_suspend_late' was here
 drivers/acpi/device_pm.c:810:5: error: redefinition of 'acpi_dev_resume_early'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:527:19: note: previous definition of 
 'acpi_dev_resume_early' was here
 drivers/acpi/device_pm.c:828:5: error: redefinition of 'acpi_subsys_prepare'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:528:19: note: previous definition of 
 'acpi_subsys_prepare' was here
 drivers/acpi/device_pm.c:846:5: error: redefinition of 
 'acpi_subsys_suspend_late'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:529:19: note: previous definition of 
 'acpi_subsys_suspend_late' was here
 drivers/acpi/device_pm.c:861:5: error: redefinition of 
 'acpi_subsys_resume_early'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:530:19: note: previous definition of 
 'acpi_subsys_resume_early' was here
 make[3]: *** [drivers/acpi/device_pm.o] Error 1
 
 
 
 
 Full randconfig file is attached.

Thanks, I'll take it for inclusion into the build testing framework.

The appended patch fixes the problem for me.

Thanks,
Rafael


---
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
Subject: ACPI / PM: Fix build for unusual combination of Kconfig options

CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
although that is unusual.  For this reason, make the headers of
functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
simultaneously depend on that combination of Kconfig options
instead of CONFIG_ACPI_SLEEP.

This fixes a build problem reported by Randy Dunlap.

Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
---
 include/linux/acpi.h |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-pm/include/linux/acpi.h
===
--- linux-pm.orig/include/linux/acpi.h
+++ linux-pm/include/linux/acpi.h
@@ -511,7 +511,7 @@ static inline int acpi_subsys_runtime_su
 static inline int acpi_subsys_runtime_resume(struct device *dev) { return 0; }
 #endif
 
-#ifdef CONFIG_ACPI_SLEEP
+#if defined(CONFIG_ACPI)  defined(CONFIG_PM_SLEEP)
 int acpi_dev_suspend_late(struct device *dev);
 int acpi_dev_resume_early(struct device *dev);
 int acpi_subsys_prepare(struct device *dev);



-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
 On 01/17/13 20:37, Stephen Rothwell wrote:
  Hi all,
 
  Changes since 20130117:
 


 on x86_64:

   CC  drivers/acpi/device_pm.o
 drivers/acpi/device_pm.c:778:5: error: redefinition of 
 'acpi_dev_suspend_late'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:526:19: note: previous definition of 
 'acpi_dev_suspend_late' was here
 drivers/acpi/device_pm.c:810:5: error: redefinition of 
 'acpi_dev_resume_early'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:527:19: note: previous definition of 
 'acpi_dev_resume_early' was here
 drivers/acpi/device_pm.c:828:5: error: redefinition of 'acpi_subsys_prepare'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:528:19: note: previous definition of 
 'acpi_subsys_prepare' was here
 drivers/acpi/device_pm.c:846:5: error: redefinition of 
 'acpi_subsys_suspend_late'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:529:19: note: previous definition of 
 'acpi_subsys_suspend_late' was here
 drivers/acpi/device_pm.c:861:5: error: redefinition of 
 'acpi_subsys_resume_early'
 In file included from include/acpi/acpi_drivers.h:29:0,
  from drivers/acpi/device_pm.c:33:
 include/linux/acpi.h:530:19: note: previous definition of 
 'acpi_subsys_resume_early' was here
 make[3]: *** [drivers/acpi/device_pm.o] Error 1




 Full randconfig file is attached.

 Thanks, I'll take it for inclusion into the build testing framework.

 The appended patch fixes the problem for me.

 Thanks,
 Rafael


 ---
 From: Rafael J. Wysocki rafael.j.wyso...@intel.com
 Subject: ACPI / PM: Fix build for unusual combination of Kconfig options

 CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
 although that is unusual.  For this reason, make the headers of
 functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
 simultaneously depend on that combination of Kconfig options
 instead of CONFIG_ACPI_SLEEP.

 This fixes a build problem reported by Randy Dunlap.

 Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
 ---
  include/linux/acpi.h |2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)

 Index: linux-pm/include/linux/acpi.h
 ===
 --- linux-pm.orig/include/linux/acpi.h
 +++ linux-pm/include/linux/acpi.h

Can you tell me how do you create such a patch with Index: line?

linux-pm.orig as a reference is not very meaninful :-).

If this is against Linux-Next (next-20130118) I would like to see:
--- next-20130118.orig/path/to/file
+++ next-20130118/path/to/file

I had used 'git format-patch' with '--subject-prefix=PATCH
next-20130118' option in such a case.
Just as a hint by not telling you how you should do your job.

/me is still a Git n00b!

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

Re: linux-next: Tree for Jan 18 (acpi)

[Rafael J. Wysocki]

On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
  On 01/17/13 20:37, Stephen Rothwell wrote:
   Hi all,
  
   Changes since 20130117:
  
 
 
  on x86_64:
 
CC  drivers/acpi/device_pm.o
  drivers/acpi/device_pm.c:778:5: error: redefinition of 
  'acpi_dev_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:526:19: note: previous definition of 
  'acpi_dev_suspend_late' was here
  drivers/acpi/device_pm.c:810:5: error: redefinition of 
  'acpi_dev_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:527:19: note: previous definition of 
  'acpi_dev_resume_early' was here
  drivers/acpi/device_pm.c:828:5: error: redefinition of 
  'acpi_subsys_prepare'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:528:19: note: previous definition of 
  'acpi_subsys_prepare' was here
  drivers/acpi/device_pm.c:846:5: error: redefinition of 
  'acpi_subsys_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:529:19: note: previous definition of 
  'acpi_subsys_suspend_late' was here
  drivers/acpi/device_pm.c:861:5: error: redefinition of 
  'acpi_subsys_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:530:19: note: previous definition of 
  'acpi_subsys_resume_early' was here
  make[3]: *** [drivers/acpi/device_pm.o] Error 1
 
 
 
 
  Full randconfig file is attached.
 
  Thanks, I'll take it for inclusion into the build testing framework.
 
  The appended patch fixes the problem for me.
 
  Thanks,
  Rafael
 
 
  ---
  From: Rafael J. Wysocki rafael.j.wyso...@intel.com
  Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
 
  CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
  although that is unusual.  For this reason, make the headers of
  functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
  simultaneously depend on that combination of Kconfig options
  instead of CONFIG_ACPI_SLEEP.
 
  This fixes a build problem reported by Randy Dunlap.
 
  Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
  ---
   include/linux/acpi.h |2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
 
  Index: linux-pm/include/linux/acpi.h
  ===
  --- linux-pm.orig/include/linux/acpi.h
  +++ linux-pm/include/linux/acpi.h
 
 Can you tell me how do you create such a patch with Index: line?
 
 linux-pm.orig as a reference is not very meaninful :-).
 
 If this is against Linux-Next (next-20130118) I would like to see:
 --- next-20130118.orig/path/to/file
 +++ next-20130118/path/to/file
 
 I had used 'git format-patch' with '--subject-prefix=PATCH
 next-20130118' option in such a case.
 Just as a hint by not telling you how you should do your job.
 
 /me is still a Git n00b!

Well, I use quilt to generate patches. :-)

This particular one was generated with quilt refresh --diffstat, I'm not
sure how to get the same result using git, sorry.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
  On 01/17/13 20:37, Stephen Rothwell wrote:
   Hi all,
  
   Changes since 20130117:
  
 
 
  on x86_64:
 
CC  drivers/acpi/device_pm.o
  drivers/acpi/device_pm.c:778:5: error: redefinition of 
  'acpi_dev_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:526:19: note: previous definition of 
  'acpi_dev_suspend_late' was here
  drivers/acpi/device_pm.c:810:5: error: redefinition of 
  'acpi_dev_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:527:19: note: previous definition of 
  'acpi_dev_resume_early' was here
  drivers/acpi/device_pm.c:828:5: error: redefinition of 
  'acpi_subsys_prepare'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:528:19: note: previous definition of 
  'acpi_subsys_prepare' was here
  drivers/acpi/device_pm.c:846:5: error: redefinition of 
  'acpi_subsys_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:529:19: note: previous definition of 
  'acpi_subsys_suspend_late' was here
  drivers/acpi/device_pm.c:861:5: error: redefinition of 
  'acpi_subsys_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:530:19: note: previous definition of 
  'acpi_subsys_resume_early' was here
  make[3]: *** [drivers/acpi/device_pm.o] Error 1
 
 
 
 
  Full randconfig file is attached.
 
  Thanks, I'll take it for inclusion into the build testing framework.
 
  The appended patch fixes the problem for me.
 
  Thanks,
  Rafael
 
 
  ---
  From: Rafael J. Wysocki rafael.j.wyso...@intel.com
  Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
 
  CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
  although that is unusual.  For this reason, make the headers of
  functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
  simultaneously depend on that combination of Kconfig options
  instead of CONFIG_ACPI_SLEEP.
 
  This fixes a build problem reported by Randy Dunlap.
 
  Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
  ---
   include/linux/acpi.h |2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
 
  Index: linux-pm/include/linux/acpi.h
  ===
  --- linux-pm.orig/include/linux/acpi.h
  +++ linux-pm/include/linux/acpi.h

 Can you tell me how do you create such a patch with Index: line?

 linux-pm.orig as a reference is not very meaninful :-).

 If this is against Linux-Next (next-20130118) I would like to see:
 --- next-20130118.orig/path/to/file
 +++ next-20130118/path/to/file

 I had used 'git format-patch' with '--subject-prefix=PATCH
 next-20130118' option in such a case.
 Just as a hint by not telling you how you should do your job.

 /me is still a Git n00b!

 Well, I use quilt to generate patches. :-)

 This particular one was generated with quilt refresh --diffstat, I'm not
 sure how to get the same result using git, sorry.


OK, I know I am a bad Git teacher, but from my p00r Git experiences...

I required some of the below options of 'git format-patch' for the
Freetz router project.

[ Fight with p0 VS. p1 patch-format aka w/ or w/o prefix ]

In general Freetz wants its patches in p0 patch-format to fit its
own freetz_patch tool.
( When I asked on the Git ML people did not know/like the terms p0
and p1 so it's in parenthesis. )
This means patches should NOT contain a/ and b/ prefixes.

   --no-prefix
   Do not show any source or destination prefix.

[ Add a source (override a/) and a destination (override b/) prefix ]

You will like this one :-).
In combination with the above I had to add
--src-prefix=linux-2.6.13.1.orig and -dst-prefix=linux-2.6.13.1
for kernel-patches.
YES, my router has a very ancient kernel-release :-(!

   --src-prefix=prefix
   Show the given source prefix instead of a/.

   --dst-prefix=prefix
   Show the given destination prefix instead of b/.

[ Do NOT number patches in a series ]

And last but not least, I personally do not like to see [PATCH]
12/23 in a series of patches.
Suppress this by using --no-numbered option.
NOTE: For a single patch this option is useless :-)!

   -N, --no-numbered
   Name output in [PATCH] format.

[ bonbon: cover-letter aka 0/x or 00/yy or 000/zzz (IMHO zzz is more a
love-letter :-)) ]

   --cover-letter
   In 

Re: linux-next: Tree for Jan 18 (acpi)

[Sedat Dilek]

On Sat, Jan 19, 2013 at 3:22 PM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Sat, Jan 19, 2013 at 3:01 PM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 02:50:17 PM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 2:45 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 05:42:20 PM Randy Dunlap wrote:
  On 01/17/13 20:37, Stephen Rothwell wrote:
   Hi all,
  
   Changes since 20130117:
  
 
 
  on x86_64:
 
CC  drivers/acpi/device_pm.o
  drivers/acpi/device_pm.c:778:5: error: redefinition of 
  'acpi_dev_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:526:19: note: previous definition of 
  'acpi_dev_suspend_late' was here
  drivers/acpi/device_pm.c:810:5: error: redefinition of 
  'acpi_dev_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:527:19: note: previous definition of 
  'acpi_dev_resume_early' was here
  drivers/acpi/device_pm.c:828:5: error: redefinition of 
  'acpi_subsys_prepare'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:528:19: note: previous definition of 
  'acpi_subsys_prepare' was here
  drivers/acpi/device_pm.c:846:5: error: redefinition of 
  'acpi_subsys_suspend_late'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:529:19: note: previous definition of 
  'acpi_subsys_suspend_late' was here
  drivers/acpi/device_pm.c:861:5: error: redefinition of 
  'acpi_subsys_resume_early'
  In file included from include/acpi/acpi_drivers.h:29:0,
   from drivers/acpi/device_pm.c:33:
  include/linux/acpi.h:530:19: note: previous definition of 
  'acpi_subsys_resume_early' was here
  make[3]: *** [drivers/acpi/device_pm.o] Error 1
 
 
 
 
  Full randconfig file is attached.
 
  Thanks, I'll take it for inclusion into the build testing framework.
 
  The appended patch fixes the problem for me.
 
  Thanks,
  Rafael
 
 
  ---
  From: Rafael J. Wysocki rafael.j.wyso...@intel.com
  Subject: ACPI / PM: Fix build for unusual combination of Kconfig options
 
  CONFIG_PM_SLEEP may be set even if CONFIG_ACPI_SLEEP is unset,
  although that is unusual.  For this reason, make the headers of
  functions built for both CONFIG_ACPI and CONFIG_PM_SLEEP set
  simultaneously depend on that combination of Kconfig options
  instead of CONFIG_ACPI_SLEEP.
 
  This fixes a build problem reported by Randy Dunlap.
 
  Signed-off-by: Rafael J. Wysocki rafael.j.wyso...@intel.com
  ---
   include/linux/acpi.h |2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
 
  Index: linux-pm/include/linux/acpi.h
  ===
  --- linux-pm.orig/include/linux/acpi.h
  +++ linux-pm/include/linux/acpi.h

 Can you tell me how do you create such a patch with Index: line?

 linux-pm.orig as a reference is not very meaninful :-).

 If this is against Linux-Next (next-20130118) I would like to see:
 --- next-20130118.orig/path/to/file
 +++ next-20130118/path/to/file

 I had used 'git format-patch' with '--subject-prefix=PATCH
 next-20130118' option in such a case.
 Just as a hint by not telling you how you should do your job.

 /me is still a Git n00b!

 Well, I use quilt to generate patches. :-)

 This particular one was generated with quilt refresh --diffstat, I'm not
 sure how to get the same result using git, sorry.


 OK, I know I am a bad Git teacher, but from my p00r Git experiences...

 I required some of the below options of 'git format-patch' for the
 Freetz router project.

 [ Fight with p0 VS. p1 patch-format aka w/ or w/o prefix ]

 In general Freetz wants its patches in p0 patch-format to fit its
 own freetz_patch tool.
 ( When I asked on the Git ML people did not know/like the terms p0
 and p1 so it's in parenthesis. )
 This means patches should NOT contain a/ and b/ prefixes.

--no-prefix
Do not show any source or destination prefix.

 [ Add a source (override a/) and a destination (override b/) prefix ]

 You will like this one :-).
 In combination with the above I had to add
 --src-prefix=linux-2.6.13.1.orig and -dst-prefix=linux-2.6.13.1
 for kernel-patches.
 YES, my router has a very ancient kernel-release :-(!

--src-prefix=prefix
Show the given source prefix instead of a/.

--dst-prefix=prefix
Show the given destination prefix instead of b/.

 [ Do NOT number patches in a series ]

 And last but not least, I personally do not like to see [PATCH]
 12/23 in a series of patches.

Just as note:
This is for the subject-line!
The numbering of patch is untouched (start: 0001 and end: 000x|00yy|0zzz).

- Sedat -

 Suppress this by using --no-numbered option.
 NOTE: For a single 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 2:55 AM, Sedat Dilek  wrote:
> On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki  wrote:
>> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
>>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>>> >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
>>> >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>>> >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
>>> >> >> wrote:
>>> >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
>>> >> >> > wrote:
>>> >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>>> >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>>> >> >> >>>  wrote:
>>> >> >> >>> > Hi all,
>>> >> >> >>> >
>>> >> >> >>> > Changes since 20130117:
>>> >> >> >>> >
>>> >> >> >>> > Undropped tree: samung
>>> >> >> >>> >
>>> >> >> >>> > The powerpc tree still had a build failure.
>>> >> >> >>> >
>>> >> >> >>> > The driver-core tree gained a build failure for which I applied 
>>> >> >> >>> > a merge
>>> >> >> >>> > fix patch.
>>> >> >> >>> >
>>> >> >> >>> > The gpio-lw tree gained a build failure so I used the version 
>>> >> >> >>> > from
>>> >> >> >>> > next-20130117.
>>> >> >> >>> >
>>> >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
>>> >> >> >>> > more
>>> >> >> >>> > against the arm-soc and slave-dma tree.
>>> >> >> >>> >
>>> >> >> >>> > 
>>> >> >> >>> >
>>> >> >> >>>
>>> >> >> >>> From my dmesg diff-file:
>>> >> >> >>>
>>> >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
>>> >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
>>> >> >> >>> seconds) done.
>>> >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
>>> >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
>>> >> >> >>> tasks
>>> >> >> >>> refusing to freeze, wq_busy=0):
>>> >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297
>>> >> >> >>>   2 0x
>>> >> >> >>> +[  314.098865]  880117ec5b68 0046 
>>> >> >> >>> 880117ec5b08
>>> >> >> >>> 81044c29
>>> >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 
>>> >> >> >>> 880117ec5fd8
>>> >> >> >>> 880117ec5fd8
>>> >> >> >>> +[  314.098871]  880119b34560 88011829dc80 
>>> >> >> >>> 880117ec5b68
>>> >> >> >>> 88011fad4738
>>> >> >> >>> +[  314.098873] Call Trace:
>>> >> >> >>> +[  314.098881]  [] ? 
>>> >> >> >>> default_spin_lock_flags+0x9/0x10
>>> >> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>>> >> >> >>> +[  314.09]  [] schedule+0x29/0x70
>>> >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>>> >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>>> >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>>> >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>>> >> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>>> >> >> >>> +[  314.098903]  [] 
>>> >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
>>> >> >> >>> +[  314.098906]  [] ? 
>>> >> >> >>> autoremove_wake_function+0x40/0x40
>>> >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>>> >> >> >>> +[  314.098913]  []
>>> >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>>> >> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>>> >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>>> >> >> >>> +[  314.098923]  [] ? 
>>> >> >> >>> try_to_del_timer_sync+0x4f/0x70
>>> >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>>> >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>>> >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>>> >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>>> >> >> >>> +[  314.098933]  [] ? 
>>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>>> >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>>> >> >> >>> +[  314.098938]  [] ? 
>>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>>> >> >> >>> +[  314.098969]
>>> >> >> >>> +[  314.098970] Restarting kernel threads ... done.
>>> >> >> >>> +[  314.099052] Restarting tasks ... done.
>>> >> >> >>>
>>> >> >> >>> Please, have a lot at it.
>>> >> >> >>
>>> >> >> >> This is a freezer failure while freezing kernel threads, so I 
>>> >> >> >> don't think it's
>>> >> >> >> related to ACPI or PM directly.
>>> >> >> >>
>>> >> >> >> Does it happen on every suspend?
>>> >> >> >>
>>> >> >> >
>>> >> >> > No, I only did one S/R.
>>> >> >> >
>>> >> >> > I have built a 2nd new kernel where I pulled-in latest 
>>> >> >> > pm.git#linux-next.
>>> >> >> > With this kernel two S/Rs were fine - but that says not much.
>>> >> >> >
>>> >> >>
>>> >> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>>> >> >>
>>> >> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
>>> >> >> ...
>>> >> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki  wrote:
> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
>> >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
>> >> >> wrote:
>> >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
>> >> >> > wrote:
>> >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>> >> >> >>>  wrote:
>> >> >> >>> > Hi all,
>> >> >> >>> >
>> >> >> >>> > Changes since 20130117:
>> >> >> >>> >
>> >> >> >>> > Undropped tree: samung
>> >> >> >>> >
>> >> >> >>> > The powerpc tree still had a build failure.
>> >> >> >>> >
>> >> >> >>> > The driver-core tree gained a build failure for which I applied 
>> >> >> >>> > a merge
>> >> >> >>> > fix patch.
>> >> >> >>> >
>> >> >> >>> > The gpio-lw tree gained a build failure so I used the version 
>> >> >> >>> > from
>> >> >> >>> > next-20130117.
>> >> >> >>> >
>> >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
>> >> >> >>> > more
>> >> >> >>> > against the arm-soc and slave-dma tree.
>> >> >> >>> >
>> >> >> >>> > 
>> >> >> >>> >
>> >> >> >>>
>> >> >> >>> From my dmesg diff-file:
>> >> >> >>>
>> >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
>> >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
>> >> >> >>> seconds) done.
>> >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
>> >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
>> >> >> >>> tasks
>> >> >> >>> refusing to freeze, wq_busy=0):
>> >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297 
>> >> >> >>>  2 0x
>> >> >> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>> >> >> >>> 81044c29
>> >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>> >> >> >>> 880117ec5fd8
>> >> >> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>> >> >> >>> 88011fad4738
>> >> >> >>> +[  314.098873] Call Trace:
>> >> >> >>> +[  314.098881]  [] ? 
>> >> >> >>> default_spin_lock_flags+0x9/0x10
>> >> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>> >> >> >>> +[  314.09]  [] schedule+0x29/0x70
>> >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>> >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>> >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>> >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>> >> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>> >> >> >>> +[  314.098903]  [] 
>> >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
>> >> >> >>> +[  314.098906]  [] ? 
>> >> >> >>> autoremove_wake_function+0x40/0x40
>> >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>> >> >> >>> +[  314.098913]  []
>> >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>> >> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>> >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>> >> >> >>> +[  314.098923]  [] ? 
>> >> >> >>> try_to_del_timer_sync+0x4f/0x70
>> >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>> >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>> >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>> >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>> >> >> >>> +[  314.098933]  [] ? 
>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>> >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>> >> >> >>> +[  314.098938]  [] ? 
>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>> >> >> >>> +[  314.098969]
>> >> >> >>> +[  314.098970] Restarting kernel threads ... done.
>> >> >> >>> +[  314.099052] Restarting tasks ... done.
>> >> >> >>>
>> >> >> >>> Please, have a lot at it.
>> >> >> >>
>> >> >> >> This is a freezer failure while freezing kernel threads, so I don't 
>> >> >> >> think it's
>> >> >> >> related to ACPI or PM directly.
>> >> >> >>
>> >> >> >> Does it happen on every suspend?
>> >> >> >>
>> >> >> >
>> >> >> > No, I only did one S/R.
>> >> >> >
>> >> >> > I have built a 2nd new kernel where I pulled-in latest 
>> >> >> > pm.git#linux-next.
>> >> >> > With this kernel two S/Rs were fine - but that says not much.
>> >> >> >
>> >> >>
>> >> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>> >> >>
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
>> >> >> ...
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
>> >> >> offline
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
>> >> >> local_softirq_pending 02
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
>> >> >> local_softirq_pending 02

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 1:00 AM, Sedat Dilek  wrote:
> On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki  wrote:
>> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
>>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>>> >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
>>> >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>>> >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
>>> >> >> wrote:
>>> >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
>>> >> >> > wrote:
>>> >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>>> >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>>> >> >> >>>  wrote:
>>> >> >> >>> > Hi all,
>>> >> >> >>> >
>>> >> >> >>> > Changes since 20130117:
>>> >> >> >>> >
>>> >> >> >>> > Undropped tree: samung
>>> >> >> >>> >
>>> >> >> >>> > The powerpc tree still had a build failure.
>>> >> >> >>> >
>>> >> >> >>> > The driver-core tree gained a build failure for which I applied 
>>> >> >> >>> > a merge
>>> >> >> >>> > fix patch.
>>> >> >> >>> >
>>> >> >> >>> > The gpio-lw tree gained a build failure so I used the version 
>>> >> >> >>> > from
>>> >> >> >>> > next-20130117.
>>> >> >> >>> >
>>> >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
>>> >> >> >>> > more
>>> >> >> >>> > against the arm-soc and slave-dma tree.
>>> >> >> >>> >
>>> >> >> >>> > 
>>> >> >> >>> >
>>> >> >> >>>
>>> >> >> >>> From my dmesg diff-file:
>>> >> >> >>>
>>> >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
>>> >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
>>> >> >> >>> seconds) done.
>>> >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
>>> >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
>>> >> >> >>> tasks
>>> >> >> >>> refusing to freeze, wq_busy=0):
>>> >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297
>>> >> >> >>>   2 0x
>>> >> >> >>> +[  314.098865]  880117ec5b68 0046 
>>> >> >> >>> 880117ec5b08
>>> >> >> >>> 81044c29
>>> >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 
>>> >> >> >>> 880117ec5fd8
>>> >> >> >>> 880117ec5fd8
>>> >> >> >>> +[  314.098871]  880119b34560 88011829dc80 
>>> >> >> >>> 880117ec5b68
>>> >> >> >>> 88011fad4738
>>> >> >> >>> +[  314.098873] Call Trace:
>>> >> >> >>> +[  314.098881]  [] ? 
>>> >> >> >>> default_spin_lock_flags+0x9/0x10
>>> >> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>>> >> >> >>> +[  314.09]  [] schedule+0x29/0x70
>>> >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>>> >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>>> >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>>> >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>>> >> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>>> >> >> >>> +[  314.098903]  [] 
>>> >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
>>> >> >> >>> +[  314.098906]  [] ? 
>>> >> >> >>> autoremove_wake_function+0x40/0x40
>>> >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>>> >> >> >>> +[  314.098913]  []
>>> >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>>> >> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>>> >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>>> >> >> >>> +[  314.098923]  [] ? 
>>> >> >> >>> try_to_del_timer_sync+0x4f/0x70
>>> >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>>> >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>>> >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>>> >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>>> >> >> >>> +[  314.098933]  [] ? 
>>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>>> >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>>> >> >> >>> +[  314.098938]  [] ? 
>>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>>> >> >> >>> +[  314.098969]
>>> >> >> >>> +[  314.098970] Restarting kernel threads ... done.
>>> >> >> >>> +[  314.099052] Restarting tasks ... done.
>>> >> >> >>>
>>> >> >> >>> Please, have a lot at it.
>>> >> >> >>
>>> >> >> >> This is a freezer failure while freezing kernel threads, so I 
>>> >> >> >> don't think it's
>>> >> >> >> related to ACPI or PM directly.
>>> >> >> >>
>>> >> >> >> Does it happen on every suspend?
>>> >> >> >>
>>> >> >> >
>>> >> >> > No, I only did one S/R.
>>> >> >> >
>>> >> >> > I have built a 2nd new kernel where I pulled-in latest 
>>> >> >> > pm.git#linux-next.
>>> >> >> > With this kernel two S/Rs were fine - but that says not much.
>>> >> >> >
>>> >> >>
>>> >> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>>> >> >>
>>> >> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
>>> >> >> ...
>>> >> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki  wrote:
> On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
>> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
>> >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
>> >> >> wrote:
>> >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
>> >> >> > wrote:
>> >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>> >> >> >>>  wrote:
>> >> >> >>> > Hi all,
>> >> >> >>> >
>> >> >> >>> > Changes since 20130117:
>> >> >> >>> >
>> >> >> >>> > Undropped tree: samung
>> >> >> >>> >
>> >> >> >>> > The powerpc tree still had a build failure.
>> >> >> >>> >
>> >> >> >>> > The driver-core tree gained a build failure for which I applied 
>> >> >> >>> > a merge
>> >> >> >>> > fix patch.
>> >> >> >>> >
>> >> >> >>> > The gpio-lw tree gained a build failure so I used the version 
>> >> >> >>> > from
>> >> >> >>> > next-20130117.
>> >> >> >>> >
>> >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
>> >> >> >>> > more
>> >> >> >>> > against the arm-soc and slave-dma tree.
>> >> >> >>> >
>> >> >> >>> > 
>> >> >> >>> >
>> >> >> >>>
>> >> >> >>> From my dmesg diff-file:
>> >> >> >>>
>> >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
>> >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
>> >> >> >>> seconds) done.
>> >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
>> >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
>> >> >> >>> tasks
>> >> >> >>> refusing to freeze, wq_busy=0):
>> >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297 
>> >> >> >>>  2 0x
>> >> >> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>> >> >> >>> 81044c29
>> >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>> >> >> >>> 880117ec5fd8
>> >> >> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>> >> >> >>> 88011fad4738
>> >> >> >>> +[  314.098873] Call Trace:
>> >> >> >>> +[  314.098881]  [] ? 
>> >> >> >>> default_spin_lock_flags+0x9/0x10
>> >> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>> >> >> >>> +[  314.09]  [] schedule+0x29/0x70
>> >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>> >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>> >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>> >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>> >> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>> >> >> >>> +[  314.098903]  [] 
>> >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
>> >> >> >>> +[  314.098906]  [] ? 
>> >> >> >>> autoremove_wake_function+0x40/0x40
>> >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>> >> >> >>> +[  314.098913]  []
>> >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>> >> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>> >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>> >> >> >>> +[  314.098923]  [] ? 
>> >> >> >>> try_to_del_timer_sync+0x4f/0x70
>> >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>> >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>> >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>> >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>> >> >> >>> +[  314.098933]  [] ? 
>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>> >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>> >> >> >>> +[  314.098938]  [] ? 
>> >> >> >>> flush_kthread_worker+0xb0/0xb0
>> >> >> >>> +[  314.098969]
>> >> >> >>> +[  314.098970] Restarting kernel threads ... done.
>> >> >> >>> +[  314.099052] Restarting tasks ... done.
>> >> >> >>>
>> >> >> >>> Please, have a lot at it.
>> >> >> >>
>> >> >> >> This is a freezer failure while freezing kernel threads, so I don't 
>> >> >> >> think it's
>> >> >> >> related to ACPI or PM directly.
>> >> >> >>
>> >> >> >> Does it happen on every suspend?
>> >> >> >>
>> >> >> >
>> >> >> > No, I only did one S/R.
>> >> >> >
>> >> >> > I have built a 2nd new kernel where I pulled-in latest 
>> >> >> > pm.git#linux-next.
>> >> >> > With this kernel two S/Rs were fine - but that says not much.
>> >> >> >
>> >> >>
>> >> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>> >> >>
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
>> >> >> ...
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
>> >> >> offline
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
>> >> >> local_softirq_pending 02
>> >> >> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
>> >> >> local_softirq_pending 02

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
> > On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
> >> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
> >> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
> >> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
> >> >> wrote:
> >> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
> >> >> > wrote:
> >> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> >> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
> >> >> >>>  wrote:
> >> >> >>> > Hi all,
> >> >> >>> >
> >> >> >>> > Changes since 20130117:
> >> >> >>> >
> >> >> >>> > Undropped tree: samung
> >> >> >>> >
> >> >> >>> > The powerpc tree still had a build failure.
> >> >> >>> >
> >> >> >>> > The driver-core tree gained a build failure for which I applied a 
> >> >> >>> > merge
> >> >> >>> > fix patch.
> >> >> >>> >
> >> >> >>> > The gpio-lw tree gained a build failure so I used the version from
> >> >> >>> > next-20130117.
> >> >> >>> >
> >> >> >>> > The samsung tree lost the majority of its conflicts but gained 
> >> >> >>> > more
> >> >> >>> > against the arm-soc and slave-dma tree.
> >> >> >>> >
> >> >> >>> > 
> >> >> >>> >
> >> >> >>>
> >> >> >>> From my dmesg diff-file:
> >> >> >>>
> >> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
> >> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
> >> >> >>> seconds) done.
> >> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
> >> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
> >> >> >>> tasks
> >> >> >>> refusing to freeze, wq_busy=0):
> >> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  
> >> >> >>> 2 0x
> >> >> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
> >> >> >>> 81044c29
> >> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
> >> >> >>> 880117ec5fd8
> >> >> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
> >> >> >>> 88011fad4738
> >> >> >>> +[  314.098873] Call Trace:
> >> >> >>> +[  314.098881]  [] ? 
> >> >> >>> default_spin_lock_flags+0x9/0x10
> >> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
> >> >> >>> +[  314.09]  [] schedule+0x29/0x70
> >> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
> >> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
> >> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
> >> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
> >> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
> >> >> >>> +[  314.098903]  [] 
> >> >> >>> out_of_line_wait_on_bit+0x7c/0x90
> >> >> >>> +[  314.098906]  [] ? 
> >> >> >>> autoremove_wake_function+0x40/0x40
> >> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
> >> >> >>> +[  314.098913]  []
> >> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
> >> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
> >> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
> >> >> >>> +[  314.098923]  [] ? 
> >> >> >>> try_to_del_timer_sync+0x4f/0x70
> >> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
> >> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
> >> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
> >> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
> >> >> >>> +[  314.098933]  [] ? 
> >> >> >>> flush_kthread_worker+0xb0/0xb0
> >> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
> >> >> >>> +[  314.098938]  [] ? 
> >> >> >>> flush_kthread_worker+0xb0/0xb0
> >> >> >>> +[  314.098969]
> >> >> >>> +[  314.098970] Restarting kernel threads ... done.
> >> >> >>> +[  314.099052] Restarting tasks ... done.
> >> >> >>>
> >> >> >>> Please, have a lot at it.
> >> >> >>
> >> >> >> This is a freezer failure while freezing kernel threads, so I don't 
> >> >> >> think it's
> >> >> >> related to ACPI or PM directly.
> >> >> >>
> >> >> >> Does it happen on every suspend?
> >> >> >>
> >> >> >
> >> >> > No, I only did one S/R.
> >> >> >
> >> >> > I have built a 2nd new kernel where I pulled-in latest 
> >> >> > pm.git#linux-next.
> >> >> > With this kernel two S/Rs were fine - but that says not much.
> >> >> >
> >> >>
> >> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
> >> >>
> >> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
> >> >> ...
> >> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
> >> >> offline
> >> >> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
> >> >> local_softirq_pending 02
> >> >> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
> >> >> local_softirq_pending 02
> >> >> Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
> >> >> offline
> >> >> Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
> >> >> offline
> 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki  wrote:
> On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
>> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
>> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
>> >> wrote:
>> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  
>> >> > wrote:
>> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>> >> >>>  wrote:
>> >> >>> > Hi all,
>> >> >>> >
>> >> >>> > Changes since 20130117:
>> >> >>> >
>> >> >>> > Undropped tree: samung
>> >> >>> >
>> >> >>> > The powerpc tree still had a build failure.
>> >> >>> >
>> >> >>> > The driver-core tree gained a build failure for which I applied a 
>> >> >>> > merge
>> >> >>> > fix patch.
>> >> >>> >
>> >> >>> > The gpio-lw tree gained a build failure so I used the version from
>> >> >>> > next-20130117.
>> >> >>> >
>> >> >>> > The samsung tree lost the majority of its conflicts but gained more
>> >> >>> > against the arm-soc and slave-dma tree.
>> >> >>> >
>> >> >>> > 
>> >> >>> >
>> >> >>>
>> >> >>> From my dmesg diff-file:
>> >> >>>
>> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
>> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
>> >> >>> seconds) done.
>> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
>> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
>> >> >>> refusing to freeze, wq_busy=0):
>> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
>> >> >>> 0x
>> >> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>> >> >>> 81044c29
>> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>> >> >>> 880117ec5fd8
>> >> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>> >> >>> 88011fad4738
>> >> >>> +[  314.098873] Call Trace:
>> >> >>> +[  314.098881]  [] ? 
>> >> >>> default_spin_lock_flags+0x9/0x10
>> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>> >> >>> +[  314.09]  [] schedule+0x29/0x70
>> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>> >> >>> +[  314.098903]  [] 
>> >> >>> out_of_line_wait_on_bit+0x7c/0x90
>> >> >>> +[  314.098906]  [] ? 
>> >> >>> autoremove_wake_function+0x40/0x40
>> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>> >> >>> +[  314.098913]  []
>> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>> >> >>> +[  314.098923]  [] ? 
>> >> >>> try_to_del_timer_sync+0x4f/0x70
>> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>> >> >>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
>> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>> >> >>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
>> >> >>> +[  314.098969]
>> >> >>> +[  314.098970] Restarting kernel threads ... done.
>> >> >>> +[  314.099052] Restarting tasks ... done.
>> >> >>>
>> >> >>> Please, have a lot at it.
>> >> >>
>> >> >> This is a freezer failure while freezing kernel threads, so I don't 
>> >> >> think it's
>> >> >> related to ACPI or PM directly.
>> >> >>
>> >> >> Does it happen on every suspend?
>> >> >>
>> >> >
>> >> > No, I only did one S/R.
>> >> >
>> >> > I have built a 2nd new kernel where I pulled-in latest 
>> >> > pm.git#linux-next.
>> >> > With this kernel two S/Rs were fine - but that says not much.
>> >> >
>> >>
>> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>> >>
>> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
>> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
>> >> offline
>> >> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 
>> >> 02
>> >> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 
>> >> 02
>> >> Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
>> >> offline
>> >> Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
>> >> offline
>> >
>> > Are you worried about the "local_softirq_pending" messages?
>> >
>>
>> That's the only new messages I have seen after several S/Rs.
>
> They are kind of unusual.
>
> Anyway, they seem to be related to CPU hotplug (CPU offline), so you can try
> if you can trigger them through the sysfs CPU offline/online interface.
>

Can you 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
> On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
> > On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
> >> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  
> >> wrote:
> >> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
> >> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> >> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
> >> >>>  wrote:
> >> >>> > Hi all,
> >> >>> >
> >> >>> > Changes since 20130117:
> >> >>> >
> >> >>> > Undropped tree: samung
> >> >>> >
> >> >>> > The powerpc tree still had a build failure.
> >> >>> >
> >> >>> > The driver-core tree gained a build failure for which I applied a 
> >> >>> > merge
> >> >>> > fix patch.
> >> >>> >
> >> >>> > The gpio-lw tree gained a build failure so I used the version from
> >> >>> > next-20130117.
> >> >>> >
> >> >>> > The samsung tree lost the majority of its conflicts but gained more
> >> >>> > against the arm-soc and slave-dma tree.
> >> >>> >
> >> >>> > 
> >> >>> >
> >> >>>
> >> >>> From my dmesg diff-file:
> >> >>>
> >> >>> +[  288.730849] PM: Syncing filesystems ... done.
> >> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 
> >> >>> seconds) done.
> >> >>> +[  294.097024] Freezing remaining freezable tasks ...
> >> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
> >> >>> refusing to freeze, wq_busy=0):
> >> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
> >> >>> 0x
> >> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
> >> >>> 81044c29
> >> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
> >> >>> 880117ec5fd8
> >> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
> >> >>> 88011fad4738
> >> >>> +[  314.098873] Call Trace:
> >> >>> +[  314.098881]  [] ? 
> >> >>> default_spin_lock_flags+0x9/0x10
> >> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
> >> >>> +[  314.09]  [] schedule+0x29/0x70
> >> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
> >> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
> >> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
> >> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
> >> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
> >> >>> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
> >> >>> +[  314.098906]  [] ? 
> >> >>> autoremove_wake_function+0x40/0x40
> >> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
> >> >>> +[  314.098913]  []
> >> >>> jbd2_journal_commit_transaction+0x1791/0x1960
> >> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
> >> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
> >> >>> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
> >> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
> >> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
> >> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
> >> >>> +[  314.098931]  [] kthread+0xc0/0xd0
> >> >>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
> >> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
> >> >>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
> >> >>> +[  314.098969]
> >> >>> +[  314.098970] Restarting kernel threads ... done.
> >> >>> +[  314.099052] Restarting tasks ... done.
> >> >>>
> >> >>> Please, have a lot at it.
> >> >>
> >> >> This is a freezer failure while freezing kernel threads, so I don't 
> >> >> think it's
> >> >> related to ACPI or PM directly.
> >> >>
> >> >> Does it happen on every suspend?
> >> >>
> >> >
> >> > No, I only did one S/R.
> >> >
> >> > I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
> >> > With this kernel two S/Rs were fine - but that says not much.
> >> >
> >>
> >> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
> >>
> >> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
> >> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
> >> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 
> >> 02
> >> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 
> >> 02
> >> Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
> >> Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline
> >
> > Are you worried about the "local_softirq_pending" messages?
> >
> 
> That's the only new messages I have seen after several S/Rs.

They are kind of unusual.

Anyway, they seem to be related to CPU hotplug (CPU offline), so you can try
if you can trigger them through the sysfs CPU offline/online interface.

> If you have a testcase for me to reproduce it here, I would be happy.

Do you mean the freezer-related issue?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki  wrote:
> On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
>> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  wrote:
>> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
>> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
>> >>>  wrote:
>> >>> > Hi all,
>> >>> >
>> >>> > Changes since 20130117:
>> >>> >
>> >>> > Undropped tree: samung
>> >>> >
>> >>> > The powerpc tree still had a build failure.
>> >>> >
>> >>> > The driver-core tree gained a build failure for which I applied a merge
>> >>> > fix patch.
>> >>> >
>> >>> > The gpio-lw tree gained a build failure so I used the version from
>> >>> > next-20130117.
>> >>> >
>> >>> > The samsung tree lost the majority of its conflicts but gained more
>> >>> > against the arm-soc and slave-dma tree.
>> >>> >
>> >>> > 
>> >>> >
>> >>>
>> >>> From my dmesg diff-file:
>> >>>
>> >>> +[  288.730849] PM: Syncing filesystems ... done.
>> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
>> >>> done.
>> >>> +[  294.097024] Freezing remaining freezable tasks ...
>> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
>> >>> refusing to freeze, wq_busy=0):
>> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
>> >>> 0x
>> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>> >>> 81044c29
>> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>> >>> 880117ec5fd8
>> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>> >>> 88011fad4738
>> >>> +[  314.098873] Call Trace:
>> >>> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
>> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>> >>> +[  314.09]  [] schedule+0x29/0x70
>> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>> >>> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
>> >>> +[  314.098906]  [] ? 
>> >>> autoremove_wake_function+0x40/0x40
>> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>> >>> +[  314.098913]  []
>> >>> jbd2_journal_commit_transaction+0x1791/0x1960
>> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>> >>> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
>> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
>> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>> >>> +[  314.098931]  [] kthread+0xc0/0xd0
>> >>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
>> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>> >>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
>> >>> +[  314.098969]
>> >>> +[  314.098970] Restarting kernel threads ... done.
>> >>> +[  314.099052] Restarting tasks ... done.
>> >>>
>> >>> Please, have a lot at it.
>> >>
>> >> This is a freezer failure while freezing kernel threads, so I don't think 
>> >> it's
>> >> related to ACPI or PM directly.
>> >>
>> >> Does it happen on every suspend?
>> >>
>> >
>> > No, I only did one S/R.
>> >
>> > I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
>> > With this kernel two S/Rs were fine - but that says not much.
>> >
>>
>> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
>>
>> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
>> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
>> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
>> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
>> Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
>> Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline
>
> Are you worried about the "local_softirq_pending" messages?
>

That's the only new messages I have seen after several S/Rs.
If you have a testcase for me to reproduce it here, I would be happy.

- Sedat -

> Rafael
>
>
> --
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:04 AM, Sedat Dilek  wrote:
> On Fri, Jan 18, 2013 at 11:54 PM, David Howells  wrote:
>> Sedat Dilek  wrote:
>>
>>> Culprit seems to be...
>>>
>>> commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
>>> "KEYS: Separate the kernel signature checking keyring from module signing"
>>
>> Try updating.  I pushed a new version out today.  This is now at commit ID
>> c82af351e270e0d95059d09a1975b61494fbbcd7.
>>
>
> Thanks for the information!
>
> OK, I see... s/select/depends on...
>
>  +config SYSTEM_TRUSTED_KEYRING
>  +  bool "Provide system-wide ring of trusted keys"
> -+  select KEYS
> ++  depends on KEYS
>
> That should fix it :-).
> I set SYSTEM_TRUSTED_KEYRING=y in kernel-config.
>
> BAD: 
> http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=patch;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e
>
> GOOD: 
> http://git.kernel.org/?p=linux/kernel/git/dhowells/linux-modsign.git;a=patch;h=c82af351e270e0d95059d09a1975b61494fbbcd7
>

I tried to revert the bad commit and replace it with the good one, but
this seems to be more work.
So, I fixed it up like in the attached patch.

- Sedat -

> - Sedat -
>
>> David


0001-KEYS-Fix-build-error-when-SYSTEM_TRUSTED_KEYRING-n.patch
Description: Binary data

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  wrote:
> > On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
> >> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> >>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
> >>> wrote:
> >>> > Hi all,
> >>> >
> >>> > Changes since 20130117:
> >>> >
> >>> > Undropped tree: samung
> >>> >
> >>> > The powerpc tree still had a build failure.
> >>> >
> >>> > The driver-core tree gained a build failure for which I applied a merge
> >>> > fix patch.
> >>> >
> >>> > The gpio-lw tree gained a build failure so I used the version from
> >>> > next-20130117.
> >>> >
> >>> > The samsung tree lost the majority of its conflicts but gained more
> >>> > against the arm-soc and slave-dma tree.
> >>> >
> >>> > 
> >>> >
> >>>
> >>> From my dmesg diff-file:
> >>>
> >>> +[  288.730849] PM: Syncing filesystems ... done.
> >>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
> >>> done.
> >>> +[  294.097024] Freezing remaining freezable tasks ...
> >>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
> >>> refusing to freeze, wq_busy=0):
> >>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
> >>> 0x
> >>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
> >>> 81044c29
> >>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
> >>> 880117ec5fd8
> >>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
> >>> 88011fad4738
> >>> +[  314.098873] Call Trace:
> >>> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
> >>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
> >>> +[  314.09]  [] schedule+0x29/0x70
> >>> +[  314.098890]  [] io_schedule+0x8f/0xd0
> >>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
> >>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
> >>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
> >>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
> >>> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
> >>> +[  314.098906]  [] ? autoremove_wake_function+0x40/0x40
> >>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
> >>> +[  314.098913]  []
> >>> jbd2_journal_commit_transaction+0x1791/0x1960
> >>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
> >>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
> >>> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
> >>> +[  314.098925]  [] kjournald2+0xb8/0x240
> >>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
> >>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
> >>> +[  314.098931]  [] kthread+0xc0/0xd0
> >>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
> >>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
> >>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
> >>> +[  314.098969]
> >>> +[  314.098970] Restarting kernel threads ... done.
> >>> +[  314.099052] Restarting tasks ... done.
> >>>
> >>> Please, have a lot at it.
> >>
> >> This is a freezer failure while freezing kernel threads, so I don't think 
> >> it's
> >> related to ACPI or PM directly.
> >>
> >> Does it happen on every suspend?
> >>
> >
> > No, I only did one S/R.
> >
> > I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
> > With this kernel two S/Rs were fine - but that says not much.
> >
> 
> After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:
> 
> Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
> Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
> Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
> Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
> Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
> Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline

Are you worried about the "local_softirq_pending" messages?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:54 PM, David Howells  wrote:
> Sedat Dilek  wrote:
>
>> Culprit seems to be...
>>
>> commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
>> "KEYS: Separate the kernel signature checking keyring from module signing"
>
> Try updating.  I pushed a new version out today.  This is now at commit ID
> c82af351e270e0d95059d09a1975b61494fbbcd7.
>

Thanks for the information!

OK, I see... s/select/depends on...

 +config SYSTEM_TRUSTED_KEYRING
 +  bool "Provide system-wide ring of trusted keys"
-+  select KEYS
++  depends on KEYS

That should fix it :-).
I set SYSTEM_TRUSTED_KEYRING=y in kernel-config.

BAD: 
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=patch;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e

GOOD: 
http://git.kernel.org/?p=linux/kernel/git/dhowells/linux-modsign.git;a=patch;h=c82af351e270e0d95059d09a1975b61494fbbcd7

- Sedat -

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

Re: linux-next: Tree for Jan 18 (powerclamp)

[Randy Dunlap]

On 01/17/13 20:37, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20130117:
> 


on i386;

drivers/built-in.o: In function `clamp_thread':
intel_powerclamp.c:(.text+0x2d39ae): undefined reference to `__udivdi3'
drivers/built-in.o: In function `poll_pkg_cstate':
intel_powerclamp.c:(.text+0x2d3bb9): undefined reference to `__udivdi3'



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

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:35:40 PM Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
> > On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> >> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
> >> wrote:
> >> > Hi all,
> >> >
> >> > Changes since 20130117:
> >> >
> >> > Undropped tree: samung
> >> >
> >> > The powerpc tree still had a build failure.
> >> >
> >> > The driver-core tree gained a build failure for which I applied a merge
> >> > fix patch.
> >> >
> >> > The gpio-lw tree gained a build failure so I used the version from
> >> > next-20130117.
> >> >
> >> > The samsung tree lost the majority of its conflicts but gained more
> >> > against the arm-soc and slave-dma tree.
> >> >
> >> > 
> >> >
> >>
> >> From my dmesg diff-file:
> >>
> >> +[  288.730849] PM: Syncing filesystems ... done.
> >> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
> >> done.
> >> +[  294.097024] Freezing remaining freezable tasks ...
> >> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
> >> refusing to freeze, wq_busy=0):
> >> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
> >> 0x
> >> +[  314.098865]  880117ec5b68 0046 880117ec5b08
> >> 81044c29
> >> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
> >> 880117ec5fd8
> >> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
> >> 88011fad4738
> >> +[  314.098873] Call Trace:
> >> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
> >> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
> >> +[  314.09]  [] schedule+0x29/0x70
> >> +[  314.098890]  [] io_schedule+0x8f/0xd0
> >> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
> >> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
> >> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
> >> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
> >> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
> >> +[  314.098906]  [] ? autoremove_wake_function+0x40/0x40
> >> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
> >> +[  314.098913]  []
> >> jbd2_journal_commit_transaction+0x1791/0x1960
> >> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
> >> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
> >> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
> >> +[  314.098925]  [] kjournald2+0xb8/0x240
> >> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
> >> +[  314.098929]  [] ? commit_timeout+0x10/0x10
> >> +[  314.098931]  [] kthread+0xc0/0xd0
> >> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
> >> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
> >> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
> >> +[  314.098969]
> >> +[  314.098970] Restarting kernel threads ... done.
> >> +[  314.099052] Restarting tasks ... done.
> >>
> >> Please, have a lot at it.
> >
> > This is a freezer failure while freezing kernel threads, so I don't think 
> > it's
> > related to ACPI or PM directly.
> >
> > Does it happen on every suspend?
> >
> 
> No, I only did one S/R.

Well, it would be good to try to reproduce it.

> I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
> With this kernel two S/Rs were fine - but that says not much.

The linux-pm.git tree doesn't contain any changes related to the freezer.

It most likely is something that removed a try_to_freeze() check from a
freezable kernel thread, but in that case the issue should be 100%
reproducible.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek  wrote:
> On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
>> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
>>> wrote:
>>> > Hi all,
>>> >
>>> > Changes since 20130117:
>>> >
>>> > Undropped tree: samung
>>> >
>>> > The powerpc tree still had a build failure.
>>> >
>>> > The driver-core tree gained a build failure for which I applied a merge
>>> > fix patch.
>>> >
>>> > The gpio-lw tree gained a build failure so I used the version from
>>> > next-20130117.
>>> >
>>> > The samsung tree lost the majority of its conflicts but gained more
>>> > against the arm-soc and slave-dma tree.
>>> >
>>> > 
>>> >
>>>
>>> From my dmesg diff-file:
>>>
>>> +[  288.730849] PM: Syncing filesystems ... done.
>>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
>>> done.
>>> +[  294.097024] Freezing remaining freezable tasks ...
>>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
>>> refusing to freeze, wq_busy=0):
>>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
>>> 0x
>>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>>> 81044c29
>>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>>> 880117ec5fd8
>>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>>> 88011fad4738
>>> +[  314.098873] Call Trace:
>>> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
>>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>>> +[  314.09]  [] schedule+0x29/0x70
>>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>>> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
>>> +[  314.098906]  [] ? autoremove_wake_function+0x40/0x40
>>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>>> +[  314.098913]  []
>>> jbd2_journal_commit_transaction+0x1791/0x1960
>>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>>> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
>>> +[  314.098925]  [] kjournald2+0xb8/0x240
>>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>>> +[  314.098931]  [] kthread+0xc0/0xd0
>>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
>>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
>>> +[  314.098969]
>>> +[  314.098970] Restarting kernel threads ... done.
>>> +[  314.099052] Restarting tasks ... done.
>>>
>>> Please, have a lot at it.
>>
>> This is a freezer failure while freezing kernel threads, so I don't think 
>> it's
>> related to ACPI or PM directly.
>>
>> Does it happen on every suspend?
>>
>
> No, I only did one S/R.
>
> I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
> With this kernel two S/Rs were fine - but that says not much.
>

After several S/Rs on the "buggy" -1 kernel I know see in my syslogs:

Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline

- Sedat -

> - Sedat -
>
>> Rafael
>>
>>
>> --
>> I speak only for myself.
>> Rafael J. Wysocki, Intel Open Source Technology Center.


dmesg-3.diff
Description: Binary data

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[David Howells]

Sedat Dilek  wrote:

> Culprit seems to be...
> 
> commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
> "KEYS: Separate the kernel signature checking keyring from module signing"

Try updating.  I pushed a new version out today.  This is now at commit ID
c82af351e270e0d95059d09a1975b61494fbbcd7.

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

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki  wrote:
> On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
>> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
>> wrote:
>> > Hi all,
>> >
>> > Changes since 20130117:
>> >
>> > Undropped tree: samung
>> >
>> > The powerpc tree still had a build failure.
>> >
>> > The driver-core tree gained a build failure for which I applied a merge
>> > fix patch.
>> >
>> > The gpio-lw tree gained a build failure so I used the version from
>> > next-20130117.
>> >
>> > The samsung tree lost the majority of its conflicts but gained more
>> > against the arm-soc and slave-dma tree.
>> >
>> > 
>> >
>>
>> From my dmesg diff-file:
>>
>> +[  288.730849] PM: Syncing filesystems ... done.
>> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
>> done.
>> +[  294.097024] Freezing remaining freezable tasks ...
>> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
>> refusing to freeze, wq_busy=0):
>> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
>> 0x
>> +[  314.098865]  880117ec5b68 0046 880117ec5b08
>> 81044c29
>> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
>> 880117ec5fd8
>> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
>> 88011fad4738
>> +[  314.098873] Call Trace:
>> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
>> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
>> +[  314.09]  [] schedule+0x29/0x70
>> +[  314.098890]  [] io_schedule+0x8f/0xd0
>> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
>> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
>> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
>> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
>> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
>> +[  314.098906]  [] ? autoremove_wake_function+0x40/0x40
>> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
>> +[  314.098913]  []
>> jbd2_journal_commit_transaction+0x1791/0x1960
>> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
>> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
>> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
>> +[  314.098925]  [] kjournald2+0xb8/0x240
>> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
>> +[  314.098929]  [] ? commit_timeout+0x10/0x10
>> +[  314.098931]  [] kthread+0xc0/0xd0
>> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
>> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
>> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
>> +[  314.098969]
>> +[  314.098970] Restarting kernel threads ... done.
>> +[  314.099052] Restarting tasks ... done.
>>
>> Please, have a lot at it.
>
> This is a freezer failure while freezing kernel threads, so I don't think it's
> related to ACPI or PM directly.
>
> Does it happen on every suspend?
>

No, I only did one S/R.

I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.

- Sedat -

> Rafael
>
>
> --
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.


dmesg-2.diff
Description: Binary data

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
> wrote:
> > Hi all,
> >
> > Changes since 20130117:
> >
> > Undropped tree: samung
> >
> > The powerpc tree still had a build failure.
> >
> > The driver-core tree gained a build failure for which I applied a merge
> > fix patch.
> >
> > The gpio-lw tree gained a build failure so I used the version from
> > next-20130117.
> >
> > The samsung tree lost the majority of its conflicts but gained more
> > against the arm-soc and slave-dma tree.
> >
> > 
> >
> 
> From my dmesg diff-file:
> 
> +[  288.730849] PM: Syncing filesystems ... done.
> +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) done.
> +[  294.097024] Freezing remaining freezable tasks ...
> +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
> refusing to freeze, wq_busy=0):
> +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
> 0x
> +[  314.098865]  880117ec5b68 0046 880117ec5b08
> 81044c29
> +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
> 880117ec5fd8
> +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
> 88011fad4738
> +[  314.098873] Call Trace:
> +[  314.098881]  [] ? default_spin_lock_flags+0x9/0x10
> +[  314.098885]  [] ? __wait_on_buffer+0x30/0x30
> +[  314.09]  [] schedule+0x29/0x70
> +[  314.098890]  [] io_schedule+0x8f/0xd0
> +[  314.098892]  [] sleep_on_buffer+0xe/0x20
> +[  314.098896]  [] __wait_on_bit+0x5f/0x90
> +[  314.098898]  [] ? submit_bh+0x121/0x1e0
> +[  314.098900]  [] ? __wait_on_buffer+0x30/0x30
> +[  314.098903]  [] out_of_line_wait_on_bit+0x7c/0x90
> +[  314.098906]  [] ? autoremove_wake_function+0x40/0x40
> +[  314.098909]  [] __wait_on_buffer+0x2e/0x30
> +[  314.098913]  []
> jbd2_journal_commit_transaction+0x1791/0x1960
> +[  314.098917]  [] ? sched_clock_cpu+0xbd/0x110
> +[  314.098920]  [] ? add_wait_queue+0x60/0x60
> +[  314.098923]  [] ? try_to_del_timer_sync+0x4f/0x70
> +[  314.098925]  [] kjournald2+0xb8/0x240
> +[  314.098927]  [] ? add_wait_queue+0x60/0x60
> +[  314.098929]  [] ? commit_timeout+0x10/0x10
> +[  314.098931]  [] kthread+0xc0/0xd0
> +[  314.098933]  [] ? flush_kthread_worker+0xb0/0xb0
> +[  314.098936]  [] ret_from_fork+0x7c/0xb0
> +[  314.098938]  [] ? flush_kthread_worker+0xb0/0xb0
> +[  314.098969]
> +[  314.098970] Restarting kernel threads ... done.
> +[  314.099052] Restarting tasks ... done.
> 
> Please, have a lot at it.

This is a freezer failure while freezing kernel threads, so I don't think it's
related to ACPI or PM directly.

Does it happen on every suspend?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 10:43 PM, Sedat Dilek  wrote:
> On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  
> wrote:
>> Hi all,
>>
>> Changes since 20130117:
>>
>> Undropped tree: samung
>>
>> The powerpc tree still had a build failure.
>>
>> The driver-core tree gained a build failure for which I applied a merge
>> fix patch.
>>
>> The gpio-lw tree gained a build failure so I used the version from
>> next-20130117.
>>
>> The samsung tree lost the majority of its conflicts but gained more
>> against the arm-soc and slave-dma tree.
>>
>> 
>>
>
> I pulled Linux v3.8-rc4 (one commit) into next-20130118.
>
> When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:
>
>   CC  security/keys/keyring.o
>   CC  kernel/module_signing.o
>   CC [M]  arch/x86/kvm/i8259.o
> kernel/module_signing.c: In function 'request_asymmetric_key':
> kernel/module_signing.c:161:36: error: 'system_trusted_keyring'
> undeclared (first use in this function)
> kernel/module_signing.c:161:36: note: each undeclared identifier is
> reported only once for each function it appears in
> make[3]: *** [kernel/module_signing.o] Error 1
> make[2]: *** [kernel] Error 2
> make[2]: *** Waiting for unfinished jobs
>

Culprit seems to be...

commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
"KEYS: Separate the kernel signature checking keyring from module signing"

- Sedat -

[1] 
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell  wrote:
> Hi all,
>
> Changes since 20130117:
>
> Undropped tree: samung
>
> The powerpc tree still had a build failure.
>
> The driver-core tree gained a build failure for which I applied a merge
> fix patch.
>
> The gpio-lw tree gained a build failure so I used the version from
> next-20130117.
>
> The samsung tree lost the majority of its conflicts but gained more
> against the arm-soc and slave-dma tree.
>
> 
>

I pulled Linux v3.8-rc4 (one commit) into next-20130118.

When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:

  CC  security/keys/keyring.o
  CC  kernel/module_signing.o
  CC [M]  arch/x86/kvm/i8259.o
kernel/module_signing.c: In function 'request_asymmetric_key':
kernel/module_signing.c:161:36: error: 'system_trusted_keyring'
undeclared (first use in this function)
kernel/module_signing.c:161:36: note: each undeclared identifier is
reported only once for each function it appears in
make[3]: *** [kernel/module_signing.o] Error 1
make[2]: *** [kernel] Error 2
make[2]: *** Waiting for unfinished jobs

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

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained more
 against the arm-soc and slave-dma tree.

 


I pulled Linux v3.8-rc4 (one commit) into next-20130118.

When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:

  CC  security/keys/keyring.o
  CC  kernel/module_signing.o
  CC [M]  arch/x86/kvm/i8259.o
kernel/module_signing.c: In function 'request_asymmetric_key':
kernel/module_signing.c:161:36: error: 'system_trusted_keyring'
undeclared (first use in this function)
kernel/module_signing.c:161:36: note: each undeclared identifier is
reported only once for each function it appears in
make[3]: *** [kernel/module_signing.o] Error 1
make[2]: *** [kernel] Error 2
make[2]: *** Waiting for unfinished jobs

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

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 10:43 PM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
 wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained more
 against the arm-soc and slave-dma tree.

 


 I pulled Linux v3.8-rc4 (one commit) into next-20130118.

 When CONFIG_SYSTEM_TRUSTED_KEYRING=n I see these error-messages on AMD64:

   CC  security/keys/keyring.o
   CC  kernel/module_signing.o
   CC [M]  arch/x86/kvm/i8259.o
 kernel/module_signing.c: In function 'request_asymmetric_key':
 kernel/module_signing.c:161:36: error: 'system_trusted_keyring'
 undeclared (first use in this function)
 kernel/module_signing.c:161:36: note: each undeclared identifier is
 reported only once for each function it appears in
 make[3]: *** [kernel/module_signing.o] Error 1
 make[2]: *** [kernel] Error 2
 make[2]: *** Waiting for unfinished jobs


Culprit seems to be...

commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
KEYS: Separate the kernel signature checking keyring from module signing

- Sedat -

[1] 
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=commitdiff;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
 wrote:
  Hi all,
 
  Changes since 20130117:
 
  Undropped tree: samung
 
  The powerpc tree still had a build failure.
 
  The driver-core tree gained a build failure for which I applied a merge
  fix patch.
 
  The gpio-lw tree gained a build failure so I used the version from
  next-20130117.
 
  The samsung tree lost the majority of its conflicts but gained more
  against the arm-soc and slave-dma tree.
 
  
 
 
 From my dmesg diff-file:
 
 +[  288.730849] PM: Syncing filesystems ... done.
 +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) done.
 +[  294.097024] Freezing remaining freezable tasks ...
 +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
 refusing to freeze, wq_busy=0):
 +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
 0x
 +[  314.098865]  880117ec5b68 0046 880117ec5b08
 81044c29
 +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
 880117ec5fd8
 +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
 88011fad4738
 +[  314.098873] Call Trace:
 +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
 +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.09]  [816b4b59] schedule+0x29/0x70
 +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
 +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
 +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
 +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
 +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
 +[  314.098906]  [8107eb00] ? autoremove_wake_function+0x40/0x40
 +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
 +[  314.098913]  [8128a6a1]
 jbd2_journal_commit_transaction+0x1791/0x1960
 +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
 +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
 +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
 +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
 +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
 +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
 +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098969]
 +[  314.098970] Restarting kernel threads ... done.
 +[  314.099052] Restarting tasks ... done.
 
 Please, have a lot at it.

This is a freezer failure while freezing kernel threads, so I don't think it's
related to ACPI or PM directly.

Does it happen on every suspend?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
 wrote:
  Hi all,
 
  Changes since 20130117:
 
  Undropped tree: samung
 
  The powerpc tree still had a build failure.
 
  The driver-core tree gained a build failure for which I applied a merge
  fix patch.
 
  The gpio-lw tree gained a build failure so I used the version from
  next-20130117.
 
  The samsung tree lost the majority of its conflicts but gained more
  against the arm-soc and slave-dma tree.
 
  
 

 From my dmesg diff-file:

 +[  288.730849] PM: Syncing filesystems ... done.
 +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
 done.
 +[  294.097024] Freezing remaining freezable tasks ...
 +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
 refusing to freeze, wq_busy=0):
 +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
 0x
 +[  314.098865]  880117ec5b68 0046 880117ec5b08
 81044c29
 +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
 880117ec5fd8
 +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
 88011fad4738
 +[  314.098873] Call Trace:
 +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
 +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.09]  [816b4b59] schedule+0x29/0x70
 +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
 +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
 +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
 +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
 +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
 +[  314.098906]  [8107eb00] ? autoremove_wake_function+0x40/0x40
 +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
 +[  314.098913]  [8128a6a1]
 jbd2_journal_commit_transaction+0x1791/0x1960
 +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
 +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
 +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
 +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
 +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
 +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
 +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098969]
 +[  314.098970] Restarting kernel threads ... done.
 +[  314.099052] Restarting tasks ... done.

 Please, have a lot at it.

 This is a freezer failure while freezing kernel threads, so I don't think it's
 related to ACPI or PM directly.

 Does it happen on every suspend?


No, I only did one S/R.

I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.

- Sedat -

 Rafael


 --
 I speak only for myself.
 Rafael J. Wysocki, Intel Open Source Technology Center.


dmesg-2.diff
Description: Binary data

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[David Howells]

Sedat Dilek sedat.di...@gmail.com wrote:

 Culprit seems to be...
 
 commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
 KEYS: Separate the kernel signature checking keyring from module signing

Try updating.  I pushed a new version out today.  This is now at commit ID
c82af351e270e0d95059d09a1975b61494fbbcd7.

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

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
 wrote:
  Hi all,
 
  Changes since 20130117:
 
  Undropped tree: samung
 
  The powerpc tree still had a build failure.
 
  The driver-core tree gained a build failure for which I applied a merge
  fix patch.
 
  The gpio-lw tree gained a build failure so I used the version from
  next-20130117.
 
  The samsung tree lost the majority of its conflicts but gained more
  against the arm-soc and slave-dma tree.
 
  
 

 From my dmesg diff-file:

 +[  288.730849] PM: Syncing filesystems ... done.
 +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
 done.
 +[  294.097024] Freezing remaining freezable tasks ...
 +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
 refusing to freeze, wq_busy=0):
 +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
 0x
 +[  314.098865]  880117ec5b68 0046 880117ec5b08
 81044c29
 +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
 880117ec5fd8
 +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
 88011fad4738
 +[  314.098873] Call Trace:
 +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
 +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.09]  [816b4b59] schedule+0x29/0x70
 +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
 +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
 +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
 +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
 +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
 +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
 +[  314.098906]  [8107eb00] ? autoremove_wake_function+0x40/0x40
 +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
 +[  314.098913]  [8128a6a1]
 jbd2_journal_commit_transaction+0x1791/0x1960
 +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
 +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
 +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
 +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
 +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
 +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
 +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
 +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
 +[  314.098969]
 +[  314.098970] Restarting kernel threads ... done.
 +[  314.099052] Restarting tasks ... done.

 Please, have a lot at it.

 This is a freezer failure while freezing kernel threads, so I don't think 
 it's
 related to ACPI or PM directly.

 Does it happen on every suspend?


 No, I only did one S/R.

 I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
 With this kernel two S/Rs were fine - but that says not much.


After several S/Rs on the buggy -1 kernel I know see in my syslogs:

Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline

- Sedat -

 - Sedat -

 Rafael


 --
 I speak only for myself.
 Rafael J. Wysocki, Intel Open Source Technology Center.


dmesg-3.diff
Description: Binary data

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:35:40 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
  On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
  wrote:
   Hi all,
  
   Changes since 20130117:
  
   Undropped tree: samung
  
   The powerpc tree still had a build failure.
  
   The driver-core tree gained a build failure for which I applied a merge
   fix patch.
  
   The gpio-lw tree gained a build failure so I used the version from
   next-20130117.
  
   The samsung tree lost the majority of its conflicts but gained more
   against the arm-soc and slave-dma tree.
  
   
  
 
  From my dmesg diff-file:
 
  +[  288.730849] PM: Syncing filesystems ... done.
  +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
  done.
  +[  294.097024] Freezing remaining freezable tasks ...
  +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
  refusing to freeze, wq_busy=0):
  +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
  0x
  +[  314.098865]  880117ec5b68 0046 880117ec5b08
  81044c29
  +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
  880117ec5fd8
  +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
  88011fad4738
  +[  314.098873] Call Trace:
  +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
  +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.09]  [816b4b59] schedule+0x29/0x70
  +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
  +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
  +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
  +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
  +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
  +[  314.098906]  [8107eb00] ? autoremove_wake_function+0x40/0x40
  +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
  +[  314.098913]  [8128a6a1]
  jbd2_journal_commit_transaction+0x1791/0x1960
  +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
  +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
  +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
  +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
  +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
  +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
  +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098969]
  +[  314.098970] Restarting kernel threads ... done.
  +[  314.099052] Restarting tasks ... done.
 
  Please, have a lot at it.
 
  This is a freezer failure while freezing kernel threads, so I don't think 
  it's
  related to ACPI or PM directly.
 
  Does it happen on every suspend?
 
 
 No, I only did one S/R.

Well, it would be good to try to reproduce it.

 I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
 With this kernel two S/Rs were fine - but that says not much.

The linux-pm.git tree doesn't contain any changes related to the freezer.

It most likely is something that removed a try_to_freeze() check from a
freezable kernel thread, but in that case the issue should be 100%
reproducible.

Thanks,
Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 (powerclamp)

[Randy Dunlap]

On 01/17/13 20:37, Stephen Rothwell wrote:
 Hi all,
 
 Changes since 20130117:
 


on i386;

drivers/built-in.o: In function `clamp_thread':
intel_powerclamp.c:(.text+0x2d39ae): undefined reference to `__udivdi3'
drivers/built-in.o: In function `poll_pkg_cstate':
intel_powerclamp.c:(.text+0x2d3bb9): undefined reference to `__udivdi3'



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

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Fri, Jan 18, 2013 at 11:54 PM, David Howells dhowe...@redhat.com wrote:
 Sedat Dilek sedat.di...@gmail.com wrote:

 Culprit seems to be...

 commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
 KEYS: Separate the kernel signature checking keyring from module signing

 Try updating.  I pushed a new version out today.  This is now at commit ID
 c82af351e270e0d95059d09a1975b61494fbbcd7.


Thanks for the information!

OK, I see... s/select/depends on...

 +config SYSTEM_TRUSTED_KEYRING
 +  bool Provide system-wide ring of trusted keys
-+  select KEYS
++  depends on KEYS

That should fix it :-).
I set SYSTEM_TRUSTED_KEYRING=y in kernel-config.

BAD: 
http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=patch;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e

GOOD: 
http://git.kernel.org/?p=linux/kernel/git/dhowells/linux-modsign.git;a=patch;h=c82af351e270e0d95059d09a1975b61494fbbcd7

- Sedat -

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

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com wrote:
  On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
  On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell s...@canb.auug.org.au 
  wrote:
   Hi all,
  
   Changes since 20130117:
  
   Undropped tree: samung
  
   The powerpc tree still had a build failure.
  
   The driver-core tree gained a build failure for which I applied a merge
   fix patch.
  
   The gpio-lw tree gained a build failure so I used the version from
   next-20130117.
  
   The samsung tree lost the majority of its conflicts but gained more
   against the arm-soc and slave-dma tree.
  
   
  
 
  From my dmesg diff-file:
 
  +[  288.730849] PM: Syncing filesystems ... done.
  +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
  done.
  +[  294.097024] Freezing remaining freezable tasks ...
  +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
  refusing to freeze, wq_busy=0):
  +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
  0x
  +[  314.098865]  880117ec5b68 0046 880117ec5b08
  81044c29
  +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
  880117ec5fd8
  +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
  88011fad4738
  +[  314.098873] Call Trace:
  +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
  +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.09]  [816b4b59] schedule+0x29/0x70
  +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
  +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
  +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
  +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
  +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
  +[  314.098906]  [8107eb00] ? autoremove_wake_function+0x40/0x40
  +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
  +[  314.098913]  [8128a6a1]
  jbd2_journal_commit_transaction+0x1791/0x1960
  +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
  +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
  +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
  +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
  +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
  +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
  +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098969]
  +[  314.098970] Restarting kernel threads ... done.
  +[  314.099052] Restarting tasks ... done.
 
  Please, have a lot at it.
 
  This is a freezer failure while freezing kernel threads, so I don't think 
  it's
  related to ACPI or PM directly.
 
  Does it happen on every suspend?
 
 
  No, I only did one S/R.
 
  I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
  With this kernel two S/Rs were fine - but that says not much.
 
 
 After several S/Rs on the buggy -1 kernel I know see in my syslogs:
 
 Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
 Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
 Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
 Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
 Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
 Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline

Are you worried about the local_softirq_pending messages?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [MODSIGN: KEYS:]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:04 AM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Fri, Jan 18, 2013 at 11:54 PM, David Howells dhowe...@redhat.com wrote:
 Sedat Dilek sedat.di...@gmail.com wrote:

 Culprit seems to be...

 commit d6941c0c6bd42c725e45240a86c4add92e9bfb3e
 KEYS: Separate the kernel signature checking keyring from module signing

 Try updating.  I pushed a new version out today.  This is now at commit ID
 c82af351e270e0d95059d09a1975b61494fbbcd7.


 Thanks for the information!

 OK, I see... s/select/depends on...

  +config SYSTEM_TRUSTED_KEYRING
  +  bool Provide system-wide ring of trusted keys
 -+  select KEYS
 ++  depends on KEYS

 That should fix it :-).
 I set SYSTEM_TRUSTED_KEYRING=y in kernel-config.

 BAD: 
 http://git.kernel.org/?p=linux/kernel/git/next/linux-next.git;a=patch;h=d6941c0c6bd42c725e45240a86c4add92e9bfb3e

 GOOD: 
 http://git.kernel.org/?p=linux/kernel/git/dhowells/linux-modsign.git;a=patch;h=c82af351e270e0d95059d09a1975b61494fbbcd7


I tried to revert the bad commit and replace it with the good one, but
this seems to be more work.
So, I fixed it up like in the attached patch.

- Sedat -

 - Sedat -

 David


0001-KEYS-Fix-build-error-when-SYSTEM_TRUSTED_KEYRING-n.patch
Description: Binary data

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
 On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com wrote:
  On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
  On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
  s...@canb.auug.org.au wrote:
   Hi all,
  
   Changes since 20130117:
  
   Undropped tree: samung
  
   The powerpc tree still had a build failure.
  
   The driver-core tree gained a build failure for which I applied a merge
   fix patch.
  
   The gpio-lw tree gained a build failure so I used the version from
   next-20130117.
  
   The samsung tree lost the majority of its conflicts but gained more
   against the arm-soc and slave-dma tree.
  
   
  
 
  From my dmesg diff-file:
 
  +[  288.730849] PM: Syncing filesystems ... done.
  +[  294.050498] Freezing user space processes ... (elapsed 0.04 seconds) 
  done.
  +[  294.097024] Freezing remaining freezable tasks ...
  +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
  refusing to freeze, wq_busy=0):
  +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
  0x
  +[  314.098865]  880117ec5b68 0046 880117ec5b08
  81044c29
  +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
  880117ec5fd8
  +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
  88011fad4738
  +[  314.098873] Call Trace:
  +[  314.098881]  [81044c29] ? default_spin_lock_flags+0x9/0x10
  +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.09]  [816b4b59] schedule+0x29/0x70
  +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
  +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
  +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
  +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
  +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
  +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
  +[  314.098906]  [8107eb00] ? 
  autoremove_wake_function+0x40/0x40
  +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
  +[  314.098913]  [8128a6a1]
  jbd2_journal_commit_transaction+0x1791/0x1960
  +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
  +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
  +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
  +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
  +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
  +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
  +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
  +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
  +[  314.098969]
  +[  314.098970] Restarting kernel threads ... done.
  +[  314.099052] Restarting tasks ... done.
 
  Please, have a lot at it.
 
  This is a freezer failure while freezing kernel threads, so I don't think 
  it's
  related to ACPI or PM directly.
 
  Does it happen on every suspend?
 
 
  No, I only did one S/R.
 
  I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
  With this kernel two S/Rs were fine - but that says not much.
 

 After several S/Rs on the buggy -1 kernel I know see in my syslogs:

 Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
 Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
 Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 02
 Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 02
 Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
 Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline

 Are you worried about the local_softirq_pending messages?


That's the only new messages I have seen after several S/Rs.
If you have a testcase for me to reproduce it here, I would be happy.

- Sedat -

 Rafael


 --
 I speak only for myself.
 Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
  On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
  wrote:
   On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
   s...@canb.auug.org.au wrote:
Hi all,
   
Changes since 20130117:
   
Undropped tree: samung
   
The powerpc tree still had a build failure.
   
The driver-core tree gained a build failure for which I applied a 
merge
fix patch.
   
The gpio-lw tree gained a build failure so I used the version from
next-20130117.
   
The samsung tree lost the majority of its conflicts but gained more
against the arm-soc and slave-dma tree.
   

   
  
   From my dmesg diff-file:
  
   +[  288.730849] PM: Syncing filesystems ... done.
   +[  294.050498] Freezing user space processes ... (elapsed 0.04 
   seconds) done.
   +[  294.097024] Freezing remaining freezable tasks ...
   +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
   refusing to freeze, wq_busy=0):
   +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
   0x
   +[  314.098865]  880117ec5b68 0046 880117ec5b08
   81044c29
   +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
   880117ec5fd8
   +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
   88011fad4738
   +[  314.098873] Call Trace:
   +[  314.098881]  [81044c29] ? 
   default_spin_lock_flags+0x9/0x10
   +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
   +[  314.09]  [816b4b59] schedule+0x29/0x70
   +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
   +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
   +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
   +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
   +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
   +[  314.098903]  [816b34dc] out_of_line_wait_on_bit+0x7c/0x90
   +[  314.098906]  [8107eb00] ? 
   autoremove_wake_function+0x40/0x40
   +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
   +[  314.098913]  [8128a6a1]
   jbd2_journal_commit_transaction+0x1791/0x1960
   +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
   +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
   +[  314.098923]  [81069fbf] ? try_to_del_timer_sync+0x4f/0x70
   +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
   +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
   +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
   +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
   +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
   +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
   +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
   +[  314.098969]
   +[  314.098970] Restarting kernel threads ... done.
   +[  314.099052] Restarting tasks ... done.
  
   Please, have a lot at it.
  
   This is a freezer failure while freezing kernel threads, so I don't 
   think it's
   related to ACPI or PM directly.
  
   Does it happen on every suspend?
  
  
   No, I only did one S/R.
  
   I have built a 2nd new kernel where I pulled-in latest pm.git#linux-next.
   With this kernel two S/Rs were fine - but that says not much.
  
 
  After several S/Rs on the buggy -1 kernel I know see in my syslogs:
 
  Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
  Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now offline
  Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 
  02
  Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 
  02
  Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now offline
  Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now offline
 
  Are you worried about the local_softirq_pending messages?
 
 
 That's the only new messages I have seen after several S/Rs.

They are kind of unusual.

Anyway, they seem to be related to CPU hotplug (CPU offline), so you can try
if you can trigger them through the sysfs CPU offline/online interface.

 If you have a testcase for me to reproduce it here, I would be happy.

Do you mean the freezer-related issue?

Rafael


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at  

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
  On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
  wrote:
   On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
   wrote:
   On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
   s...@canb.auug.org.au wrote:
Hi all,
   
Changes since 20130117:
   
Undropped tree: samung
   
The powerpc tree still had a build failure.
   
The driver-core tree gained a build failure for which I applied a 
merge
fix patch.
   
The gpio-lw tree gained a build failure so I used the version from
next-20130117.
   
The samsung tree lost the majority of its conflicts but gained more
against the arm-soc and slave-dma tree.
   

   
  
   From my dmesg diff-file:
  
   +[  288.730849] PM: Syncing filesystems ... done.
   +[  294.050498] Freezing user space processes ... (elapsed 0.04 
   seconds) done.
   +[  294.097024] Freezing remaining freezable tasks ...
   +[  314.098849] Freezing of tasks failed after 20.01 seconds (1 tasks
   refusing to freeze, wq_busy=0):
   +[  314.098862] jbd2/loop0-8D 8180d780 0   297  2 
   0x
   +[  314.098865]  880117ec5b68 0046 880117ec5b08
   81044c29
   +[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
   880117ec5fd8
   +[  314.098871]  880119b34560 88011829dc80 880117ec5b68
   88011fad4738
   +[  314.098873] Call Trace:
   +[  314.098881]  [81044c29] ? 
   default_spin_lock_flags+0x9/0x10
   +[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
   +[  314.09]  [816b4b59] schedule+0x29/0x70
   +[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
   +[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
   +[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
   +[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
   +[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
   +[  314.098903]  [816b34dc] 
   out_of_line_wait_on_bit+0x7c/0x90
   +[  314.098906]  [8107eb00] ? 
   autoremove_wake_function+0x40/0x40
   +[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
   +[  314.098913]  [8128a6a1]
   jbd2_journal_commit_transaction+0x1791/0x1960
   +[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
   +[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
   +[  314.098923]  [81069fbf] ? 
   try_to_del_timer_sync+0x4f/0x70
   +[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
   +[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
   +[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
   +[  314.098931]  [8107ded0] kthread+0xc0/0xd0
   +[  314.098933]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
   +[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
   +[  314.098938]  [8107de10] ? flush_kthread_worker+0xb0/0xb0
   +[  314.098969]
   +[  314.098970] Restarting kernel threads ... done.
   +[  314.099052] Restarting tasks ... done.
  
   Please, have a lot at it.
  
   This is a freezer failure while freezing kernel threads, so I don't 
   think it's
   related to ACPI or PM directly.
  
   Does it happen on every suspend?
  
  
   No, I only did one S/R.
  
   I have built a 2nd new kernel where I pulled-in latest 
   pm.git#linux-next.
   With this kernel two S/Rs were fine - but that says not much.
  
 
  After several S/Rs on the buggy -1 kernel I know see in my syslogs:
 
  Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs ...
  Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
  offline
  Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: local_softirq_pending 
  02
  Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: local_softirq_pending 
  02
  Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
  offline
  Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
  offline
 
  Are you worried about the local_softirq_pending messages?
 

 That's the only new messages I have seen after several S/Rs.

 They are kind of unusual.

 Anyway, they seem to be related to CPU hotplug (CPU offline), so you can try
 if you can trigger them through the sysfs CPU offline/online interface.


Can you explain that a bit clearer or give some sample lines for testing?

 If you have a testcase for me to reproduce it here, I would be happy.

 Do you mean the freezer-related issue?


Any one as I am still stepping in the dark.
I checked my disc-space as I built a lot of software today 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Rafael J. Wysocki]

On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
   wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied a 
 merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297  
2 0x
+[  314.098865]  880117ec5b68 0046 880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I don't 
think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
   ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are kind of unusual.
 
  Anyway, they seem to be related to CPU hotplug (CPU offline), so you can try
  if you can trigger them through the sysfs CPU offline/online interface.
 
 
 Can you explain that a bit clearer or give some sample lines for testing?

There is a 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
   wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied 
 a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version 
 from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297 
 2 0x
+[  314.098865]  880117ec5b68 0046 880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I don't 
think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
   ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are kind of unusual.
 
  Anyway, they seem to be related to CPU hotplug (CPU offline), so you can 
  try
  if you can trigger them through the sysfs CPU offline/online interface.
 

 Can 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 1:00 AM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
   wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied 
 a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version 
 from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297
  2 0x
+[  314.098865]  880117ec5b68 0046 
880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 
880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 
880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I 
don't think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
   ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are kind of unusual.
 
  Anyway, they seem to be related to CPU hotplug (CPU offline), so you can 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
   wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied 
 a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version 
 from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297 
 2 0x
+[  314.098865]  880117ec5b68 0046 880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I don't 
think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
   ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are kind of unusual.
 
  Anyway, they seem to be related to CPU hotplug (CPU offline), so you can 
  try
  if you can trigger them through the sysfs CPU offline/online interface.
 

 Can 

Re: linux-next: Tree for Jan 18 [ BROKEN suspend: jbd2|acpi|pm? ]

[Sedat Dilek]

On Sat, Jan 19, 2013 at 2:55 AM, Sedat Dilek sedat.di...@gmail.com wrote:
 On Sat, Jan 19, 2013 at 12:58 AM, Rafael J. Wysocki r...@sisk.pl wrote:
 On Saturday, January 19, 2013 12:41:11 AM Sedat Dilek wrote:
 On Sat, Jan 19, 2013 at 12:39 AM, Rafael J. Wysocki r...@sisk.pl wrote:
  On Saturday, January 19, 2013 12:28:55 AM Sedat Dilek wrote:
  On Sat, Jan 19, 2013 at 12:25 AM, Rafael J. Wysocki r...@sisk.pl wrote:
   On Friday, January 18, 2013 11:56:53 PM Sedat Dilek wrote:
   On Fri, Jan 18, 2013 at 11:35 PM, Sedat Dilek sedat.di...@gmail.com 
   wrote:
On Fri, Jan 18, 2013 at 11:20 PM, Rafael J. Wysocki r...@sisk.pl 
wrote:
On Friday, January 18, 2013 11:11:07 PM Sedat Dilek wrote:
On Fri, Jan 18, 2013 at 5:37 AM, Stephen Rothwell 
s...@canb.auug.org.au wrote:
 Hi all,

 Changes since 20130117:

 Undropped tree: samung

 The powerpc tree still had a build failure.

 The driver-core tree gained a build failure for which I applied 
 a merge
 fix patch.

 The gpio-lw tree gained a build failure so I used the version 
 from
 next-20130117.

 The samsung tree lost the majority of its conflicts but gained 
 more
 against the arm-soc and slave-dma tree.

 

   
From my dmesg diff-file:
   
+[  288.730849] PM: Syncing filesystems ... done.
+[  294.050498] Freezing user space processes ... (elapsed 0.04 
seconds) done.
+[  294.097024] Freezing remaining freezable tasks ...
+[  314.098849] Freezing of tasks failed after 20.01 seconds (1 
tasks
refusing to freeze, wq_busy=0):
+[  314.098862] jbd2/loop0-8D 8180d780 0   297
  2 0x
+[  314.098865]  880117ec5b68 0046 
880117ec5b08
81044c29
+[  314.098868]  88011829dc80 880117ec5fd8 
880117ec5fd8
880117ec5fd8
+[  314.098871]  880119b34560 88011829dc80 
880117ec5b68
88011fad4738
+[  314.098873] Call Trace:
+[  314.098881]  [81044c29] ? 
default_spin_lock_flags+0x9/0x10
+[  314.098885]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.09]  [816b4b59] schedule+0x29/0x70
+[  314.098890]  [816b4c2f] io_schedule+0x8f/0xd0
+[  314.098892]  [811c63ee] sleep_on_buffer+0xe/0x20
+[  314.098896]  [816b342f] __wait_on_bit+0x5f/0x90
+[  314.098898]  [811c5aa1] ? submit_bh+0x121/0x1e0
+[  314.098900]  [811c63e0] ? __wait_on_buffer+0x30/0x30
+[  314.098903]  [816b34dc] 
out_of_line_wait_on_bit+0x7c/0x90
+[  314.098906]  [8107eb00] ? 
autoremove_wake_function+0x40/0x40
+[  314.098909]  [811c63de] __wait_on_buffer+0x2e/0x30
+[  314.098913]  [8128a6a1]
jbd2_journal_commit_transaction+0x1791/0x1960
+[  314.098917]  [8109269d] ? sched_clock_cpu+0xbd/0x110
+[  314.098920]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098923]  [81069fbf] ? 
try_to_del_timer_sync+0x4f/0x70
+[  314.098925]  [8128e4e8] kjournald2+0xb8/0x240
+[  314.098927]  [8107eac0] ? add_wait_queue+0x60/0x60
+[  314.098929]  [8128e430] ? commit_timeout+0x10/0x10
+[  314.098931]  [8107ded0] kthread+0xc0/0xd0
+[  314.098933]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098936]  [816be52c] ret_from_fork+0x7c/0xb0
+[  314.098938]  [8107de10] ? 
flush_kthread_worker+0xb0/0xb0
+[  314.098969]
+[  314.098970] Restarting kernel threads ... done.
+[  314.099052] Restarting tasks ... done.
   
Please, have a lot at it.
   
This is a freezer failure while freezing kernel threads, so I 
don't think it's
related to ACPI or PM directly.
   
Does it happen on every suspend?
   
   
No, I only did one S/R.
   
I have built a 2nd new kernel where I pulled-in latest 
pm.git#linux-next.
With this kernel two S/Rs were fine - but that says not much.
   
  
   After several S/Rs on the buggy -1 kernel I know see in my syslogs:
  
   Jan 18 23:50:02 fambox kernel: [  141.853828] Disabling non-boot CPUs 
   ...
   Jan 18 23:50:02 fambox kernel: [  141.956943] smpboot: CPU 1 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  141.957438] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  141.957454] NOHZ: 
   local_softirq_pending 02
   Jan 18 23:50:02 fambox kernel: [  142.060830] smpboot: CPU 2 is now 
   offline
   Jan 18 23:50:02 fambox kernel: [  142.164639] smpboot: CPU 3 is now 
   offline
  
   Are you worried about the local_softirq_pending messages?
  
 
  That's the only new messages I have seen after several S/Rs.
 
  They are kind of unusual.
 
  Anyway, they seem to be related to CPU hotplug (CPU offline), so you can 

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20130117:

Undropped tree: samung

The powerpc tree still had a build failure.

The driver-core tree gained a build failure for which I applied a merge
fix patch.

The gpio-lw tree gained a build failure so I used the version from
next-20130117.

The samsung tree lost the majority of its conflicts but gained more
against the arm-soc and slave-dma tree.



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one.  You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc,
sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 211 trees (counting Linus' and 28 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ .  Thanks to Frank Seidel.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (72ffaa4 Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux)
Merging fixes/master (d287b87 Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs)
Merging kbuild-current/rc-fixes (02f3e53 Merge branch 'yem-kconfig-rc-fixes' of 
git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes)
Merging arm-current/fixes (d106de3 ARM: 7614/1: mm: fix wrong branch from 
Cortex-A9 to PJ4b)
Merging m68k-current/for-linus (e7e29b4 m68k: Wire up finit_module)
Merging powerpc-merge/merge (e6449c9 powerpc: Add missing NULL terminator to 
avoid boot panic on PPC40x)
Merging sparc/master (b7c13f7 sparc: remove __devinit, __devexit annotations)
Merging net/master (01fe944 macvlan: fix macvlan_get_size())
Merging sound-current/for-linus (6f54c36 ALSA: hda/hdmi - Work around "alsactl 
restore" errors)
Merging pci-current/for-linus (9e16721 PCI: Allow pcie_aspm=force even when 
FADT indicates it is unsupported)
Merging wireless/master (4668cce ath9k: disable the tasklet before taking the 
PCU lock)
Merging driver-core.current/driver-core-linus (f1688e0 debugfs: convert gid= 
argument from decimal, not octal)
Merging tty.current/tty-linus (ebebd49 8250/16?50: Add support for Broadcom 
TruManage redirected serial port)
Merging usb.current/usb-linus (8cf65dc usb: ftdi_sio: Crucible Technologies 
COMET Caller ID - pid added)
Merging staging.current/staging-linus (1ee4c55 staging: vt6656: Fix 
inconsistent structure packing)
Merging char-misc.current/char-misc-linus (33080c1 Drivers: hv: balloon: Fix a 
memory leak)
Merging input-current/for-linus (b666263 Input: document that unregistering 
managed devices is not necessary)
Merging md-current/for-linus (a9add5d md/raid5: add blktrace calls)
Merging audit-current/for-linus (c158a35 audit: no leading space in 
audit_log_d_path prefix)
Merging crypto-current/master (a2c0911 crypto: caam - Updated SEC-4.0 device 
tree binding for ERA information.)
Merging ide/master (9974e43 ide: fix generic_ide_suspend/resume Oops)
Merging dwmw2/master (084a0ec x86: add CONFIG_X86_MOVBE option)
CONFLICT (content): Merge conflict in arch/x86/Kconfig
Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to 
inline functions)
Merging irqdomain-current/irqdomain/merge (a0d271c Linux 3.6)
Merging devicetree-current/devicetree/merge (ab28698 of: define struct device 
in of_platform.h if !OF_DEVICE and !OF_ADDRESS)
Merging spi-current/spi/merge (d3601e5 spi/sh-hspi: fix return value check in 
hspi_probe().)
Merging gpio-current/gpio/merge (bc1008c gpio/mvebu-gpio: Make mvebu-gpio 
depend on OF_CONFIG)
Merging 

linux-next: Tree for Jan 18

[Stephen Rothwell]

Hi all,

Changes since 20130117:

Undropped tree: samung

The powerpc tree still had a build failure.

The driver-core tree gained a build failure for which I applied a merge
fix patch.

The gpio-lw tree gained a build failure so I used the version from
next-20130117.

The samsung tree lost the majority of its conflicts but gained more
against the arm-soc and slave-dma tree.



I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
are tracking the linux-next tree using git, you should not use git pull
to do so as that will try to merge the new linux-next release with the
old one.  You should use git fetch as mentioned in the FAQ on the wiki
(see below).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc,
sparc64 and arm defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.

Below is a summary of the state of the merge.

We are up to 211 trees (counting Linus' and 28 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.

Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.

Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
Gortmaker for triage and bug fixes.

There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ .  Thanks to Frank Seidel.

-- 
Cheers,
Stephen Rothwells...@canb.auug.org.au

$ git checkout master
$ git reset --hard stable
Merging origin/master (72ffaa4 Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux)
Merging fixes/master (d287b87 Merge branch 'for-linus' of 
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs)
Merging kbuild-current/rc-fixes (02f3e53 Merge branch 'yem-kconfig-rc-fixes' of 
git://gitorious.org/linux-kconfig/linux-kconfig into kbuild/rc-fixes)
Merging arm-current/fixes (d106de3 ARM: 7614/1: mm: fix wrong branch from 
Cortex-A9 to PJ4b)
Merging m68k-current/for-linus (e7e29b4 m68k: Wire up finit_module)
Merging powerpc-merge/merge (e6449c9 powerpc: Add missing NULL terminator to 
avoid boot panic on PPC40x)
Merging sparc/master (b7c13f7 sparc: remove __devinit, __devexit annotations)
Merging net/master (01fe944 macvlan: fix macvlan_get_size())
Merging sound-current/for-linus (6f54c36 ALSA: hda/hdmi - Work around alsactl 
restore errors)
Merging pci-current/for-linus (9e16721 PCI: Allow pcie_aspm=force even when 
FADT indicates it is unsupported)
Merging wireless/master (4668cce ath9k: disable the tasklet before taking the 
PCU lock)
Merging driver-core.current/driver-core-linus (f1688e0 debugfs: convert gid= 
argument from decimal, not octal)
Merging tty.current/tty-linus (ebebd49 8250/16?50: Add support for Broadcom 
TruManage redirected serial port)
Merging usb.current/usb-linus (8cf65dc usb: ftdi_sio: Crucible Technologies 
COMET Caller ID - pid added)
Merging staging.current/staging-linus (1ee4c55 staging: vt6656: Fix 
inconsistent structure packing)
Merging char-misc.current/char-misc-linus (33080c1 Drivers: hv: balloon: Fix a 
memory leak)
Merging input-current/for-linus (b666263 Input: document that unregistering 
managed devices is not necessary)
Merging md-current/for-linus (a9add5d md/raid5: add blktrace calls)
Merging audit-current/for-linus (c158a35 audit: no leading space in 
audit_log_d_path prefix)
Merging crypto-current/master (a2c0911 crypto: caam - Updated SEC-4.0 device 
tree binding for ERA information.)
Merging ide/master (9974e43 ide: fix generic_ide_suspend/resume Oops)
Merging dwmw2/master (084a0ec x86: add CONFIG_X86_MOVBE option)
CONFLICT (content): Merge conflict in arch/x86/Kconfig
Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to 
inline functions)
Merging irqdomain-current/irqdomain/merge (a0d271c Linux 3.6)
Merging devicetree-current/devicetree/merge (ab28698 of: define struct device 
in of_platform.h if !OF_DEVICE and !OF_ADDRESS)
Merging spi-current/spi/merge (d3601e5 spi/sh-hspi: fix return value check in 
hspi_probe().)
Merging gpio-current/gpio/merge (bc1008c gpio/mvebu-gpio: Make mvebu-gpio 
depend on OF_CONFIG)
Merging