Comment 12 for bug 240648

Tim, this issue also can be found even with cold boot.
As I am investigating, I found the failed cold boot has this result in dmesg. Seems intel audio is initializing during NIC driver initialization. Maybe it’s the root cause. I am adding spinlock to the in NIC driver. But it doesn’t work.

[ 22.370396] r8169 Gigabit Ethernet driver 2.2LK loaded
[ 22.370469] ACPI: PCI Interrupt 0000:09:00.0[A] -> GSI 17 (level, low) -> IRQ 17
[ 22.370517] PCI: Setting latency timer of device 0000:09:00.0 to 64
[ 22.370551] r8169 0000:09:00.0: unknown MAC (27a00000)
[ 22.371049] eth0: RTL8169 at 0xf8abc000, 00:21:70:6e:00:64, XID 24a00000 IRQ 220
[ 22.371051] Lock On //I turn spinlock on before I enter init_phy()
[ 22.440670] ACPI: Video Device [VID2] (multi-head: yes rom: no post: no)
[ 22.460622] ieee80211_crypt: registered algorithm 'NULL'
[ 22.552819] wl: module license 'unspecified' taints kernel.
[ 22.849354] Bluetooth: Core ver 2.11
[ 22.850283] NET: Registered protocol family 31
[ 22.850286] Bluetooth: HCI device and connection manager initialized
[ 22.850290] Bluetooth: HCI socket layer initialized
[ 22.885883] Bluetooth: HCI USB driver ver 2.9
[ 22.887565] usbcore: registered new interface driver hci_usb
[ 23.228843] Lock Off//I turn off spinlock before I exit init_phy()
[ 23.228851] eth0: RTL8169 at 0xf8abc000, 00:21:70:6e:00:64, XID 7cf0f8ff IRQ 220