2012-07-23 05:45, Zack Breckenridge<zbr...@gmail.com> wrote:
>Attached is the kernel configuration file I used to build my kernel without
>VESA.
>
>I went through the same process as you: setting suspend bounce, etc., and
>looking at the dmesg output. Again, I also looked at the witness output
>from my Intel driver when resuming X -- and I noticed that it simply wasn't
>able to reach the GPU.
>
>So I think it is some sort of bus error on resume and is related to our
>different BIOSes. Since it worked for me, probably some int 10 call in VESA
>was causing the error. In your case - not being able to issue commands to
>an ATA device could also be a bus issue, caused by NOT calling the proper
>INT 10 setup functions on resume.
>
>I'm going to build a debug kernel today and see if I can start tracking the
>problem to it's root.
>
>- Zack
>
Are you new messages?
My kernel configuration file is similar to your.
But I removed the debugging options.
Can you list a step to test?
I'll test each side to provide you with full information, which make it easy
to find the problem?
_______________________________________________
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"
