> 2012/6/4, Theo de Raadt <[email protected]>: > >> 2012/6/4, Theo de Raadt <[email protected]>: > >> >> Try with acpi disabled. > >> > > >> > Sure, try with acpi disabled, and when something else doesn't work, > >> > we will completely ignore that mail. > >> > > >> > Without acpi is like saying "disable pci". > >> > > >> > >> Of course this is temporary solution. > > > > Stop spreading lies. > > > > Most modern PC's will not run if the ACPI code is disabled. They will > > break in a multitude of other ways, and you are not helping find the > > bug AT ALL. The least of the problem is that the fan might not run. > > > > They might map reigsters wrong. They might map interrupts wrong. They > > will route interrupts from from behind ppb bridges. Disabling the acpi > > codebase creates many crazy, crazy, crazy side effects. > > > > Stop giving such bad advice! > > > > If you want to help debug his problem, then help him. But giving him > > bad advice and then putting the problem on us is unacceptable. > > > > Gregor Pintar, if you are unqualified to give good advice in an area, > > don't reply to people. > > > > I didn't mean as solution to run with acpi disabled, but only to get more > info. > Sorry, I wasn't clear.
Geez, you're not listening; Disabling acpi does not help get more info! 10 years ago, it did. On any machine build after 2009, it doesn't. There must be bloody way to stop the spread of bad advice!
