Bug #7606
closed
Using limiters and VLANs on Supermicro Xeon D boards crashes with kernel panic
0%
Description
Confirmed on three different Supermicro Xeon D boards, 1508/1518/1521. With the similarities between these boards that I've seen, I wouldn't be surprised if it affected the whole line.
Confirmed on 2.3.4 RELEASE and 2.4 beta.
Was NOT able to reproduce on a VM
Uses the igb and ix drivers.
Used "pfSense-CE-2.3.4-RELEASE-amd64.iso".
1. Plugged "WAN" into port 1, plugged "LAN/Laptop" into port 2. Both are the gigabit ports, not the 10Gb ports. But I've seen it happen on both.
2. Install
3. Run though the basic setup
4. Set up a new random VLAN, attached to ibg1, used 99
5. Set up a new interface using VLAN_99, OPT.
6. Set up static IP and DHCP on OPT, 10.23.1.1, 10.23.1.10-20
7. Use the multi-LAN/WAN wizard to create a new limiter. Used LAN and OPT1. Used CBQ. All options on step 2-8 are default.
Server now runs fine. But it instantly implodes the second any traffic transverses the VLAN interface. The instant the laptop grabs a DHCP address on the VLAN network and tries to connect to the Internet, kernel panic.
At this point the server is locked, not responding to keyboard input, including CNTL-ALT-DEL and needs a hard power cycle.
Rebooting does a few things, just based on the timing of the traffic over the VLAN interface:
1. Kernel panics and bootloops when it tries to activate the firewall. On a busy VLAN, this is generally what happens.
2. Hard locks, without even the kernel panic, once traffic moves over the VLAN interface. With just one client on the VLAN, this is what happened through a couple of reboots.
Files
| IMG_0480.jpg (700 KB) IMG_0480.jpg | Kernel panic | ||
| 1.jpg (112 KB) 1.jpg | |||
| 2.jpg (109 KB) 2.jpg | |||
| 4.jpg (110 KB) 4.jpg | |||
| 3.jpg (114 KB) 3.jpg | |||
| 5.jpg (114 KB) 5.jpg | |||
| 6.jpg (103 KB) 6.jpg | |||
| 7.jpg (94.7 KB) 7.jpg | |||
| 8.jpg (78.6 KB) 8.jpg | |||
| begin-crash.JPG (67.7 KB) begin-crash.JPG |
Updated by 
Updated by 
Updated by 
