Opened 4 years ago

Closed 4 years ago

#15988 closed bug (duplicate)

Freeze when running "configure" script

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

Description (last modified by maquak)

Running hrev54139 x86_64 on AMD CPU based computer. It's my first installation of Haiku on this computer, so the bug is not necessarily new.

Problem: when I run "configure" script to configure Haiku build, my system freezes. Mouse stops working, clock stops updating. It also froze once when I just opened Terminal and once at the end of boot, but in general it works (right now it's almost at 30 minute uptime with me writing a bug report in WebPositive without problems).

KDL does not open automatically and Alt+SysRq+D does not trigger it too.

I can't tell if it freezes on any specific check in configure script, sometimes it takes a couple, sometimes tens of seconds.

I have buildtools and haiku checked out in /boot/home/dev directory. To reproduce I do the following:

cd dev/haiku
rm -rf generated.x86_64
cd generated.x86_64
../configure --build-cross-tools x86_64 ../../buildtools

The only clue that I have right now is that I tried it a couple of times with tail -f /boot/system/var/log/syslog running to see if there's anything logged: sometimes nothing appeared, but 2 times there was message like this:

KERN: slab memory manager: created area 0xffffffffa4001000 (26339)

Change History (4)

comment:1 by waddlesplash, 4 years ago

Is this an AMD FX processor? If so, this is a duplicate of #14082.

comment:2 by maquak, 4 years ago

Description: modified (diff)

comment:3 by maquak, 4 years ago

That was quick! Indeed, it's AMD FX-8150

comment:4 by waddlesplash, 4 years ago

Blocked By: 14082 added
Resolution: duplicate
Status: newclosed

We are generally pretty quick to reply to issues, yes. Fixing them, well...

As you can see, though, that ticket is rather long-running, and nobody has any real idea of what the actual problem is after exhausting a lot of possibilities. So unless you are skilled with low-level development and want to investigate yourself, you may be kind of sunk here.

Note: See TracTickets for help on using tickets.