Displaying 20 results from an estimated 500 matches similar to: "problems with the mfi"
2012 Aug 07
4
LSI 9240-4i 4K alignment
Hi all,
We have a server with a LSI 9240-4i controller configured in JBOD with
4 SATA disks. Running FreeBSD 9.1-Beta1:
Relevant dmesg:
FreeBSD 9.1-BETA1 #0: Thu Jul 12 09:38:51 UTC 2012
root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
CPU: Intel(R) Xeon(R) CPU E31230 @ 3.20GHz (3200.09-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model =
2013 Feb 26
3
mfi timeouts
> On 28/10/2011 04:14, Jan Mikkelsen wrote:
> >/ Hi,
> />/
> />/ There is a patch linked to from this PR, which seems very similar:
> />/
> />/ http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/140416
> />/
> />/ http://lists.freebsd.org/pipermail/freebsd-scsi/2011-March/004839.html
> />/
> />/ The problem is also consistent with running
2012 Mar 30
6
9-STABLE, ZFS, NFS, ggatec - suspected memory leak
Hi all,
Setup:
I'm running 2 machines (amd64, 16GB) with FreeBSD 9-STABLE (Mar 14 so
far) acting as NFS servers. They each serve 3 zpools (holding a single
zfs, hourly snapshots). The zpools each are 3-way mirrors of ggate
devices, each 2 TB, so 2 TB per zpool. Compression is "on" (to save
bandwith to the backend, compressratio around 1.05 to 1.15), atime is
off.
There is no
2013 Feb 12
2
ix? / Intel(R) PRO/10GbE
I finally got a 10G card that is recognized by FreeBSD (9.1-stable):
...
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.4.8> port
0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device
0.0 on pci4
ix0: Using MSIX interrupts with 9 vectors
ix0: RX Descriptors exceed system mbuf max, using default instead!
ix0: Ethernet address: 90:e2:ba:29:c0:54
2012 Jul 13
2
stable/9 panic Bad tailq NEXT(0xffffffff80e52660->tqh_last) != NULL
Well this is new. I haven't a clue what Dell has done on this R620, but
this popped up today after I did a boat load of BIOS updates and tried
to install stable/9 from our yahoo tree. If anyone sees the obvious
solution here, I'd love to figure it out.
found-> vendor=0x14e4, dev=0x165f, revid=0x00
domain=0, bus=2, slot=0, func=1
class=02-00-00, hdrtype=0x00, mfdev=1
2008 Aug 01
1
reboot sometimes freezes, adaptic scsi card possible problem
On reboot, one out of 10 times, reboot (from hardware initialization) stops.
Referring to this portion of the dmesg -v output, of a successful boot,
where i have marked ">>>HERE<<<" is where the boot freezes on an
unsuccessful boot. This is a constnat problem, on 6.2 as well as 6.3
unchanged.
ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA33 cable=40 wire
acd0: setting
2015 Sep 15
3
FreeBSD 10 & default_vsz_limit causing reboots?
Ok,
So this is really more of an observation than anything else.?
I had a FreeBSD 10.1 server that was running great. Some SSL issue came up,
or I upgrade Dovecot in ports - something occurred and the machine started
rebooting randomly.? It would run for 2 weeks, then reboot.? It might run
for 5 days and then reboot. So I started doing more FreeBSD upgrades,
thinking it was a kernel issue. The
2015 Sep 24
0
FreeBSD 10 & default_vsz_limit causing reboots?
Update.? Only a single reboot has occurred since changing
defalt_vsz_limit from 384M to 512M.? It would seem that something the
users are doing is causing that virtual memory size to be exceeded
(possibly a mailbox search?), and when that occurs Dovecot/FreeBSD is not
handling the event as smoothly as expected.
Here's my dmesg for more basic info.
Sep 17 11:25:39 romulus syslogd: kernel boot
2012 Nov 13
1
thread taskq / unp_gc() using 100% cpu and stalling unix socket IPC
Hi there
We have a pair of servers running FreeBSD 9.1-RC3 that act as transparent layer 7 loadbalancer (relayd) and pop/imap proxy (dovecot). Only one of them is active at a given time, it's a failover setup. From time to time the active one gets in a state in which the 'thread taskq' thread uses up 100% of one cpu on its own, like here:
----
PID USERNAME PRI NICE SIZE
2008 Jun 17
0
MFI driver
Hi folks;
I have acquired a rackmount Intel server with a RAID card in it that appears
to be compatable with the MFI driver.
To put it mildly, this thing SMOKES! It is SCREAMING fast. Insane, in
fact.
Ok, enough supurlatives.
Now the question is this - exactly what board(s) will this driver support?
Is it only the two that are listed in the hardware release notes?
LSI has a number of
2013 Dec 17
1
[LLVMdev] Out of tree targets: API Change to MFI::CreateStackObject
Hi,
I will soon be committing a change to MachineFrameInfo::CreateStackObject
that removes the "bool MayNeedSP" parameter. This API change is part of larger
patch that re-works stack layout passes to use analysis from the StackProtector
pass to layout StackProtected objects (http://llvm-reviews.chandlerc.com/D2158).
Out of tree targets will need to update their usage accordingly. The
2008 Oct 14
1
FreeBSD 7-STABLE, isp(4), QLE2462: panic & deadlocks
Hello everybody,
we recently got three Dell PowerEdge servers equipped with Qlogic
QLE2462 cards (dual FC 4Gbps ports) and an EMC CLARiiON CX3-40 SAN.
The servers with the FC cards were successfully and extensively
tested with an older SUN StorEdge T3 SAN.
However, when we connect them to the CX3-40, create and mount a new
partition and then do something as simple as "tar -C /san -xf
2009 Mar 22
4
7.2-PRERELEASE/sunx2200/bge/msi broken
Hi,
between March 16 and now, bge on a Sun X2200 stopped working,
turning off msi (via hw..pci.enable_msi=0) got it working again.
I tried first replacing bge with an older version but that did not help.
please advice :-)
Danny
2013 Jan 25
2
bge numbering
Hi,
this server, a Dell R720 has 4 bge on board,
Broadcom NetXtreme Gigabit Ethernet, ASIC rev. 0x5720000
bge0: APE FW version: NCSI v1.1.7.0
bge0: CHIP ID 0x05720000; ASIC REV 0x5720; CHIP REV 0x57200; PCI-E
miibus0: <MII bus> on bge0
...
I have connected the ethernet to port labeled 0, but it appears
as bge2, how can this be corrected?
thanks,
danny
2009 Feb 05
3
impossible packet length ...
Hi,
on 2 different servers, running 7.1-stable + zfs, I get this
error rather frequently:
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (543383918) from
nfs server sunfire:/dist
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1936028704) from
nfs server sunfire:/dist
Feb 5 17:01:03 warhol-00 kernel: impossible packet length (1869363744) from
nfs server sunfire:/dist
2012 Jul 21
2
lsof needs update
hi, lsof on freebsd 9.1:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
ntpd 1707 root cwd unknown file
system type: newnfs
ntpd 1707 root rtd unknown file
system type: newnfs
ntpd 1707 root txt unknown file
system type: newnfs
ntpd 1707
2013 May 15
1
still mbuf leak in 9.0 / 9.1?
Hi list,
since we activated 10gbe on ixgbe cards + jumbo frames(9k) on 9.0 and now on 9.1 we recognize that after a random period of time, sometimes a week, sometimes only a day, the
system doesn't send any packets out. The phenomenon is that you can't login via ssh, nfs and istgt is not operative. Yet you can login on the console and execute commands.
A clean shutdown isn't possible
2008 Jun 22
1
3.0.3pre2 errors under interix
I've been trying to sync two directories under interix between two
machines on the local network and I keep getting the flowing errors:-
The first error is "failed: Bad address (14)" which always occurs
rsync: readlink "/dev/fs/D/Media/Audio/The Hoosiers/desktop.ini" failed: Bad address (14)
The second is randomly occuring, restarting will make it continue
for a bit then
2013 Sep 03
2
Intel 10Gb network card
hi,
I have a hard time figuring this out, the kernel says:
...
ix0: <Intel(R) PRO/10GbE PCI-Express Network Driver, Version - 2.5.15> port
0xecc0-0xecdf mem 0xd9e80000-0xd9efffff,0xd9ff8000-0xd9ffbfff irq 40 at device
0.0 on pci4
ix0: Using MSIX interrupts with 9 vectors
ix0: Ethernet address: 90:e2:ba:29:c0:54
ix0: PCI Express Bus: Speed 5.0GT/s Width x8
ix1: <Intel(R) PRO/10GbE
2013 Jul 22
1
FreeBSD 9 and PERC H200
I got a Dell T110-II server on 2013-July-19. It has two 1Tbyte drives
that the PERC H200 controls, RAID 1. I tried to install
FreeBSD-9.1-RELEASE from a DVD from FreebsdMall. The autopart segfaulted,
evidently because it could not find any disks. I think there is a PR
about the segfaulting (bad bug, no messages).
I worked around the problem by going to the loader prompt when the initial