https://bugzilla.kernel.org/show_bug.cgi?id=74451
--- Comment #7 from Aaron Sosnick <[email protected]> --- Okay. In the hopes of getting some help I've upgraded the motherboard firmware, and upgraded to the latest 3.14.2 kernel and separately attached dmesg and lspci output after good and bad boots. This is not a regression. Behavior was the same with all previous versions of the kernel and firmware. Maybe it's not ACPI, but then can someone advise me where to report or look for help? I find it interesting that the dmesg output is longer after an initial good boot. The first diff in dmesg output shows that a little more RAM is usable during the good boot: $ diff dmesg.bad.20140429 dmesg.good.20140429 32c32 < [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000044f5fffff] usable --- > [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000004505fffff] usable What about a shutdown, hibernate, and suspend could twiddle the CMOS into missing some memory? We see more memory address range differences. Then we see some differences after a message that MTRR variable ranges are enabled. 119,123c227,231 < [ 0.000000] 3 base 00C0000000 mask 7FC0000000 uncachable < [ 0.000000] 4 base 00A0000000 mask 7FE0000000 uncachable < [ 0.000000] 5 base 009F800000 mask 7FFF800000 uncachable < [ 0.000000] 6 base 044F800000 mask 7FFF800000 uncachable < [ 0.000000] 7 base 044F600000 mask 7FFFE00000 uncachable --- > [ 0.000000] 3 base 0450000000 mask 7FFFC00000 write-back > [ 0.000000] 4 base 0450400000 mask 7FFFE00000 write-back > [ 0.000000] 5 base 00C0000000 mask 7FC0000000 uncachable > [ 0.000000] 6 base 00A0000000 mask 7FE0000000 uncachable > [ 0.000000] 7 base 009F800000 mask 7FFF800000 uncachable Lots more differences with memory ranges for things. Then 230c464b < [ 0.000000] DMA zone: 25 pages reserved --- > [ 0.000000] DMA zone: 27 pages reserved Then we have to remove the timestamps for diff to be useful. The good boot has messages about *BAD*gran_size and mtrr_cleanup: can not find optimal value More memory range differences Then we see a missing line in the bad boot about ehci-pci 730,731c967,969 < Magic number: 10:30:712 < rtc_cmos 00:06: setting system clock to 2014-04-30 01:44:28 UTC (1398822268) --- > Magic number: 10:133:813 > ehci-pci 0000:00:1a.0: hash matches > rtc_cmos 00:06: setting system clock to 2014-04-30 01:50:52 UTC (1398822652) The differences get harder to follow. Things seem to be happening in different orders, IRQ numbers vary. Just grepping for e1000e though $ grep e1000e dmesg.good.20140429 [ 0.697939] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 0.697941] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 0.698090] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 0.698104] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X [ 0.866888] e1000e 0000:00:19.0 eth0: registered PHC clock [ 0.866890] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) bc:5f:f4:d7:c1:0b [ 0.866891] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection [ 0.866935] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF [ 2.845759] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X [ 2.949233] e1000e 0000:00:19.0: irq 41 for MSI/MSI-X [ 5.776351] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx $ grep e1000e [ 0.701104] e1000e: Intel(R) PRO/1000 Network Driver - 2.3.2-k [ 0.701107] e1000e: Copyright(c) 1999 - 2013 Intel Corporation. [ 0.712900] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode [ 0.712922] e1000e 0000:00:19.0: irq 43 for MSI/MSI-X [ 1.705047] e1000e: probe of 0000:00:19.0 failed with error -3 And I notice that somehow I've reverted to an old e1000e driver. Upgrading, however doesn't help. Are there any more logs that I can provide or more debugging that I can do? I'd like to look for relevant messages during the shutdown after a good boot, but don't have a clue how to make those be stored somewhere where I can find them later after a reboot. HELP! -- You are receiving this mail because: You are watching the assignee of the bug. ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ acpi-bugzilla mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
