Opened 10 years ago

Closed 9 years ago

#4470 closed bug (duplicate)

net_server crash and static IP not working

Reported by: marcusoverhagen Owned by: axeld
Priority: normal Milestone: R1/alpha3
Component: Servers/net_server Version: R1/Development
Keywords: Cc:
Blocked By: #5668 Blocking:
Has a Patch: no Platform: All

Description

I'm not using DHCP.

On first start of a fresh initialized haiku image, net_server does crash. Entering static IP information into Network preferences has no effect, network (ping, etc) is not working.

After the first reboot, network is working, and net_server no longer crashes.

Tested with hrev33042

available information from syslog:

DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 0)
DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 0)
DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 1)
DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 2)
DAEMON 'DHCP': DHCP timeout shift: 2 secs (try 2)
DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 2)
DAEMON 'DHCP': DHCP timeout shift: 4 secs (try 2)
DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 2)
DAEMON 'DHCP': DHCP timeout shift: 8 secs (try 2)
DAEMON 'DHCP': DHCP for /dev/net/ipro1000/0, status: Operation timed out
KERN: 119: DEBUGGER: looperlist is not locked; proceed at great risk!
KERN: debug_server: Thread 119 entered the debugger: Debugger call: `looperlist is not locked; proceed at great risk!'
KERN: stack trace, current PC 0xffff0114  :
KERN:   (0x70080b7c)  0x2da99d  AssertLocked__Q28BPrivate11BLooperList + 0x35
DAEMON 'DHCP': DHCP for /dev/net/rtl8169/0, status: Operation timed out
KERN:   (0x70080bac)  0x2da11a  IsLooperValid__Q28BPrivate11BLooperListPC7BLooper + 0x3a
KERN: 122: DEBUGGER: looperlist is not locked; proceed at great risk!
KERN:   (0x70080bec)  0x2d838f  IsLocked__C7BLooper + 0x27
KERN:   (0x70080c1c)  0x2d994b  AssertLocked__C7BLooper + 0x1f
KERN:   (0x70080c4c)  0x2d7f68  RemoveHandler__7BLooperP8BHandler + 0x28
KERN:   (0x70080c7c)  0x20e7f0  _RemoveClient__16AutoconfigLooper + 0x30
KERN:   (0x70080cac)  0x20e9b8  _Configure__16AutoconfigLooper + 0x18c
KERN:   (0x70080e8c)  0x20eca0  _ReadyToRun__16AutoconfigLooper + 0x30
KERN:   (0x70080ecc)  0x20ece4  MessageReceived__16AutoconfigLooperP8BMessage + 0x38
KERN:   (0x70080f0c)  0x2d7df7  DispatchMessage__7BLooperP8BMessageP8BHandler + 0x5b
KERN:   (0x70080f3c)  0x2d9765  task_looper__7BLooper + 0x211
KERN:   (0x70080f7c)  0x2d9353  _task0___7BLooperPv + 0x3f
KERN:   (0x70080fac)  0x5390c8  thread_entry + 0x20

Attachments (1)

syslog-ahci (99.6 KB) - added by marcusoverhagen 10 years ago.

Download all attachments as: .zip

Change History (4)

Changed 10 years ago by marcusoverhagen

Attachment: syslog-ahci added

comment:1 Changed 10 years ago by marcusoverhagen

I'm using the ipro1000, the rtl device is not connected.

comment:2 Changed 10 years ago by scottmc

Milestone: R1/alpha1R1/alpha2

comment:3 Changed 9 years ago by axeld

Blocked By: 5668 added
Component: Network & Internet/StackServers/net_server
Resolution: duplicate
Status: newclosed
Version: R1/pre-alpha1R1/Development

Bug #5668 contains better information for this problem.

Note: See TracTickets for help on using tickets.