Re: Crash on TOSHIBA PORTEGE Z30-A laptop
> If there isn't a newer BIOS that resolves this, I would tend to return the > box as not suitable. This is the case, there’s no BIOS update. Thank you very much, anyway. Cheers, /Wesley De : Philip Guenther Envoyé : lundi 23 octobre 2023 00:39 À : wes...@technicien.io Cc : bugs@openbsd.org; m...@openbsd.org Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop On Sat, Oct 21, 2023 at 2:27 AM mailto:wes...@technicien.io> > wrote: Hi Philip, Thank you very much for your answer. I tried to disable all options (+devices) possible. Same issue. And what's about disable acpi in the kernel using the bsd.re-config? As Mike and Theo noted, this will certainly cause problems. Do you think If I replace the wireless card by somthing else, It could resolve this issue? Very unlikely. The problem is the stack depth of the ACPI processing. The crash you saw had the wifi interrupt occur during the ACPI processing but it could just as well happen with some other device interrupting the ACPI processing. If there isn't a newer BIOS that resolves this, I would tend to return the box as not suitable. Phlip Guenther
Re: Crash on TOSHIBA PORTEGE Z30-A laptop
On Sat, Oct 21, 2023 at 2:27 AM wrote: > Hi Philip, > > Thank you very much for your answer. > > I tried to disable all options (+devices) possible. Same issue. > And what's about disable acpi in the kernel using the bsd.re-config? > As Mike and Theo noted, this will certainly cause problems. > Do you think If I replace the wireless card by somthing else, It could > resolve this issue? > Very unlikely. The problem is the stack depth of the ACPI processing. The crash you saw had the wifi interrupt occur during the ACPI processing but it could just as well happen with some other device interrupting the ACPI processing. If there isn't a newer BIOS that resolves this, I would tend to return the box as not suitable. Phlip Guenther
Re: Crash on TOSHIBA PORTEGE Z30-A laptop
Mike Larkin wrote: > On Sat, Oct 21, 2023 at 01:27:21PM +0400, wes...@technicien.io wrote: > > Hi Philip, > > > > Thank you very much for your answer. > > > > I tried to disable all options (+devices) possible. Same issue. > > And what's about disable acpi in the kernel using the bsd.re-config? > > > > Not advisable. You'll probably end up causing even more problems. You mean, like > disable acpi* Meaning, using a glob, which is a lot like a regular expression. Are you not aware of the wise words on the internet about 'and now you have two problems'? Anytime anyone says 'disable acpi', they should be corrected. The correct command is 'disable pci'. Trust me.
Re: Crash on TOSHIBA PORTEGE Z30-A laptop
On Sat, Oct 21, 2023 at 01:27:21PM +0400, wes...@technicien.io wrote: > Hi Philip, > > Thank you very much for your answer. > > I tried to disable all options (+devices) possible. Same issue. > And what's about disable acpi in the kernel using the bsd.re-config? > Not advisable. You'll probably end up causing even more problems. > Do you think If I replace the wireless card by somthing else, It could > resolve this issue? > > > /Wesley > > > > -Message d'origine- > De : owner-b...@openbsd.org De la part de Philip > Guenther > Envoyé : samedi 21 octobre 2023 03:23 > À : wes...@technicien.io > Cc : bugs@openbsd.org; m...@openbsd.org > Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop > > On Fri, Oct 20, 2023 at 1:23 PM wrote: > > > I've recently installed OpenBSD 7.4 on this laptop. > > > > However, I'm experiencing random crashes. These occur at various > > times, including during kernel loading (before running /etc/rc), > > > > or later while I'm using the system. > > > > > > I've included the contents of /var/run/dmesg.boot below and attached > > the screens with the ddb output command. > > > ... > > > bios0: vendor TOSHIBA version "Version 4.30" date 04/26/2018 > > > > The screenshots show that the fault happens during a wifi interrupt that > catches the ACPI thread processing a very deeply nested AML code. I suspect > it's actually running out of kernel stack space as a result. > Everything below is based on that hypothesis. > > So, the first thing to try is to see if there's a BIOS update newer than the > 2018 rev it currently has. They may have optimized the AML code, or at least > made it less deeply nested. > > Another possibility is to see if there's a device you can disable that would > result in that AML not being called. If there's anything that you aren't > using then disable it in the BIOS and hope. > > The last possibility would be to build a kernel which allocates more pages > per thread for its kernel stack by bumping the UPAGES #define in > /usr/src/sys/arch/amd64/include/param.h and building a new kernel. It's > really only the ACPI thread that needs this, but we don't currently have code > to control that on a per-thread basis. > > > Philip Guenther >
Re: Crash on TOSHIBA PORTEGE Z30-A laptop
Hi Philip, Thank you very much for your answer. I tried to disable all options (+devices) possible. Same issue. And what's about disable acpi in the kernel using the bsd.re-config? Do you think If I replace the wireless card by somthing else, It could resolve this issue? /Wesley -Message d'origine- De : owner-b...@openbsd.org De la part de Philip Guenther Envoyé : samedi 21 octobre 2023 03:23 À : wes...@technicien.io Cc : bugs@openbsd.org; m...@openbsd.org Objet : Re: Crash on TOSHIBA PORTEGE Z30-A laptop On Fri, Oct 20, 2023 at 1:23 PM wrote: > I've recently installed OpenBSD 7.4 on this laptop. > > However, I'm experiencing random crashes. These occur at various > times, including during kernel loading (before running /etc/rc), > > or later while I'm using the system. > > > I've included the contents of /var/run/dmesg.boot below and attached > the screens with the ddb output command. > ... > bios0: vendor TOSHIBA version "Version 4.30" date 04/26/2018 > The screenshots show that the fault happens during a wifi interrupt that catches the ACPI thread processing a very deeply nested AML code. I suspect it's actually running out of kernel stack space as a result. Everything below is based on that hypothesis. So, the first thing to try is to see if there's a BIOS update newer than the 2018 rev it currently has. They may have optimized the AML code, or at least made it less deeply nested. Another possibility is to see if there's a device you can disable that would result in that AML not being called. If there's anything that you aren't using then disable it in the BIOS and hope. The last possibility would be to build a kernel which allocates more pages per thread for its kernel stack by bumping the UPAGES #define in /usr/src/sys/arch/amd64/include/param.h and building a new kernel. It's really only the ACPI thread that needs this, but we don't currently have code to control that on a per-thread basis. Philip Guenther
Re: Crash on TOSHIBA PORTEGE Z30-A laptop
On Fri, Oct 20, 2023 at 1:23 PM wrote: > I've recently installed OpenBSD 7.4 on this laptop. > > However, I'm experiencing random crashes. These occur at various times, > including during kernel loading (before running /etc/rc), > > or later while I'm using the system. > > > I've included the contents of /var/run/dmesg.boot below and attached the > screens with the ddb output command. > ... > bios0: vendor TOSHIBA version "Version 4.30" date 04/26/2018 > The screenshots show that the fault happens during a wifi interrupt that catches the ACPI thread processing a very deeply nested AML code. I suspect it's actually running out of kernel stack space as a result. Everything below is based on that hypothesis. So, the first thing to try is to see if there's a BIOS update newer than the 2018 rev it currently has. They may have optimized the AML code, or at least made it less deeply nested. Another possibility is to see if there's a device you can disable that would result in that AML not being called. If there's anything that you aren't using then disable it in the BIOS and hope. The last possibility would be to build a kernel which allocates more pages per thread for its kernel stack by bumping the UPAGES #define in /usr/src/sys/arch/amd64/include/param.h and building a new kernel. It's really only the ACPI thread that needs this, but we don't currently have code to control that on a per-thread basis. Philip Guenther
