Re: Sudden reboot every 5-10 minutes on latest snapshot
Ali Farzanrad wrote: > Thomas Frohwein wrote: > > On Sat, May 25, 2024 at 12:06:39PM +, Ali Farzanrad wrote: > > > Ali Farzanrad wrote: > > > > Alexandre Ratchov wrote: > > > > > On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote: > > > > > > Alexandre Ratchov wrote: > > > > > > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote: > > > > [...] > > > > > > I have another problem here. My USB keyboard works great in BOOTX64.EFI > > > > but will not work on kernel config. > > > > > > > > I created /etc/bsd.re-config file and rebooted my system twice to > > > > disable azalia and then checked if it is disabled using config(8) and > > > > dmesg(8). > > > > > > > > Even when azalia is disabled my system gets sudden reboots. > > > > First sudden reboot was just after playing a music; but next 2 reboots > > > > was happened without playing anything. > > > > > > > > > Then, just do your regular stuff and see if the system reboots. > > > > > > I tested again with my patch. When azalia is disabled, it suddenly > > > reboots after few minutes, without playing anything. When azalia is > > > enabled, it lives. > > > > > > > This looks to me like you are chasing down a new rabbit hole every time > > I open one of your emails. I'd suggest you take a step back from all > > the stuff you seem to be trying without having a firm grasp on how to > > observe or report reproducibility. Have you tried out sthen@'s advice > > to check old kernels + snapshots[1]? I may have missed your response to > > this. You wrote that you rarely got the issue prior 17-May-2024? If > > that *is correct*, then you should be able to bisect using the snapshot > > archive around what date things change. > > Actually I see some kind of sudden reboots for such a long time (maybe > since the time I have this mini pc) which happen almost certainly on > every boot after a long shutdown! > > It is funny that my Windows 11 don't get those reboots; so I usually > use Windows for an hour, then reboot to OpenBSD without facing those > sudden reboots. > > Anyway, I tested this snapshot for few days: > https://ftp.hostserver.de/archive/2024-05-20-0105 > > I only get sudden reboots after a long shutdown (for example boot after > 3 hours off); however using the next snapshot: > https://ftp.hostserver.de/archive/2024-05-21-0105 > > I saw this other kind of sudden reboots which might happen after every > boot/reboot (not just after a long shutdown). > > > I am highlighting *is correct* above because your issue seems to be > > unpredictable enough that a few minutes of testing don't mean anything. > > I suggest you try to find a *clear difference*, meaning between a > > snapshot where no reboot happens for ideally a whole day of use, and > > the next one where it clearly happens very quickly (and reproducible > > at least a second or third time). > > I couldn't find a snapshot without any sudden reboot at all. > > > Your reports also make me wonder how much customization you are > > running. You've mentioned at least compiling custom kernels and > > setting bsd.re-config. It's easy to find yourself in virtually > > unsolvable scenarios by configuring too much. It might be best to try > > a clean install, ideally without activating xenodm/X11. > > The bsd.re-config file was just for disabling azalia. > I have FDE using softraid level C without swap and /tmp mounted as mfs. > I don't think that I configured too much. > > Anyway, I also tested those snapshots on a clean install on a single > partition outside softraid and again without swap (I don't like swap); > I see similar results. > > I also disabled xenodm/X11 and see my OpenBSD lived for more than an > hour, then I started xenodm and it suddenly rebooted in less than 3 > minutes. > > I didn't test OpenBSD without xenodm/X11 much, because I need them; > that's why I disabled amdgpu and placed it in my bsd.re-config file. > Since then (~3 days) I see no single sudden reboot at all (not even I'm really sorry. My whole snapshot tests takes about 3 days. I tested 2024-05-20-0105 snapshot for about 2 days, and 2024-05-21-0105 snapshot with disabled amdgpu and then latest snapshot with disabled amdgpu together for about 1 day. > after a long shutdown). > > I'm currenly on latest snapshot with amdgpu disabled. > > Alexandre Ratchov wrote: > > On Sat, May 25, 2024 at 09:13:56AM +, Ali Farzanrad wrote: > > > > > > Even when azalia is disabled my system gets sudden reboots. > > > First sudden reboot was just after playing a music; but next 2 reboots > > > was happened without playing anything. > > > > > > > This suggests the reboots are not directly caused by the azalia's msi > > vs old-style interrupts. > > > > I'd suggest that you find and old enough snapshot (or release) that > > used to work reliably on this machine and make sure it still works > > reliably with the old software version. Not just an hour, use it few > > days for real work. > > As
Re: Sudden reboot every 5-10 minutes on latest snapshot
Thomas Frohwein wrote: > On Sat, May 25, 2024 at 12:06:39PM +, Ali Farzanrad wrote: > > Ali Farzanrad wrote: > > > Alexandre Ratchov wrote: > > > > On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote: > > > > > Alexandre Ratchov wrote: > > > > > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote: > > [...] > > > > I have another problem here. My USB keyboard works great in BOOTX64.EFI > > > but will not work on kernel config. > > > > > > I created /etc/bsd.re-config file and rebooted my system twice to > > > disable azalia and then checked if it is disabled using config(8) and > > > dmesg(8). > > > > > > Even when azalia is disabled my system gets sudden reboots. > > > First sudden reboot was just after playing a music; but next 2 reboots > > > was happened without playing anything. > > > > > > > Then, just do your regular stuff and see if the system reboots. > > > > I tested again with my patch. When azalia is disabled, it suddenly > > reboots after few minutes, without playing anything. When azalia is > > enabled, it lives. > > > > This looks to me like you are chasing down a new rabbit hole every time > I open one of your emails. I'd suggest you take a step back from all > the stuff you seem to be trying without having a firm grasp on how to > observe or report reproducibility. Have you tried out sthen@'s advice > to check old kernels + snapshots[1]? I may have missed your response to > this. You wrote that you rarely got the issue prior 17-May-2024? If > that *is correct*, then you should be able to bisect using the snapshot > archive around what date things change. Actually I see some kind of sudden reboots for such a long time (maybe since the time I have this mini pc) which happen almost certainly on every boot after a long shutdown! It is funny that my Windows 11 don't get those reboots; so I usually use Windows for an hour, then reboot to OpenBSD without facing those sudden reboots. Anyway, I tested this snapshot for few days: https://ftp.hostserver.de/archive/2024-05-20-0105 I only get sudden reboots after a long shutdown (for example boot after 3 hours off); however using the next snapshot: https://ftp.hostserver.de/archive/2024-05-21-0105 I saw this other kind of sudden reboots which might happen after every boot/reboot (not just after a long shutdown). > I am highlighting *is correct* above because your issue seems to be > unpredictable enough that a few minutes of testing don't mean anything. > I suggest you try to find a *clear difference*, meaning between a > snapshot where no reboot happens for ideally a whole day of use, and > the next one where it clearly happens very quickly (and reproducible > at least a second or third time). I couldn't find a snapshot without any sudden reboot at all. > Your reports also make me wonder how much customization you are > running. You've mentioned at least compiling custom kernels and > setting bsd.re-config. It's easy to find yourself in virtually > unsolvable scenarios by configuring too much. It might be best to try > a clean install, ideally without activating xenodm/X11. The bsd.re-config file was just for disabling azalia. I have FDE using softraid level C without swap and /tmp mounted as mfs. I don't think that I configured too much. Anyway, I also tested those snapshots on a clean install on a single partition outside softraid and again without swap (I don't like swap); I see similar results. I also disabled xenodm/X11 and see my OpenBSD lived for more than an hour, then I started xenodm and it suddenly rebooted in less than 3 minutes. I didn't test OpenBSD without xenodm/X11 much, because I need them; that's why I disabled amdgpu and placed it in my bsd.re-config file. Since then (~3 days) I see no single sudden reboot at all (not even after a long shutdown). I'm currenly on latest snapshot with amdgpu disabled. Alexandre Ratchov wrote: > On Sat, May 25, 2024 at 09:13:56AM +, Ali Farzanrad wrote: > > > > Even when azalia is disabled my system gets sudden reboots. > > First sudden reboot was just after playing a music; but next 2 reboots > > was happened without playing anything. > > > > This suggests the reboots are not directly caused by the azalia's msi > vs old-style interrupts. > > I'd suggest that you find and old enough snapshot (or release) that > used to work reliably on this machine and make sure it still works > reliably with the old software version. Not just an hour, use it few > days for real work. As I said above, I couldn't find such reliable snapshot. I only get reliably using disabled amdgpu, or (I didn't test this much) disabled xenodm/X11. > This would confirm that the hardware is still OK. I used my Windows 11 a lot and never seen any sudden reboot in Windows at all; so I think maybe it is not a hardware issue, but amdgpu issue. > Take few quick notes > of what devices are involved, how the machine is used, etc. Save the > dmesg. Most of the time I never
Re: Sudden reboot every 5-10 minutes on latest snapshot
On Sat, May 25, 2024 at 09:13:56AM +, Ali Farzanrad wrote: > > Even when azalia is disabled my system gets sudden reboots. > First sudden reboot was just after playing a music; but next 2 reboots > was happened without playing anything. > This suggests the reboots are not directly caused by the azalia's msi vs old-style interrupts. I'd suggest that you find and old enough snapshot (or release) that used to work reliably on this machine and make sure it still works reliably with the old software version. Not just an hour, use it few days for real work. This would confirm that the hardware is still OK. Take few quick notes of what devices are involved, how the machine is used, etc. Save the dmesg. If this isn't a hardware problem, then grab a new snapshot and try to understand what changed, compare the dmesg, compare the usage pattern etc. Possibly start bissecting the kernel until you find the change that causes the reboots. HTH
Re: Sudden reboot every 5-10 minutes on latest snapshot
On Sat, May 25, 2024 at 12:06:39PM +, Ali Farzanrad wrote: > Ali Farzanrad wrote: > > Alexandre Ratchov wrote: > > > On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote: > > > > Alexandre Ratchov wrote: > > > > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote: [...] > > I have another problem here. My USB keyboard works great in BOOTX64.EFI > > but will not work on kernel config. > > > > I created /etc/bsd.re-config file and rebooted my system twice to > > disable azalia and then checked if it is disabled using config(8) and > > dmesg(8). > > > > Even when azalia is disabled my system gets sudden reboots. > > First sudden reboot was just after playing a music; but next 2 reboots > > was happened without playing anything. > > > > > Then, just do your regular stuff and see if the system reboots. > > I tested again with my patch. When azalia is disabled, it suddenly > reboots after few minutes, without playing anything. When azalia is > enabled, it lives. > This looks to me like you are chasing down a new rabbit hole every time I open one of your emails. I'd suggest you take a step back from all the stuff you seem to be trying without having a firm grasp on how to observe or report reproducibility. Have you tried out sthen@'s advice to check old kernels + snapshots[1]? I may have missed your response to this. You wrote that you rarely got the issue prior 17-May-2024? If that *is correct*, then you should be able to bisect using the snapshot archive around what date things change. I am highlighting *is correct* above because your issue seems to be unpredictable enough that a few minutes of testing don't mean anything. I suggest you try to find a *clear difference*, meaning between a snapshot where no reboot happens for ideally a whole day of use, and the next one where it clearly happens very quickly (and reproducible at least a second or third time). Your reports also make me wonder how much customization you are running. You've mentioned at least compiling custom kernels and setting bsd.re-config. It's easy to find yourself in virtually unsolvable scenarios by configuring too much. It might be best to try a clean install, ideally without activating xenodm/X11. [1] https://marc.info/?l=openbsd-misc=171646884302309=2
Re: Sudden reboot every 5-10 minutes on latest snapshot
Ali Farzanrad wrote:
> Alexandre Ratchov wrote:
> > On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote:
> > > Alexandre Ratchov wrote:
> > > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote:
> > > > > Hi again,
> > > > >
> > > > > During my tests it seems that this version of kernel works fine:
> > > > >
> > > > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
> > > > >
> > > > > But this version of kernel will cause sudden reboots without any
> > > > > kernel
> > > > > panic or message after 5-60 minutes in my Minisforum UM790:
> > > > >
> > > > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
> > > > >
> > > > > After investigation I found this patch could fix my problem:
> > > > >
> > > > > Index: azalia.c
> > > > > ===
> > > > > RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
> > > > > diff -u -p -r1.287 azalia.c
> > > > > --- azalia.c 17 May 2024 19:43:45 - 1.287
> > > > > +++ azalia.c 24 May 2024 16:26:38 -
> > > > > @@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
> > > > > azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
> > > > > }
> > > > >
> > > > > + /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
> > > > > + if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
> > > > > + switch (PCI_PRODUCT(sc->pciid)) {
> > > > > + case PCI_PRODUCT_AMD_17_HDA:
> > > > > + case PCI_PRODUCT_AMD_17_1X_HDA:
> > > > > + case PCI_PRODUCT_AMD_HUDSON2_HDA:
> > > > > + pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
> > > > > + }
> > > > > + }
> > > > > +
> > > > > /* interrupt */
> > > > > if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
> > > > > printf(": can't map interrupt\n");
> > > > >
> > > > > However it breaks my front 3.5mm audio port and I should use my
> > > > > USB-to-3.5mm audio port adapter again.
> > > > >
> > > > > How may I investigate more?
> > > > >
> > > >
> > > > could you confirm that the system reboots only while you're using the
> > > > azalia device?
> > >
> > > I disabled sndiod, and unplugged my USB-to-3.5mm audio adapter and also
> > > unplugged front 3.5mm audio port, then reboot my OpenBSD and waited on
> > > xenodm login screen for few minutes; most of the time it reboots in
> > > less than 10 minutes... without any interaction from me, or playing
> > > anything...
> > >
> >
> > Could you disable the azalia driver and redo your test? reboot, then
> > on the boot(8) prompt type "boot -c", then "disable azalia", then
> > "quit".
>
> I have another problem here. My USB keyboard works great in BOOTX64.EFI
> but will not work on kernel config.
>
> I created /etc/bsd.re-config file and rebooted my system twice to
> disable azalia and then checked if it is disabled using config(8) and
> dmesg(8).
>
> Even when azalia is disabled my system gets sudden reboots.
> First sudden reboot was just after playing a music; but next 2 reboots
> was happened without playing anything.
>
> > Then, just do your regular stuff and see if the system reboots.
I tested again with my patch. When azalia is disabled, it suddenly
reboots after few minutes, without playing anything. When azalia is
enabled, it lives.
Re: Sudden reboot every 5-10 minutes on latest snapshot
Alexandre Ratchov wrote:
> On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote:
> > Alexandre Ratchov wrote:
> > > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote:
> > > > Hi again,
> > > >
> > > > During my tests it seems that this version of kernel works fine:
> > > >
> > > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
> > > >
> > > > But this version of kernel will cause sudden reboots without any kernel
> > > > panic or message after 5-60 minutes in my Minisforum UM790:
> > > >
> > > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
> > > >
> > > > After investigation I found this patch could fix my problem:
> > > >
> > > > Index: azalia.c
> > > > ===
> > > > RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
> > > > diff -u -p -r1.287 azalia.c
> > > > --- azalia.c17 May 2024 19:43:45 - 1.287
> > > > +++ azalia.c24 May 2024 16:26:38 -
> > > > @@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
> > > > azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
> > > > }
> > > >
> > > > + /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
> > > > + if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
> > > > + switch (PCI_PRODUCT(sc->pciid)) {
> > > > + case PCI_PRODUCT_AMD_17_HDA:
> > > > + case PCI_PRODUCT_AMD_17_1X_HDA:
> > > > + case PCI_PRODUCT_AMD_HUDSON2_HDA:
> > > > + pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
> > > > + }
> > > > + }
> > > > +
> > > > /* interrupt */
> > > > if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
> > > > printf(": can't map interrupt\n");
> > > >
> > > > However it breaks my front 3.5mm audio port and I should use my
> > > > USB-to-3.5mm audio port adapter again.
> > > >
> > > > How may I investigate more?
> > > >
> > >
> > > could you confirm that the system reboots only while you're using the
> > > azalia device?
> >
> > I disabled sndiod, and unplugged my USB-to-3.5mm audio adapter and also
> > unplugged front 3.5mm audio port, then reboot my OpenBSD and waited on
> > xenodm login screen for few minutes; most of the time it reboots in
> > less than 10 minutes... without any interaction from me, or playing
> > anything...
> >
>
> Could you disable the azalia driver and redo your test? reboot, then
> on the boot(8) prompt type "boot -c", then "disable azalia", then
> "quit".
I have another problem here. My USB keyboard works great in BOOTX64.EFI
but will not work on kernel config.
I created /etc/bsd.re-config file and rebooted my system twice to
disable azalia and then checked if it is disabled using config(8) and
dmesg(8).
Even when azalia is disabled my system gets sudden reboots.
First sudden reboot was just after playing a music; but next 2 reboots
was happened without playing anything.
> Then, just do your regular stuff and see if the system reboots.
Re: Sudden reboot every 5-10 minutes on latest snapshot
On Fri, May 24, 2024 at 09:04:29PM +, Ali Farzanrad wrote:
> Alexandre Ratchov wrote:
> > On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote:
> > > Hi again,
> > >
> > > During my tests it seems that this version of kernel works fine:
> > >
> > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
> > >
> > > But this version of kernel will cause sudden reboots without any kernel
> > > panic or message after 5-60 minutes in my Minisforum UM790:
> > >
> > > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
> > >
> > > After investigation I found this patch could fix my problem:
> > >
> > > Index: azalia.c
> > > ===
> > > RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
> > > diff -u -p -r1.287 azalia.c
> > > --- azalia.c 17 May 2024 19:43:45 - 1.287
> > > +++ azalia.c 24 May 2024 16:26:38 -
> > > @@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
> > > azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
> > > }
> > >
> > > + /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
> > > + if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
> > > + switch (PCI_PRODUCT(sc->pciid)) {
> > > + case PCI_PRODUCT_AMD_17_HDA:
> > > + case PCI_PRODUCT_AMD_17_1X_HDA:
> > > + case PCI_PRODUCT_AMD_HUDSON2_HDA:
> > > + pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
> > > + }
> > > + }
> > > +
> > > /* interrupt */
> > > if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
> > > printf(": can't map interrupt\n");
> > >
> > > However it breaks my front 3.5mm audio port and I should use my
> > > USB-to-3.5mm audio port adapter again.
> > >
> > > How may I investigate more?
> > >
> >
> > could you confirm that the system reboots only while you're using the
> > azalia device?
>
> I disabled sndiod, and unplugged my USB-to-3.5mm audio adapter and also
> unplugged front 3.5mm audio port, then reboot my OpenBSD and waited on
> xenodm login screen for few minutes; most of the time it reboots in
> less than 10 minutes... without any interaction from me, or playing
> anything...
>
Could you disable the azalia driver and redo your test? reboot, then
on the boot(8) prompt type "boot -c", then "disable azalia", then
"quit".
Then, just do your regular stuff and see if the system reboots.
Re: Sudden reboot every 5-10 minutes on latest snapshot
Alexandre Ratchov wrote:
> On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote:
> > Hi again,
> >
> > During my tests it seems that this version of kernel works fine:
> >
> > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
> >
> > But this version of kernel will cause sudden reboots without any kernel
> > panic or message after 5-60 minutes in my Minisforum UM790:
> >
> > # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
> >
> > After investigation I found this patch could fix my problem:
> >
> > Index: azalia.c
> > ===
> > RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
> > diff -u -p -r1.287 azalia.c
> > --- azalia.c17 May 2024 19:43:45 - 1.287
> > +++ azalia.c24 May 2024 16:26:38 -
> > @@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
> > azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
> > }
> >
> > + /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
> > + if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
> > + switch (PCI_PRODUCT(sc->pciid)) {
> > + case PCI_PRODUCT_AMD_17_HDA:
> > + case PCI_PRODUCT_AMD_17_1X_HDA:
> > + case PCI_PRODUCT_AMD_HUDSON2_HDA:
> > + pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
> > + }
> > + }
> > +
> > /* interrupt */
> > if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
> > printf(": can't map interrupt\n");
> >
> > However it breaks my front 3.5mm audio port and I should use my
> > USB-to-3.5mm audio port adapter again.
> >
> > How may I investigate more?
> >
>
> could you confirm that the system reboots only while you're using the
> azalia device?
I disabled sndiod, and unplugged my USB-to-3.5mm audio adapter and also
unplugged front 3.5mm audio port, then reboot my OpenBSD and waited on
xenodm login screen for few minutes; most of the time it reboots in
less than 10 minutes... without any interaction from me, or playing
anything...
> when you apply above diff, is audio unstable or it doesn't work at
> all?
It doesn't work at all. No input, no output. Even sndioctl will
freeze.
However when I plug my USB-to-3.5mm audio adapter, and run sndiod with
these arguments: -f rsnd/0 -F rsnd/1
I have audio output. However I don't have audio input for such a long
time, maybe 2 months (if it could help I can search for latest version
of kernel which my mic works with USB-to-3.5mm audio adapter).
With latest kernel front 3.5mm audio port works great, both as input and
as output; the only problem that I have with it is sudden reboots :(
Re: Sudden reboot every 5-10 minutes on latest snapshot
On Fri, May 24, 2024 at 04:30:52PM +, Ali Farzanrad wrote:
> Hi again,
>
> During my tests it seems that this version of kernel works fine:
>
> # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
>
> But this version of kernel will cause sudden reboots without any kernel
> panic or message after 5-60 minutes in my Minisforum UM790:
>
> # TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
>
> After investigation I found this patch could fix my problem:
>
> Index: azalia.c
> ===
> RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
> diff -u -p -r1.287 azalia.c
> --- azalia.c 17 May 2024 19:43:45 - 1.287
> +++ azalia.c 24 May 2024 16:26:38 -
> @@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
> azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
> }
>
> + /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
> + if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
> + switch (PCI_PRODUCT(sc->pciid)) {
> + case PCI_PRODUCT_AMD_17_HDA:
> + case PCI_PRODUCT_AMD_17_1X_HDA:
> + case PCI_PRODUCT_AMD_HUDSON2_HDA:
> + pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
> + }
> + }
> +
> /* interrupt */
> if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
> printf(": can't map interrupt\n");
>
> However it breaks my front 3.5mm audio port and I should use my
> USB-to-3.5mm audio port adapter again.
>
> How may I investigate more?
>
could you confirm that the system reboots only while you're using the
azalia device?
when you apply above diff, is audio unstable or it doesn't work at
all?
Re: Sudden reboot every 5-10 minutes on latest snapshot
Hi again,
During my tests it seems that this version of kernel works fine:
# TZ=UTC cvs -Qd /cvs get -D "2024-05-17 19:30" -P src
But this version of kernel will cause sudden reboots without any kernel
panic or message after 5-60 minutes in my Minisforum UM790:
# TZ=UTC cvs -Qd /cvs get -D "2024-05-17 20:00" -P src
After investigation I found this patch could fix my problem:
Index: azalia.c
===
RCS file: /home/cvs/src/sys/dev/pci/azalia.c,v
diff -u -p -r1.287 azalia.c
--- azalia.c17 May 2024 19:43:45 - 1.287
+++ azalia.c24 May 2024 16:26:38 -
@@ -557,6 +557,16 @@ azalia_pci_attach(struct device *parent,
azalia_pci_write(sc->pc, sc->tag, ICH_PCI_MMC, reg);
}
+ /* disable MSI for AMD Summit Ridge/Raven Ridge HD Audio */
+ if (PCI_VENDOR(sc->pciid) == PCI_VENDOR_AMD) {
+ switch (PCI_PRODUCT(sc->pciid)) {
+ case PCI_PRODUCT_AMD_17_HDA:
+ case PCI_PRODUCT_AMD_17_1X_HDA:
+ case PCI_PRODUCT_AMD_HUDSON2_HDA:
+ pa->pa_flags &= ~PCI_FLAGS_MSI_ENABLED;
+ }
+ }
+
/* interrupt */
if (pci_intr_map_msi(pa, ) && pci_intr_map(pa, )) {
printf(": can't map interrupt\n");
However it breaks my front 3.5mm audio port and I should use my
USB-to-3.5mm audio port adapter again.
How may I investigate more?
> > > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel
> > > > Panic or visible message how may I debug it?
> > > > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO:
> > > > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024
> > >
> > > Not a lot to go on really.
> > >
> > > Is the machine doing anything or just idle?
> >
> > It get reboot even in xenodm login screen without any interaction from me.
> >
> > > Is X running?
> >
> > It's funny. I disabled the xenodm and it lived for more than 10 minutes;
> > then I enabled and started xenodm and it suddenly rebooted after few
> > minutes!
> >
> > Next time I keep xenodm running, but switched to ttyC0 terminal using
> > Alt+Ctrl+F1 key and it lived for more than 10 minutes; then I just
> > switched to Xorg using Alt+Ctrl+F5 and it suddenly rebooted again after
> > few minutes!
> >
> > > Do you get the same with 7.5? if yes, try older releases - can you
> > > find one where it doesn't happen?
> >
> > I rarely got same issue in previous snapshots (I think my last snapshot
> > was for 6 days ago and I had no serious issue with that).
> >
> > I think I sould compile and test previous versions of xenocara, right?
>
> Try with just an older kernel first and leave userland alone.
> ftp.hostserver.de and openbsd.cs.toronto.edu both have some old
> snaps in /archive. (If no snap was built on a certain day then
> the files will be identical in the archive so no point testing
> when there was no change - you can use what(1) to show the
> version - I'd save a few under names like /bsd.mp.
> and type "boot bsd.mp." at the boot loader).
>
>
> > > >
> > > > # (dmesg; sysctl hw.sensors)
> > > > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024
> > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
> > > > real mem = 31909883904 (30431MB)
> > > > avail mem = 30921310208 (29488MB)
> > > > random: good seed from bootblocks
> > > > mpath0 at root
> > > > scsibus0 at mpath0: 256 targets
> > > > mainbus0 at root
> > > > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries)
> > > > bios0: vendor American Megatrends International, LLC. version "1.01"
> > > > date 06/05/2023
> > > > bios0: Micro Computer (HK) Tech Limited F7BSC
> > > > efi0 at bios0: UEFI 2.8
> > > > efi0: American Megatrends rev 0x5001d
> > > > acpi0 at bios0: ACPI 6.4
> > > > acpi0: sleep states S0 S4 S5
> > > > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT
> > > > CRAT CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS
> > > > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT
> > > > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4)
> > > > SWUS(S4) GP12(S4) SWUS(S4)
> > > > acpitimer0 at acpi0: 3579545 Hz, 32 bits
> > > > acpimcfg0 at acpi0
> > > > acpimcfg0: addr 0xe000, bus 0-255
> > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> > > > cpu0 at mainbus0: apid 0 (boot processor)
> > > > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz,
> > > > 19-74-01, patch 0a704101
> > > > cpu0: cpuid 1
> > > > edx=178bfbff
> > > >
> > > > ecx=76f8320b
> > > > cpu0: cpuid 6 eax=4 ecx=1
> > > > cpu0: cpuid 7.0
> > > > ebx=f1bf97a9
> > > > ecx=405fce edx=1000
> > > > cpu0: cpuid d.1 eax=f
> > > > cpu0: cpuid 8001 edx=2fd3fbff
> > > > ecx=75c237ff
> > > > cpu0: cpuid 8007 edx=e799
> > > > cpu0: cpuid 8008
> > > > ebx=791ef257
> > > > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way
Re: Sudden reboot every 5-10 minutes on latest snapshot
On 2024/05/23 12:12, Ali Farzanrad wrote: > Hi Stuart, > > Stuart Henderson wrote: > > On 2024-05-23, Ali Farzanrad wrote: > > > Hi misc@, > > > > > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > > > Panic or visible message how may I debug it? > > > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > > > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 > > > > Not a lot to go on really. > > > > Is the machine doing anything or just idle? > > It get reboot even in xenodm login screen without any interaction from me. > > > Is X running? > > It's funny. I disabled the xenodm and it lived for more than 10 minutes; > then I enabled and started xenodm and it suddenly rebooted after few > minutes! > > Next time I keep xenodm running, but switched to ttyC0 terminal using > Alt+Ctrl+F1 key and it lived for more than 10 minutes; then I just > switched to Xorg using Alt+Ctrl+F5 and it suddenly rebooted again after > few minutes! > > > Do you get the same with 7.5? if yes, try older releases - can you > > find one where it doesn't happen? > > I rarely got same issue in previous snapshots (I think my last snapshot > was for 6 days ago and I had no serious issue with that). > > I think I sould compile and test previous versions of xenocara, right? Try with just an older kernel first and leave userland alone. ftp.hostserver.de and openbsd.cs.toronto.edu both have some old snaps in /archive. (If no snap was built on a certain day then the files will be identical in the archive so no point testing when there was no change - you can use what(1) to show the version - I'd save a few under names like /bsd.mp. and type "boot bsd.mp." at the boot loader). > > > > > > # (dmesg; sysctl hw.sensors) > > > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > real mem = 31909883904 (30431MB) > > > avail mem = 30921310208 (29488MB) > > > random: good seed from bootblocks > > > mpath0 at root > > > scsibus0 at mpath0: 256 targets > > > mainbus0 at root > > > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > > > bios0: vendor American Megatrends International, LLC. version "1.01" date > > > 06/05/2023 > > > bios0: Micro Computer (HK) Tech Limited F7BSC > > > efi0 at bios0: UEFI 2.8 > > > efi0: American Megatrends rev 0x5001d > > > acpi0 at bios0: ACPI 6.4 > > > acpi0: sleep states S0 S4 S5 > > > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > > > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT > > > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > > > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) > > > SWUS(S4) GP12(S4) SWUS(S4) > > > acpitimer0 at acpi0: 3579545 Hz, 32 bits > > > acpimcfg0 at acpi0 > > > acpimcfg0: addr 0xe000, bus 0-255 > > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > > cpu0 at mainbus0: apid 0 (boot processor) > > > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu0: cpuid 1 > > > edx=178bfbff > > > > > > ecx=76f8320b > > > cpu0: cpuid 6 eax=4 ecx=1 > > > cpu0: cpuid 7.0 > > > ebx=f1bf97a9 > > > ecx=405fce edx=1000 > > > cpu0: cpuid d.1 eax=f > > > cpu0: cpuid 8001 edx=2fd3fbff > > > ecx=75c237ff > > > cpu0: cpuid 8007 edx=e799 > > > cpu0: cpuid 8008 > > > ebx=791ef257 > > > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > > > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > > > cpu0: smt 0, core 0, package 0 > > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > > cpu0: apic clock running at 24MHz > > > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > > > cpu1 at mainbus0: apid 2 (application processor) > > > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu1: smt 0, core 1, package 0 > > > cpu2 at mainbus0: apid 4 (application processor) > > > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu2: smt 0, core 2, package 0 > > > cpu3 at mainbus0: apid 6 (application processor) > > > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu3: smt 0, core 3, package 0 > > > cpu4 at mainbus0: apid 8 (application processor) > > > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu4: smt 0, core 4, package 0 > > > cpu5 at mainbus0: apid 10 (application processor) > > > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu5: smt 0, core 5, package 0 > > > cpu6 at mainbus0: apid 12 (application processor) > > > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > > patch 0a704101 > > > cpu6: smt 0, core 6, package 0 > > > cpu7 at mainbus0: apid 14 (application
Re: Sudden reboot every 5-10 minutes on latest snapshot
Hi Stuart, Stuart Henderson wrote: > On 2024-05-23, Ali Farzanrad wrote: > > Hi misc@, > > > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > > Panic or visible message how may I debug it? > > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 > > Not a lot to go on really. > > Is the machine doing anything or just idle? It get reboot even in xenodm login screen without any interaction from me. > Is X running? It's funny. I disabled the xenodm and it lived for more than 10 minutes; then I enabled and started xenodm and it suddenly rebooted after few minutes! Next time I keep xenodm running, but switched to ttyC0 terminal using Alt+Ctrl+F1 key and it lived for more than 10 minutes; then I just switched to Xorg using Alt+Ctrl+F5 and it suddenly rebooted again after few minutes! > Do you get the same with 7.5? if yes, try older releases - can you > find one where it doesn't happen? I rarely got same issue in previous snapshots (I think my last snapshot was for 6 days ago and I had no serious issue with that). I think I sould compile and test previous versions of xenocara, right? > > > > # (dmesg; sysctl hw.sensors) > > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > real mem = 31909883904 (30431MB) > > avail mem = 30921310208 (29488MB) > > random: good seed from bootblocks > > mpath0 at root > > scsibus0 at mpath0: 256 targets > > mainbus0 at root > > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > > bios0: vendor American Megatrends International, LLC. version "1.01" date > > 06/05/2023 > > bios0: Micro Computer (HK) Tech Limited F7BSC > > efi0 at bios0: UEFI 2.8 > > efi0: American Megatrends rev 0x5001d > > acpi0 at bios0: ACPI 6.4 > > acpi0: sleep states S0 S4 S5 > > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT > > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) SWUS(S4) > > GP12(S4) SWUS(S4) > > acpitimer0 at acpi0: 3579545 Hz, 32 bits > > acpimcfg0 at acpi0 > > acpimcfg0: addr 0xe000, bus 0-255 > > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > > cpu0 at mainbus0: apid 0 (boot processor) > > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu0: cpuid 1 > > edx=178bfbff > > > > ecx=76f8320b > > cpu0: cpuid 6 eax=4 ecx=1 > > cpu0: cpuid 7.0 > > ebx=f1bf97a9 > > ecx=405fce edx=1000 > > cpu0: cpuid d.1 eax=f > > cpu0: cpuid 8001 edx=2fd3fbff > > ecx=75c237ff > > cpu0: cpuid 8007 edx=e799 > > cpu0: cpuid 8008 > > ebx=791ef257 > > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB > > 64b/line 8-way L2 cache, 16MB 64b/line 16-way L3 cache > > cpu0: smt 0, core 0, package 0 > > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > > cpu0: apic clock running at 24MHz > > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > > cpu1 at mainbus0: apid 2 (application processor) > > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu1: smt 0, core 1, package 0 > > cpu2 at mainbus0: apid 4 (application processor) > > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu2: smt 0, core 2, package 0 > > cpu3 at mainbus0: apid 6 (application processor) > > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu3: smt 0, core 3, package 0 > > cpu4 at mainbus0: apid 8 (application processor) > > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu4: smt 0, core 4, package 0 > > cpu5 at mainbus0: apid 10 (application processor) > > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu5: smt 0, core 5, package 0 > > cpu6 at mainbus0: apid 12 (application processor) > > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu6: smt 0, core 6, package 0 > > cpu7 at mainbus0: apid 14 (application processor) > > cpu7: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > > patch 0a704101 > > cpu7: smt 0, core 7, package 0 > > cpu8 at mainbus0: apid 1 (application processor) > > cpu8: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu8: smt 1, core 0, package 0 > > cpu9 at mainbus0: apid 3 (application processor) > > cpu9: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu9: smt 1, core 1, package 0 > > cpu10 at mainbus0: apid 5 (application processor) > > cpu10: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > > patch 0a704101 > > cpu10:
Re: Sudden reboot every 5-10 minutes on latest snapshot
On 2024-05-23, Ali Farzanrad wrote: > Hi misc@, > > My Minisforum UM790 keeps reboot every 5-10 minutes, without any Kernel > Panic or visible message how may I debug it? > I'm using latest OpenBSD snapshot with this amd64/BUILDINFO: > Build date: 1716424636 - Thu May 23 00:37:16 UTC 2024 Not a lot to go on really. Is the machine doing anything or just idle? Is X running? Do you get the same with 7.5? if yes, try older releases - can you find one where it doesn't happen? > > # (dmesg; sysctl hw.sensors) > OpenBSD 7.5-current (GENERIC.MP) #78: Wed May 22 18:31:14 MDT 2024 > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 31909883904 (30431MB) > avail mem = 30921310208 (29488MB) > random: good seed from bootblocks > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 3.5 @ 0x9ab7f000 (45 entries) > bios0: vendor American Megatrends International, LLC. version "1.01" date > 06/05/2023 > bios0: Micro Computer (HK) Tech Limited F7BSC > efi0 at bios0: UEFI 2.8 > efi0: American Megatrends rev 0x5001d > acpi0 at bios0: ACPI 6.4 > acpi0: sleep states S0 S4 S5 > acpi0: tables DSDT FACP SSDT SSDT FIDT MCFG FPDT VFCT BGRT TPM2 SSDT CRAT > CDIT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT WSMT APIC IVRS SSDT SSDT > SSDT SSDT SSDT SSDT SSDT SSDT SSDT SSDT > acpi0: wakeup devices GPP1(S4) GPP0(S4) GPP5(S4) GPP7(S4) GP11(S4) SWUS(S4) > GP12(S4) SWUS(S4) > acpitimer0 at acpi0: 3579545 Hz, 32 bits > acpimcfg0 at acpi0 > acpimcfg0: addr 0xe000, bus 0-255 > acpimadt0 at acpi0 addr 0xfee0: PC-AT compat > cpu0 at mainbus0: apid 0 (boot processor) > cpu0: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu0: cpuid 1 > edx=178bfbff > > ecx=76f8320b > cpu0: cpuid 6 eax=4 ecx=1 > cpu0: cpuid 7.0 > ebx=f1bf97a9 > ecx=405fce edx=1000 > cpu0: cpuid d.1 eax=f > cpu0: cpuid 8001 edx=2fd3fbff > ecx=75c237ff > cpu0: cpuid 8007 edx=e799 > cpu0: cpuid 8008 > ebx=791ef257 > cpu0: 32KB 64b/line 8-way D-cache, 32KB 64b/line 8-way I-cache, 1MB 64b/line > 8-way L2 cache, 16MB 64b/line 16-way L3 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 24MHz > cpu0: mwait min=64, max=64, C-substates=1.1, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu2: smt 0, core 2, package 0 > cpu3 at mainbus0: apid 6 (application processor) > cpu3: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu3: smt 0, core 3, package 0 > cpu4 at mainbus0: apid 8 (application processor) > cpu4: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu4: smt 0, core 4, package 0 > cpu5 at mainbus0: apid 10 (application processor) > cpu5: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu5: smt 0, core 5, package 0 > cpu6 at mainbus0: apid 12 (application processor) > cpu6: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu6: smt 0, core 6, package 0 > cpu7 at mainbus0: apid 14 (application processor) > cpu7: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.00 MHz, 19-74-01, > patch 0a704101 > cpu7: smt 0, core 7, package 0 > cpu8 at mainbus0: apid 1 (application processor) > cpu8: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu8: smt 1, core 0, package 0 > cpu9 at mainbus0: apid 3 (application processor) > cpu9: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu9: smt 1, core 1, package 0 > cpu10 at mainbus0: apid 5 (application processor) > cpu10: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu10: smt 1, core 2, package 0 > cpu11 at mainbus0: apid 7 (application processor) > cpu11: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu11: smt 1, core 3, package 0 > cpu12 at mainbus0: apid 9 (application processor) > cpu12: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu12: smt 1, core 4, package 0 > cpu13 at mainbus0: apid 11 (application processor) > cpu13: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu13: smt 1, core 5, package 0 > cpu14 at mainbus0: apid 13 (application processor) > cpu14: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 > cpu14: smt 1, core 6, package 0 > cpu15 at mainbus0: apid 15 (application processor) > cpu15: AMD Ryzen 9 7940HS w/ Radeon 780M Graphics, 4000.01 MHz, 19-74-01, > patch 0a704101 >
