Opened 13 years ago

Closed 9 years ago

#1403 closed bug (fixed)

vlance driver calls acquire_sem_etc() from its interrupt routine

Reported by: diver Owned by:
Priority: low Milestone: R1
Component: Drivers/Network Version: R1/pre-alpha1
Keywords: Cc:
Blocked By: Blocking:
Platform: All


Haiku stops booting 4 times at different stages until this crash. See screenshot. Using vmware in linux with hrev21987.

Attachments (2)

panic.png (31.7 KB ) - added by diver 13 years ago.
Haiku.vmx (1.1 KB ) - added by diver 13 years ago.

Download all attachments as: .zip

Change History (12)

by diver, 13 years ago

Attachment: panic.png added

by diver, 13 years ago

Attachment: Haiku.vmx added

comment:1 by diver, 13 years ago

In this configuration i can't boot at all! But disabling network device "Connect on power on" in vmware settings let me to boot.

comment:2 by axeld, 13 years ago

Component: System/KernelDrivers/Network
Owner: axeld removed
Summary: [Panic] acquare_sem_etcvlance driver calls acquire_sem_etc() from its interrupt routine

I've removed the vlance driver from the image which is apparently broken.

comment:3 by umccullough, 13 years ago

Currently, vlance driver performance is pretty bad anyway - I've noticed very high packet loss.

Much better workaround at this point is to set ethernet0.virtualDev="e1000" in the .vmx which causes Haiku to use the ipro1000 driver instead. This driver has shown much better performance.

I'm certain the vlance driver will be improved eventually.

comment:4 by diver, 13 years ago

Is there any reason to keep this bug open? Or vlance driver is used somewhere outside vmware? If so, one should be ported from FreeBSD.

comment:5 by diver, 12 years ago


comment:6 by axeld, 12 years ago

Priority: normallow

The driver still has this bug. I'm not sure if this driver supports some actual hardware besides VMware; if not, we should just remove it.

comment:7 by umccullough, 12 years ago

I believe the VMWare vlance interface emulates the AMD PCNet32 device which does supposedly exist in real hardware (although I've personally not ever seen it myself).

Whether this vlance driver was also written to support the original AMD PCNet32 devices, on the other hand, I have no clue.

FWIW, I do remember Travis telling me that NewOS previously had a rudimentary pcnet32 driver as well...

comment:8 by umccullough, 12 years ago

Even more interesting, it looks like Haiku's repo already has the beginnings of a FreeBSD port of "if_le" which includes pcnet/lance:

Maybe if that was finished, vlance could be replaced in the image.

comment:9 by diver, 11 years ago

Maybe we should close this one and open a new ticket about porting if_le driver then?

comment:10 by diver, 9 years ago

Resolution: fixed
Status: newclosed

We use FreeBSD pcnet driver since hrev42295.

Note: See TracTickets for help on using tickets.