Martin, Theo, I would like to apologize you and other developers for spreading unhelpful advises which hurt the project.
I truly regret that and I am very sorry. Regards, Mikolaj On Fri, Jan 09, 2015 at 02:34:36AM +0100, Martin Pieuchot wrote: > Dear Mikolaj, > > On 09/01/15(Fri) 00:30, Mikolaj Kucharski wrote: > > Hi, > > > > This problem looks very similar as: > > > > https://marc.info/?l=openbsd-misc&m=140288534929223&w=2 > > > > On my i386 KVM after each upgrade I run this: > > > > #!/bin/sh > > > > for kernel in /bsd /bsd.mp > > do > > config -fe $kernel << EOF > > find mpbios > > disable mpbios > > find mpbios > > find acpimadt > > disable acpimadt > > find acpimadt > > quit > > EOF > > done > > > > > > Please CC me in any replies, I'm not receiving mails from `misc` > > Your email makes me really sad. > > It makes me really sad because I want to believe that you sent it in > order to help somebody. However you're doing the contrary and you are > doing it publicly. That means other people will later find your email > and, believing that you are trying to help, do what you recommend. > > Please do not recommend to *disable* anything in a kernel. > > Disabling something that you don't understand might be good enough for > you. But it does not help me, or I believe anyone else, to fix the > damn problem people are having. > > Instead of giving such advices, I'd suggest you to read sendbug(1) and > fill a bug report as complete as possible such that competent people > might have a chance to help you fix your problem. If you do that you > might be able to run a GENERIC kernel without disabling anything. You > might also prevent other people to send other bug reports for the same > problem. > > Think about it, the system you're running is good because *a lot* of > other people did not deactivate anything but instead sent good or not > so good bug reports. > > Sadly you've just answered to yet another bug report without information, > giving a bad advice and nobody can improve OpenBSD. > > I hope I didn't sound to harsh and I hope to see a nice bug report from > you in bugs@ soon. > > Best regards, > Martin On Thu, Jan 08, 2015 at 06:56:46PM -0700, Theo de Raadt wrote: > > This problem looks very similar as: > > > > https://marc.info/?l=openbsd-misc&m=140288534929223&w=2 > > > > On my i386 KVM after each upgrade I run this: > > > > #!/bin/sh > > > > for kernel in /bsd /bsd.mp > > do > > config -fe $kernel << EOF > > find mpbios > > disable mpbios > > find mpbios > > find acpimadt > > disable acpimadt > > find acpimadt > > quit > > EOF > > done > > > > > > Please CC me in any replies, I'm not receiving mails from `misc` > > Mikolaj, > > This kind of mail wants me want to push for removal of the config -e > support. > > It is incredibly bad advice. > > Yes, there are bugs in the interrupt handling code, every operating > system on PCs has this because it is very difficult code to debug. > And machines are slowly changing in behaviour. But advising users to > all run different code paths leads to a fragmented userbase running > different kernel code paths, which lead them to all submit different > misleading bug reports and as a result, more pressure on fewer > developers. Who might eventually stop caring as much. > > If as a general rule we all want better code running on our systems, > where do you fit in? > > Let me be blunt. Your advice is bad.
