Date: Mon, 01 Jul 2019 13:25:48 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 238037] [PATCH] Implement ig4 suspend/resume Message-ID: <bug-238037-227-jE9FXAstJ5@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238037-227@https.bugs.freebsd.org/bugzilla/> References: <bug-238037-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D238037 --- Comment #9 from J.R. Oldroyd <fbsd@opal.com> --- Created attachment 205461 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D205461&action= =3Dedit patch with ig4_iic.c ig4iic_attach() updates from DragonflyBSD The iichid/ims init problem on boot is fixed for me. I had it too some time back. The fix was (I think) to load it using: kld_load=3D"iic ig4 acpi_iichid" in /etc/rc.conf. Now I did also pull in from Dragonfly a handful of updates to the ig4_iic.c attach code and I am uploading that patch here. At this point I don't reca= ll if these were also needed in order for iichid to init properly on boot. At any rate, iichid inits properly on boot 100% of the time for me now. It's just on resume that it fails. It fails after the system has been suspended for a while, say 10 seconds or more. If I suspend and then immediately resume after the power goes off, it does actually resume ok mos= t of the time. That's what led me to think we might be missing some registers on resume. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238037-227-jE9FXAstJ5>