Actions
Bug #4283
closed
Constant cas# device timeout errors and crashes with Sun 501-6738-10
Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Operating System
Target version:
-
Start date:
01/24/2015
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:
i386
Description
Updated a copy of a working 2.1.5 production system to 2.2 and, during the boot, see constant cas2 and cas3 device timeout errors (cas1-3 interfaces are configured). Looks like yet another "ol' workhorse" NIC has been obsoleted. <sigh>
The test system has a Intel Celeron 2.2 GHz processor. After completing a very slow boot (>10 minutes), if pfSense doesn't crash, it's certainly unusably slow (i.e., takes "forever" even to reconfigure -- presumably because everything's mostly blocked due to the device timeouts).
I'm assuming there's no hope of this getting fixed?
Updated by Chris Buechler about 9 years ago
- Category changed from Interfaces to Operating System
- Status changed from New to Rejected
not something we're going to fix, you can replicate on stock FreeBSD and report upstream to see if that gets any results.
Actions