Opened 6 weeks ago
Closed 6 weeks ago
#19304 closed bug (fixed)
[virtio_net] ioctl: unknown message 22e1
Reported by: | haikupr | Owned by: | nobody |
---|---|---|---|
Priority: | normal | Milestone: | Unscheduled |
Component: | Drivers/Network/virtio | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
Since I updated to hrev58436, from time to time a flurry of messages related to virtio_net are logged in /var/log/syslog:
2024-12-20 07:25:19 KERN: virtio_net: ioctl: unknown message 22e1 Last message repeated 137 times
There is no other obvious symptoms. This haiku instance run under Bhyve on a FreeBSD host.
At boot time, I also observe a single 2716 unknown message. This is not new, the message is present since at least hrev57257. The message and its surroundings as produced by hrev58436:
2024-12-20 06:32:07 KERN: register_domain(1, internet) 2024-12-20 06:32:07 KERN: allocate_io_interrupt_vectors: allocated 3 vectors starting from 35 2024-12-20 06:32:07 KERN: msi_allocate_vectors: allocated 3 vectors starting from 35 2024-12-20 06:32:07 KERN: msix configured for 3 vectors 2024-12-20 06:32:07 KERN: msi-x enabled: 0x8002 2024-12-20 06:32:07 KERN: virtio_pci: using MSI-X count 3 starting at 35 2024-12-20 06:32:07 KERN: virtio_net: no mtu feature 2024-12-20 06:32:07 KERN: virtio_net: ioctl: unknown message 2716 2024-12-20 06:32:07 KERN: register_domain(5, internet6)
Note:
See TracTickets
for help on using tickets.
2716 == 10006 == ETHER_SET_LINK_STATE_SEM. It appears the virtio driver doesn't support that, but it doesn't need to.
22e1 == 8929 == SIOCGIFSTATS. That was added recently, I guess it might be nice to add that to the driver to reduce spamming. But it's harmless anyway.