Opened 2 months ago

Last modified 44 hours ago

#19129 new bug

no boot with beta5, stuck before desktop

Reported by: Alexco Owned by: nobody
Priority: normal Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: Cc: mmlr
Blocked By: Blocking:
Platform: All

Description

Beta5 does not boot on my old Celeron 32-Bit system. This system already has some reported issues with Matrox GFX card:

https://dev.haiku-os.org/ticket/12254

https://dev.haiku-os.org/ticket/18310

So I use fail-safe gfx driver and set a resolution of 1024x786x32 for booting. The boot stops right after the last icon (rocket), it stays there forever, never shows KDL or the desktop.

I attached the beta3 and beta5 syslogs.

Attachments (2)

syslog_beta5.txt (95.4 KB ) - added by Alexco 2 months ago.
syslog_hrev55181-51.txt (384.6 KB ) - added by Alexco 2 months ago.

Download all attachments as: .zip

Change History (7)

by Alexco, 2 months ago

Attachment: syslog_beta5.txt added

by Alexco, 2 months ago

Attachment: syslog_hrev55181-51.txt added

comment:1 by korli, 2 months ago

Cc: mmlr added
Version: R1/beta5R1/Development

from syslog beta5, actually it's master:

KERN: assuming memory type 20000000 for overlapping 0xd8000000, 0x8000 area 7163 from existing 0xd8000000, 0x300000 area 143
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/matrox

in beta3

KERN: set MTRRs to:
KERN:   mtrr:  0: base:    0xff000, size:     0x1000, type: 0
KERN:   mtrr:  1: base: 0x2fff0000, size:    0x10000, type: 0
KERN:   mtrr:  2: base: 0xd8000000, size:     0x8000, type: 0
KERN:   mtrr:  3: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  4: base: 0xd8000000, size:  0x8000000, type: 1
KERN: set MTRRs to:
KERN:   mtrr:  0: base:    0xff000, size:     0x1000, type: 0
KERN:   mtrr:  1: base: 0x2fff0000, size:    0x10000, type: 0
KERN:   mtrr:  2: base: 0xe0000000, size: 0x20000000, type: 0
KERN:   mtrr:  3: base: 0x80000000, size: 0x80000000, type: 1
KERN: loaded driver /boot/system/add-ons/kernel/drivers/dev/graphics/matrox

comment:2 by korli, 2 months ago

Alexco, you can try in the bootloader to enable "Disable PAT support".

comment:3 by mmlr, 8 weeks ago

It looks like the CPU here falls into the group with broken PAT support. I've compared with FreeBSD and Linux and both special case certain CPUs with PAT errata, either disabling PAT (FreeBSD) or using a different PAT layout (Linux) to work around the issue.

I've uploaded this change that should disable PAT on such CPUs. Until this change is merged, using the safemode option "Disable PAT" as korli suggested above should yield the same result.

comment:4 by Alexco, 8 weeks ago

Sorry, but disabling PAT in the bootloader does not solve the issue, neither the Matrox KDL issue, nor the non booting one. It simply says at that red rocket forever.

comment:5 by waddlesplash, 44 hours ago

Can you collect a second syslog with PAT disabled?

Note: See TracTickets for help on using tickets.