PANIC in mmu_init()

[manveru]

I'm trying the anyboot image on an USB stick on my "Fujitsu FMV-BIBLO MG/G75N".

The BIOS is "Phoenix BIOS 1.12", and the CPU is "Intel Core i7 CPU M 620 @ 2.67GHz", the machine has 4GB of RAM.

Soon after selecting to boot from the stick, I get following error message: "mmu_init(): Failed to add physical memory range 0x100000000 - 0x138000000"

Before that there is a glimpse of a magenta underscore that pauses sometimes if i hold shift, but continues to the panic as soon as I release shift.

I have tried with R1/alpha3 and hrev42471-x86gcc2hybrid-anyboot without any visible difference.

On IRC, aldeck suggested that it might be caused by "sandy bridge".

Thanks in advance.

[manveru]

Output of /proc/cpuinfo

[manveru]

Output of dmesg

[Dilbert]

Similar problem here.

I have two laptops. Haiku runs fine on My aging Acer Aspire. My other laptop is a super awesome Asus G73S with 64 bits i7 Sandy Bridge processor and 6 gb ram. Haiku does not load on this one.

The error message is the folowing:

* PANIC *

mmu_init(): Failed to add physical memory range 0xdf7e8000 - 0xdf7fd000

Press key to reboot.

[phoudoin]

The BIOS reports 10 usable physical memory address ranges. Unfortunatly, Haiku supports only 8 currently, hence why mmu_init() failed.

I guess the solution should be to improve this limit, in headers/private/kernel/boot/platform/bios_ia32/platform_kernel_args.h :

#define MAX_PHYSICAL_MEMORY_RANGE 32
#define MAX_PHYSICAL_ALLOCATED_RANGE 32
#define MAX_VIRTUAL_ALLOCATED_RANGE 32

I did a quick search, and I think there is no bad side-effect to fear, but I'll prefer one kernel guru check this before applying such change. The bios_ia32 platform may not be the unique one needing such change, too.

Meanwhile, if someone could test this change and report, thanks in advance.

[axeld]

The only consequence is that whenever you change the kernel args, you'll need to update the kernel and the boot loader. Otherwise, this change looks fine to me.

[phoudoin]

Replying to axeld:

The only consequence is that whenever you change the kernel args, you'll need to update the kernel and the boot loader. Otherwise, this change looks fine to me.

No possible issue with kernel_args size being to big?

[axeld]

I wouldn't expect any for quite some time, at least, but it's not that I would remember what's going on (it's just part of the bss in the boot loader, and a pointer is passed into the kernel where it is then copied into the kernel bss section) ;-)

[phoudoin]

Done in hrev42715.

Thanks to test and report (rebuild and update both haiku_loader and kernel_x86 from source, or just wait next nightly build).

[taos]

Just for your information, hrev42715 also solved the boot problems of a HP G5333de desktop computer (Intel Core i3-550, 6 GB DDR3) that before only booted to:

PANIC: get_boot_partitions failed!

Thanks!

[phoudoin]

Replying to taos:

Just for your information, hrev42715 also solved the boot problems of a HP G5333de desktop computer (Intel Core i3-550, 6 GB DDR3) that before only booted to:

PANIC: get_boot_partitions failed!

Interesting. I guess I'll have to search every tickets we have about this panic and see if it can be related indeed.

Thanks!

You're welcome ;-) Thanks for reporting it.

[phoudoin]

Dilbert, manveru, could you try the fix and report the result, so we could close or move on this ticket? Thanks.

[Dilbert2]

Finally. I tried to recover my password several times, but I could not log in. This is a new account, because Dilbert could not log on.

OK. Booted the latest nightly. Got a error message. The screen is black, with the HAIKU logo and the seven grey icons that become more colorful when Haiku loads. All seems to be normal until a big white text box fills the top of the screen.

PANIC: did not find any boot partitions! Welcome to Kernel debugging Land... Thread 22 "main2" running on CPU5 stack trace for thread 22 "main2"

Kernel stack: 0x81f60000 to 0x81f64000

Then there's a few lines with frame, caller, <image>:function + offset

I don't know if all that text is worth the effort of typing it here. Tell me if you really need it.

Four of the grey icons have got color. The last 3 are still grey.

By the way: Everytime I try to boot, the error message changes slightly. This time, "main2" is running on CPU 0 instead of 5.

The laptop is a Asus G73s with Sandy Bridge i7 2GHz 4 cores and hyperthreading.

[Dilbert2]

New info.

The error that I mentioned earlier was when booting from DVD. The Asus G73sw manages to perfectly boot Haiku Nightly from a USB memory stick.

The problem seems to be the booting Haiku from DVD on this computer. Memory stick worked great.

[waddlesplash]

OK, then this ticket is fixed. If the DVD issue persists (it was probably also fixed) please open a new ticket.

[nielx]

Assign tickets with status=closed and resolution=fixed within the R1/beta2 development window to the R1/beta2 Milestone