Ticket #1403 (new bug)

Opened 13 months ago

Last modified 3 months ago

vlance driver calls acquire_sem_etc() from its interrupt routine

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

Description

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

Attachments

panic.png (31.7 kB) - added by diver 13 months ago.
Haiku.vmx (1.1 kB) - added by diver 13 months ago.

Change History

Changed 13 months ago by diver

Changed 13 months ago by diver

Changed 13 months ago by diver

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

Changed 13 months ago by axeld

  • owner axeld deleted
  • component changed from System/Kernel to Drivers/Network
  • summary changed from [Panic] acquare_sem_etc to vlance driver calls acquire_sem_etc() from its interrupt routine

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

Changed 13 months ago by umccullough

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.

Changed 5 months ago by diver

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.

Changed 3 months ago by diver

Axel?

Changed 3 months ago by axeld

  • priority changed from normal to low

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.

Changed 3 months ago by umccullough

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...

Changed 3 months ago by umccullough

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

http://dev.haiku-os.org/browser/haiku/trunk/src/add-ons/kernel/drivers/network/pcnet/dev/le

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

Note: See TracTickets for help on using tickets.