Date: Sat, 04 Apr 2009 11:44:10 -0500 From: Robert Noland <rnoland@FreeBSD.org> To: Dominic Fandrey <kamikaze@bsdforen.de> Cc: Alexander Motin <mav@FreeBSD.org>, freebsd-stable@freebsd.org Subject: Re: powerd broken Message-ID: <1238863450.65025.55.camel@balrog.2hip.net> In-Reply-To: <49D73715.6050700@bsdforen.de> 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> <49D5DA33.4010800@bsdforen.de> <1238778004.65025.30.camel@balrog.2hip.net> <49D73715.6050700@bsdforen.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-r00CPZI/2yqbBTSXUAlu Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2009-04-04 at 12:31 +0200, Dominic Fandrey wrote: > Robert Noland wrote: > > On Fri, 2009-04-03 at 11:43 +0200, Dominic Fandrey wrote: > >> 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.=20 > >>> You have other examples? If you mean "irq16: hdac0 uhci+" string, the= n > >>> "+" there means "and some other devices", which in this case is proba= bly > >>> drm0. > >>> > >>> 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. > >>> > >> Is there anything I can do, apart from turning off drm? This is really > >> annoying (well, it eats a whole core while I'm compiling and it keeps > >> the fans going, when the machine should be idle). > >> > >> Is there somehow I can generate useful information? Someone to send a > >> kernel dump to? > >=20 > > Use a radeon? ;( >=20 > Nay, I use an Intel GM965. >=20 > > I've been working on the Intel vblank / irq issues. Every time I commi= t > > something thinking that I have it resolved, it isn't. So I'm waiting o= n > > hardware to arrive that will let me test this all more thoroughly. I d= o > > have a patch that I think fixes most of the issues on Intel, but the dd= x > > driver is still doing some silly things that cause issues in some cases= . > > I *think* the only outstanding issue I have with Intel is if something > > is rendering (synced to vblank or not) when the display goes into dpms > > sleep, there isn't anything to block that app, so it renders as hard as > > it can even though it isn't being displayed. In reality, this probably > > isn't a huge issue, but running gears while the display is asleep keeps > > the cpu at 100%, which isn't ideal. Normal apps that aren't trying to > > draw as fast as they can, shouldn't cause an issue. > >=20 > > The other issue with my current patches is that I had to change around = a > > fair amount of infrastructure code to try and fix Intel's brain damage, > > so I have to finish fixing the rest of the drivers so they don't break. > > I have Intel and radeon fixed, I just have to hit the more obscure > > drivers. > >=20 > > robert. >=20 > So it appears all I've got to do is wait. Correct me if I'm wrong. You can set the tuneable hw.drm.msi=3D0 for now and see if that helps. I haven't followed this whole thread, but the primary issue that people were having is that interrupts would not work after a vt switch with msi. So, it that isn't your issue, you may need to look elsewhere. robert. > Regards --=20 Robert Noland <rnoland@FreeBSD.org> FreeBSD --=-r00CPZI/2yqbBTSXUAlu Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEABECAAYFAknXjloACgkQM4TrQ4qfROOFswCfSiqSWpiEW6w/OZbt+ivVkcSz 4y4An2RSOccgMZ1dTMWSMT4i68ksJJKx =Bzm/ -----END PGP SIGNATURE----- --=-r00CPZI/2yqbBTSXUAlu--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1238863450.65025.55.camel>