On Monday, September 12, 2016, Borja Marcos <bor...@sarenet.es> wrote:
>
> > On 12 Sep 2016, at 17:23, Jim Harris <jim.har...@gmail.com
> <javascript:;>> wrote:
> >
> > There is an updated DCT 3.0.2 at: https://downloadcenter.intel.
> > com/dow
On Mon, Aug 1, 2016 at 11:49 AM, Jim Harris <jim.har...@gmail.com> wrote:
>
>
> On Mon, Aug 1, 2016 at 7:38 AM, Borja Marcos <bor...@sarenet.es> wrote:
>
>>
>> >
>> > It looks like all of the TRIM commands are formatted properly. The
>&g
On Mon, Aug 1, 2016 at 7:38 AM, Borja Marcos <bor...@sarenet.es> wrote:
>
> > On 29 Jul 2016, at 17:44, Jim Harris <jim.har...@gmail.com> wrote:
> >
> >
> >
> > On Fri, Jul 29, 2016 at 1:10 AM, Borja Marcos <bor...@sarenet.es> wrote:
>
On Fri, Jul 29, 2016 at 1:10 AM, Borja Marcos <bor...@sarenet.es> wrote:
>
> > On 28 Jul 2016, at 19:25, Jim Harris <jim.har...@gmail.com> wrote:
> >
> > Yes, you should worry.
> >
> > Normally we could use the dump_debug sysctls to help debug th
On Thu, Jul 28, 2016 at 3:29 AM, Borja Marcos wrote:
> Hi :)
>
> Still experimenting with NVMe drives and FreeBSD, and I have ran into
> problems, I think.
>
> I´ve got a server with 10 Intel DC P3500 NVMe drives. Right now, running
> 11-BETA2.
>
> I have updated the firmware
On Mon, Mar 7, 2016 at 5:33 AM, Borja Marcos wrote:
>
> Hello,
>
> I am trying a SuperMicro server with NVME disks. The system boots FreeBSD
> 10.2, panics when booting FreeBSD 10.3.
>
> It was compiled on March 7th and Revision 296191 is included.
>
> On 10.3 it’s crashing
ue to the inability to assign
>> all the interrupts because of
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321 <
>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199321>. Jim Harris
>> helped fix this issue so I bought several more of these servers, Inclu
On Tue, Oct 6, 2015 at 11:46 AM, Steven Hartland <kill...@multiplay.co.uk>
wrote:
> On 06/10/2015 19:03, Jim Harris wrote:
>
>
>
> On Tue, Oct 6, 2015 at 9:42 AM, Steven Hartland <
> <kill...@multiplay.co.uk>kill...@multiplay.co.uk> wrote:
>
>> Also lo
On Mon, Sep 7, 2015 at 10:37 PM, Bradley W. Dutton <
brad-fbsd-sta...@duttonbros.com> wrote:
> Quoting Jim Harris <jim.har...@gmail.com>:
>
> On Mon, Sep 7, 2015 at 7:29 PM, Bradley W. Dutton <
>> brad-fbsd-sta...@duttonbros.com> wrote:
>>
>> There are
On Mon, Sep 7, 2015 at 7:29 PM, Bradley W. Dutton <
brad-fbsd-sta...@duttonbros.com> wrote:
> There are 2 devices in the same group so I passed both of them:
> http://duttonbrosllc.com/misc/vmware_esxi_passthrough_config.png
>
> At the time I wasn't sure if this was necessary but I just tried the
On Mon, Sep 7, 2015 at 10:34 AM, Bradley W. Dutton <
brad-fbsd-sta...@duttonbros.com> wrote:
> Hi,
>
> I'm having trouble with the isci driver in both stable and current. I see
> the following dmesg in stable:
>
> isci0: port
>
On Fri, Jul 17, 2015 at 9:35 PM, dy...@techtangents.com
dy...@techtangents.com wrote:
Hi,
I've installed an Intel 750 400GB NVMe PCIe SSD in a Dell R320 running
FreeBSD 10.2-beta-1... not STABLE, but not far behind, I think. Apologies
if this is the wrong mailing list, or if this has been
On Thu, May 21, 2015 at 8:33 AM, Sean Kelly smke...@smkelly.org wrote:
Greetings.
I have a Dell R630 server with four of Dell’s 800GB NVMe SSDs running
FreeBSD 10.1-p10. According to the PCI vendor, they are some sort of
rebranded Samsung drive. If I boot the system and then load nvme.ko and
On Thu, Jun 27, 2013 at 6:38 PM, Jeremy Chadwick j...@koitsu.org wrote:
Intel Patsburg is otherwise known as Intel X79. The X79
chipset/southbridge offers 6 SATA ports, 2 of which are SATA600, and the
remaining 4 are SATA300:
http://en.wikipedia.org/wiki/Intel_X79
While Wikipedia
On Mon, Dec 17, 2012 at 9:26 AM, Willem Jan Withagen w...@digiware.nlwrote:
On 2012-12-17 15:38, Steven Hartland wrote:
Check the smart results of each disk in the array you may have a failing
disk.
- Original Message - From: Willem Jan Withagen
w...@digiware.nl
To: FreeBSD
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nlwrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts are occurring on inquiry commands to non-zero LUNs.
arcmsr(4) is returning CAM_SEL_TIMEOUT instead of CAM_DEV_NOT_THERE for
inquiry commands to this device
On Mon, Dec 17, 2012 at 3:21 PM, Willem Jan Withagen w...@digiware.nlwrote:
On 17-12-2012 23:10, Jim Harris wrote:
On Mon, Dec 17, 2012 at 2:45 PM, Willem Jan Withagen w...@digiware.nl
mailto:w...@digiware.nl wrote:
On 17-12-2012 20:16, Jim Harris wrote:
The timeouts
On Mon, Dec 17, 2012 at 4:52 PM, Willem Jan Withagen w...@digiware.nlwrote:
Right,
That did the trick.
Thanx for the code.
--WjW
Patch committed as r244369. It will get MFC'd but obviously won't be in 9.1.
Thanks,
-Jim
___
On Fri, Oct 26, 2012 at 1:18 PM, John-Mark Gurney j...@funkthat.com wrote:
I'm seeing similar stuff on the hpt27xx driver:
(probe18:hpt27xx0:0:18:0): INQUIRY. CDB: 12 0 0 0 24 0
(probe18:hpt27xx0:0:18:0): CAM status: Invalid Target ID
(probe18:hpt27xx0:0:18:0): Error 22, Unretryable error
On Sat, Sep 22, 2012 at 1:32 AM, Thomas Mueller muelle...@insightbb.com wrote:
The specific subject of this thread is not my issue, but I did notice
problems apparently related to CAM on a SATA hard drive.
I would suggest starting a new thread if you have a different issue.
I use one UFS
On Fri, Sep 21, 2012 at 1:07 PM, Mike Tancsa m...@sentex.net wrote:
Hi,
I have been trying out a nice new tws controller and decided to enable
debugging in the kernel and run some stress tests. With a regular
GENERIC kernel, it boots up fine. But with debugging, it panics on
boot. Anyone
On Fri, Sep 21, 2012 at 3:11 PM, Mike Tancsa m...@sentex.net wrote:
On 9/21/2012 4:59 PM, Jim Harris wrote:
snip
Thanks, that allows it to boot up now!
pci2: ACPI PCI bus on pcib2
LSI 3ware device driver for SAS/SATA storage controllers, version:
10.80.00.003
tws0: LSI 3ware SAS/SATA
On Fri, Sep 21, 2012 at 5:37 PM, Mike Tancsa m...@sentex.net wrote:
On 9/21/2012 8:03 PM, Jim Harris wrote:
.
then a lot of
.
(probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0
(probe65:tws0:0:65:0): CAM status: Invalid Target ID
(probe65:tws0:0:65:0): Error 22, Unretryable error
(probe1
On Fri, Aug 3, 2012 at 5:06 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi all,
I sent a PR [1] but I decided to also send the problem here.
If you try to destroy a geom_virstor that does not exist, this causes a
kernel panic immediately.
Just try:
gvirstor load
gvirstor destroy
On Fri, Aug 3, 2012 at 10:04 AM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
When I applied the patch gave this error:
# patch /root/patch.diff
Hmm... Looks like a unified diff to me...
The text leading up to this was:
--
|---
On Fri, Aug 3, 2012 at 1:12 PM, Marcelo Gondim gon...@bsdinfo.com.br wrote:
Hi Jim,
Perfect!!!
# gvirstor destroy tudo
gvirstor: Don't know anything about 'tudo'
Patch applied to head as r239021. I have requested approval from re@
to merge to stable/9.
Thank you for confirming the
26 matches
Mail list logo