Project

General

Profile

Actions

Bug #4014

open

kernel hiccups when creating vlan on ixgbe interface with no SFP+ module

Added by Alasdair Lumsden almost 9 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
driver - device drivers
Start date:
2013-08-08
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage
Gerrit CR:

Description

Hi There,

On OpenIndiana oi_151a7 I attempted to create a vlan interface by running:

  1. dladm create-vlan -v 1426 -l ixgbe1 ixgbe1vlan1426

ixgbe1 was down, had not previously been configured, and had no SFP+ module inserted.

The dladm command hung, and the box seemed to have hung - pings to it started timing out. However approximately 30 seconds later the box recovered, with the dladm command still hung.

I first attempted to truss the dladm process, no joy there - it hung. Ctrl-c'd truss, that quit. I attempted to kill -9 the dladm process, it didn't die.

Then every 2-5 minutes for varying times between 10 seconds and 2 minutes the kernel would just stall, pings would time out, then suddenly it'd respond to all the pings and come back to life.

After around 35 minutes dladm exited, and dmesg reported this:

Aug  8 15:48:38 nfs1-1.ixlon1.everycity.co.uk ixgbe: [ID 611667 kern.warning] WARNING: ixgbe1: Could not allocate dma buffer memory: ffffffff
Aug  8 15:48:38 nfs1-1.ixlon1.everycity.co.uk ixgbe: [ID 611667 kern.warning] WARNING: ixgbe1: Allocate tx dma buffer failed
Aug  8 15:48:39 nfs1-1.ixlon1.everycity.co.uk ixgbe: [ID 611667 kern.warning] WARNING: ixgbe1: Failed to allocate DMA resource

This is a fairly busy nfs box with 100 disks attached and around 50 nfs clients, and had been up for over 150 days at this point.

The box seems stable since dladm returned, with no more pauses seen.

I suspect the main issue here is a lack of handling for when an SFP+ module is not present in the port. I will attempt to reproduce this at a later date.

No data to display

Actions

Also available in: Atom PDF