Re: ISCI bus_alloc_resource failed

Quoting Jim Harris : 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 wa

Re: ISCI bus_alloc_resource failed

ssing through the wrong device, or someone added the wrong PCI device id data to the driver? Scott On Sep 7, 2015, at 11:34 AM, Bradley W. Dutton wrote: Hi, I'm having trouble with the isci driver in both stable and current. I see the following dmesg in stable: isci0: port 0x5

Re: ISCI bus_alloc_resource failed

Quoting Jim Harris : 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 0x5000-0x50ff mem 0xe7afc000-0xe7af

ISCI bus_alloc_resource failed

Hi, I'm having trouble with the isci driver in both stable and current. I see the following dmesg in stable: isci0: port 0x5000-0x50ff mem 0xe7afc000-0xe7af,0xe740-0xe77f irq 19 at device 0.0 on pci11 isci: 1:51 ISCI bus_alloc_resource failed I'm running FreeBSD on VMW

ZFS issue?

I updated my stable box (i386) on Tuesday and started seeing errors like the below intermittently. Is anyone else seeing anything like this? I saw similar errors periodically doing portupgrade and portinstall. Besides the intermittent errors the stability is much improved, my i386 box hasn't crash

em watchdog timeout

Hi, I'm still seeing watchdog timeouts on my em card using stable from Nov 28. Before the flurry of messages/activity about this last month I never had any timeout problems, they only started occurring after the em changes were committed in November. Generally when the timeout occurs everything ha

graid3 rebuild panic: mb_dtor_pack: ext_size != MCLBYTES

Hi, I get the below panic when rebuilding a graid3 array. Is this indicative of a hardware or software problem? Or is some of the data on my array corrupt and I should just rebuild the array? I searched on google and didn't find much. panic: mb_dtor_pack: ext_size != MCLBYTES Thanks for your tim

graid3 configure on 6 stable

Hi, I just tried 'graid3 configure -a' on a degraded array and received the following: panic: lock geom topology not exclusively locked @ /usr/src/sys/geom/raid3/g_raid3_ctl.c:105 Thanks, Brad ___ freebsd-stable@freebsd.org mailing list http://lists.fr

Re: 6.1 prerelease graid3 livelock?

he serial console was a little garbled, it did >>> say >>> something like: >>> sx lock, geom topology locked... >>> >>> I did an "alltrace" at that point which I'll send seperately. >>> >>> Thanks, >>> Brad >&

Re: 6.1 prerelease graid3 livelock?

e serial console was a little garbled, it did say >> something like: >> sx lock, geom topology locked... >> >> I did an "alltrace" at that point which I'll send seperately. >> >> Thanks, >> Brad >> >> >>> On Thu, Apr 27,

Re: 6.1 prerelease graid3 livelock?

2006 at 08:55:35AM +0200, Pawel Jakub Dawidek wrote: >> +> On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradley W. Dutton wrote: >> +> +> Hi, >> +> +> >> +> +> I'm experiencing a sort of livelock on a 6.1 prerelease box. It >> appears >> +> +

Re: 6.1 prerelease graid3 livelock?

d, it did say something like: sx lock, geom topology locked... I did an "alltrace" at that point which I'll send seperately. Thanks, Brad > On Thu, Apr 27, 2006 at 08:55:35AM +0200, Pawel Jakub Dawidek wrote: > +> On Sun, Apr 23, 2006 at 12:04:33PM -0700, Bradle

6.1 prerelease graid3 livelock?

Hi, I'm experiencing a sort of livelock on a 6.1 prerelease box. It appears all of the IO related activity hangs but the box continues to do routing/NAT/etc for internet access from my other boxes. I can usually get the lockup to occur within about 12 hours of booting. I've narrowed down the co