{"action":"created","issue":{"url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/8","repository_url":"https://api.github.com/repos/Mieze/IntelMausiEthernet","labels_url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/8/labels{/name}","comments_url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/8/comments","events_url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/8/events","html_url":"https://github.com/Mieze/IntelMausiEthernet/issues/8","id":200886014,"number":8,"title":"Crash in the driver, perhaps related to sleep wake and or heavy load","user":{"login":"emlynmac","id":3941071,"avatar_url":"https://avatars.githubusercontent.com/u/3941071?v=3","gravatar_id":"","url":"https://api.github.com/users/emlynmac","html_url":"https://github.com/emlynmac","followers_url":"https://api.github.com/users/emlynmac/followers","following_url":"https://api.github.com/users/emlynmac/following{/other_user}","gists_url":"https://api.github.com/users/emlynmac/gists{/gist_id}","starred_url":"https://api.github.com/users/emlynmac/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/emlynmac/subscriptions","organizations_url":"https://api.github.com/users/emlynmac/orgs","repos_url":"https://api.github.com/users/emlynmac/repos","events_url":"https://api.github.com/users/emlynmac/events{/privacy}","received_events_url":"https://api.github.com/users/emlynmac/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2017-01-15T18:43:08Z","updated_at":"2017-01-15T22:35:00Z","closed_at":null,"body":"Driver works great for the most part, but if I leave the system with Time Machine going, it will reliably crash.\r\n\r\nDriver version 2.2.0; OS X version 10.12.2\r\nCard is an Intel i217V.\r\n\r\n\r\nCrash dump:\r\n\r\n````\r\n*** Panic Report ***\r\npanic(cpu 2 caller 0xffffff8014605ead): Kernel trap at 0xffffff7f97a768a7, type 14=page fault, registers:\r\nCR0: 0x000000008001003b, CR2: 0xffffff820474d008, CR3: 0x000000001fa83000, CR4: 0x00000000001627e0\r\nRAX: 0xffffff803b3da400, RBX: 0xffffff81b77ce000, RCX: 0x0000000000000000, RDX: 0x0000000000000100\r\nRSP: 0xffffff9206e63cf0, RBP: 0xffffff9206e63d70, RSI: 0xffffff803b3d0000, RDI: 0x0000000000000000\r\nR8:  0x0000000000000000, R9:  0xffffff81f8776068, R10: 0x0000000000000000, R11: 0xffffff81d80e5058\r\nR12: 0xffffff81b77ce000, R13: 0xffffff803a299de8, R14: 0xffffff820474d000, R15: 0x0000000000000000\r\nRFL: 0x0000000000010246, RIP: 0xffffff7f97a768a7, CS:  0x0000000000000008, SS:  0x0000000000000010\r\nFault CR2: 0xffffff820474d008, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1\r\n\r\nBacktrace (CPU 2), Frame : Return Address\r\n0xffffff9206e63980 : 0xffffff80144f211c \r\n0xffffff9206e63a00 : 0xffffff8014605ead \r\n0xffffff9206e63be0 : 0xffffff80144a3743 \r\n0xffffff9206e63c00 : 0xffffff7f97a768a7 \r\n0xffffff9206e63d70 : 0xffffff7f97a77232 \r\n0xffffff9206e63d90 : 0xffffff7f95a6f9d4 \r\n0xffffff9206e63dc0 : 0xffffff8014abf81a \r\n0xffffff9206e63e30 : 0xffffff7f95a6fa3b \r\n0xffffff9206e63e80 : 0xffffff7f95a73c7a \r\n0xffffff9206e63ef0 : 0xffffff801478a005 \r\n0xffffff9206e63fb0 : 0xffffff80144a0af7 \r\n      Kernel Extensions in backtrace:\r\n         com.apple.iokit.IONetworkingFamily(3.2)[6326DB88-5330-3F0C-91F6-D478AB5E7503]@0xffffff7f95a67000->0xffffff7f95a93fff\r\n         com.insanelymac.IntelMausiEthernet(2.2)[3A6046E0-A8B1-32C2-9532-1EBF16AEB28B]@0xffffff7f97a73000->0xffffff7f97a86fff\r\n            dependency: com.apple.iokit.IONetworkingFamily(3.2)[6326DB88-5330-3F0C-91F6-D478AB5E7503]@0xffffff7f95a67000\r\n            dependency: com.apple.iokit.IOPCIFamily(2.9)[6F8D3ACB-27CB-3B57-9E06-53E377762F5C]@0xffffff7f94d46000\r\n\r\nBSD process name corresponding to current thread: kernel_task\r\nBoot args: dart=0 \r\n````\r\n\r\nWoL disabled and UEFI network stack also disabled. \r\nI've got the source and will start digging into the why if I can."},"comment":{"url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/comments/272743490","html_url":"https://github.com/Mieze/IntelMausiEthernet/issues/8#issuecomment-272743490","issue_url":"https://api.github.com/repos/Mieze/IntelMausiEthernet/issues/8","id":272743490,"user":{"login":"Mieze","id":4229650,"avatar_url":"https://avatars.githubusercontent.com/u/4229650?v=3","gravatar_id":"","url":"https://api.github.com/users/Mieze","html_url":"https://github.com/Mieze","followers_url":"https://api.github.com/users/Mieze/followers","following_url":"https://api.github.com/users/Mieze/following{/other_user}","gists_url":"https://api.github.com/users/Mieze/gists{/gist_id}","starred_url":"https://api.github.com/users/Mieze/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Mieze/subscriptions","organizations_url":"https://api.github.com/users/Mieze/orgs","repos_url":"https://api.github.com/users/Mieze/repos","events_url":"https://api.github.com/users/Mieze/events{/privacy}","received_events_url":"https://api.github.com/users/Mieze/received_events","type":"User","site_admin":false},"created_at":"2017-01-15T22:35:00Z","updated_at":"2017-01-15T22:35:00Z","body":"OS X has become more and more picky about the ACPI data structures starting with El Capitan. When I set up my test machine with an Asrock H97M-Pro4 under Yosemite, the board was almost hassle-free. After upgrading to El Capitan, I got an instant kernel panic on boot with a discrete GPU installed due to broken interrupt routing functions in the DSDT and even after resolving that problem, I had random kernel panics on sleep/wake with WoL enabled in OS X. In order to solve this problem, I had to keep Thunderbolt support enabled in BIOS (who knows why???), although there is no thunderbolt hardware installed in the system, and had to rewrite about 10% of the DSDT's code in order to get it stable with WoL enabled in OS X. The Sierra upgrade resulted in a bunch of new ACPI errors in the kernel logs too so that I had to rework the DSDT again. Look for ACPI errors in the kernel logs as a starting point and try to disable WoL in System Preferences when possible.\r\n\r\nWith regard to the UEFI setup, consult your board's manual and check all options which may affect the NIC's operation, in particular the UEFI network stack, network boot and power management. I even had a case where a user needed to to enable the network stack temporarily in order to get access to an option which had to be disabled for stable operation. Some things are straightforward while others need trial and error to find out like my Thunderbolt issue. ;-)\r\n\r\nMessed up systems usually result from things going wrong while installing new drivers and require a reinstall in order to recover from that situation. During development I had a case where any version of the driver, even older versions which used to work fine, caused the machine to crash on boot. After a reinstall, the system work fine with the driver. I even watched this happen with Apple provided drivers."}}
{"actor":{"display_login":"Mieze"}}