It looks like the following config file changes were made between v3.1.0-2.3 and v3.2.0-1.1:
* [Config] enforcer -- ensure CONFIG_FAT_FS is built-in on arm
* [Config] Enable PCI_IOV on powerpc
* [Config] Temporarily disable CONFIG_PASEMI_MAC on powerpc
* [Config] updateconfigs after select ARM_AMBA
* [Config] Temporarily disable CONFIG_KVM_BOOK3S_32 on powerpc
* [Config] Enable CONFIG_EXT2_FS=m
* [Config] Build in CONFIG_SATA_AHCI=y
* [Config] Enable EVENT_POWER_TRACING_DEPRECATED=y for powertop
* [Config] Built-in xen-netfront and xen-blkfront
* [Config] CONFIG_USB_XHCI_HCD=y
* [Config] CONFIG_R6040=m
* [Config] Consolidated amd64 server flavour into generic
* [Config] updateconfigs after rebase to 3.2-rc1
* [Config] Disabled dm-raid4-5
* [Config] Disabled ndiswrapper
* [Config] Disable vt6656
* [Config] exclude ppp-modules for virtual flavour
* [Config] CONFIG_MEMSTICK_R592=m
I'll investigate further and will post a test kernel. I may be able to build a v3.2.0-1.1 test kernel using the v3.1.0-2.3 config file. That will confirm that one of the config options about causes this bug.
It looks like the following config file changes were made between v3.1.0-2.3 and v3.2.0-1.1:
* [Config] enforcer -- ensure CONFIG_FAT_FS is built-in on arm KVM_BOOK3S_ 32 on powerpc TRACING_ DEPRECATED= y for powertop USB_XHCI_ HCD=y MEMSTICK_ R592=m
* [Config] Enable PCI_IOV on powerpc
* [Config] Temporarily disable CONFIG_PASEMI_MAC on powerpc
* [Config] updateconfigs after select ARM_AMBA
* [Config] Temporarily disable CONFIG_
* [Config] Enable CONFIG_EXT2_FS=m
* [Config] Build in CONFIG_SATA_AHCI=y
* [Config] Enable EVENT_POWER_
* [Config] Built-in xen-netfront and xen-blkfront
* [Config] CONFIG_
* [Config] CONFIG_R6040=m
* [Config] Consolidated amd64 server flavour into generic
* [Config] updateconfigs after rebase to 3.2-rc1
* [Config] Disabled dm-raid4-5
* [Config] Disabled ndiswrapper
* [Config] Disable vt6656
* [Config] exclude ppp-modules for virtual flavour
* [Config] CONFIG_
I'll investigate further and will post a test kernel. I may be able to build a v3.2.0-1.1 test kernel using the v3.1.0-2.3 config file. That will confirm that one of the config options about causes this bug.