Opened 11 years ago

Closed 8 years ago

#2504 closed bug (fixed)

Haiku freezes at bootup (leaf icon)

Reported by: El-Al Owned by: axeld
Priority: normal Milestone: R1
Component: - General Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by mmlr)

My system freezes at bootup when the disc icon is highlighted. With on screen debug on the system prints the following output:

usb_uhci: no devices found
usb_ohci: successfully started the controller
usb_ehci: claiming ownership of the host controller
usb_ehci: successfully took ownership of the host controller
usb_ehci: successfully started the controller

At this point the cursor freezes and nothing happens. A hard reboot is required. This was a working haiku system until the driver architecture got overhauled. Iv'e tried all the safe mode options to no avail.

Change History (10)

comment:1 by mmlr, 11 years ago

Can you please try removing the usb_disk driver from "/boot/beos/system/add-ons/kernel/drivers/bin" and see if this changes behaviour. If it does it is an OHCI issue (bug #1044) otherwise it's something else :-). When this happens, are you still able to enter KDL by pressing F12? If so, please run the "ints" command and check for exceptionally large numbers and post back here if you find any.

comment:2 by mmlr, 11 years ago

Description: modified (diff)

comment:3 by PieterPanman, 11 years ago

Which revision? I had something similar, but it turned out to be #2337. If you wait for 10 minutes, does it finally boot? Any release prior to hrev26325 might cause this

comment:4 by El-Al, 11 years ago

Summary: Haiku freezes at bootup (disks icon)Haiku freezes at bootup (leaf icon)

I removed usb_disk from the build, rebooted with a ps2 mouse/keyboard and got a completely different set of errors:

get_boot_partition(): boot volume message: field: "booted from image", type: BOOL (0x424f4f4c) [0] false

I can't seem to enter KDL at all by pressing F12.

Also tried waiting for 15/20 minutes for it to boot. Still nothing.

(This is an ASROCK mobo with ali/uli chipset and 2x AMD 64 3800+ cpus btw)

comment:5 by mmlr, 11 years ago

No need for the PS/2 hardware. Removing usb_disk just causes the USB stack to be loaded later, it doesn't disable it. So you don't get the USB related messages anymore, but otherwise it hangs at more or less the same place? The output you posted isn't an error message BTW, it's just dumping the content of the boot volume message coming from the bootloader. Though if that's the only line that gets printed from the boot volume message that's strange. It should contain "booted from image", "partition offset", "boot method", "boot drive number" and "disk identifier". I could imagine it being an interrupt flood from ATA. You could try replacing the ide with the ata bus_manager to see if that makes a difference. To do that change the line saying "SubInclude HAIKU_TOP src add-ons kernel bus_managers ide ;" to "SubInclude HAIKU_TOP src add-ons kernel bus_managers ata ;" in the "src/add-ons/kernel/bus_managers/Jamfile" and maybe use "jam -a ide" once to make sure it is rebuilt.

comment:6 by El-Al, 11 years ago

A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post.

in reply to:  6 ; comment:7 by El-Al, 11 years ago

Replying to El-Al:

A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post.

Even tried installing to an IDE drive as opposed to SATA. Same problem occurs. I guess the driver overhaul hasn't caused this problem at all. I'm stumped!

in reply to:  7 ; comment:8 by El-Al, 10 years ago

Replying to El-Al:

Replying to El-Al:

A little progress here. After performing the above the system now boots up to the last icon on the splash screen. Thereafter, the boot splash either moves a couple of inches across the screen to the left or, stretches itself out across the entire (bottom) of the screen and breaks up into short strips. In either case, I can't use F12 to access KDL and the system is essentially frozen. Using the on-screen debug option, I get exactly the same output as my original post.

Even tried installing to an IDE drive as opposed to SATA. Same problem occurs. I guess the driver overhaul hasn't caused this problem at all. I'm stumped!

Well, it seems as though this problem is related to a limitation in the motherboards BIOS.

I have now changed the motherboard for another make and model. Haiku boots perfectly well now.

I noticed (whilst looking through the BIOS) in the USB Configuration options a switch for BIOS EHCI hand-off.

The explaination of the switch is as follows:

This is a workaround for OSes without EHCI hand-off support. The EHCI ownership change should claim by EHCI driver.

As can be seen by the original screen output, the systen froze at the point of change of ownership.

This option was not available in the previous BIOS although the system was booting fine up to a point in time. What puzzles me is what actually happened in order to make the system stop booting.

I can only think of two possibilities:

  1. That I was responsible by flashing the BIOS (which I recall doing at some point).
  2. That ongoing work to the USB subsystem has somehow exposed the problem.

in reply to:  8 comment:9 by mmlr, 10 years ago

As can be seen by the original screen output, the systen froze at the point of change of ownership.

No it didn't. At those points the handover has been done already and the controller was started.

This option was not available in the previous BIOS although the system was booting fine up to a point in time. What puzzles me is what actually happened in order to make the system stop booting.

I don't quite understand. Does it not boot when setting this BIOS setting to either?

comment:10 by scottmc, 8 years ago

Resolution: fixed
Status: newclosed

If you still have the motherboard that failed can you recheck it with a recent build of Haiku as it may have been fixed in the past couple of years. If so and it still fails please reopen this ticket.

Note: See TracTickets for help on using tickets.