Frequent system crash on ifconfig

1

Hi,

because I can’t report a bug on Haiku’s bug tracker, I do it here:

When I install the latest sis900 driver an the latest networking kit (from the Haiku factory) on my BeOS Max 3 and do an “ifconfig sis9000 192.168.2.102 netmask 255.255.255.0” , I get often, not always, a crash. That’s the output of the debugger:

kernel debugger: Welcome to kernel Debugging Land...

eax 00000000 ebp fc023fa8 cs 0008 | area 053c7958 (core_seg0)
ebx 00000000 esp fc0239a8 ss 0010 | addr 6004c000 size 0000e000
ecx 00000206 edi fc0239b8 ds 0010 |
edx 012e19a8 esi 013becc8 es 0010 | Thread: si s9000_rx_thread
ei p 6004f822 flag 00010246 fs 0823 | Team: kernel_team
trap 0000000e err 00000002 gs 0000 | Stack Trace follows:

00000000 6004f822

I’m using an ASRock K7S8X mainbord, Athlon XP 2200+ processor, NVidia GF FX5200, 1GB RAM.

2

First, thanks schlesi for both testing and reporting.
I’ll forward your report to the team mailing-list.

To help us more, can you answer these questions:

  • when in KDL, can you type “sc” command and report what it display then ?
  • Did you try or are using the sis900 driver with net_server or BONE too ? Does it works then ?
    Or this issue raise only when using the driver with Haiku’s stack?

Thanks.

3

Philippe,

I’ve tried to use it with Haiku’s networking kit. I’ve first installed the sis900-driver and then the networking kit, both from the Haiku factory. I did it on a fresh BeOS Max 3 installation, I didn’t install BONE.

When I do the “sc” command in kdebug, it shows me:

Stack back trace from thread 254
KERNEL--   frame                retaddr
              0x00000000 0x60098822

I’ll set up a fresh installation this afternoon and test it with net_server and then with BONE.

Thomas

4

Ok, next take:

I’ve installed the Haiku sis900-driver on a fresh install of BeOS Max 3. Before the installation of the Haiku sis-driver, I configured the network interface and checked the connection. After the installation of the Haiku driver, the ping didn’t work. So I started the network configuration dialog, checked the configuration an klicked on “Restart networking”. The app crashed:

Thread Name: ether-reader
Error; segment violation

Team-ID: 62 Thread ID: 160
EIP: 0x800391a4

Then I clicked on the “Debugger”-button an got this output:

loading symbols
segment violation occured
800391a4 read_fault
ether-reader:

Thomas

5

I can’t test the sis-drivers with BONE. When I install BONE (7a) on my machine and make a reboot, the machine gets into an endless reboot loop, even when I install the Athlon XP patch before BONE.

Thomas

6
schlesi wrote:
I can't test the sis-drivers with BONE. When I install BONE (7a) on my machine and make a reboot, the machine gets into an endless reboot loop, even when I install the Athlon XP patch before BONE.

Thomas

Install it AFTER BONE, BEFORE the reboot.

7

When I use the networking kit with the default sis900-drivers (of BeOS Max 3), I got often a crash, too:

kernel debugger: Welcome to kernel Debugging Land... 

eax 00000000 ebp fc023fa8 cs 0008 | area 053a5738 (core_seg0) 
ebx 00000000 esp fc0239a8 ss 0010 | addr 6007f000 size 0000f000
ecx 00000206 edi fc0239b8 ds 0010 | 
edx 0134cc90 esi 01453828 es 0010 | Thread: si s9000_rx_thread 
ei p 600831d2 flag 00010246 fs 06bb | Team: kernel_team 
trap 0000000e err 00000002 gs 0000 | Stack Trace follows: 

00000000 600831 d2

The “sc”-command says:

Stack back trace for thread 256
KERNEL--   frame         retaddr
         0x00000000  0x600831 d2

Because the install.sh of the haiku-cvs-networking-kit seems not to work for me, I’ve installed it in all my tests as desrcibed here: http://www.haiku-os.org/forums/viewtopic.php?t=225

Thomas

8

MYOB,

BeOS comes also into an endless loop, when I install the Athlon patch after the BONE installation and before the reboot.

Thomas

9

Yeh, I also tried using the latest sis900 driver from the build factory on netserver without success - the version on BeBits works fine though.

I got a 100% CPU usage after startup, in the thread ether_reader

Simon