Date: Mon, 30 Mar 2009 05:53:09 +0200 From: Dominic Fandrey <kamikaze@bsdforen.de> To: Alexander Motin <mav@FreeBSD.org> Cc: freebsd-stable@freebsd.org Subject: Re: powerd broken Message-ID: <49D04225.7070207@bsdforen.de> In-Reply-To: <49CF9C19.3020509@FreeBSD.org> References: <1238293386.00093672.1238281804@10.7.7.3> <49CF0803.1070505@FreeBSD.org> <49CF2F8D.6000905@bsdforen.de> <49CF4EB9.60108@FreeBSD.org> <49CF49F5.6010800@bsdforen.de> <49CF615A.6050304@FreeBSD.org> <49CF595A.30805@bsdforen.de> <49CF6B28.2080400@FreeBSD.org> <49CF60AB.4040709@bsdforen.de> <49CF6899.2060002@bsdforen.de> <49CF8E8D.1080604@bsdforen.de> <49CF9C19.3020509@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Motin wrote: > Dominic Fandrey wrote: >> I can rule out drm0 as the cause, because uhci0 is the only common >> presence in all occurrences of this problem. > > You have other examples? If you mean "irq16: hdac0 uhci+" string, then > "+" there means "and some other devices", which in this case is probably > drm0. I didn't know that. > There were some drm related commits last time and there are also some > IRQ related problems were reported/patched in CURRENT recently. So I > would not ignore this possibility without additional testing. > Thanks, will do.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49D04225.7070207>