I cannot repro this, I used your kernel config, this is on a Dell 1850 btw,
I ran netperf stress from 3 clients, and have seen no watchdogs :(
Jack
On Tue, Jun 21, 2011 at 7:59 PM, Joshua Boyd wrote:
> If needed, I can reproduce this on demand. Just need to know what sort of
> statistics are n
If needed, I can reproduce this on demand. Just need to know what sort of
statistics are needed when the problem is occurring. I've had to turn off my
weekly scrubs until I can figure out how to fix this problem.
On Wed, Jun 15, 2011 at 8:37 PM, Joshua Boyd wrote:
> In the kernel. Here's my kern
I have hardware now, am working on reproducing this. Just curious, do you
have
the em driver defined in the kernel, or as a module?
Jack
On Wed, Jun 15, 2011 at 2:09 AM, Joshua Boyd wrote:
> On Wed, Jun 15, 2011 at 3:57 AM, Jeremy Chadwick
> wrote:
>
> > On Wed, Jun 15, 2011 at 03:14:43AM -040
In the kernel. Here's my kernel configuration:
http://pastebin.com/raw.php?i=4JL814m3
On Wed, Jun 15, 2011 at 8:20 PM, Jack Vogel wrote:
> I have hardware now, am working on reproducing this. Just curious, do you
> have
> the em driver defined in the kernel, or as a module?
>
> Jack
>
>
> On We
On Wed, Jun 15, 2011 at 3:57 AM, Jeremy Chadwick
wrote:
> On Wed, Jun 15, 2011 at 03:14:43AM -0400, Joshua Boyd wrote:
> > I recently updated my server to the latest 8-STABLE, and upgraded to v28
> > ZFS. I have not had these problems on any other version of 8-STABLE or
> > 7-STABLE, which this bo
On Wed, Jun 15, 2011 at 03:14:43AM -0400, Joshua Boyd wrote:
> I recently updated my server to the latest 8-STABLE, and upgraded to v28
> ZFS. I have not had these problems on any other version of 8-STABLE or
> 7-STABLE, which this box was upgraded from some time ago.
>
> Now, during my weekly scr
On Wed, Aug 11, 2010 at 02:26:01PM +0200, Vonarburg David wrote:
> Hi
> i am also searching for the dcgdis.zip file to prevent watchdog timeout on
> em0 device
> Where can i get it
> Thanks
> David
Which watchdog issue are you referring to? There are many reported
watchdog timeout issues with em
Hi
i am also searching for the dcgdis.zip file to prevent watchdog timeout on em0
device
Where can i get it
Thanks
David
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail t
BTW, I've always been somewhat dissatisfied with the watchdog design and
think
its kinda flawed, I could try and make you an experimental with debug and
some
changes that you can try if you'd like.
I'm game -- it would be nice if the machine still reset the watchdog in
3 seconds and didn't
Hmmm, I did have one of the drivers print more info at watchdog time, but I
just looked
and that's not em, time to add that I guess.
Since you're in the driver there isn't a huge amount of info that you can
print, it still
may not be enough to help.
BTW, I've always been somewhat dissatisfied wit
Finally, while doing some comparisons, I realized that the motherboard
having the problem was _not_ the same as the others; it was similar, but
not identical.
This is a good piece of info. I can try swapping out the MB and see
what happens.
I do want to add: thank you Jack for all your help
On Mon, Oct 05, 2009 at 08:32:14PM +0200, Daniel Bond wrote:
> What I need is useful advice/help. I never stated I needed a driver
> developer.
>
> I'd like to be able to run my favorite OS on cool hardware, in the
> future, for a high-performing NFS-server, without problems like I've
> ex
Sorry, its a Monday morning, I was being kinda facetious, guess it didn't
work very well :) I apologize.
I know it must be annoying for you, its as much so for me when its something
I can't just fix because its not reproducible. So, I feel your pain.
Will try to restrain my Monday blues in the fu
Hi Jack,
I'll comment your mail inline:
On Oct 5, 2009, at 6:57 PM, Jack Vogel wrote:
This posting just muddies the issue, first you talk about having a
problem that
involves Broadcom, ok, so post about that on something other than
em :)
I only meant to indicate that the problem might ex
This posting just muddies the issue, first you talk about having a problem
that
involves Broadcom, ok, so post about that on something other than em :)
Then you make some references to hardware that you "might have bought"
but didn't, I'm not about debugging 'possible worlds problems' though so
ca
On Oct 2, 2009, at 4:36 PM, Rudy wrote:
Today, I set net.inet.ip.fw.enable=0 and I'll see if that helps. I
have
a feeling that isn't related to the NIC at all, but I'm not sure what
else to try.
Just curious, have you tried (or are you using) device polling?
--
Robert Blayzor, BOFH
INOC, L
Hi,
I've been struggling with watchdog timeouts in 7.1/7.2-RELEASE for the
past 6months too. It looks related.
I've tried to replace the hardware 3 times (2 different IBM x3755
chassis, one IBM x3650 chassis).
I tried first with onboard broadcom NICs (bce-based) PCIx-based, until
I had is
Ah, I'll stop messing with them.
I just set them all to 0 to see if that will help and noticed the card
was leaving tx_int_delay=1.
# sysctl dev.em.4.debug=1
Oct 2 13:26:07 mango kernel: em4: tx_int_delay = 1, tx_abs_int_delay = 0
Oct 2 13:26:07 mango kernel: em4: rx_int_delay = 0, rx_abs_in
Watchdog resets the adapter. Messing with these values is of dubious value
anyway.
Jack
On Fri, Oct 2, 2009 at 11:36 AM, Rudy wrote:
>
> I noticed something interesting.
>
> I set the rc_int_delay to 0:
> sysctl dev.em.5.rx_int_delay=0
>
> Chcking via sysctl dev.em.5.debug=1 shows ex_int_dela
I noticed something interesting.
I set the rc_int_delay to 0:
sysctl dev.em.5.rx_int_delay=0
Chcking via sysctl dev.em.5.debug=1 shows ex_int_delay is indeed 0:
Oct 1 17:32:41 mango kernel: em5: rx_int_delay = 0, rx_abs_int_delay = 66
After a watchdog event, sysctl dev.em.5.debug=1 shows ex_
> What about system load, perhaps something is bogging the thing down so that
> it cannot adequately service the network interrupts??
>
Hardly anything is running on the box...
Only things on the box: zebra bgpd (3 peers...) sshd snmpd
Here is the top of 'top':
load averages: 0.06, 0.08, 0.
I would say that 1024 should be enough, I thought maybe you were at 256.
amd64 kernels just perform better at a lot of things, however I/O is not
necessarily
one of them, so I wouldn't claim it for sure, still I'd always default to 64
bit these
days unless there's some other reason not to.
What ab
I have a quad card in a PCIe 8x port, and there are 2 ports on the
motherboard. I just read the manual and see that the on board ports are
PCIe 1x.
I have been seeing watchdog events on the onboard ports as well as on
the PCIe card. The router is doing roughly 50Mbps on em0, em4 & em5.
D
I have rxd and txd set to 1024. How high can I safely go?
# add more descriptors to em devices.
hw.em.rxd=1024
hw.em.txd=1024
### other settings... I have tried rx_int_delay=0 and 32 ... doesn't
seem to make the watchdogs go away.
dev.em.4.rx_int_delay: 32
dev.em.4.tx_int_delay: 66
dev.em.4
Increase the size of your TX ring, meaning the number of TX descriptors.
You said this is a quad port card, what size PCI E slot are you in? On
some motherboards slot connectors might suggest its of a certain size
but its not really wired fully. If you are not in a x8 lane slot move it to
one.
Wh
Rudy wrote:
Rudy wrote:
I am having watchdog timeout issues
Oh, here is some more info from 'pciconf -lcv'.
I offloaded half the traffic from em0 to em5 and there has only been one
watchdog timeout today (on em5) vs. 10 watchdog timeouts yesterday. We
do streaming out of our network and th
Stefan Krueger wrote:
In muc.lists.freebsd.stable, you wrote:
Rudy wrote:
I am having watchdog timeout issues with my Intel 82573 Pro/1000 ...
http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html
link to dcgdis.zip didn't work. Do you have a copy?
Thanks, Jac
In muc.lists.freebsd.stable, you wrote:
> Rudy wrote:
>> I am having watchdog timeout issues with my Intel 82573 Pro/1000 ...
>> http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html
>>
>> link to dcgdis.zip didn't work. Do you have a copy?
>>
>
> Thanks, Jack. Got the file and f
Rudy wrote:
> I am having watchdog timeout issues with my Intel 82573 Pro/1000 ...
> http://lists.freebsd.org/pipermail/freebsd-net/2008-May/018075.html
>
> link to dcgdis.zip didn't work. Do you have a copy?
>
Thanks, Jack. Got the file and flashed -- no upgrade needed.
So, while the router
29 matches
Mail list logo
