New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] System reboots while on sleep #284
Comments
Please provide hardware details, kernel log & IOReg :) |
Oh sorry haha, here you are my specs: Laptop Dell Inspiron 5370 GenI2C IORegistryExplorer 3.0.2 dump Kernel log (last 30 hours) |
As suggested by @marianopela, below the dump of log_with_sscn_fmcn.txt My DSDT.aml doesn't have SSCN and FMCN bus speed config and that seems a little bit strange. Also I'm running in polling mode, may I have any chance to run it with Interrupt mode? |
Same happening on MSFT0001 with i5 10210u. I'll attach logs in a few hours |
@marianopela @dreamwhite mind testing this? |
I'll surely test it out on 10.15.4. Hope they fix it asap |
Thanks, it seems to be fixing my sleep/wake problem. Unfortunately I still experienced a Panic and reboot while in sleep, as you can see here tonight_cut.txt , with the usual I think VoodooI2C/VoodooI2CHID#31 could have something to do with my System Panics, as with those changes I didn't experience any. I'll be testing more in the next hours. |
@marianopela mind giving a try to this? have removed the |
Sure, right away. It might take some time to test eventual problems. |
Thanks @Goshin! Works great here on a Lenovo Yoga 920. Excellent job! |
What changed in the second archive? Also, could you please explain how removing |
just removed the polling frequency adjustment, it should make no difference to your test.
You can check out the explanation for the related commits here. |
@Goshin No panics nor reboots, trackpad always worked after every sleep/wake. Same for @dreamwhite . It's a keeper! |
Same here, this is good! Thumbs up! |
I tried this but still have problem with wake. BSD process name corresponding to current thread: kernel_task Mac OS version: Kernel version: System uptime in nanoseconds: 11686257364431
|
Yesterday, with great amazement, my system rebooted while in sleep. I don't know if the cause of the panic-reboot is due to VoodooI2C but I've saved the log of "Report Panic". Thanks in advance. Hope this bug can be fixed asap :D |
comment
From your log, deadlock happened in the interrupt handler when trying to read register, maybe related to #279. comment
Can't tell the cause from the given log. |
@Goshin Backtrace (CPU 1), Frame : Return Address BSD process name corresponding to current thread: kernel_task Mac OS version: Kernel version: System uptime in nanoseconds: 660564039537
` |
@gujiangjiang Same cause. Are you using in GPIO mode or polling mode? |
@Goshin |
@dreamwhite @gujiangjiang Try this one |
@Goshin |
@Goshin panic(cpu 0 caller 0xffffff800be4c32a): Kernel trap at 0xffffff7f8fc1898b, type 14=page fault, registers: Backtrace (CPU 0), Frame : Return Address BSD process name corresponding to current thread: kernel_task Mac OS version: Kernel version: System uptime in nanoseconds: 8534727004805
|
Another bug found on the v2.4 version of VoodooI2C. It seems that after putting laptop in sleep the mouse doesn't wake up :'( Infos about my machine are here |
@gujiangjiang same cause. Does the problem exist in polling mode? No idea what was happening, maybe this would help. |
Found that after putting laptop in sleep mode, the trackpad doesn't wake up. This happened with vanilla VoodooI2C 2.4 + VoodooI2CHID. @alexandred what can we do in order to fix it? |
@kprinssu thanks for the pointer, I just did - so far so good, I'll observe. If you don't hear from me, that's a good sign :) |
@kprinssu I do not want to open a new issue but with latest version (2.4.1) laptop does not sleep and wake instantly. if I remove anything related to voodooi2c , it sleeps properly. |
Hi there, today I got my first panic using VoodooI2C 2.4. I also had a problem which made trackpad frozen even if in IOReg it was detected. Needed to restart to fix this. I've updated to VoodooI2C 2.4.1 right now and everything seems working:
EDITSleep seems working Many thx <3 |
@lersy Please create a new issue with the usual troubleshooting documentation. |
Please make sure to run |
It shows the same message such as 10 times
If I show instead the last 120 minutes, I see a lot of those "Power Wake reason", but I don't think I have to worry about it, as I always resume from sleep using the Power Button.
Do I need to setup a spoofed GLAN device or whatelse? I don't have any RJ45 port on my laptop (Dell Inspiron 5370)
Is there any documentation you can suggest me, in order to setup GPRW/UPRW?
Yep I think so, as the panic reason is related to VoodooI2C
My USB configuration is properly setup (correctly mapped USB 2.0, USB 3.0 and USB-C 3.0), and I've also added USBX device through SSDT-USBX.aml I apologize if USBMap can't be used as debugging method, but it clearly says that my EC and USBX device are properly setup. Maybe I don't have to worry about it? |
I strongly assume there are other sources for your problem - i.e. make sure you have deactivated Wake for Ethernet network access, and also Bluetooth wakes. GLAN is clearly connected to the network. Since this is all off-topic here, I suggest you move over to Tonymac and seek for help on a more general platform. Another experiences I have gathered while trying to fix sleep:
Good luck! |
@dreamwhite Please use 2.4.1 and the logs are irrevelant to the sleep/wake as it shows bluetooth to be the cause. You should probably apply the USB GPRW patch, but that is irrelevant to VoodooI2C. @edd1024 @dreamwhite please take non-VoodooI2C related discussions out of this issue. |
Oke np |
Update to 2.4.1 but still reboot after wake... Now only this one with no problem with wake. |
@gujiangjiang The changes above have not been merged yet. |
@gujiangjiang, if you observe a kernel panic in macOS, a kernel panic report is useless by default, since all symbols are stripped. To provide a full kernel panic report you should use keepsyms=1 in boot-args. |
After updating successfully to VoodooI2C 2.4.2, after a sleep/wake cycle, my trackpad stopped working. I attach the output of |
@dreamwhite it looks your device is "waking" up from sleep, but perhaps the I2C commands are failing. What is your touchpad, it looks like it's a USB device? |
It is an MSFT0001, like mine. I2CHID is the only satellite Anyways, I haven't had any problems with sleep/wake lately, on 10th gen |
@marianopela did you not also have sleep/wake issues with earlier versions of VoodooI2C? |
I had, and solved earlier in this Issue, here. Never had problems of this kind since then. |
Here too, however there are casual KP's, but nohing driving me mad so far. In most cases when I leave the laptop unattended, attempting to go to sleep by itself after 15min or so. |
Might be addressed in VoodooI2C/VoodooGPIO#7 and VoodooI2C/VoodooI2CHID#33 with more robust toggling of the interrupt. |
In @dreamwhite 's case, he is running in polling mode |
@Goshin here you are my infos about the trackpad: DeviceName: You can find my two DSDTs, the origin and the patched version: I noticed also that the issue about the trackpad which stops working after a sleep-wake cycle doesn't happen everytimes. I've tested it for 5 times, and only 2 times, the trackpad stopped working. Do you think that this is due to the polling mode? |
I am not sure about the cause. Try to build with the changes mentioned in #284 (comment), as it will completely disable and unregister the polling timer before sleeping, and restore when waking up. |
@dreamwhite Please do not use |
As per title, when I put my hackintosh in sleep mode, by closing the lid, after few hours it reboots. The issue was the same even with VoodooI2C 2.3. I'm actually using VoodooI2C 2.4 + VoodooI2CHID.
Below a screenshot of the panic report (which is pretty the same of VoodooI2C 2.4):
My EFI folder is available here
Actually everything is working except this problem.
hibernatemode
andproximitywake
are set to 0:Many thanks in advance
The text was updated successfully, but these errors were encountered: