Date: Tue, 8 May 2007 23:38:51 -0700 From: Louis Kowolowski <louisk@cryptomonkeys.com> To: Sam Leffler <sam@errno.com> Cc: freebsd-current@freebsd.org Subject: Re: if_ath breaks s3 suspend/resume [Was: ACPI S3 wakeup problem (beeeeeeeeep)] Message-ID: <20070509063851.GD1724@cryptomonkeys.com> In-Reply-To: <46414861.50800@errno.com> References: <200705081904.39469.h.schmalzbauer@omnisec.de> <200705090035.40756.h.schmalzbauer@omnisec.de> <46414861.50800@errno.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--3Pql8miugIZX0722 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, May 08, 2007 at 09:04:49PM -0700, Sam Leffler wrote: > Harald Schmalzbauer wrote: > > Am Dienstag, 8. Mai 2007 schrieb Harald Schmalzbauer: > >> Hello, > >> > >> I found the sysctl "debug.acpi.resume_beep" and enabled it. > >> When I send my Vaio SRX41p sleeping with acpiconf -s3 it never waked up > >> again. Now with this sysctl enabled I hear a continuing beep, but the= =20 > >> hard drive stays powered down, also the LCD keeps unlit. > >> > >> Any hints how I can find out what's going wrong? > >> Tuning hw.acpi.reset_video doesn't change anything. > >=20 > > Again, the fabulous handbook gave me the hint to remove all devices from > > the kernel and dynamically load them. > > This revealse if_ath as the culprit. (the last I tried after usb,=20 > > fwohci, pcm, ichsmb) > >=20 > > Could this be related to the interrupt strom problems with ath (I often= =20 > > get storm warnings, all drivers share IRQ9 on this laptop)? >=20 > Unclear but there's been an outstanding complaint against ath related to > suspend for a while. Specifically if you touch certain registers in the > h/w after the chip has been put to sleep you can hang the pci bus. I've > asked people that can reproduce the problem to narrow down the code path > by which the driver is entered but w/o luck. >=20 I don't know for sure, but I think I might be seeing a similar issue with atheros, but during bootup instead of suspend. It's not reproducable in a reliable fashion, but sometimes I get a hang during bootup shortly after=20 ath0 is brought up. I also see an interupt storm on irq11, which I believe= =20 is also shared by ichsmb (at least on my Thinkpad T60p). If there is more information I can make available, I'm more than willing. = =20 I'd like to provide a defined way to cause this, but it doesn't seem to=20 happen in a "regular" way. If anyone has suggestions on this, please share. Thanks. --=20 Louis Kowolowski KE7BAX louisk@cryptomonkeys.com Cryptomonkeys: http://www.cryptomonkeys.com/~louisk Warning: Do not point laser at remaining eye! --3Pql8miugIZX0722 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGQWx7Zk0r6oAkN7YRAjJ7AKCBMDLiSFD8XOMY0IeCJS2KGPfWzQCfeb+Q tSdf3OloTykixll8QI4a4c4= =tDG6 -----END PGP SIGNATURE----- --3Pql8miugIZX0722--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070509063851.GD1724>