Re: Kernel 9.1 panic with azalia
On Sat, Jun 26, 2021 at 06:49:17AM +0200, Martin Husemann wrote: > Also any reason to use 9.1 instead of 9.2 or 9.2_STABLE? > (Not that I think it would make a difference for azalia) Practical reason: I start to update the node I'm doing my main programing/developing work on and I then, after having verified that things are rolling and with some delay---specially if the node is a remote production server that it is not possible to update easily and for safety only when I have physical access to it in case of problem (this time: there was)---I put other nodes in sync to not have to cross-compile between NetBSD versions. When I updated the developing node, NetBSD was at 9.1. Since, for what I know (not much), virtualization always(?) present a defined common pseudo-hardware interface, I imagine that there is no virtualization that will allow to test a kernel in a VM, with access to an image of the real hardware present, so that one can verify that a tentative kernel will run on the actual hardware before switching kernels? I have still to verify that an UEFI bootloader will allow to implement by scripting a "boot once", so that if a new kernel (on a remote host) crashes, it reboots with a kernel that is known to work. It is probably possible to implement this with the existence of persistent storage of UEFI variables. -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: Kernel 9.1 panic with azalia
On Fri, Jun 25, 2021 at 09:32:40PM +, RVP wrote: > On Fri, 25 Jun 2021, RVP wrote: > > >On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: > > > >>But if azalia is not supported anymore because it crashes the > >>kernel, shouldn't it be removed and not simply be commented out? > >> > > > >I think that your message is the first indication that azalia(4) > >is slowly bit-rotting... > > > > Just checked, and azalia no longer exists in the 9.99[.82] tree. Thanks to have checked! -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: Kernel 9.1 panic with azalia
Also any reason to use 9.1 instead of 9.2 or 9.2_STABLE? (Not that I think it would make a difference for azalia) Martin
Re: Kernel 9.1 panic with azalia
On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: But if azalia is not supported anymore because it crashes the kernel, shouldn't it be removed and not simply be commented out? I think that your message is the first indication that azalia(4) is slowly bit-rotting... -RVP
Re: Kernel 9.1 panic with azalia
On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: The new kernel panics at boot time with azalia (it is not crucial since it is a server and I have no use with it but I have added the support since it's here and 7.1.1 has no problem with it). You must've compiled a custom kernel. 9.1 GENERIC has the `azalia' driver commented out; hdaudio(4) is used instead. Try the same. -RVP
Re: Kernel 9.1 panic with azalia
Hello, On Fri, Jun 25, 2021 at 08:47:30PM +, RVP wrote: > On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: > > >The new kernel panics at boot time with azalia (it is not crucial since > >it is a server and I have no use with it but I have added the support > >since it's here and 7.1.1 has no problem with it). > > > > You must've compiled a custom kernel. 9.1 GENERIC has the `azalia' > driver commented out; hdaudio(4) is used instead. Try the same. Sure. But if azalia is not supported anymore because it crashes the kernel, shouldn't it be removed and not simply be commented out? (To give some context, when I build a new kernel, I just adjust the previous config for things that have been removed or changed, so I'm mainly diffing GENERIC to GENERIC to see changes, while my configs are not GENERIC---I remove support for whatever hardware is not here or whatever filesystems the node will not use ever, for example). Thanks for the tip though. Best, -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
Re: Kernel 9.1 panic with azalia
On Fri, 25 Jun 2021, RVP wrote: On Fri, 25 Jun 2021, tlaro...@polynum.com wrote: But if azalia is not supported anymore because it crashes the kernel, shouldn't it be removed and not simply be commented out? I think that your message is the first indication that azalia(4) is slowly bit-rotting... Just checked, and azalia no longer exists in the 9.99[.82] tree. -RVP
Kernel 9.1 panic with azalia
Hello, I was trying to update a server, running a NetBSD 7.1.1 (amd64) to NetBSD 9.1. The new kernel panics at boot time with azalia (it is not crucial since it is a server and I have no use with it but I have added the support since it's here and 7.1.1 has no problem with it). It's a production server so I can not easily do tests. Here is the message (reconstructed by hand from written info---may contain blunders): azalia0: codec[2]: 0x1106/0x0441 (rev. 1.0), HDA rev. 1.0 panic: kmem_free(0xce000801,11) != allocated size 1844660333743030159360 vpanic() at netbsd:vpanic +0x143 snprintf() at netbsd:snprintf kmem_alloc() at netbsd:kmem_alloc generic_mixer_ensure_capacity() at netbsd:generic_mixer_ensure_capacity +0x7b generic_mixer_init() at netbsd:generic_mixer_init +0x1143 azalia_attach_intr() at netbsd:azalia_attach_intr +0xbf8 config_interrupts_thread() at netbsd:config_interrupts_thread +0x7e cpu0: End Traceback fatal breakpoint trap in supervisor mode trap type 1 code 0 rip 0x8021cc2d cs 0x8 rflags 0x202 0 ilevel 0 rsp 0xcc006741 curlwp 0x060092cacd80 pid 0.37 lowest kstack 0xcc00674192e0 stopped in pid 0.37 (system) at netbsd:breakpoint: 0x5: leave Note: with the 7.1.1 kernel, for azalia I have: azalia0: codec[2]: 0x1106/0x0441 (rev. 1.0), HDA rev. 1.0 azalia0: codec[3]: 0x8086/0x2806 (rev. 0.0), HDA rev. 1.0 The size in the panic is non sense. Hoping this can give enough clue to debug. TIA, -- Thierry Laronde http://www.kergis.com/ http://kertex.kergis.com/ http://www.sbfa.fr/ Key fingerprint = 0FF7 E906 FBAF FE95 FD89 250D 52B1 AE95 6006 F40C
