From bugmaster at FreeBSD.org  Mon Aug  3 11:07:08 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug  3 11:09:53 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200908031107.n73B76Vx088776@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/136718  scsi       [ciss] ciss driver issue on HP DL585
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

38 problems total.

From sthaug at nethelp.no  Tue Aug  4 11:50:33 2009
From: sthaug at nethelp.no (sthaug@nethelp.no)
Date: Tue Aug  4 11:50:40 2009
Subject: Dell 1850/PERC 4e/Si (Megaraid) with "too many retries" error
Message-ID: <20090804.132349.112551733.sthaug@nethelp.no>

I have a FreeBSD 7.2-STABLE server which is physically a Dell 1850
with a PERC 4e/Si (Megaraid) controller and 2 x 73 GB disk in a RAID 1
configuration:

amr0: <LSILogic MegaRAID 1.53> mem 0xf80f0000-0xf80fffff,0xfe9e0000-0xfe9fffff irq 46 at device 14.0 on pci2
amr0: [ITHREAD]
amr0: delete logical drives supported by controller
amr0: <LSILogic PERC 4e/Si> Firmware 521X, BIOS H430, 256MB RAM
...
amr0: delete logical drives supported by controller
amrd0: <LSILogic MegaRAID logical drive> on amr0
amrd0: 69880MB (143114240 sectors) RAID 1 (optimal)

Occasionally the Megaraid controller will report the followin to syslog:

May  6 19:59:07 dhcp2 kernel: amr0: Too many retries on command 0xc3d31738.  Controller is likely dead
May 21 11:58:58 dhcp2 kernel: amr0: Too many retries on command 0xc3d311b8.  Controller is likely dead
Jul 24 22:22:34 dhcp2 kernel: amr0: Too many retries on command 0xc3d2fa58.  Controller is likely dead
Aug  1 07:52:30 dhcp2 kernel: amr0: Too many retries on command 0xc3d31318.  Controller is likely dead

However, there are no apparent ill effects, and the machine just keeps
running with no other sign of problems.

My question is: Should I be worried about these error messages?

Steinar Haug, Nethelp consulting, sthaug@nethelp.no
From tim-projects at sentinelchicken.org  Wed Aug  5 01:58:56 2009
From: tim-projects at sentinelchicken.org (Tim)
Date: Wed Aug  5 01:59:04 2009
Subject: "Inappropriate ioctl for device" when using scsi_sg
Message-ID: <20090805013213.GF2654@sentinelchicken.org>

Hello,

I'm trying to port a small piece of software from Linux to FreeBSD
which utilizes the Linux SCSI sg interface.  I saw that FreeBSD offers
a similar interface in version 7 and later, so I thought I would give
it a try.

Please pardon my ignorance as I haven't seriously worked with FreeBSD
since 4.x.  After searching for hours trying to find a recent
(7.x-based) downloadable live CD (I lack a good system for a full
install), I settled on trying out TrueBSD (version 2.0 RC2) to do my
testing. 

The software I'm porting
(http://projects.sentinelchicken.org/tableau-parm/) sends nonstandard
SCSI commands to proprietary devices over USB or Firewire.  Under
Linux, these commands are handled in either case using the same sg
interface.  I was able to compile my software fine on FreeBSD after a
few minor header file and symbol fixes, but when I attempt to send one
of these commands to the disk device file (/dev/da0 for instance), I
simply receive the error "Inappropriate ioctl for device".

Any ideas what I'm doing wrong?  I can provide source code, though it
is almost identical to the current release version (see link above).
Initially I mostly just wanted to ensure I wasn't missing something
obvious.  If this isn't the appropriate mailing list, please direct me
to the correct one. 

Thanks!
tim
From delphij at delphij.net  Wed Aug  5 23:48:32 2009
From: delphij at delphij.net (Xin LI)
Date: Wed Aug  5 23:48:40 2009
Subject: "Inappropriate ioctl for device" when using scsi_sg
In-Reply-To: <20090805013213.GF2654@sentinelchicken.org>
References: <20090805013213.GF2654@sentinelchicken.org>
Message-ID: <4A7A19F3.1040207@delphij.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi, Tim,

Tim wrote:
> Hello,
> 
> I'm trying to port a small piece of software from Linux to FreeBSD
> which utilizes the Linux SCSI sg interface.  I saw that FreeBSD offers
> a similar interface in version 7 and later, so I thought I would give
> it a try.
[...]
> Any ideas what I'm doing wrong?  I can provide source code, though it
> is almost identical to the current release version (see link above).
> Initially I mostly just wanted to ensure I wasn't missing something
> obvious.  If this isn't the appropriate mailing list, please direct me
> to the correct one. 

My understanding is that, by default (GENERIC), sg device is not
compiled into the kernel, so, in order to use it, you may have to
compile your own kernel and add:

	device sg

In the configuration.  The device would appear as "/dev/sg0", etc.;
Linux style "/dev/sga /dev/sgb" would appear as symlinks.

Cheers,
- --
Xin LI <delphij@delphij.net>	http://www.delphij.net/
FreeBSD - The Power to Serve!
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (FreeBSD)

iEYEARECAAYFAkp6GfIACgkQi+vbBBjt66DTKwCfe8I/ijSY4LifmqRghfd9Gbmi
424AoItYL9LxrUOEdi2JGMSHAGEMX5Qs
=AHh0
-----END PGP SIGNATURE-----
From tim-projects at sentinelchicken.org  Thu Aug  6 00:01:30 2009
From: tim-projects at sentinelchicken.org (Tim)
Date: Thu Aug  6 00:01:37 2009
Subject: "Inappropriate ioctl for device" when using scsi_sg
In-Reply-To: <4A7A19F3.1040207@delphij.net>
References: <20090805013213.GF2654@sentinelchicken.org>
	<4A7A19F3.1040207@delphij.net>
Message-ID: <20090806000123.GJ2654@sentinelchicken.org>


Xin,

Thanks much for your response.

> My understanding is that, by default (GENERIC), sg device is not
> compiled into the kernel, so, in order to use it, you may have to
> compile your own kernel and add:
> 
> 	device sg
> 
> In the configuration.  The device would appear as "/dev/sg0", etc.;
> Linux style "/dev/sga /dev/sgb" would appear as symlinks.

I figured it might be something like that.  Oddly, Linux allows me to
send these special SCSI commands directly to the original disk devices
(such as /dev/sd{a,b,c,..}) without the need for using any sg-specific
device files.  Using /dev/sg{0,...} is not a problem though.  I'll
have to find a system to do a full install on and get that compiled
in.

Thanks again,
tim
From nox at jelal.kn-bremen.de  Thu Aug  6 22:57:08 2009
From: nox at jelal.kn-bremen.de (Juergen Lock)
Date: Thu Aug  6 22:57:26 2009
Subject: cd(4) vs bluray ...
In-Reply-To: <20090806200715.GA16313@triton.kn-bremen.de>
References: <20090806184510.GA12039@triton.kn-bremen.de>
	<4A7B3328.5020307@FreeBSD.org>
	<20090806200715.GA16313@triton.kn-bremen.de>
Message-ID: <20090806223806.GA6332@triton.kn-bremen.de>

On Thu, Aug 06, 2009 at 10:07:15PM +0200, Juergen Lock wrote:
> On Thu, Aug 06, 2009 at 10:46:48PM +0300, Alexander Motin wrote:
> > Juergen Lock wrote:
> > >  So I put the problematic optical drive on a siis pcie card now because
> > > I wanted to play with esata too which seems to be kinda broken on the
> > > jmicron that I used before at least with _this_ esata drive (hw issue
> > > most likely, has been reported by users of other OSes too) - and I
> > > noticed two things:
> > > 
> > > 1. cd(4) (which the new ahci and siis drivers now also use) fails to do
> > > any reads when a drive fails the read toc command as seems to happen
> > > with bluray (data) discs at least; I was able to work around this
> > > by moving the bailout: label up a few lines in scsi_cd.c:cdcheckmedia():
> > > 
> > > Index: sys/cam/scsi/scsi_cd.c
> > > @@ -2868,12 +2868,18 @@
> > >  	}
> > >  
> > >  	softc->flags |= CD_FLAG_VALID_TOC;
> > > +
> > > +bailout:
> > >  	softc->disk->d_maxsize = DFLTPHYS;
> > >  	softc->disk->d_sectorsize = softc->params.blksize;
> > >  	softc->disk->d_mediasize =
> > >  	    (off_t)softc->params.blksize * softc->params.disksize;
> > >  
> > > +/* if
> > >  bailout:
> > > + * is here read requests will fail when the toc cant be read although
> > > + * CD_FLAG_VALID_MEDIA is set.
> > > + */
> > >  
> > >  	/*
> > >  	 * We unconditionally (re)set the blocksize each time the
> > > 
> > >  (I say work around because I don't know if there might be stuff
> > > somewhere that depends on the old behaviour, although thats probably
> > > unlikely; also acd(4) seems to behave similarly.)
> > 
> > I have no idea about this, ...
> > 
> Btw with `acd(4) seems to behave similarly' I meant a drive on acd
> _can_ read bluray.

Ok what do the -scsi folks say about this?  Should it check for the
disc (or drive?) to be bluray on only accept read toc failure in
that case?  Or is the patch fine as it is?  As I said the old acd(4)
driver seems not to care i.e. reads from bluray discs just fine...

 Wondering,
	Juergen
From artemb at gmail.com  Fri Aug  7 18:39:12 2009
From: artemb at gmail.com (Artem Belevich)
Date: Fri Aug  7 18:39:18 2009
Subject: mpt errors - UNIT ATTENTION asc:29,0
Message-ID: <ed91d4a80908071106l3951f384r3fa845eda2fcb0d3@mail.gmail.com>

Hi,

I'm running 8.0-BETA2 on Asus p5BV/SAS with built-in LSI1068
controller with 8 SATA ports. 6 of the ports hooked up to 1TB WD Green
drives. The drives are used as a single raidz2 ZFS pool:

	NAME        STATE     READ WRITE CKSUM
	z2          ONLINE       0     0     0
	  raidz2    ONLINE       0     0     0
	    da1     ONLINE       0     0     0
	    da0     ONLINE       0     0     0
	    da2     ONLINE       0     0     0
	    da3     ONLINE       0     0     0
	    da4     ONLINE       0     0     0
	    da5     ONLINE       0     0     0

I'm runing a simple stress test that copies 10GB file until it fills
the volume and then runs "zfs scrub" on it.

dd if=/dev/urandom of=/z2/f.0 bs=1m count=10240
for f in {1..350}; do echo $f; cp f.$[$f-1] f.$f; done;
zpool scrub z2

What concerns me is that I'm periodically getting error messages from
MPT driver. They usually start few hours after the start of the script
and by the end of it they are happening every few minutes seemingly
randomly on all six drives.

Aug  7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
Aug  7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): READ(10). CDB: 28 0 46
32 97 c0 0 0 80 0
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): CAM Status: SCSI Status Error
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): SCSI Status: Check Condition
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): UNIT ATTENTION asc:29,0
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Power on, reset, or bus
device reset occurred
Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Retrying Command (per Sense Data)

ZFS scrub does not seem to report any issues so far - no checksum or
read/write errors. WD's hard drive diagnostics tools didn't find any
issues with te drives either.

Sould somebody shed some light on why would such error happen? Is that
some sort of hardware issue? Driver bug? Issue with compatibility
between controller and the drives? System configuration issue (some
sysctl/tunable needs tweaking, perhaps)?

I'd appreciate any hints on what could be going on and what should be
done about it.

Thanks,
--Artem
From morganw at chemikals.org  Fri Aug  7 19:42:39 2009
From: morganw at chemikals.org (Wes Morgan)
Date: Fri Aug  7 19:42:52 2009
Subject: mpt errors - UNIT ATTENTION asc:29,0
In-Reply-To: <ed91d4a80908071106l3951f384r3fa845eda2fcb0d3@mail.gmail.com>
References: <ed91d4a80908071106l3951f384r3fa845eda2fcb0d3@mail.gmail.com>
Message-ID: <alpine.BSF.2.00.0908071438540.95674@ibyngvyr.purzvxnyf.bet>

On Fri, 7 Aug 2009, Artem Belevich wrote:

> Hi,
>
> I'm running 8.0-BETA2 on Asus p5BV/SAS with built-in LSI1068
> controller with 8 SATA ports. 6 of the ports hooked up to 1TB WD Green
> drives. The drives are used as a single raidz2 ZFS pool:
>
> 	NAME        STATE     READ WRITE CKSUM
> 	z2          ONLINE       0     0     0
> 	  raidz2    ONLINE       0     0     0
> 	    da1     ONLINE       0     0     0
> 	    da0     ONLINE       0     0     0
> 	    da2     ONLINE       0     0     0
> 	    da3     ONLINE       0     0     0
> 	    da4     ONLINE       0     0     0
> 	    da5     ONLINE       0     0     0
>
> I'm runing a simple stress test that copies 10GB file until it fills
> the volume and then runs "zfs scrub" on it.
>
> dd if=/dev/urandom of=/z2/f.0 bs=1m count=10240
> for f in {1..350}; do echo $f; cp f.$[$f-1] f.$f; done;
> zpool scrub z2
>
> What concerns me is that I'm periodically getting error messages from
> MPT driver. They usually start few hours after the start of the script
> and by the end of it they are happening every few minutes seemingly
> randomly on all six drives.
>
> Aug  7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
> Aug  7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): READ(10). CDB: 28 0 46
> 32 97 c0 0 0 80 0
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): CAM Status: SCSI Status Error
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): SCSI Status: Check Condition
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): UNIT ATTENTION asc:29,0
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Power on, reset, or bus
> device reset occurred
> Aug  7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Retrying Command (per Sense Data)
>
> ZFS scrub does not seem to report any issues so far - no checksum or
> read/write errors. WD's hard drive diagnostics tools didn't find any
> issues with te drives either.
>
> Sould somebody shed some light on why would such error happen? Is that
> some sort of hardware issue? Driver bug? Issue with compatibility
> between controller and the drives? System configuration issue (some
> sysctl/tunable needs tweaking, perhaps)?

I have that same board with 8 500gb drives in a raidz2. I used to 
be using a SATA backplane and I would see those timeouts fairly regularly 
when moving lots of data around. To eliminate the cable mess I switched to 
an SAS backplane with fanout cables and since then I have not seen the 
timeouts.

From danny at cs.huji.ac.il  Sat Aug  8 10:06:25 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Sat Aug  8 10:06:32 2009
Subject: request test drivers for iscsi_initiator 2.2.3
Message-ID: <E1MZiog-000GRx-V9@kabab.cs.huji.ac.il>

This new version:
 o - has some bug fixes.
 o - has full header/data digest support, thanks to Daisuke Aoyama
     <aoyama@peach.ne.jp>.
 o - the limit for the number of sessions is now 64, but can be
     raised - eventually via a sysctl call.
 o - the number of LUNs is unlimited, but things might get hairy
     over 128.
 o - now compiles & works under -current (8.0).

The tag option is supported, but by default is set very low (0),
if someone knows of a way to figure the optimal value I'll gladly
add it.

If it works for you, please let me know the model/make of the target so
I can update the list.

cheers,
	danny


From danny at cs.huji.ac.il  Sat Aug  8 10:11:44 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Sat Aug  8 10:11:51 2009
Subject: request test drivers for iscsi_initiator 2.2.3 
Message-ID: <E1MZitq-000GUu-FA@kabab.cs.huji.ac.il>

wups, forgot a small little detail:
	ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz

danny


From mav at mavhome.dp.ua  Sat Aug  8 15:37:38 2009
From: mav at mavhome.dp.ua (Alexander Motin)
Date: Sat Aug  8 15:37:45 2009
Subject: request test drivers for iscsi_initiator 2.2.3 
In-Reply-To: <1249741381.00149226.1249729205@10.7.7.3>
References: <1249741381.00149226.1249729205@10.7.7.3>
Message-ID: <4A7D8D7A.5030303@mavhome.dp.ua>

Hi.

Danny Braniss wrote:
> wups, forgot a small little detail:
> 	ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz

Is there reason why
	cpi->transport = XPORT_ISCSI;
covered by
#if defined(KNOB_VALID_ADDRESS)
?

-- 
Alexander Motin
From mav at FreeBSD.org  Sat Aug  8 15:46:08 2009
From: mav at FreeBSD.org (Alexander Motin)
Date: Sat Aug  8 15:46:20 2009
Subject: request test drivers for iscsi_initiator 2.2.3
In-Reply-To: <4A7D8D7A.5030303@mavhome.dp.ua>
References: <1249741381.00149226.1249729205@10.7.7.3>
	<4A7D8D7A.5030303@mavhome.dp.ua>
Message-ID: <4A7D8F72.8090905@FreeBSD.org>

Alexander Motin wrote:
> Danny Braniss wrote:
>> wups, forgot a small little detail:
>>     ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
> 
> Is there reason why
>     cpi->transport = XPORT_ISCSI;
> covered by
> #if defined(KNOB_VALID_ADDRESS)
> ?

Sorry, wrong question. But those who will test on CURRENT should take 
care about it.

-- 
Alexander Motin
From danny at cs.huji.ac.il  Sun Aug  9 07:00:55 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Sun Aug  9 07:01:15 2009
Subject: request test drivers for iscsi_initiator 2.2.3 
In-Reply-To: <4A7D8F72.8090905@FreeBSD.org> 
References: <1249741381.00149226.1249729205@10.7.7.3> 
	<4A7D8D7A.5030303@mavhome.dp.ua> <4A7D8F72.8090905@FreeBSD.org>
Message-ID: <E1Ma2Oi-0000Ah-7g@kabab.cs.huji.ac.il>

> Alexander Motin wrote:
> > Danny Braniss wrote:
> >> wups, forgot a small little detail:
> >>     ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.2.3.tar.gz
> > 
> > Is there reason why
> >     cpi->transport = XPORT_ISCSI;
> > covered by
> > #if defined(KNOB_VALID_ADDRESS)
> > ?
> 
I needed something to differentiate between the new CAM changes and the
old (in <= 7.2), so if you have a better knob ...

> Sorry, wrong question. But those who will test on CURRENT should take 
> care about it.
why? it compiles - and works - ok under 8.0, at least till the last
svn update :-)
cheers,
	danny


From fbsdlist at src.cx  Sun Aug  9 17:12:43 2009
From: fbsdlist at src.cx (Artem Belevich)
Date: Sun Aug  9 17:12:49 2009
Subject: [SOLVED] Re: mpt errors - UNIT ATTENTION asc:29,0
In-Reply-To: <ed91d4a80908071106l3951f384r3fa845eda2fcb0d3@mail.gmail.com>
References: <ed91d4a80908071106l3951f384r3fa845eda2fcb0d3@mail.gmail.com>
Message-ID: <ed91d4a80908091012t2a9db9f8v89dfd9c06fa35113@mail.gmail.com>

A bit more digging showed that these mpt errors match
UDMA_CRC_Error_Count reported by drives via SMART.
Connecting the same drives with the same cables to ICH7 SATA ports
completely eliminates the errors which suggests that drives and cables
themself are OK.
So, my guess is that there's fair amount of cross-talk between LSI1068
ports on the motherboard (Asus P5BV/SAS).

In the end I've switched on spread spectrum clocking on the drives
(jumper 1-2 on WD SATA drives) and the errors almost completely
disappeared. I've got 1 CRC error vs hundreds there used to be after
~10TB have been read/written.

What didn't quite work:
* Forcing drives into 1.5Gb mode (jumper 5-6 on WD drives). Errors
became somewhat less frequent, but didn't go away.
* replacing SATA cables -- tried three different sets with virtually
no change in error rate.

--Artem



On Fri, Aug 7, 2009 at 11:06 AM, Artem Belevich<artemb@gmail.com> wrote:
> Hi,
>
> I'm running 8.0-BETA2 on Asus p5BV/SAS with built-in LSI1068
> controller with 8 SATA ports. 6 of the ports hooked up to 1TB WD Green
> drives. The drives are used as a single raidz2 ZFS pool:
>
> ? ? ? ?NAME ? ? ? ?STATE ? ? READ WRITE CKSUM
> ? ? ? ?z2 ? ? ? ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ?raidz2 ? ?ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da1 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da0 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da2 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da3 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da4 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
> ? ? ? ? ? ?da5 ? ? ONLINE ? ? ? 0 ? ? 0 ? ? 0
>
> I'm runing a simple stress test that copies 10GB file until it fills
> the volume and then runs "zfs scrub" on it.
>
> dd if=/dev/urandom of=/z2/f.0 bs=1m count=10240
> for f in {1..350}; do echo $f; cp f.$[$f-1] f.$f; done;
> zpool scrub z2
>
> What concerns me is that I'm periodically getting error messages from
> MPT driver. They usually start few hours after the start of the script
> and by the end of it they are happening every few minutes seemingly
> randomly on all six drives.
>
> Aug ?7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
> Aug ?7 10:25:32 buz kernel: mpt0: mpt_cam_event: 0x16
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): READ(10). CDB: 28 0 46
> 32 97 c0 0 0 80 0
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): CAM Status: SCSI Status Error
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): SCSI Status: Check Condition
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): UNIT ATTENTION asc:29,0
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Power on, reset, or bus
> device reset occurred
> Aug ?7 10:25:32 buz kernel: (da4:mpt0:0:4:0): Retrying Command (per Sense Data)
>
> ZFS scrub does not seem to report any issues so far - no checksum or
> read/write errors. WD's hard drive diagnostics tools didn't find any
> issues with te drives either.
>
> Sould somebody shed some light on why would such error happen? Is that
> some sort of hardware issue? Driver bug? Issue with compatibility
> between controller and the drives? System configuration issue (some
> sysctl/tunable needs tweaking, perhaps)?
>
> I'd appreciate any hints on what could be going on and what should be
> done about it.
>
> Thanks,
> --Artem
>
From bugmaster at FreeBSD.org  Mon Aug 10 11:07:05 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 10 11:09:21 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200908101107.n7AB732x025295@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/136718  scsi       [ciss] ciss driver issue on HP DL585
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

38 problems total.

From edwardchuang at gmail.com  Thu Aug 13 14:42:49 2009
From: edwardchuang at gmail.com (Edward Chuang)
Date: Thu Aug 13 14:42:55 2009
Subject: multiple server attach to same iscsi target
Message-ID: <e9bbde360908130719y769e85a1p3dbabab31ca774be@mail.gmail.com>

Folks,

I've tried deploy my iSCSI target and trying to attach same iSCSI target
on different servers.

However, the second server which attach the iSCSI, it shows following
console message
and any change on this disk will not be seen by other computer.

da0 at iscsi0 bus 0 target 0 lun 0
da0: <proIPS SB-3164E-G1S3 1.0.> Fixed Direct Access SCSI-4 device
GEOM_LABEL: Label for provider da0p1 is ufsid/4a841a8316484a8d.
GEOM_LABEL: Label for provider da0p1 is ufs/iscsi.
GEOM_LABEL: Label ufs/iscsi removed.
GWEAORMN_ILNAGB:E L/i:s cLsaib ewla su fnsoitd /p4rao8p4e1ral8y3
1d6i4s8m4oau8ndt erdem
oved.
ap2#

It looks like a buffer overflow/underrun message. I have no clue even
no idea whether it is cause by iscsi or not.

Any suggestion will be appreciated.

Regards,
Ed
From danny at cs.huji.ac.il  Fri Aug 14 08:46:22 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Fri Aug 14 08:46:29 2009
Subject: multiple server attach to same iscsi target 
In-Reply-To: <e9bbde360908130719y769e85a1p3dbabab31ca774be@mail.gmail.com> 
References: <e9bbde360908130719y769e85a1p3dbabab31ca774be@mail.gmail.com>
Message-ID: <E1MbsQW-000DUS-22@kabab.cs.huji.ac.il>

> Folks,
> 
> I've tried deploy my iSCSI target and trying to attach same iSCSI target
> on different servers.
> 
> However, the second server which attach the iSCSI, it shows following
> console message
> and any change on this disk will not be seen by other computer.
> 
> da0 at iscsi0 bus 0 target 0 lun 0
> da0: <proIPS SB-3164E-G1S3 1.0.> Fixed Direct Access SCSI-4 device
> GEOM_LABEL: Label for provider da0p1 is ufsid/4a841a8316484a8d.
> GEOM_LABEL: Label for provider da0p1 is ufs/iscsi.
> GEOM_LABEL: Label ufs/iscsi removed.
> GWEAORMN_ILNAGB:E L/i:s cLsaib ewla su fnsoitd /p4rao8p4e1ral8y3
> 1d6i4s8m4oau8ndt erdem
> oved.
> ap2#
> 
> It looks like a buffer overflow/underrun message. I have no clue even
> no idea whether it is cause by iscsi or not.
> 
it's called 'garbled' :-)
G E O M _ L A B E L i s c s i   w a s   n o t   p r o p e r l y ...
 W A R N I N G :   / :   L a b e l   u f s i d / ...
-which is intself garbled :-)

> Any suggestion will be appreciated.
you can recompile the kernel an add to your configuration file:
options         PRINTF_BUFR_SIZE=256

which helps
	danny

> 
> Regards,
> Ed
> _______________________________________________
> freebsd-scsi@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"
> 


From edwardchuang at gmail.com  Fri Aug 14 09:03:40 2009
From: edwardchuang at gmail.com (Edward Chuang)
Date: Fri Aug 14 09:03:49 2009
Subject: multiple server attach to same iscsi target
In-Reply-To: <E1MbsQW-000DUS-22@kabab.cs.huji.ac.il>
References: <e9bbde360908130719y769e85a1p3dbabab31ca774be@mail.gmail.com> 
	<E1MbsQW-000DUS-22@kabab.cs.huji.ac.il>
Message-ID: <e9bbde360908140203u666ab7cfp350e3d676815032f@mail.gmail.com>

Hi,

So it looks like the when disk mounted on different computer, the
later one will consider this disk was dirty.
Is this normal ? And if there's possible to avoid this ? (I am using
UFS and ZFS)

Regards,
Ed


On Fri, Aug 14, 2009 at 4:46 PM, Danny Braniss<danny@cs.huji.ac.il> wrote:
>> Folks,
>>
>> I've tried deploy my iSCSI target and trying to attach same iSCSI target
>> on different servers.
>>
>> However, the second server which attach the iSCSI, it shows following
>> console message
>> and any change on this disk will not be seen by other computer.
>>
>> da0 at iscsi0 bus 0 target 0 lun 0
>> da0: <proIPS SB-3164E-G1S3 1.0.> Fixed Direct Access SCSI-4 device
>> GEOM_LABEL: Label for provider da0p1 is ufsid/4a841a8316484a8d.
>> GEOM_LABEL: Label for provider da0p1 is ufs/iscsi.
>> GEOM_LABEL: Label ufs/iscsi removed.
>> GWEAORMN_ILNAGB:E L/i:s cLsaib ewla su fnsoitd /p4rao8p4e1ral8y3
>> 1d6i4s8m4oau8ndt erdem
>> oved.
>> ap2#
>>
>> It looks like a buffer overflow/underrun message. I have no clue even
>> no idea whether it is cause by iscsi or not.
>>
> it's called 'garbled' :-)
> G E O M _ L A B E L i s c s i ? w a s ? n o t ? p r o p e r l y ...
> ?W A R N I N G : ? / : ? L a b e l ? u f s i d / ...
> -which is intself garbled :-)
>
>> Any suggestion will be appreciated.
> you can recompile the kernel an add to your configuration file:
> options ? ? ? ? PRINTF_BUFR_SIZE=256
>
> which helps
> ? ? ? ?danny
>
>>
>> Regards,
>> Ed
>> _______________________________________________
>> freebsd-scsi@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-scsi
>> To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org"
>>
>
>
>
From danny at cs.huji.ac.il  Fri Aug 14 09:44:08 2009
From: danny at cs.huji.ac.il (Danny Braniss)
Date: Fri Aug 14 09:44:14 2009
Subject: multiple server attach to same iscsi target 
In-Reply-To: <e9bbde360908140203u666ab7cfp350e3d676815032f@mail.gmail.com> 
References: <e9bbde360908130719y769e85a1p3dbabab31ca774be@mail.gmail.com> 
	<E1MbsQW-000DUS-22@kabab.cs.huji.ac.il>
	<e9bbde360908140203u666ab7cfp350e3d676815032f@mail.gmail.com>
Message-ID: <E1MbtKR-000Dwl-35@kabab.cs.huji.ac.il>

> Hi,
> 
> So it looks like the when disk mounted on different computer, the
> later one will consider this disk was dirty.
> Is this normal ? And if there's possible to avoid this ? (I am using> UFS and ZFS)
> 
careful, you have just stepped on a minefield!
you cannot mount the same disk on more than one computer using UFS or ZFS or the like.
If you want to share it then you should use NFS or GFS or Luster.
You could share it if it's readonly for ALL hosts.

danny


From bugmaster at FreeBSD.org  Mon Aug 17 11:07:03 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 17 11:09:40 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200908171107.n7HB722E075935@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/136718  scsi       [ciss] ciss driver issue on HP DL585
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

38 problems total.

From gdoe6545 at yahoo.it  Fri Aug 21 16:35:06 2009
From: gdoe6545 at yahoo.it (Gianni)
Date: Fri Aug 21 16:35:17 2009
Subject: mpt problems on RAID re-sync
Message-ID: <ADE45CD4-E24A-4657-B1FA-3421F7A01DA7@yahoo.it>

I'm trying to rebuild an mpt raid 1 array, at first the system kept  
panicking when the new disk was inserted, I upgraded from 7.1 to 7.2  
which fixed that problem.
The problem now is that the rebuild gets so far and then I get the  
following:

mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 156988075 of 286310400 blocks remaining
mpt0: IOC Generated Bus Reset Port: 0
(mpt0:vol0:1): Physical Disk Status Changed
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled )
(mpt0:vol0:1): No longer configured

Any ideas what could be causing this, is it likely to be a hardware  
issue or driver related?
Full dmesg below.
-Gianni


Copyright (c) 1992-2009 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
	The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-STABLE #3: Thu Aug 20 17:43:50 CEST 2009
     root@neptune.proiv-solutions.com:/usr/obj/usr/src/sys/NEPTUNE
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Xeon(TM) CPU 2.80GHz (2822.51-MHz K8-class CPU)
   Origin = "GenuineIntel"  Id = 0xf41  Stepping = 1
    
Features 
= 
0xbfebfbff 
< 
FPU 
,VME 
,DE 
,PSE 
,TSC 
,MSR 
,PAE 
,MCE 
,CX8 
,APIC 
,SEP 
,MTRR 
,PGE 
,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Features2=0x641d<SSE3,DTES64,MON,DS_CPL,CNXT-ID,CX16,xTPR>
   AMD Features=0x20100800<SYSCALL,NX,LM>
   TSC: P-state invariant
   Logical CPUs per core: 2
usable memory = 2135527424 (2036 MB)
avail memory  = 2059137024 (1963 MB)
ACPI APIC Table: <PTLTD  	 APIC  >
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
  cpu0 (BSP): APIC ID:  0
  cpu1 (AP/HT): APIC ID:  1
  cpu2 (AP): APIC ID:  6
  cpu3 (AP/HT): APIC ID:  7
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
ioapic2 <Version 2.0> irqs 48-71 on motherboard
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
acpi0: <PTLTD   RSDT> on motherboard
acpi0: [ITHREAD]
acpi0: Power Button (fixed)
Timecounter "ACPI-safe" frequency 3579545 Hz quality 850
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1008-0x100b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <unknown> at device 0.1 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 0.2 on pci1
pci3: <ACPI PCI bus> on pcib3
mpt0: <LSILogic 1030 Ultra4 Adapter> port 0x2000-0x20ff mem  
0xdd210000-0xdd21ffff,0xdd200000-0xdd20ffff irq 18 at device 5.0 on pci3
mpt0: [ITHREAD]
mpt0: MPI Version=1.2.12.0
mpt0: Capabilities: ( RAID-1E RAID-1 SAFTE )
mpt0: 1 Active Volume (1 Max)
mpt0: 2 Hidden Drive Members (6 Max)
em0: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2400-0x243f  
mem 0xdd220000-0xdd23ffff irq 16 at device 6.0 on pci3
em0: [FILTER]
em0: Ethernet address: 00:0a:e4:13:e1:dc
em1: <Intel(R) PRO/1000 Network Connection 6.9.6> port 0x2440-0x247f  
mem 0xdd280000-0xdd29ffff,0xdd240000-0xdd27ffff irq 17 at device 6.1  
on pci3
em1: [FILTER]
em1: Ethernet address: 00:0a:e4:13:e1:dd
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0x1400-0x141f  
irq 16 at device 29.0 on pci0
uhci0: [GIANT-LOCKED]
uhci0: [ITHREAD]
usb0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0x1420-0x143f  
irq 19 at device 29.1 on pci0
uhci1: [GIANT-LOCKED]
uhci1: [ITHREAD]
usb1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: <Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
uhub1: 2 ports with 2 removable, self powered
ehci0: <Intel 82801EB/R (ICH5) USB 2.0 controller> mem  
0xdd001000-0xdd0013ff irq 23 at device 29.7 on pci0
ehci0: [GIANT-LOCKED]
ehci0: [ITHREAD]
usb2: EHCI version 1.0
usb2: companion controllers, 2 ports each: usb0 usb1
usb2: <Intel 82801EB/R (ICH5) USB 2.0 controller> on ehci0
usb2: USB revision 2.0
uhub2: <Intel EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb2
uhub2: 4 ports with 4 removable, self powered
pcib4: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci4: <ACPI PCI bus> on pcib4
vgapci0: <VGA-compatible display> port 0x3000-0x30ff mem  
0xde000000-0xdeffffff,0xdd300000-0xdd300fff irq 16 at device 1.0 on pci4
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH5 UDMA100 controller> port  
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1460-0x146f at device 31.1 on pci0
ata0: <ATA channel 0> on atapci0
ata0: [ITHREAD]
ata1: <ATA channel 1> on atapci0
ata1: [ITHREAD]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
acpi_button0: <Power Button> on acpi0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
fdc0: <floppy drive controller> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on  
acpi0
fdc0: [FILTER]
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
cpu0: <ACPI CPU> on acpi0
p4tcc0: <CPU Frequency Thermal Control> on cpu0
cpu1: <ACPI CPU> on acpi0
p4tcc1: <CPU Frequency Thermal Control> on cpu1
cpu2: <ACPI CPU> on acpi0
p4tcc2: <CPU Frequency Thermal Control> on cpu2
cpu3: <ACPI CPU> on acpi0
p4tcc3: <CPU Frequency Thermal Control> on cpu3
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xcbfff, 
0xdc000-0xdffff on isa0
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio0: [FILTER]
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on  
isa0
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
Waiting 5 seconds for SCSI devices to settle
mpt0: Volume(0:0): Volume Status Changed
mpt0:vol0(mpt0:0:0): Settings ( Hot-Plug-Spares )
mpt0:vol0(mpt0:0:0): Using Spare Pool: 0
mpt0:vol0(mpt0:0:0): 2 Members:
       (mpt0:1:0:0): Primary Online
       (mpt0:1:1:0): Secondary Out of Sync Online
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled )
(mpt0:vol0:0): Physical (mpt0:0:0:0), Pass-thru (mpt0:1:0:0)
(mpt0:vol0:0): Online
(mpt0:vol0:1): Physical (mpt0:0:1:0), Pass-thru (mpt0:1:1:0)
(mpt0:vol0:1): Online
(mpt0:vol0:1): Status ( Out-Of-Sync )
acd0: DVDROM <HL-DT-STDVD-ROM GDR8082N/0B11> at ata0-master UDMA33
mpt0:vol0(mpt0:0:0): Volume Status Changed
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 285959992 of 286310400 blocks remaining
(probe0:mpt0:0:8:0): TEST UNIT READY. CDB: 0 0 0 0 0 0
(probe0:mpt0:0:8:0): CAM Status: SCSI Status Error
(probe0:mpt0:0:8:0): SCSI Status: Check Condition
(probe0:mpt0:0:8:0): UNIT ATTENTION asc:29,0
(probe0:mpt0:0:8:0): Power on, reset, or bus device reset occurred
(probe0:mpt0:0:8:0): Retrying Command (per Sense Data)
ses0 at mpt0 bus 0 target 8 lun 0
ses0: <SDR GEM318 0> Fixed Processor SCSI-2 device
ses0: 3.300MB/s transfers
ses0: SAF-TE Compliant Device
da0 at mpt0 bus 0 target 0 lun 0
da0: <LSILOGIC 1030          IM 1000> Fixed Direct Access SCSI-2 device
da0: 320.000MB/s transfers (160.000MHz DT, offset 63, 16bit)
da0: Command Queueing Enabled
da0: 139800MB (286310400 512 byte sectors: 255H 63S/T 17821C)
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
SMP: AP CPU #2 Launched!
Trying to mount root from ufs:/dev/da0s1a
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 277264363 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 267855403 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 258577387 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 249307819 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 239962219 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 230796139 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 221505451 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 212263339 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 202926187 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 193658731 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 184629931 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 175632811 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 166314667 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 161750635 of 286310400 blocks remaining
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled Re-Syncing )
mpt0:vol0(mpt0:0:0): Low Priority Re-Sync
mpt0:vol0(mpt0:0:0): 156988075 of 286310400 blocks remaining
mpt0: IOC Generated Bus Reset Port: 0
(mpt0:vol0:1): Physical Disk Status Changed
mpt0:vol0(mpt0:0:0): RAID-1 - Degraded
mpt0:vol0(mpt0:0:0): Status ( Enabled )
(mpt0:vol0:1): No longer configured

From bugmaster at FreeBSD.org  Mon Aug 24 11:07:04 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 24 11:09:24 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200908241107.n7OB73hi048722@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/136718  scsi       [ciss] ciss driver issue on HP DL585
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

38 problems total.

From samflanker at gmail.com  Mon Aug 24 11:30:03 2009
From: samflanker at gmail.com (Vladimir Ermakov)
Date: Mon Aug 24 11:30:09 2009
Subject: kern/123666: [aac] attach fails with Adaptec SAS RAID 3805
 controller and MSI RC410-M2 rev. 1.0 motherboard
Message-ID: <200908241130.n7OBU3ax072351@freefall.freebsd.org>

The following reply was made to PR kern/123666; it has been noted by GNATS.

From: Vladimir Ermakov <samflanker@gmail.com>
To: bug-followup@FreeBSD.org
Cc:  
Subject: re: kern/123666: [aac] attach fails with Adaptec SAS RAID 3805 controller
 and MSI RC410-M2 rev. 1.0 motherboard
Date: Mon, 24 Aug 2009 15:27:23 +0400

 Romain Tartiere, try call to adaptec support, this very specific problem.
 
From scottl at samsco.org  Tue Aug 25 17:19:14 2009
From: scottl at samsco.org (Scott Long)
Date: Tue Aug 25 17:19:21 2009
Subject: [PATCH] FIx for HP P210/212/410 adapters in FreeBSD 8.0
Message-ID: <20090825101145.S20031@pooker.samsco.org>

All,

ANyone who is having troubles booting with a new generation HP Smartarray 
adapter (P210/212/410/etc) under FreeBSD 8.0 is encouraged to try the 
patch below.  Also, those with older adapters, especially series-5 
adapters, are encouraged to test this as well to confirm that I didn't 
break anything.  Please let me know ASAP if works/doesn't work for you.

http://people.freebsd.org/~scottl/ciss_p410.diff

Thanks,
Scott

From gavin at FreeBSD.org  Tue Aug 25 18:09:34 2009
From: gavin at FreeBSD.org (gavin@FreeBSD.org)
Date: Tue Aug 25 18:09:41 2009
Subject: kern/136718: [ciss] ciss driver issue on HP DL585
Message-ID: <200908251809.n7PI9YSN072375@freefall.freebsd.org>

Synopsis: [ciss] ciss driver issue on HP DL585

State-Changed-From-To: open->feedback
State-Changed-By: gavin
State-Changed-When: Tue Aug 25 18:04:04 UTC 2009
State-Changed-Why: 
To submitter: I'm not sure it'll help, but is there any chance
you can try the patch at http://people.freebsd.org/~scottl/ciss_p410.diff
and see if that fixes things for you?


Responsible-Changed-From-To: freebsd-scsi->gavin
Responsible-Changed-By: gavin
Responsible-Changed-When: Tue Aug 25 18:04:04 UTC 2009
Responsible-Changed-Why: 
Track

http://www.freebsd.org/cgi/query-pr.cgi?pr=136718
From linimon at FreeBSD.org  Mon Aug 31 10:31:53 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Aug 31 10:32:01 2009
Subject: kern/138376: [cam] [patch] Memory leak in scsi_low_attach_xs()
	in file sys/cam/scsi/scsi_low.c
Message-ID: <200908311031.n7VAVrq9039855@freefall.freebsd.org>

Old Synopsis: Memory leak in scsi_low_attach_xs() in file sys/cam/scsi/scsi_low.c
New Synopsis: [cam] [patch] Memory leak in scsi_low_attach_xs() in file sys/cam/scsi/scsi_low.c

Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 31 10:31:12 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=138376
From linimon at FreeBSD.org  Mon Aug 31 10:33:13 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Aug 31 10:33:24 2009
Subject: kern/138379: [aic7xxx] [patch] Memory leak in output_listing()
	in file sys/dev/aic7xxx/aicasm/aicasm.c
Message-ID: <200908311033.n7VAXD0M040379@freefall.freebsd.org>

Old Synopsis: Memory leak in output_listing() in file sys/dev/aic7xxx/aicasm/aicasm.c
New Synopsis: [aic7xxx] [patch] Memory leak in output_listing() in file sys/dev/aic7xxx/aicasm/aicasm.c

Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 31 10:32:53 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=138379
From bugmaster at FreeBSD.org  Mon Aug 31 11:07:15 2009
From: bugmaster at FreeBSD.org (FreeBSD bugmaster)
Date: Mon Aug 31 11:09:29 2009
Subject: Current problem reports assigned to freebsd-scsi@FreeBSD.org
Message-ID: <200908311107.n7VB7Etg070702@freefall.freebsd.org>

Note: to view an individual PR, use:
  http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).

The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.


S Tracker      Resp.      Description
--------------------------------------------------------------------------------
o kern/138379  scsi       [aic7xxx] [patch] Memory leak in output_listing() in f
o kern/138376  scsi       [cam] [patch] Memory leak in scsi_low_attach_xs() in f
o kern/134488  scsi       [mpt] MPT SCSI driver probes max. 8 LUNs per device
o amd64/132394 scsi       [isp] - bad underruns with QLogic qla2300 and amd64
o kern/132250  scsi       [ciss] ciss driver does not support more then 15 drive
o kern/132206  scsi       [mpt] system panics on boot when mirroring and 2nd dri
o kern/131032  scsi       [panic] hald causing panic in scsi_sg
o kern/130735  scsi       [cam] [patch] pass M_NOWAIT to the malloc() call insid
o kern/130621  scsi       [mpt] tranfer rate is inscrutable slow when use lsi213
o kern/129602  scsi       [ahd] ahd(4) gets confused and wedges SCSI bus
o kern/128452  scsi       [sa] [panic] Accessing SCSI tape drive randomly crashe
o kern/128245  scsi       [scsi] "inquiry data fails comparison at DV1 step" [re
o kern/127927  scsi       [isp] isp(4) target driver crashes kernel when set up 
o kern/126866  scsi       [isp] [panic] kernel panic on card initialization
o kern/124667  scsi       [amd] [panic] FreeBSD-7 kernel page faults at amd-scsi
o kern/123674  scsi       [ahc] ahc driver dumping
o kern/123666  scsi       [aac] attach fails with Adaptec SAS RAID 3805 controll
o sparc/121676 scsi       [iscsi] iscontrol do not connect iscsi-target on sparc
o kern/120487  scsi       [sg] scsi_sg incompatible with scanners
o kern/120247  scsi       [mpt] FreeBSD 6.3 and LSI Logic 1030 = only 3.300MB/s 
o kern/119668  scsi       [cam] [patch] certain errors are too verbose comparing
o kern/114597  scsi       [sym] System hangs at SCSI bus reset with dual HBAs
o kern/110847  scsi       [ahd] Tyan U320 onboard problem with more than 3 disks
o kern/99954   scsi       [ahc] reading from DVD failes on 6.x [regression]
o kern/94838   scsi       Kernel panic while mounting SD card with lock switch o
o kern/92798   scsi       [ahc] SCSI problem with timeouts
o kern/90282   scsi       [sym] SCSI bus resets cause loss of ch device
o kern/76178   scsi       [ahd] Problem with ahd and large SCSI Raid system
o kern/74627   scsi       [ahc] [hang] Adaptec 2940U2W Can't boot 5.3
s kern/61165   scsi       [panic] kernel page fault after calling cam_send_ccb
o kern/60641   scsi       [sym] Sporadic SCSI bus resets with 53C810 under load
o kern/60598   scsi       wire down of scsi devices conflicts with config
s kern/57398   scsi       [mly] Current fails to install on mly(4) based RAID di
o kern/52638   scsi       [panic] SCSI U320 on SMP server won't run faster than 
o kern/44587   scsi       dev/dpt/dpt.h is missing defines required for DPT_HAND
o kern/40895   scsi       wierd kernel / device driver bug
o kern/39388   scsi       ncr/sym drivers fail with 53c810 and more than 256MB m
o kern/38828   scsi       [dpt] [request] DPT PM2012B/90 doesn't work
o kern/35234   scsi       World access to /dev/pass? (for scanner) requires acce

39 problems total.

From linimon at FreeBSD.org  Mon Aug 31 17:31:52 2009
From: linimon at FreeBSD.org (linimon@FreeBSD.org)
Date: Mon Aug 31 17:32:03 2009
Subject: kern/138384: [ips] [patch] NULL pointer dereference in
	ipsd_dump() in file sys/dev/ips/ips_disk.c
Message-ID: <200908311731.n7VHVq75067173@freefall.freebsd.org>

Synopsis: [ips] [patch] NULL pointer dereference in ipsd_dump() in file sys/dev/ips/ips_disk.c

Responsible-Changed-From-To: freebsd-bugs->freebsd-scsi
Responsible-Changed-By: linimon
Responsible-Changed-When: Mon Aug 31 17:31:44 UTC 2009
Responsible-Changed-Why: 
Over to maintainer(s).

http://www.freebsd.org/cgi/query-pr.cgi?pr=138384