Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. After it proved impossible to capture an oops through netconsole, I started git bisect. This will apparently take almost a week, as git estimated 13 bisection steps and I will be allowing about 12 hours of uptime as a sign for a good kernel. (In my four or five tests of bad kernels before I started bisection, they hung after 3 minutes...5.5 hours uptime, with no discernible difference in workload. Maybe 12 h cutoff is even too short...) -- Stefan Richter -==- -=-- ===-= http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. After it proved impossible to capture an oops through netconsole, I started git bisect. This will apparently take almost a week, as git estimated 13 bisection steps and I will be allowing about 12 hours of uptime as a sign for a good kernel. (In my four or five tests of bad kernels before I started bisection, they hung after 3 minutes...5.5 hours uptime, with no discernible difference in workload. Maybe 12 h cutoff is even too short...) -- Stefan Richter -==- -=-- ===-= http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 27 Stefan Richter wrote: > On Apr 27 Stefan Richter wrote: > > Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly > > after boot and xdm login to try capturing an oops. But throughout 5 hours > > uptime now, the hang was not reproduced. > > ...and 20 minutes after this post went out, the PC hang. > There was nothing logged over netconsole, alas. One more hang, now after 12 minutes uptime. Again no netconsole output. For the time being I can't investigate further. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 27 Stefan Richter wrote: > On Apr 27 Stefan Richter wrote: > > Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly > > after boot and xdm login to try capturing an oops. But throughout 5 hours > > uptime now, the hang was not reproduced. > > ...and 20 minutes after this post went out, the PC hang. > There was nothing logged over netconsole, alas. One more hang, now after 12 minutes uptime. Again no netconsole output. For the time being I can't investigate further. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 27 Stefan Richter wrote: > Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly > after boot and xdm login to try capturing an oops. But throughout 5 hours > uptime now, the hang was not reproduced. ...and 20 minutes after this post went out, the PC hang. There was nothing logged over netconsole, alas. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 27 Stefan Richter wrote: > Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly > after boot and xdm login to try capturing an oops. But throughout 5 hours > uptime now, the hang was not reproduced. ...and 20 minutes after this post went out, the PC hang. There was nothing logged over netconsole, alas. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly after boot and xdm login to try capturing an oops. But throughout 5 hours uptime now, the hang was not reproduced. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Today I booted a 2nd time into v4.6-rc5, and loaded netconsole shortly after boot and xdm login to try capturing an oops. But throughout 5 hours uptime now, the hang was not reproduced. -- Stefan Richter -==- -=-- ==-== http://arcgraph.de/sr/
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Attached: lspci -vvnn, obtained while on the good v4.5.2 -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/ 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] (rev 06) Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM Controller [15d9:0805] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:2010] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 4191 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <1us, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > v4.6-rc solidly hangs after a short while after boot, login to X11, and > doing nothing much remarkable on the just brought up X desktop. > > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Attached: lspci -vvnn, obtained while on the good v4.5.2 -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/ 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller [8086:0c08] (rev 06) Subsystem: Super Micro Computer Inc Xeon E3-1200 v3 Processor DRAM Controller [15d9:0805] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:0c01] (rev 06) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: [88] Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller [8086:2010] Capabilities: [80] Power Management version 3 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME- Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Address: feeff00c Data: 4191 Capabilities: [a0] Express (v2) Root Port (Slot+), MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0 ExtTag- RBE+ DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported- RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop- MaxPayload 128 bytes, MaxReadReq 128 bytes DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend- LnkCap: Port #2, Speed 8GT/s, Width x8, ASPM L0s L1, Exit Latency L0s <1us, L1 <8us ClockPM- Surprise- LLActRep- BwNot+ ASPMOptComp+ LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt+ ABWMgmt- SltCap: AttnBtn- PwrCtrl- MRL- AttnInd- PwrInd- HotPlug- Surprise- Slot #1, PowerLimit 75.000W; Interlock- NoCompl+ SltCtl: Enable: AttnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- LinkChg- Control: AttnInd Unknown, PwrInd Unknown, Power- Interlock- SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock- Changed: MRL- PresDet- LinkState- RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna+ CRSVisible- RootCap: CRSVisible- RootSta: PME ReqID , PMEStatus- PMEPending- DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR+, OBFF Via WAKE# ARIFwd- LnkCtl2: Target Link Speed: 8GT/s, EnterCompliance- SpeedDis- Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS- Compliance De-emphasis: -6dB LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1- EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest- Capabilities: [100 v1] Virtual Channel Caps: LPEVC=0 RefClk=100ns PATEntryBits=1 Arb:
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Attached: linux-4.6-rc5/.config -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/ # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.6.0-rc5 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_PERF_EVENTS_INTEL_UNCORE=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_MMU=y CONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_64_SMP=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_DEBUG_RODATA=y CONFIG_PGTABLE_LEVELS=4 CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y # CONFIG_USELIB is not set # CONFIG_AUDIT is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ_FULL is not set CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # # RCU Subsystem # CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y # CONFIG_TASKS_RCU is not set CONFIG_RCU_STALL_COMMON=y # CONFIG_TREE_RCU_TRACE is not set # CONFIG_RCU_EXPEDITE_BOOT is not set # CONFIG_BUILD_BIN2C is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=18 CONFIG_LOG_CPU_MAX_BUF_SHIFT=12 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y
Re: Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
On Apr 26 Stefan Richter wrote: > Hardware: x86-64, E3-1245 v3 (Haswell), > mainboard Supermicro X10SAE, > using integrated Intel graphics (HD P4600, i915 driver), > C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, > Intel LAN (i217, igb driver), > several IEEE 1394 controllers, some of them behind > PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) > and one PCI-to-CardBus bridge (Ricoh) > > kernel.org kernel, Gentoo Linux userland > > 1. known good: v4.5-rc5 (gcc 4.9.3) >known bad: v4.6-rc2 (gcc 4.9.3), only tried one time > > 2. known good: v4.5.2 (gcc 5.2.0) >known bad: v4.6-rc5 (gcc 5.2.0), only tried one time > > I will send my linux-4.6-rc5/.config in a follow-up message. > > In theory I could collect more info (simplify the hardware, run > netconsole, bisect). In practice I cannot do so for the the time being > due to lack of spare time. That's also the reason why I did not already > send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] > more than once yet. Attached: linux-4.6-rc5/.config -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/ # # Automatically generated file; DO NOT EDIT. # Linux/x86 4.6.0-rc5 Kernel Configuration # CONFIG_64BIT=y CONFIG_X86_64=y CONFIG_X86=y CONFIG_INSTRUCTION_DECODER=y CONFIG_PERF_EVENTS_INTEL_UNCORE=y CONFIG_OUTPUT_FORMAT="elf64-x86-64" CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig" CONFIG_LOCKDEP_SUPPORT=y CONFIG_STACKTRACE_SUPPORT=y CONFIG_MMU=y CONFIG_ARCH_MMAP_RND_BITS_MIN=28 CONFIG_ARCH_MMAP_RND_BITS_MAX=32 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MIN=8 CONFIG_ARCH_MMAP_RND_COMPAT_BITS_MAX=16 CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_GENERIC_BUG=y CONFIG_GENERIC_BUG_RELATIVE_POINTERS=y CONFIG_GENERIC_HWEIGHT=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_GENERIC_CALIBRATE_DELAY=y CONFIG_ARCH_HAS_CPU_RELAX=y CONFIG_ARCH_HAS_CACHE_LINE_SIZE=y CONFIG_HAVE_SETUP_PER_CPU_AREA=y CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y CONFIG_NEED_PER_CPU_PAGE_FIRST_CHUNK=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_ARCH_WANT_HUGE_PMD_SHARE=y CONFIG_ARCH_WANT_GENERAL_HUGETLB=y CONFIG_ZONE_DMA32=y CONFIG_AUDIT_ARCH=y CONFIG_ARCH_SUPPORTS_OPTIMIZED_INLINING=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_X86_64_SMP=y CONFIG_ARCH_HWEIGHT_CFLAGS="-fcall-saved-rdi -fcall-saved-rsi -fcall-saved-rdx -fcall-saved-rcx -fcall-saved-r8 -fcall-saved-r9 -fcall-saved-r10 -fcall-saved-r11" CONFIG_ARCH_SUPPORTS_UPROBES=y CONFIG_FIX_EARLYCON_MEM=y CONFIG_DEBUG_RODATA=y CONFIG_PGTABLE_LEVELS=4 CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_IRQ_WORK=y CONFIG_BUILDTIME_EXTABLE_SORT=y # # General setup # CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" # CONFIG_COMPILE_TEST is not set CONFIG_LOCALVERSION="" # CONFIG_LOCALVERSION_AUTO is not set CONFIG_HAVE_KERNEL_GZIP=y CONFIG_HAVE_KERNEL_BZIP2=y CONFIG_HAVE_KERNEL_LZMA=y CONFIG_HAVE_KERNEL_XZ=y CONFIG_HAVE_KERNEL_LZO=y CONFIG_HAVE_KERNEL_LZ4=y CONFIG_KERNEL_GZIP=y # CONFIG_KERNEL_BZIP2 is not set # CONFIG_KERNEL_LZMA is not set # CONFIG_KERNEL_XZ is not set # CONFIG_KERNEL_LZO is not set # CONFIG_KERNEL_LZ4 is not set CONFIG_DEFAULT_HOSTNAME="(none)" CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y CONFIG_CROSS_MEMORY_ATTACH=y CONFIG_FHANDLE=y # CONFIG_USELIB is not set # CONFIG_AUDIT is not set CONFIG_HAVE_ARCH_AUDITSYSCALL=y # # IRQ subsystem # CONFIG_GENERIC_IRQ_PROBE=y CONFIG_GENERIC_IRQ_SHOW=y CONFIG_GENERIC_PENDING_IRQ=y CONFIG_IRQ_DOMAIN=y CONFIG_IRQ_DOMAIN_HIERARCHY=y CONFIG_GENERIC_MSI_IRQ=y CONFIG_GENERIC_MSI_IRQ_DOMAIN=y CONFIG_IRQ_FORCED_THREADING=y CONFIG_SPARSE_IRQ=y CONFIG_CLOCKSOURCE_WATCHDOG=y CONFIG_ARCH_CLOCKSOURCE_DATA=y CONFIG_CLOCKSOURCE_VALIDATE_LAST_CYCLE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y CONFIG_GENERIC_CLOCKEVENTS_MIN_ADJUST=y CONFIG_GENERIC_CMOS_UPDATE=y # # Timers subsystem # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ_COMMON=y # CONFIG_HZ_PERIODIC is not set CONFIG_NO_HZ_IDLE=y # CONFIG_NO_HZ_FULL is not set CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y # # CPU/Task time and stats accounting # CONFIG_TICK_CPU_ACCOUNTING=y # CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set # CONFIG_IRQ_TIME_ACCOUNTING is not set CONFIG_BSD_PROCESS_ACCT=y # CONFIG_BSD_PROCESS_ACCT_V3 is not set # CONFIG_TASKSTATS is not set # # RCU Subsystem # CONFIG_PREEMPT_RCU=y # CONFIG_RCU_EXPERT is not set CONFIG_SRCU=y # CONFIG_TASKS_RCU is not set CONFIG_RCU_STALL_COMMON=y # CONFIG_TREE_RCU_TRACE is not set # CONFIG_RCU_EXPEDITE_BOOT is not set # CONFIG_BUILD_BIN2C is not set # CONFIG_IKCONFIG is not set CONFIG_LOG_BUF_SHIFT=18 CONFIG_LOG_CPU_MAX_BUF_SHIFT=12 CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH=y
Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
Hi, v4.6-rc solidly hangs after a short while after boot, login to X11, and doing nothing much remarkable on the just brought up X desktop. Hardware: x86-64, E3-1245 v3 (Haswell), mainboard Supermicro X10SAE, using integrated Intel graphics (HD P4600, i915 driver), C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, Intel LAN (i217, igb driver), several IEEE 1394 controllers, some of them behind PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) and one PCI-to-CardBus bridge (Ricoh) kernel.org kernel, Gentoo Linux userland 1. known good: v4.5-rc5 (gcc 4.9.3) known bad: v4.6-rc2 (gcc 4.9.3), only tried one time 2. known good: v4.5.2 (gcc 5.2.0) known bad: v4.6-rc5 (gcc 5.2.0), only tried one time I will send my linux-4.6-rc5/.config in a follow-up message. In theory I could collect more info (simplify the hardware, run netconsole, bisect). In practice I cannot do so for the the time being due to lack of spare time. That's also the reason why I did not already send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] more than once yet. -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/
Regression of v4.6-rc vs. v4.5: hangs after a few minutes after boot
Hi, v4.6-rc solidly hangs after a short while after boot, login to X11, and doing nothing much remarkable on the just brought up X desktop. Hardware: x86-64, E3-1245 v3 (Haswell), mainboard Supermicro X10SAE, using integrated Intel graphics (HD P4600, i915 driver), C226 PCH's AHCI and USB 2/3, ASMedia ASM1062 AHCI, Intel LAN (i217, igb driver), several IEEE 1394 controllers, some of them behind PCIe bridges (IDT, PLX) or PCIe-to-PCI bridges (TI, Tundra) and one PCI-to-CardBus bridge (Ricoh) kernel.org kernel, Gentoo Linux userland 1. known good: v4.5-rc5 (gcc 4.9.3) known bad: v4.6-rc2 (gcc 4.9.3), only tried one time 2. known good: v4.5.2 (gcc 5.2.0) known bad: v4.6-rc5 (gcc 5.2.0), only tried one time I will send my linux-4.6-rc5/.config in a follow-up message. In theory I could collect more info (simplify the hardware, run netconsole, bisect). In practice I cannot do so for the the time being due to lack of spare time. That's also the reason why I did not already send a report when I tested v4.6-rc2, and why I did not boot v4.6-rc[25] more than once yet. -- Stefan Richter -==- -=-- ==-=- http://arcgraph.de/sr/
