NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
kern/43533: Recent changes to wm(4) prevent it from working properly in virtualized environments
>Number: 43533
>Category: kern
>Synopsis: Recent changes to wm(4) prevent it from working properly in
>virtualized environments
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: kern-bug-people
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun Jun 27 00:00:00 +0000 2010
>Originator: David H. Gutteridge
>Release: 5.99.33
>Organization:
>Environment:
>Description:
As reported on by Kurt Schreiner on current-users:
>I just build new kernels for my NetBSD virtual machines running on
>MacOSx in VirtualBox and VMwareFusion, respectivly. Both virtualizers
>are configured with (virtual) Intel ethernet adapters and worked w/o
>issues with (customized) 5.99.30 kernels compiled some time ago.
>
>With new kernels (using same customized config files as for the older,
>working kernels) built from -current source cvs updated an hour or so
>ago I get the following (this is from VMware, but same issue with
>VirtualBox):
>
>Jun 26 13:15:26 /netbsd: wm0 at pci2 dev 0 function 0: Intel i82545EM
>1000BASE-T Ethernet, rev. 1
>Jun 26 13:15:26 /netbsd: wm0: interrupting at ioapic0 pin 18
>Jun 26 13:15:26 /netbsd: wm0: 32-bit 66MHz PCI bus
>Jun 26 13:15:26 /netbsd: wm0: 256 word (8 address bits) MicroWire EEPROM
>
>i.e. the adapter is recognized but there's no MAC address found and
>no PHY is attached anymore. (I tried all three possible Intel adapters
>offered by VirtualBox...)
>
>The respective lines from /var/log/messages with the old kernel booted
>are shown here: both MAC adress and PHY are found...
>
>Jun 26 13:16:32 /netbsd: wm0 at pci2 dev 0 function 0: Intel i82545EM
>1000BASE-T Ethernet, rev. 1
>Jun 26 13:16:32 /netbsd: wm0: interrupting at ioapic0 pin 18
>Jun 26 13:16:32 /netbsd: wm0: 32-bit 66MHz PCI bus
>Jun 26 13:16:32 /netbsd: wm0: 256 word (8 address bits) MicroWire EEPROM
>Jun 26 13:16:32 /netbsd: wm0: Ethernet address 00:50:56:2d:fa:5f
>Jun 26 13:16:32 /netbsd: makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY,
>rev. 3
>Jun 26 13:16:33 ntpd[327]: Listening on interface #1 wm0, 10.7.76.64#
>
>Any idea anyone where's the culprit?
>
>Kurt
The change in behaviour was caused by:
http://mail-index.netbsd.org/source-changes/2010/06/25/msg011190.html
>How-To-Repeat:
(As above.)
>Fix:
Reversion of the change.
Home |
Main Index |
Thread Index |
Old Index