#30 closed bug (fixed)
Reproducable crash after running ifconfig.
Reported by: | Owned by: | phoudoin | |
---|---|---|---|
Priority: | blocker | Milestone: | R1 |
Component: | - General | Version: | |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Running Haiku in VMware. Press space to get the safe menu and chose 1024x768@32 as the screen resolution. Haiku boots up to app_server and MiniTerminal loads.
Type ping hostname, and obviously the host can't be found as networking hasn't
been configured, then type ifconfig to see the networking settings, it reports the usage and then the system hangs hard.
I can get more info if you tell me how you want it.
Change History (8)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
Owner: | changed from | to
---|
comment:3 by , 19 years ago
A bug that loaded recursively the /dev/net/stack device driver (freezing the kernel into an infinite get_module() calls loop...) was fixed recently. As the first ifconfig call, accessing /dev/net/stack thru libnet.so, load this driver, it can be the hang origin.
Please, test again with latest haiku kernel and net_stack_driver's driver.
comment:4 by , 19 years ago
severity: | normal → blocker |
---|
comment:5 by , 19 years ago
Changing the severity to "blocker" as this problem crashes the whole system.
comment:6 by , 19 years ago
Status: | new → closed |
---|
comment:8 by , 19 years ago
Resolution: | → fixed |
---|
Just tested on my machine, running Haiku natively. ifconfig runs, and exits cleanly. Was able to run other commands after it.
Possibly flag this up to the VMWare interface?