On Thursday 29 September 2016, okaya@codeaurora.org wrote: > On 2016-09-29 05:10, Ondrej Zary wrote: > > On Thursday 29 September 2016, Sinan Kaya wrote: > >> On 9/28/2016 3:23 PM, Ondrej Zary wrote: > >> > On Wednesday 28 September 2016 20:22:40 Sinan Kaya wrote: > >> >> On 9/28/2016 1:02 PM, Ondrej Zary wrote: > >> >>>> Thanks, It sounds like you have more than one machine with similar > >> >>>> > >> >>>>> problems. Can you collect the log from the other machines with > >> >>>>> 4.8-rc8? > >> >>>>> > >> >>>>> and also a boot log with 4.6 kernel where things are working? > >> >>> > >> >>> The attached logs are from another machine: > >> >>> > >> >>> dmesg-bad-debug.txt: 4.8-rc8 with your debug patch - bad > >> >>> > >> >>> dmesg-reverted.txt: 4.8-rc8 with patches (as per Rafael's > >> >>> suggestion) reverted - good > >> >>> > >> >>> dmesg-3.6.txt: 4.6 (Debian kernel) - good > >> >> > >> >> I think I see a race condition for the SCI interrupt. I need another > >> >> dump from 4.8-rc8 with the attached patch to confirm. Let's remove > >> >> the previous one and apply this one. > >> > > >> > dmesg-reverted.txt: 4.8-rc8 w/patches reverted (good) > >> > $ head /proc/interrupts > >> > CPU0 > >> > 0: 8531 XT-PIC timer > >> > 1: 9 XT-PIC i8042 > >> > 2: 0 XT-PIC cascade > >> > 8: 1 XT-PIC rtc0 > >> > 11: 713 XT-PIC acpi, uhci_hcd:usb1, uhci_hcd:usb2, nvkm, > >> > eth0 12: 161 XT-PIC i8042 > >> > 14: 4042 XT-PIC pata_via > >> > 15: 0 XT-PIC pata_via > >> > NMI: 0 Non-maskable interrupts > >> > > >> > dmesg-bad-debug.txt: 4.8-rc8 (bad) > >> > $ head /proc/interrupts > >> > CPU0 > >> > 0: 8027 XT-PIC timer > >> > 1: 286 XT-PIC i8042 > >> > 2: 0 XT-PIC cascade > >> > 8: 1 XT-PIC rtc0 > >> > 10: 0 XT-PIC uhci_hcd:usb1, uhci_hcd:usb2 > >> > 11: 0 XT-PIC acpi, nvkm, eth0 > >> > 12: 161 XT-PIC i8042 > >> > 14: 4069 XT-PIC pata_via > >> > 15: 0 XT-PIC pata_via > >> > > >> > (I'm moving between different machines through the day - these logs > >> > are from different machine than the last ones). > >> > >> Can you try these patches on your machines please? > > > > It doesn't even boot :( > > Ok, since I have not seen the full boot log I am guessing that isa api > gets called before the link objects are initialized. Netconsole did not work (probably because it crashes too early?) and I don't have a null-modem cable. > Can you appply the first three only (0001, 0002 and 0003) to see if it > makes a difference? It boots with first 3 patches only but the problem remains - see the attached log. -- Ondrej Zary