On Tue, 1 Nov 2011, Sebastian Chmielewski wrote:
> On Tue, 01 Nov 2011 13:53:52 +0000
> Gavin Atkinson <ga...@freebsd.org> wrote:
>
> > Can I confirm that you have tried suspend/resume without any of the USB
> > code loaded?
> >
> > If you set sysctl debug.acpi.resume_beep=1 before suspend, do you hear a
> > beep on resume?
> >
> >
> I have
> kldunload {uhci,ohci,ehci} in rc.suspend.
> kldload {uhci,ohci,ehci} in rc.resume.
Just checking: this is with a kernel built without uhci, ohci and ehci?
> There is no beep on resume but beep maybe simulated through soudcard? (It's a
> laptop).
The beep is generated by programming the good old-fashioned timer chip;
if the laptop normally beeps on boot or error it should beep on resume.
With this, my Thinkpad T23 (piercingly) beeped for a full 60 seconds on
resume for months, until learning it was (here) uhci causing that hang.
(I've been vaguely hoping this might be fixed before 9.0-RELEASE ..)
> Screen is blank and nothing happens. Firewire is not functional too much
> (which I've reported).
> Same symptoms on 8.2-STABLE and 9.0-RC1.
You could try setting sysctl hw.acpi.verbose=1 from /etc/sysctl.conf and
then booting with verbose messages, which logs a lot more detail around
suspend and resume, which may provide clues (though some of that logging
obviously occurs after resume succeeds). Worth also maybe trying sysctl
hw.syscons.sc_no_suspend_vtswitch=1 which has helped on some laptops.
cheers, Ian
_______________________________________________
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"
