Re: [OpenIndiana-discuss] Boot hangs after configuring, devices (last notice is of pseudo devices
Am 24.03.23 um 11:02 schrieb russell: On 24. Mar 2023, at 10:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not ?if? but ?when? - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? It is a bit premature to declare everything dead, but, the fact is, we can not rely on binary only drivers forever. As soon as Oracle will decide to stop distributing Solaris, nvidia will have no reason to distribute those binary drivers. Note, we *still* do rely on few closed binaries to distribute illumos itself. rgds, toomas There was a feature request #8069 for AMDGPU support which is the latest open source AMD driver for AMD graphics cards, given how AMD has improved their CPUs and Graphics Cards under Lisa Su, would now be the time to consider adding better support for AMD cards. Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss We need people to do the work. Alas we seem to lack companies interested in desktop usage and thus there is absolutely no interest in funding/supporting illumos driver development for graphics cards and other desktop related areas. I myself am missing support for Blutooth LE which is being used in newer mice and keyboards (eg. from Logitech). Regards Andreas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring, devices (last notice is of pseudo devices
On 24. Mar 2023, at 10:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not ?if? but ?when? - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? It is a bit premature to declare everything dead, but, the fact is, we can not rely on binary only drivers forever. As soon as Oracle will decide to stop distributing Solaris, nvidia will have no reason to distribute those binary drivers. Note, we *still* do rely on few closed binaries to distribute illumos itself. rgds, toomas There was a feature request #8069 for AMDGPU support which is the latest open source AMD driver for AMD graphics cards, given how AMD has improved their CPUs and Graphics Cards under Lisa Su, would now be the time to consider adding better support for AMD cards. Kind Regards Russell ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 24/03/2023 10:03, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 10:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? It is a bit premature to declare everything dead, but, the fact is, we can not rely on binary only drivers forever. As soon as Oracle will decide to stop distributing Solaris, nvidia will have no reason to distribute those binary drivers. Solaris is officially supported until 2030, so there's (at least formally) time left as long as the ABI does not become incompatible without a possible workaround. And after that, old drivers will still work until new graphics cards appear. So there's time to work on a possible migration path. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/24/23 09:50, Udo Grabowski (IMK) wrote: On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Maybe it's only because i use legacy boot or some Dell bios specific special case... ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
> On 24. Mar 2023, at 10:50, Udo Grabowski (IMK) wrote: > > > > On 24/03/2023 09:43, Marc Lobelle wrote: >> On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: >>> On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: > The challenge of answering that is you often don't know the answer > until you see it > > The ::stacks command will give you asummarized view of every kernel > thread's stack > the ::cpuinfo -v command will show you what the CPUs are doing now (or > were doing, before you got into kmdb). > > Both or either might have a smoking gun of some kind, but it's hard to > predict what it might look like. > > ___ > openindiana-discuss mailing list > openindiana-discuss@openindiana.org > https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? >>> That is something one can work out with debugger. But, this is binary only >>> driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside >>> Oracle Solaris? This means, the question is not “if” but “when” - it is >>> only question of time when such drivers become unusable for us. Without gfx >>> driver development, the desktop variant of illumos is dead end. >> without desktop, it would unfortunately mean the dead of illumos. If Oracle >> solaris drivers become unusable shouldn't illumos move to another driver >> interface that is maintained ? > > Maybe we wait until the cause for the problem is known before > declaring everything dead ? > It is a bit premature to declare everything dead, but, the fact is, we can not rely on binary only drivers forever. As soon as Oracle will decide to stop distributing Solaris, nvidia will have no reason to distribute those binary drivers. Note, we *still* do rely on few closed binaries to distribute illumos itself. rgds, toomas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 24/03/2023 09:43, Marc Lobelle wrote: On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Maybe we wait until the cause for the problem is known before declaring everything dead ? ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/24/23 08:16, Toomas Soome via openindiana-discuss wrote: On 24. Mar 2023, at 07:58, Stephan Althaus wrote: On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. without desktop, it would unfortunately mean the dead of illumos. If Oracle solaris drivers become unusable shouldn't illumos move to another driver interface that is maintained ? Best regards Marc rgds, toomas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
> On 24. Mar 2023, at 07:58, Stephan Althaus > wrote: > > On 3/22/23 20:56, Richard Lowe wrote: >> The challenge of answering that is you often don't know the answer >> until you see it >> >> The ::stacks command will give you asummarized view of every kernel >> thread's stack >> the ::cpuinfo -v command will show you what the CPUs are doing now (or >> were doing, before you got into kmdb). >> >> Both or either might have a smoking gun of some kind, but it's hard to >> predict what it might look like. >> >> ___ >> openindiana-discuss mailing list >> openindiana-discuss@openindiana.org >> https://openindiana.org/mailman/listinfo/openindiana-discuss > > Hello! > > In one of my earlier update-tests i had a problem with the first > OI-nvidia-525 version in cooperation with Virtualbox, > so i had the idea to test this: > > I uninstalled 'userland-incorporation' and 'entire' as prerequisite to > install nvidia version 515, > now it boots! > > So, nvidia in the most recent version 525 stopped the boot process. (?) > > i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) > is on the supported list for this version: > https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ > > > How/Why should the display driver be able to interrupt the boot process ? > How/Why should the display driver be able to interrupt the boot process > without further notice? > That is something one can work out with debugger. But, this is binary only driver? Built *for Oracle Solaris 11.4*? With API interfaces changed inside Oracle Solaris? This means, the question is not “if” but “when” - it is only question of time when such drivers become unusable for us. Without gfx driver development, the desktop variant of illumos is dead end. rgds, toomas ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/22/23 20:56, Richard Lowe wrote: The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! In one of my earlier update-tests i had a problem with the first OI-nvidia-525 version in cooperation with Virtualbox, so i had the idea to test this: I uninstalled 'userland-incorporation' and 'entire' as prerequisite to install nvidia version 515, now it boots! So, nvidia in the most recent version 525 stopped the boot process. (?) i checked with NVidia Solaris Driver Archive that my chipset (Quadro M1200) is on the supported list for this version: https://www.nvidia.com/Download/driverResults.aspx/199661/en-us/ How/Why should the display driver be able to interrupt the boot process ? How/Why should the display driver be able to interrupt the boot process without further notice? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
The challenge of answering that is you often don't know the answer until you see it The ::stacks command will give you asummarized view of every kernel thread's stack the ::cpuinfo -v command will show you what the CPUs are doing now (or were doing, before you got into kmdb). Both or either might have a smoking gun of some kind, but it's hard to predict what it might look like. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/22/23 10:42, Udo Grabowski (IMK) wrote: On 21/03/2023 23:09, Stephan Althaus wrote: On 3/21/23 20:53, Richard Lowe wrote: A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for your input. I tried the kmdb switched on on boot, with ::cont i have the same situation that i can't escape the running process to get the ::stack Comparing the boot messages of the working BE and the not-working one, it stops between these two pseudo-devices: Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: signalfd0 *Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is /pseudo/signalfd@0* Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0 Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is /pseudo/timerfd@0 The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then nothing more happens. You can pin that down to timerfd if you just mount the new BE and move away /usr/kernel/drv/amd64/timerfd and see if it then boots. Consult 'man timerfd' to convince yourself that that driver is irrelevant to illumos... ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! I followed your hint and removed timerfd, and uninstalled smartmontools in the new BE but no change. I looked around a bit more with the help of ::dcmds and found all sort of drivers, threads, tasks, it seems that rpool/ is mounted, (how can i verify?) almost everything i think of is there (sort of) - and no word of errors.. I just can't find a reason why it is not "going on everything looks fine..." Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 21/03/2023 23:09, Stephan Althaus wrote: On 3/21/23 20:53, Richard Lowe wrote: A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for your input. I tried the kmdb switched on on boot, with ::cont i have the same situation that i can't escape the running process to get the ::stack Comparing the boot messages of the working BE and the not-working one, it stops between these two pseudo-devices: Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: signalfd0 *Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is /pseudo/signalfd@0* Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0 Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is /pseudo/timerfd@0 The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then nothing more happens. You can pin that down to timerfd if you just mount the new BE and move away /usr/kernel/drv/amd64/timerfd and see if it then boots. Consult 'man timerfd' to convince yourself that that driver is irrelevant to illumos... -- Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT http://www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/21/23 20:53, Richard Lowe wrote: A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello! Thanks for your input. I tried the kmdb switched on on boot, with ::cont i have the same situation that i can't escape the running process to get the ::stack Comparing the boot messages of the working BE and the not-working one, it stops between these two pseudo-devices: Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: signalfd0 *Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] signalfd0 is /pseudo/signalfd@0* Mar 21 22:19:56 dell7720 pseudo: [ID 129642 kern.notice] pseudo-device: timerfd0 Mar 21 22:19:56 dell7720 genunix: [ID 936769 kern.notice] timerfd0 is /pseudo/timerfd@0 The line with "*signalfd0 is /pseudo/signalfd@0*" is the last output, then nothing more happens. Now i was able to enable kmdb. i found processes, stacks related to my USB keyboard, apix_no_interrupt,.. would be nice if i knew what to search for :-) how to find and select the right thread and then get the stack?? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
A good thing to do is to get into mdb when it's hung, and see where we are with the ::stacks command. https://illumos.org/books/dev/debugging.html has other tips. I would add if you set the 1 bit of `moddebug` when you're in kmdb (I think moddebug/W 8001 is verbose and stop on _init, but I tend to forget), we will stop whenever a module `_init` is called, which can be a good trick to try to narrow down where things might have gone wrong if we don't respond to any means to get into kmdb. More manually, an illumos version which works and one which doesn't work will narrow down which illumos changes might have caused problems. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 3/21/23 14:23, Udo Grabowski (IMK) wrote: On 20/03/2023 21:45, Stephan Althaus wrote: Hello! On 18.03.2023 i made a pkg update, after that the Boot hangs after configuring devices (last notice is of pseudo devices with boot option 'verbose') Nothing happens on the prompt... "beadm mount..." shows no fresh logfiles, so no info there, i should use some debug options but i am not familiar to that :-/ Any hints ? Didn't have such a failure after updating and booting today, but didn't reboot since 14.3. So I would recommend to revert to the previous BE and update that again. ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss Hello Udo! I did that yesterday, no change. i have in mind there was a relatively change in device numbering when building the device tree.. To summarize, the working BE is of 2022:11:23, the newly created by 'pkg update' won't work and stops after "configuring devices". Any things i could do to debug? Regards, Stephan ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
Re: [OpenIndiana-discuss] Boot hangs after configuring devices (last notice is of pseudo devices
On 20/03/2023 21:45, Stephan Althaus wrote: Hello! On 18.03.2023 i made a pkg update, after that the Boot hangs after configuring devices (last notice is of pseudo devices with boot option 'verbose') Nothing happens on the prompt... "beadm mount..." shows no fresh logfiles, so no info there, i should use some debug options but i am not familiar to that :-/ Any hints ? Didn't have such a failure after updating and booting today, but didn't reboot since 14.3. So I would recommend to revert to the previous BE and update that again. -- Dr.Udo Grabowski Inst.f.Meteorology & Climate Research IMK-ASF-SAT http://www.imk-asf.kit.edu/english/sat.php KIT - Karlsruhe Institute of Technology http://www.kit.edu Postfach 3640,76021 Karlsruhe,Germany T:(+49)721 608-26026 F:-926026 ___ openindiana-discuss mailing list openindiana-discuss@openindiana.org https://openindiana.org/mailman/listinfo/openindiana-discuss
