hrev 54484 freezes when booting

[wkocay]

I have been using nightly hrevs for several years on my xw9400 and they have worked well. I tried installing hrev54484 from an anyboot usb stick. It boots from the usb stick with no problem, and installs Haiku. But then it will not boot from the HD. It stalls after the 4th icon lights up – ie, on the chip-icon. I have tried safe mode and safe video mode, and others, with no change. I tried nightly versions 54484, 54460, 54412 – all with the same results. If I remove the usb stick, which was still mounted, it will boot, but the mouse is frozen. In debugging mode, it fills a few screens with output, and then it just stalls. But hrev 53624 and previous work.

There is more: I booted from another volume. Then in preparing the files to send, I located to /tmp and did cat usb_report_hid_descriptor_*.bin The computer froze, and destroyed the partition from which Haiku was running. Apparently I have lost all the files.

[wkocay]

This is the 32-bit version of Haiku. The computer is an HP xw9400 with an opteron 2435 with 12 cores.

[mmlr]

Can you take a picture of the last screen of the on-screen debug output when booting stalls? Note that with on-screen debug output you will probably have to disable paging as USB input will stop once the USB stack initializes.

It is not clear to me where the attachments syslogboot.txt and syslog2.txt are coming from, can you elaborate on how you got them?

The former appears to show a shutdown, which implies that the boot worked. The latter shows odd symbol lookup errors that would imply a mismatch between virtio drivers and the kernel. This shouldn't happen as both are part of the same Haiku HPKG. Possibly the bootloader preloaded them off the wrong volume? Are there release (beta) installs and nightlies mixed on that machine by any chance?

There is also a driver init line in the second log which should only come up in a later stage of the boot process than the fourth icon.

[wkocay]

Thank you for your response.

syslogboot.txt is the last lines of the syslog file on a failed boot when it stalled after the 4th icon lit up. There was a usb stick plugged on that attempt.

syslog2.txt is the last lines of the syslog file when it booted, but the mouse was frozen. There was no usb stick plugged in on that attempt.

Apparently there is a problem with the usb drivers.

Two photos are attached, but they don't show much. Just the last screen of debug output on failed boots.

syslog3.txt and syslogold3.txt are the last lines of the syslog file and syslog.old file on these failed boots.

About 2 weeks ago I tried to upgrade to R1/beta2 using pkgman, but it stalled part way thru. Then yesterday I decided to try a newer nightly hrev, as it writes a new system file. It installed but wouldn't boot.

[diver]

About 2 weeks ago I tried to upgrade to R1/beta2 using pkgman, but it stalled part way thru. Then yesterday I decided to try a newer nightly hrev, as it writes a new system file. It installed but wouldn't boot.

Did you format your bfs partition or installed over existing one? I noticed in syslogold3.txt the following package conflict which may or may not be related:

package openexr-2.2.1-3 conflicts with ilmbase provided by ilmbase-2.2.1-2
package_daemon
      solution 1:
package_daemon
     - allow deinstallation of ilmbase-2.2.1-2
package_daemon
     solution 2:
package_daemon
     - allow deinstallation of openexr-2.2.1-3

ilmbase package was removed in ​https://git.haiku-os.org/haiku/commit/?id=14af81415606117c278dbcb2c33430c725db9f60 (2020-04-19) which was before beta2 release.

This looks like a messed up install which confuses package_daemon.

[wkocay]

I did not reformat the disk, as I have many gigabytes of files that I want to keep. There are 3 bootable Haiku partitions on that computer -- two are 32-bit Haiku, one is 64-bits. I also tried using pkgman to install 64-bit R1/beta2, and it also stalled part way thru.

[wkocay]

OK, I copied my files to another disk, reformatted the other disks, and did a clean install of R1beta2. 32-bits and 64-bits. The 32-bit volume runs perfectly. The 64-bit haiku boots, but has troubles when running. When I run Paladin, it frequently freezes, and I have to reboot -- every 10 minutes. When rebooting, after the rocket icon, the screen often goes black, and I have to reboot again. It is very unstable. The previous 64-bit nighty I was using worked well most of the time. Paladin did not crash or freeze it.