From owner-freebsd-current@FreeBSD.ORG  Thu Oct 11 11:30:25 2007
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B9C8E16A418
	for <freebsd-current@freebsd.org>; Thu, 11 Oct 2007 11:30:25 +0000 (UTC)
	(envelope-from mh@kernel32.de)
Received: from crivens.terrorteam.de (crivens.terrorteam.de [81.169.171.191])
	by mx1.freebsd.org (Postfix) with ESMTP id A5C4A13C461
	for <freebsd-current@freebsd.org>; Thu, 11 Oct 2007 11:30:25 +0000 (UTC)
	(envelope-from mh@kernel32.de)
Received: from localhost (localhost [127.0.0.1])
	by crivens.terrorteam.de (Postfix) with ESMTP id CFA0FB023F
	for <freebsd-current@freebsd.org>;
	Thu, 11 Oct 2007 13:30:23 +0200 (CEST)
MIME-Version: 1.0
Date: Thu, 11 Oct 2007 13:30:23 +0200
From: Marian Hettwer <mh@kernel32.de>
To: freebsd-current@freebsd.org
Message-ID: <fd2dd42ffea7af469dcf01b3308de1d3@127.0.0.1>
X-Sender: mh@kernel32.de
User-Agent: RoundCube Webmail/0.1b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
Subject: mpt0: QUEUE FULL EVENT: Bus 0x00 Target 0x04 Depth 129
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2007 11:30:25 -0000

Hi All,

I'm trying out -CURRENT on an IBM HS21 blade. So far the machine looks stable.
Only thing that bothers me is the message as stated above.

db46-23-freebsd# uptime
11:25AM  up 55 mins, 5 users, load averages: 0.01, 0.90, 1.21
db46-23-freebsd# dmesg | grep -c "QUEUE FULL EVENT"
111
db46-23-freebsd# uname -a
FreeBSD db46-23-freebsd 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Thu Oct 11 11:09:46 CEST 2007     root@blowfish:/usr/obj/amd64/usr/src/sys/GENERIC  amd64
db46-23-freebsd#

Is this something to worry about?

The LSI Logic controller in question is configured as a hardware RAID-0
Informations about the controller:
at boot time from dmesg:

mpt0: <LSILogic SAS/SATA Adapter> port 0x4000-0x40ff mem 0xdeffc000-0xdeffffff,0xdefe0000-0xdefeffff irq 16 at device 0.0 on pci2
mpt0: [ITHREAD]
mpt0: MPI Version=1.5.13.0
mpt0: mpt_cam_event: 0x16
mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required).
mpt0: mpt_cam_event: 0x12
mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required).
mpt0: mpt_cam_event: 0x12
mpt0: Unhandled Event Notify Frame. Event 0x12 (ACK not required).
mpt0: mpt_cam_event: 0x16
mpt0: Unhandled Event Notify Frame. Event 0x16 (ACK not required).
mpt0: mpt_cam_event: 0x21
mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required).
mpt0: mpt_cam_event: 0x21
mpt0: Unhandled Event Notify Frame. Event 0x21 (ACK not required).
da0 at mpt0 bus 0 target 0 lun 0

and from pciconf -lv

mpt0@pci0:2:0:0:        class=0x010000 card=0x03061014 chip=0x00561000 rev=0x02 hdr=0x00
    vendor     = 'LSI Logic (Was: Symbios Logic, NCR)'
    device     = 'SAS 3000 series, 4-port with 1064E -StorPort'
    class      = mass storage
    subclass   = SCSI

regards,
Marian
PS.: FWIW, Linux 2.6.20 had severe problems with this specific mpt controller - patches came with Linux 2.6.21
Looks like the LSI Logic stuff isn't very well supported. On the other hand, there's now way around them when using IBM blades :(
Same counts for the bce(4) NIC.